Q&A for CM11 based on 4.4.2 OTA
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Thanks!
JackpotClavin said:
K I'm back on my CM11 builds. New build will be released tomorrow if I have time!
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
This is a really nice ROM. I bought a VS980 (for cash, even) and was disappointed that Cyanogenmod didn't seem to be maintaining the build for it anymore. Battery life is so good I thought the battery meter was broken at first. I'm seeing 75% full at the end of a typical day of calls and texts and apps.
Thanks a lot for making this!
Is the OCT 13th build using 26a binaries, drivers and kernel?
Sent from my VS980 4G
I'm on 24a on paranoid android. Can I just go ahead and flash this like I do any other ROM or do I need to follow all the steps on the front page?
Sent from my LG-VS980 using XDA Free mobile app
babygetoboy said:
I'm on 24a on paranoid android. Can I just go ahead and flash this like I do any other ROM or do I need to follow all the steps on the front page?
Sent from my LG-VS980 using XDA Free mobile app
Click to expand...
Click to collapse
Just flash it is fine.
Curious what those on CM and CM based Roms are using for SMS..the stock app only sends compressed pictures that look like garbage. How are you all sending uncompressed? Personally I've been using Textra, but would prefer to mod stock SMS if possible...anyone?
What's the point of this thread? I don't understand what to ask here instead of in the original thread.
CaptainElwood said:
What's the point of this thread? I don't understand what to ask here instead of in the original thread.
Click to expand...
Click to collapse
Kinda wondering the same thing. I guess it's good for people who don't have enough posts to use the development thread, on the other hand it splits conversations about the rom to two different places. I could understand if the developer specifically asked for all Q & A to go here but I don't think that's the case is it?
CaptainElwood said:
What's the point of this thread? I don't understand what to ask here instead of in the original thread.
Click to expand...
Click to collapse
Based on the OP and the name of the poster, I'm guessing this is automated by XDA.
I think threads like these could be useful. For instance the question I posed above in no way contributes to the development of a ROM, it's features, or is a bug that needs sorting out.
Lately I've noticed mods pointing those who ask questions in a development thread to Q&A threads like this..I can only guess that XDA prefers things in this direction now.
Hope this isn't too dumb a question.
So I've been reading a LOT of this thread and I just need to clarify a few things.
First, I have the 26A build and cannot flash the regular CM11 (I get stuck in the LG boot loop) so this is how I found this thread. Now, is this thread specifically for a special build of CM that gets around this problem? The last 20 pages or so are more about bugs and things within this build so I'm getting a little confused on if this is actually the thread and build I need.
Second thing: If this IS the zip I need for my boot loop problem, can I simply flash it in recovery or do I need to go through the steps in the OP? I saw someone ask this question a few pages back but didn't really understand the answer. If it's as simple as a flash of the zip, whey would the long string of instructions still be in the OP? Thank you for clarifying.
Third thing is: If I flash this build and the official CM builds later somehow work with the 26A firmware, can I simply flash the new, official CM build(s) or will I need to wipe and install the official build clean?
Thank you for answering these annoying questions. I've literally spend the last 3 days trying to root and boot and finally found this thread and spent the last day reading up on it.
blue duck butter said:
So I've been reading a LOT of this thread and I just need to clarify a few things.
First, I have the 26A build and cannot flash the regular CM11 (I get stuck in the LG boot loop) so this is how I found this thread. Now, is this thread specifically for a special build of CM that gets around this problem? The last 20 pages or so are more about bugs and things within this build so I'm getting a little confused on if this is actually the thread and build I need.
Second thing: If this IS the zip I need for my boot loop problem, can I simply flash it in recovery or do I need to go through the steps in the OP? I saw someone ask this question a few pages back but didn't really understand the answer. If it's as simple as a flash of the zip, whey would the long string of instructions still be in the OP? Thank you for clarifying.
Third thing is: If I flash this build and the official CM builds later somehow work with the 26A firmware, can I simply flash the new, official CM build(s) or will I need to wipe and install the official build clean?
Thank you for answering these annoying questions. I've literally spend the last 3 days trying to root and boot and finally found this thread and spent the last day reading up on it.
Click to expand...
Click to collapse
1.Official CM is still using 4.2 sources.
2. Yes, just wipe and flash this then gapps. Ignore all the complicated instructions, they're outdated.
3. I'd recommend a clean flash, but, yes, when/if CM finally updates to true kitkat sources.
jesssiii said:
1.Official CM is still using 4.2 sources.
2. Yes, just wipe and flash this then gapps. Ignore all the complicated instructions, they're outdated.
3. I'd recommend a clean flash, but, yes, when/if CM finally updates to true kitkat sources.
Click to expand...
Click to collapse
Great! Thanks for clarifying. Is the CM team slow at updating the sources? I was under the impression that CM worked fairly quickly. From what I gather, the VS98026A build has been around for about a month, correct? Also, does that mean 26A is the first firmware from LG built on 4.4?
blue duck butter said:
Great! Thanks for clarifying. Is the CM team slow at updating the sources? I was under the impression that CM worked fairly quickly. From what I gather, the VS98026A build has been around for about a month, correct? Also, does that mean 26A is the first firmware from LG built on 4.4?
Click to expand...
Click to collapse
24A was first, then 2nd, then 26A. Not all were official. As far as CM goes, I don't know.
Getting same error message as other user
I have fewer than 10 posts so I can't post in the forum but I'm getting the same error message that user AO4EVER was getting. Here is his post:
"Same error message with the new build
Can't install this package on top of incompatible data. Please try another package or run a factory reset. E: Error executing updater binary in zip's '/data/media/0/sideload.zip'
Anyone else is getting this? [Don't think it is due to build, something is off the device itself]" - AO4EVER
He was confused because nobody else was getting that error message. Well, that's the message I get when I try to flash JPC's build of CM11. I am rooted on stock 26A.
Does anyone know why this is happening? The user said he ended up deleting some of the verification code to get it to finally work. Can anyone explain how I would go about doing this? I don't know a ton but I feel comfortable enough in terminal/command prompt to make changes if I know what changes to make.
*EDIT* I deleted the part of the verification code that was preventing me from flashing JPC's CM11 build and have successfully flashed it now.
Just updated to 20141026, GPS is broke (was broke on an earlier Oct build). I see others confirming GPS working, how do I test to make sure I don't have bad hardware?
laf gets overwritten
The aboot and boot replacement works fine. The md5sums match over many reboots. However, something keeps overwriting the laf file. I tried replacing mmcblk0p24 directly, and the md5sum for that and the laf symlink in by-name are correct, but when the phone reboots something has overwritten it. I also made a copy of mmcblk0p24 in the block folder, and strangely that gets deleted on reboot as well. But aboot and boot keep the changes. Weird. Do you know what could be causing this?
updating
If i followed this guide to install the cm 11 m11 build and i want to update to m12 how do i do that
boggsmicah said:
If i followed this guide to install the cm 11 m11 build and i want to update to m12 how do i do that
Click to expand...
Click to collapse
Wipe and flash rom and gapps as usual.
LG G2 VS980
I have the same problem with screen off during call after screen timeout has elapsed, did u manage to get it fixed? im on 26A and im using 2014 11 02 nightly build, M12 gave me call drop so i opted for the nightly
CM 11 (M12) vs980 Camera w Flash problem
Hello all,
So, i've been running the latest builds of CM 11 4.4.4 through the help of JackpotCalvin's write up and kernel exploit.
I figure I should ask if anyone else has had some issues with the camera and taking pictures with flash enabled?
for whatever reason the white balance is faulty with flash enabled and the pictures come out whitewashed. It didn't used to do this with previous updates (before the M12 stapshot).
maybe something is bogging down performance and i dont realize it. Anyway, thanks for any feedback.
-Mike M
Related
To keep the development thread clean, this thread is meant to post any questions with regards to Evervolv's Jellybean builds for your Nexus One, such as "Has issue X been solved in build Y?", or "I have a problem X. Is anybody else experience the same?". The kind users on XDA will try to answer all your questions, or point you to the relevant location to solve/address your issue.
For general discussions about the Rom, please use this thread: http://forum.xda-developers.com/showthread.php?t=1795954
Please don't forget to include as much details as possible to any questions (build number + release date, steps to reproduce the issue etc.).
Before you post a question, you should
1.) Search this thread
2.) Search the development thread: http://forum.xda-developers.com/showthread.php?t=1762790
if you can find an answer for your question.
Before you post any questions with regards to a problem you're facing, you should
1.) Search this thread
2.) Search the development thread: http://forum.xda-developers.com/showthread.php?t=1762790
3.) Search the Evervolv Code review site: http://review.evervolv.com/#/q/branch:jellybean,n,z
to check if there's already a solution that is not mentioned in OP, or if the issue was filed and/or a fix is pipelined by the developers already.
Thanks for helping to keep everything clean!
I hate to start off this thread with such a base question...but I just got a Nexus One and flashed this ROM. Wondering if anyone has a kernel suggestion to maximize smoothness...
mtmjr90 said:
I hate to start off this thread with such a base question...but I just got a Nexus One and flashed this ROM. Wondering if anyone has a kernel suggestion to maximize smoothness...
Click to expand...
Click to collapse
First off, thanks for posting to the correct thread! Now, to answer your question: Since this Rom is in a real early stage development phase, there're a few "hacks" implemented to get things running. Personally I didn't tried to flash another kernel, nor am I a kernel dev. However, to ensure functionality it might be the best choice to stay with the released kernels for the moment. I know that's not the answer you wanted, but just my 2 cents.
Edit: Especially because you were asking for "smoothness".. The Evervolv team is working to the graphic related stuff "with priority". Many libs are broken or partitially incompatible. So I think another kernel won't change anything with regards to "smoothness". But we can expect updates on that soon.
Bexton said:
First off, thanks for posting to the correct thread! Now, to answer your question: Since this Rom is in a real early stage development phase, there're a few "hacks" implemented to get things running. Personally I didn't tried to flash another kernel, nor am I a kernel dev. However, to ensure functionality it might be the best choice to stay with the released kernels for the moment. I know that's not the answer you wanted, but just my 2 cents.
Edit: Especially because you were asking for "smoothness".. The Evervolv team is working to the graphic related stuff "with priority". Many libs are broken or partitially incompatible. So I think another kernel won't change anything with regards to "smoothness". But we can expect updates on that soon.
Click to expand...
Click to collapse
Ah, thanks for the info. I got the N1 to play with and with a Galaxy Nexus as my primary device I can really feel the difference...which was of course expected I obviously haven't followed Evervolv's development in the past, just out of curiosity, how frequent are releases in general? I'm running AOKP on my GNex and they release approx every other week, so I'm hoping for something similar here.
mtmjr90 said:
Ah, thanks for the info. I got the N1 to play with and with a Galaxy Nexus as my primary device I can really feel the difference...which was of course expected I obviously haven't followed Evervolv's development in the past, just out of curiosity, how frequent are releases in general? I'm running AOKP on my GNex and they release approx every other week, so I'm hoping for something similar here.
Click to expand...
Click to collapse
Probably the best answer to get, is by looking at the release history of the Evervolv TexasIce Cream Sandwich thread (post 2 & 3): http://forum.xda-developers.com/showthread.php?p=19785288#post19785288
But don't expect weekly updates. Updates come, as Texasice think that it's worth to bump to a new build.
I didn't followed any AOKP projects.. But I know that some devs publish new builds for "every" commit they push to their repos to keep users up to date with the latest stuff. However, Evervolv is a small team of 3 devs and Texasice, who works on N1 stuff, additionally works on other devices and other stuff as well. From what I can see, he's pushing new releases when "something big" was fixed, or was improved, but not for every tiny change.
However, they build nightlies, too. So if you want, you could update every morning. But a better idea would be to follow the progress via their code review site and if you see any commit which you think you would like to have that, go ahead and grab the next nightly.
All Jellybean commits: http://review.evervolv.com/#/q/branch:jellybean,n,z
Jellybean commits that have been merged: http://review.evervolv.com/#/q/status:merged+branch:jellybean,n,z
Finally, you can find the source at GitHub and build yourself as often as you want. https://github.com/Evervolv
Lots of questions coming from me today I'm afraid... I am curious what everyone is doing to solve the Insufficient Space error. I posted a general question in the Q&A forum but I don't know if there's any particularities resulting from being on JB rather than GB (CM7).
mtmjr90 said:
Lots of questions coming from me today I'm afraid... I am curious what everyone is doing to solve the Insufficient Space error. I posted a general question in the Q&A forum but I don't know if there's any particularities resulting from being on JB rather than GB (CM7).
Click to expand...
Click to collapse
There are no peculiarities to JB that I know of. All I had to do was enter a2sd install in Terminal (after getting SU there first). I assume you already had an sd-ext partition on your SD.
Hey guys....loving the Jelly Bean experience so far!!
Real silly question here...but what do 0p1, 0p2, 0p3 mean on the nightlies. Is it just releases?
Also is there somewhere we can see what changes are made to each nightly release?
Thanks!
mothor said:
Hey guys....loving the Jelly Bean experience so far!!
Real silly question here...but what do 0p1, 0p2, 0p3 mean on the nightlies. Is it just releases?
Also is there somewhere we can see what changes are made to each nightly release?
Thanks!
Click to expand...
Click to collapse
It is version 3.0.0
p stands for pre-alpha (see it as pre-release) and the build number The JB build is just beginning TexasIce will come up hopefully soon with an alpha build once all the merging is completed
I'm coming from ICS as my daily driver, but hesitant on JB just yet.
Is the included Apps2SD working with xdata like the ICS version? I know that was an experimental feature, but it always works better for me than the normal install did.
Thanks,
-sj
I'm having serious stability issues and I just want to confirm what causing them...namely is it the ROM or perhaps a hardware issue. I've had the ROM set up and running three times now and each time (once over night, twice just having it sit around for an hour or so) it just freezes up and when I battery pull to reboot, almost all of my apps and settings have been erased. I've used the built in a2sd to move apps and dalvik to sd-ext, dunno if that could be part of the problem... Anyone else have similar issues? I'm thinking if it's not the ROM, it could be corrupt storage or something.
Is butter working in these builds?
This is more in response to your rant on the development thread than in relation to the ROM directly, but I was thinking it would possibly reduce the amount of posts about stuff not appropriate for the development thread if you could put a warning to come up when someone is writing a post for the thread asking if what they're writing is going to contribute to the development of the ROM and with links to this and the discussion thread suggesting them as more appropriate places to post. Dunno if that's possible, or if someone like you with lots of posts could suggest it as a solution to this problem that plagues so many threads?
Sent from my Nexus One using xda app-developers app
Another question which is more directly related to the ROM.
Is it possible for an option to be added to remap the soft keys? Such as remapping the search key to be a multitasking key as is in actual ICS phones?
I know I personally hardly ever use the search key but often use the multitasking features which would make it awesome to have that functionality!
Just a thought, thanks if you implement it!
Sent from my Nexus One using xda app-developers app
Just wondering when TI will release next build. Am having trouble with notifications. I have pushed all the libs but still the video playing is broken. I really don't know what bexton has fixed but p1 with all fixes was just awesome. I know TI will incorporate all those stuffs so just waitimg eagerly for a p3.
Sent from my Nexus One using Tapatalk
I don't know if it's a bug or not... sometimes screen display doesn't turn off but phone is asleep (I think). See the lockscreen but doesnt respond to touchscreen. Works fine once I wake up phone with power button. On latest nightly(7/27).
Sent from my Nexus One
seinjunkie said:
I'm coming from ICS as my daily driver, but hesitant on JB just yet.
Is the included Apps2SD working with xdata like the ICS version? I know that was an experimental feature, but it always works better for me than the normal install did.
Thanks,
-sj
Click to expand...
Click to collapse
i am using the xdata flag everything seems to work in regards to that
With smartassV2 governor the rom is faster without any reboot or similar
Has someone try it?
ironjon said:
With smartassV2 governor the rom is faster without any reboot or similar
Has someone try it?
Click to expand...
Click to collapse
Where do you change the governor? Don't see evervolv toolbox under settings. On 7/27 nightly
Sent from my Nexus One
vimitake said:
Where do you change the governor? Don't see evervolv toolbox under settings. On 7/27 nightly
Sent from my Nexus One
Click to expand...
Click to collapse
I did it with setcpu
Enviado desde mi HTC Desire usando Tapatalk 2
Hello everyone, I have been lurking for a long time and I just want to say what a great community this is and thank you to everyone who develops and/or contributes. I have learned everything I know about android dev from reading these forums and I am confident enough now to start posting and trying to offer whatever I can from my experiences. Now for my question
What is the general opinion about flashing nightly builds? Is it generally only for people who are testing/debugging? I am running cm-11-20140805-NIGHTLY-moto_msm8960_jbbl on my Atrix HD right now and I am very happy with it - in fact I am ecstatic to have found a 4.4.4 rom that works smooth, fast, and stable for me (I got tired of waiting for AT&T to release their OTA update!). Consider this a positive endorsement of it. However, I see that new builds were released on 8/9 and 8/10 (as I would expect for nightly builds to be updated often, of course). I looked at the changelogs and I don't fully understand every last thing I see there, but I have not encountered any issues with the build I am running, so should I bother to flash the newest nightly releases when they come out? Is there a way to update without resetting everything or should I just restore my apps with Titanium Backup after flashing a new nightly? Finally, what is the best way for me to contribute to development (short of submitting code myself, as I do not feel confident enough to do so just yet)?
Since it seems I am not allowed to have a sig until I reach a certain number of posts(?) I will post my current devices below:
AT&T Motorola Atrix HD MB886
ClockworkMod Recovery v6.0.4.4
CyanogenMod 11 cm-11-20140805-NIGHTLY-moto_msm8960_jbbl (KK 4.4.4)
pa_gapps-stock-4.4.4-20140804-signed
Acer Iconia A500
Skrilax_CZ's Bootloader v8
ClockworkMod Recovery Thor v1.7.3
CyanogenMod 10.2 cm-10.2-20131004-UNOFFICIAL-a500 (JB 4.3)
P.S. - special thanks to the Myth Team, Djrbliss, skeevydude, leanix, osm0sis, chainfaire, PhilZ for making it super easy to root and unlock my phone :good:
Fanarkle said:
Hello everyone, I have been lurking for a long time and I just want to say what a great community this is and thank you to everyone who develops and/or contributes. I have learned everything I know about android dev from reading these forums and I am confident enough now to start posting and trying to offer whatever I can from my experiences. Now for my question
What is the general opinion about flashing nightly builds? Is it generally only for people who are testing/debugging? I am running cm-11-20140805-NIGHTLY-moto_msm8960_jbbl on my Atrix HD right now and I am very happy with it - in fact I am ecstatic to have found a 4.4.4 rom that works smooth, fast, and stable for me (I got tired of waiting for AT&T to release their OTA update!). Consider this a positive endorsement of it. However, I see that new builds were released on 8/9 and 8/10 (as I would expect for nightly builds to be updated often, of course). I looked at the changelogs and I don't fully understand every last thing I see there, but I have not encountered any issues with the build I am running, so should I bother to flash the newest nightly releases when they come out? Is there a way to update without resetting everything or should I just restore my apps with Titanium Backup after flashing a new nightly? Finally, what is the best way for me to contribute to development (short of submitting code myself, as I do not feel confident enough to do so just yet)?
Since it seems I am not allowed to have a sig until I reach a certain number of posts(?) I will post my current devices below:
AT&T Motorola Atrix HD MB886
ClockworkMod Recovery v6.0.4.4
CyanogenMod 11 cm-11-20140805-NIGHTLY-moto_msm8960_jbbl (KK 4.4.4)
pa_gapps-stock-4.4.4-20140804-signed
Acer Iconia A500
Skrilax_CZ's Bootloader v8
ClockworkMod Recovery Thor v1.7.3
CyanogenMod 10.2 cm-10.2-20131004-UNOFFICIAL-a500 (JB 4.3)
P.S. - special thanks to the Myth Team, Djrbliss, skeevydude, leanix, osm0sis, chainfaire, PhilZ for making it super easy to root and unlock my phone :good:
Click to expand...
Click to collapse
Nightly builds are just that, builds that are made nightly. They are the most up to date. Snapshots/M(*insert number here*) releases are generally more stable, but we got knocked out of being eligible for them after the release of M8 (thanks kk bootloader). CM has made a msm8960 jb bl section, which you did find. This might get us up and running for a M10 next month if they choose to do that, but then again, msm8960 did not get a M9. Nightly's are for everyone. CM makes a few tweaks to their code and pushes it to each nightly. Some tweaks make it better, some tweaks make it worse. If you are satisfied with the release that you currently are running, you don't need to flash the update if you don't want to. Since you would be flashing an update, you just flash it, no backups of apps. Now if you were going from CM11 down to CM10, 10.1, or 10.2, then yes, back them up b/c you'd wipe those partitions before flashing the ROM.
Sent from my MB886 using XDA Free mobile app
palmbeach05 said:
Since you would be flashing an update, you just flash it, no backups of apps. Now if you were going from CM11 down to CM10, 10.1, or 10.2, then yes, back them up b/c you'd wipe those partitions before flashing the ROM.
Click to expand...
Click to collapse
How would I go about updating without losing anything? Do I just boot into recovery, wipe only delvik cache, and flash cm-11-20140810-NIGHTLY-moto_msm8960_jbbl.zip? Or is there a separate file just for updating? If I don't have to set everything up all over again after each nightly then I will gladly keep updating and providing feedback.
Fanarkle said:
How would I go about updating without losing anything? Do I just boot into recovery, wipe only delvik cache, and flash cm-11-20140810-NIGHTLY-moto_msm8960_jbbl.zip? Or is there a separate file just for updating? If I don't have to set everything up all over again after each nightly then I will gladly keep updating and providing feedback.
Click to expand...
Click to collapse
You can just clear cache in recovery then flash the update and it would keep all of your settings, data, everything the same. It is not recommended. If you have enough space, you can nand backup your current version and that eliminates the risk of losing everything if updating doesn't work, but it's recommended that you wipe cache and wipe data before flashing a new nightly. I've rarely had a problem flashing a nightly on top of my existing build without wiping data, but to each his own.
Just make sure you're flashing the jbbl nightlies and you should be fine.
Dr. Orange said:
You can just clear cache in recovery then flash the update and it would keep all of your settings, data, everything the same. It is not recommended. If you have enough space, you can nand backup your current version and that eliminates the risk of losing everything if updating doesn't work, but it's recommended that you wipe cache and wipe data before flashing a new nightly. I've rarely had a problem flashing a nightly on top of my existing build without wiping data, but to each his own.
Just make sure you're flashing the jbbl nightlies and you should be fine.
Click to expand...
Click to collapse
When you say "clear cache", do you mean "wipe cache partition," "format /cache," or "wipe delvik cache?" So basically what you are saying is that it is possible to flash a nightly on top of an existing build without losing anything but it is generally not recommended? I always create a backup image before I flash anything so no problem there.
Yes. Wipe cache. It will format automagically. You can wipe dalvik cache as well. Usually I just select the first "wipe cache" option in clockworkmod recovery then start flashing. Works 99% of the time.
Some say they develop problems doing it that way, but I've never had an issue with it. Maybe my phones (I had a moto bravo before the atrix hd) just like me.
Fanarkle said:
So basically what you are saying is that it is possible to flash a nightly on top of an existing build without losing anything but it is generally not recommended? I always create a backup image before I flash anything so no problem there.
Click to expand...
Click to collapse
Dr. Orange said:
You can wipe dalvik cache as well. Usually I just select the first "wipe cache" option in clockworkmod recovery then start flashing. Works 99% of the time.
Some say they develop problems doing it that way, but I've never had an issue with it. Maybe my phones (I had a moto bravo before the atrix hd) just like me.
Click to expand...
Click to collapse
The method of flashing over-top of an existing ROM is referred to as "dirty flashing". The issue isn't so much that it's not recommended or that it develops problems, but it could potentially develop problems, because there's always a chance that the new build relies on some random file that should have been deleted, changed, etc.
So, in summary, it's perfectly fine to dirty flash a CM nightly over your existing version, especially if it works fine for you. HOWEVER, if you develop problems, then you should refrain from reporting them until you have done a CLEAN wipe of everything and installed clean from scratch. If you still have an issue after a clean install, then feel free to report any issues as "bugs."
quasihellfish said:
if you develop problems, then you should refrain from reporting them until you have done a CLEAN wipe of everything and installed clean from scratch. If you still have an issue after a clean install, then feel free to report any issues as "bugs."
Click to expand...
Click to collapse
OK, thanks. What is the best avenue and method of reporting bugs if I do find any after a clean install? xda-forums? Cyanogenmod.org? Directly from the phone?
Fanarkle said:
OK, thanks. What is the best avenue and method of reporting bugs if I do find any after a clean install? xda-forums? Cyanogenmod.org? Directly from the phone?
Click to expand...
Click to collapse
Depends on how confident you are
I usually just ask/report in the appropriate XDA thread and look for feedback. There is a thread for the Atrix HD, but the thread for the RazrHD is much more active. You'll get a lot more activity and responses in the RazrHD thread because it's essentially the same device, just be sure to note that you're on the JB bootloader.
I suppose if you're really sure of a "bug", you could always report it at cyanogenmod.org, but I've never felt to be in the right position to do that.
quasihellfish said:
Depends on how confident you are
I usually just ask/report in the appropriate XDA thread and look for feedback. There is a thread for the Atrix HD, but the thread for the RazrHD is much more active. You'll get a lot more activity and responses in the RazrHD thread because it's essentially the same device, just be sure to note that you're on the JB bootloader.
I suppose if you're really sure of a "bug", you could always report it at cyanogenmod.org, but I've never felt to be in the right position to do that.
Click to expand...
Click to collapse
Thanks, I will stick with XDA then :good: I was looking at jira.cyanogenmod.org and I can't figure out how to report anything specific to a nighly build anyway What is the useful/relevant information that I should post (besides what build I am running) to be the most helpful? i.e. How do I generate a log/report with all the relevant info?
Fanarkle said:
Thanks, I will stick with XDA then :good: I was looking at jira.cyanogenmod.org and I can't figure out how to report anything specific to a nighly build anyway What is the useful/relevant information that I should post (besides what build I am running) to be the most helpful? i.e. How do I generate a log/report with all the relevant info?
Click to expand...
Click to collapse
Well, then I just recommend sticking with XDA. If one of the real CM devs/maintainers then recognizes a bug, someone will report it. Or re-ask this question over there, and they can help you.
Why this topic is still open?
Where are the forum admins?
Sent from my GT-I9505 using XDA Free mobile app
RatusNatus said:
Why this topic is still open?
Where are the forum admins?
Click to expand...
Click to collapse
Did I do something wrong? I am creating a backup and "dirty" flashing the latest nightly right now. I was going to post how it went after I finished just so other people would have the info if they were looking for it.
Success! I rebooted into recovery and, after creating a backup, performed "wipe cache partition" and "wipe delvik cache" before installing cm-11-20140811-NIGHTLY-moto_msm8960_jbbl.zip on top of the build I was running. I rebooted and everything is as it was, except that my custom boot animation was reverted back to CM default (which was expected, no big deal) and the new version I flashed is correctly shown on the "About phone" screen. If I encounter any issues going forward, I will post in the appropriate thread.
Fanarkle said:
Did I do something wrong?
Click to expand...
Click to collapse
No.
RatusNatus said:
Why this topic is still open?
Where are the forum admins?
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Why did you post here if you had nothing constructive to say?
I'm glad you got it to work fanarkle[emoji4]
Q&A for [ROM] Odexed/Deodexed
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] Odexed/Deodexed. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
hulu not working
hello anyone having issues trying to play videos on the deoxed rom ? getting error that says strange....
Cant install
I love it, thanks!!
--my impatience sometimes causes me too many problems, sorry for the trouble. edited away previous issue.
Hey guys, I'd prefer it if we just use the main thread for discussion.
Not booting for me either. Looper v1.2 on Galaxy s6 t920
The rom is not booting up for me. I was previously running version 1.1 and it was fine, but after trying to flash the newest one it failed to boot so I restored from my backup. I am using the latest twrp and I have always lurked these forums and am quite knowledgeable but never posted before. This is just a heads up to the Dev that it is not booting in case he wants to look into it. I see that it is working for other so I am wondering what has gone wrong here.
I am aware of the issue. Thank you
update
@mikeyinid.
Love the rom! Quick question, when an OTA/update arrives will you be updating your rom to incorporate it? Thanks
yellowsn0w said:
@mikeyinid.
Love the rom! Quick question, when an OTA/update arrives will you be updating your rom to incorporate it? Thanks
Click to expand...
Click to collapse
Yes. Start with a clean base.
SystemUI.apk
How do you get rid of center clock? I tried installing the SystemUI apk you had but it says App not installed.
Where is the download link of the final version? I saw your changelog and i can't wait to try it
why are there no customization options like on the international roms?
virulentt said:
Where is the download link of the final version? I saw your changelog and i can't wait to try it
Click to expand...
Click to collapse
I haven't uploaded it yet.
yellowsn0w said:
why are there no customization options like on the international roms?
Click to expand...
Click to collapse
I'm not a dev. And you don't have to use the ROM.
Thanks! Installing right now!
Hey if I use flashify to install this (after removing the boot.img and editing the updater script) do I do a clean wipe or do I not wipe at all? Thanks
Sent from my SM-G920T using XDA Free mobile app
Ambiant display seems to cause a black/blue screen a second before i see the lockscreen when i press the power button to wake my phone.
Best ROM i've seen so far. I flashed L Speed v2.1 Revolution and its buttery smooth, best battery life. I kept ROM's stock kernel and I absolutely love it. Thanks mike
virulentt said:
Best ROM i've seen so far. I flashed L Speed v2.1 Revolution and its buttery smooth, best battery life. I kept ROM's stock kernel and I absolutely love it. Thanks mike
Click to expand...
Click to collapse
How would you compare it to XtreStoLite?
Tried installing it and it bootlooped
I'm on the edge with obviously and updated modem and bootloader on 5.1.1
Wiped everything tried installing and flashed a kernel
Sent from my SM-G925F using Tapatalk
deodexing tool updated
I hear there was an update today. Let me know if you need some testing help for 5.1.1
Latest Version
I attempted to download your deodexed and debloated 5.1.1. But the it indicates the file is no longer up on android file host.
Can you confirm - or is it just not working for me.
thanks for all your work!! I've been on looper for awhile and its been great.
I recently decided to do some personal builds of CM for the OnePlus 3. I have seen that the other threads are not updating their builds since they are the ones working on them. I am simply sharing the current builds from the CyanongenMod Repos. I did not do any of the development work and I will kill this thread the moment we get official nightly builds. I am not responsible for anything that may happen and I do not care what does and does not work. You are deciding to flash this ROM. Bugs can be reported to the CM devs but include a logcat or GTFO.
Link to build folder - https://www.androidfilehost.com/?w=files&flid=74080
Instructions:
1. Unlock Bootloader
2. Flash TWRP
3. Fastboot format userdata
4. Boot into TWRP
5. Flash ROM
6. Flash GAPPS
7. Reboot
Thanks for making another ROM for our OP 3
papi92 said:
I recently decided to do some personal builds of CM for the OnePlus 3. I have seen that the other threads are not updating their builds since they are the ones working on them. I am simply sharing the current builds from the CyanongenMod Repos. I did not do any of the development work and I will kill this thread the moment we get official nightly builds. I am not responsible for anything that may happen and I do not care what does and does not work. You are deciding to flash this ROM. Bugs can be reported to the CM devs but include a logcat or GTFO.
Link to build folder - coming soon (waiting on AFH approval)
Instructions:
1. Unlock Bootloader
2. Flash TWRP
3. Fastboot format userdata
4. Boot into TWRP
5. Flash ROM
6. Flash GAPPS
7. Reboot
Click to expand...
Click to collapse
Hehe thanks for this Started building them as well but don't really know how, so made a little guide for others like me Feel free to share your knowledge if you want
build is up
papi92 said:
build is up
Click to expand...
Click to collapse
Downloading...
_MartyMan_ said:
Downloading...
Click to expand...
Click to collapse
Thanks
Thanks for doing this dude. Going to download now. Can finally ditch OOS.
Sent from my ONEPLUS A3000 using Tapatalk
Wooohoo! Everything is working Good job!
_MartyMan_ said:
Wooohoo! Everything is working Good job!
Click to expand...
Click to collapse
Does VoLTE work? I haven't stuck in my T-Mobile SIM lol and i didn't do anything so no thanks to me. It's all @Grarak and @Romanbb
Not trolling but we dont need several twrp, cm, resurrection and so on rom threads here. I believe the mods starting closing these. Not discouraging you from building but several threads just confuse people.
Nah mods don't close it, maybe move it.
It's a nightly build from cm13, did u see a nightly build around? Nope.
Good work, fastest cm13 build around, good to have some nightlys around. Thanks
fix-this! said:
Not trolling but we dont need several twrp, cm, resurrection and so on rom threads here. I believe the mods starting closing these. Not discouraging you from building but several threads just confuse people.
Click to expand...
Click to collapse
These are nightlies. I'm more than happy to close once CM sends the OnePlus into Jenkins.
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
nadejo said:
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
Click to expand...
Click to collapse
Yeah not my work at all. Nor would I pretend it is. Way over my head
So anyone confirm VoLTE is working? I want to switch to T-Mobile once it does.
nadejo said:
I really hope this thread doesnt get closed till we see official builds. I know some devs might be mad about this. But since you dont ask for any reward for compiling these builds its ok.
Click to expand...
Click to collapse
Tbh i dont think alot of devs even have the device in hand yet. thats why im running stock rooted. no offense to the op, wasnt my intention. just been seeing alot of the same threads pop up and its confusing and uneeded. im sure these nightlies are appreciated.
Put up a second build. I saw some commits to snap and wanted to share.
Possible to link the source?
Not that I know where it is, but I'm to lazy to search all the time.
Only thing I noticed is the battery drain compared to stock, not a big one, maybe it need to settle a little.
1 hour SOT 21% on cm
1 hour SOT 14-16% on stock.
Lets see how it settle.
Edit:
Compared to others Roms who looks like they are on a older source, it's running like it should, compared to stock min. the same smoothness, maybe even better.
And I can't test lte because I only have a h+
secXces_debaki said:
Possible to link the source?
Not that I know where it is, but I'm to lazy to search all the time.
Only thing I noticed is the battery drain compared to stock, not a big one, maybe it need to settle a little.
1 hour SOT 21% on cm
1 hour SOT 14-16% on stock.
Lets see how it settle.
Edit:
Compared to others Roms who looks like they are on a older source, it's running like it should, compared to stock min. the same smoothness, maybe even better.
And I can't test lte because I only have a h+
Click to expand...
Click to collapse
The source is just github.com/cyanogenmod
papi92 said:
Does VoLTE work? I haven't stuck in my T-Mobile SIM lol and i didn't do anything so no thanks to me. It's all @Grarak and @Romanbb
Click to expand...
Click to collapse
Sorry I can' test that
Flashed 15 different times today, stock OOS 7.0. camera works fine on stock, even with magisk installed. As soon as I flash any custom kernel the camera app gets unknown error. Tried clearing cache, etc everything. Only stock kernel works. What gives?
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
954wrecker said:
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
Click to expand...
Click to collapse
Thanks brain.
Magisk is the reason for those errors, im using custom kernel since android 7.0 with system less superSU only, I already tried three different custom kernels here and they didn't gave me any camera errors
J4DedPrez said:
Thanks brain.
Click to expand...
Click to collapse
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
exaflare said:
Magisk is the reason for those errors, im using custom kernel since android 7.0 with system less superSU only, I already tried three different custom kernels here and they didn't gave me any camera errors
Click to expand...
Click to collapse
Thank you friend, sometimes being nice and giving the simple solution is the simplest method.
Migdilu said:
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
Click to expand...
Click to collapse
Typical XDA user... It's a real shame kids these days act the way they do
J4DedPrez said:
Typical XDA user... It's a real shame kids these days act the way they do
Click to expand...
Click to collapse
What it's a shame is that there are people who don't know how to read.
Magisk does work with custom kernels, but the order you flash them in is important. Magisk alters certain files in the /boot partition, which is also where the kernel is located. You should flash Magisk first over a clean ROM prior to flashing any custom kernels, or else you may run into issues. If an update for Magisk is pushed, you should also install it in the following order:
1) Dirty flash ROM (or stock kernel)
2) Flash Magisk
3) Flash custom kernel
I'm currently using Magisk v11.6 with Franco's r16 on OOS 4.1.0 without a problem.
Don't mean to be rude, but did you flash the compatible kernel; and not using adb sideload problems; on TWRP 3.0.4-1?
If you did, well then Magisk seems to be a problem for you.
And do post logs next time of you encounter a problem until and unless you are sure you everybody can reproduce that problem with the steps mentioned (which should be though)
If you're still in Android 7.0 (like me), do not use the latest custom kernel release, it will break your camera (Unknown Error). I think it's because the dev has rebased their kernel to the new Android 7.1.1.
Currently, I'm still on FredomOS 2.5 (OOS 4.0.3) and its combined with BluSpark v.72 (last release before the 7.1.1 rebase).
I don't want to use the latest OOS update since it's still full of annoying bugs.
In my opinion only people who understand what they are doing with this kind of stuff should get the oneplus 3 or 3t as it isn't very noob friendly and takes someone that is some what an advanced user or at least knows a little about flashing ROMs and kernels etc..... Or at least is willing to search around and read before they complain to everyone that they can't figure it out. If you want a phone that is simple and noob use friendly then go to Samsung or Apple. not oneplus as phone from this company are aimed at the intermediate up to power user that understands how to solve irregular problems. I've had none of these issues even when I was using my oneplus x. I use the unofficial RR with ex kernel and no problems with camera or anything and great battery life. Bottom line is (in my opinion anyways) oneplus phones are for the more technically savvy so if you aren't some one like that expect to run in to difficulties and have to do some deep research in certain cases. But this is a great community here at xda and we are all willing to help as much as we can but patience is a must.
Anova's Origin said:
Magisk does work with custom kernels, but the order you flash them in is important. Magisk alters certain files in the /boot partition, which is also where the kernel is located. You should flash Magisk first over a clean ROM prior to flashing any custom kernels, or else you may run into issues. If an update for Magisk is pushed, you should also install it in the following order:
1) Dirty flash ROM (or stock kernel)
2) Flash Magisk
3) Flash custom kernel
I'm currently using Magisk v11.6 with Franco's r16 on OOS 4.1.0 without a problem.
Click to expand...
Click to collapse
Same exact order as you, even flashed fresh ROM and kernel only. Can't explain it at all. For now, I'm on stock with no custom kernel but have magisk.
mrinmaydhar said:
Don't mean to be rude, but did you flash the compatible kernel; and not using adb sideload problems; on TWRP 3.0.4-1?
If you did, well then Magisk seems to be a problem for you.
And do post logs next time of you encounter a problem until and unless you are sure you everybody can reproduce that problem with the steps mentioned (which should be though)
Click to expand...
Click to collapse
No sideload, using most recent TWRP, and yes, I will have logs to post tomorrow. As a quick flasher I never really bother for the logs, but this time I'm getting down to the bottom of this. I'll have logs tomorrow
motherninja said:
If you're still in Android 7.0 (like me), do not use the latest custom kernel release, it will break your camera (Unknown Error). I think it's because the dev has rebased their kernel to the new Android 7.1.1.
Currently, I'm still on FredomOS 2.5 (OOS 4.0.3) and its combined with BluSpark v.72 (last release before the 7.1.1 rebase).
I don't want to use the latest OOS update since it's still full of annoying bugs.
Click to expand...
Click to collapse
This is exactly the issue. Thank you
se7ensde said:
In my opinion only people who understand what they are doing with this kind of stuff should get the oneplus 3 or 3t as it isn't very noob friendly and takes someone that is some what an advanced user or at least knows a little about flashing ROMs and kernels etc..... Or at least is willing to search around and read before they complain to everyone that they can't figure it out. If you want a phone that is simple and noob use friendly then go to Samsung or Apple. not oneplus as phone from this company are aimed at the intermediate up to power user that understands how to solve irregular problems. I've had none of these issues even when I was using my oneplus x. I use the unofficial RR with ex kernel and no problems with camera or anything and great battery life. Bottom line is (in my opinion anyways) oneplus phones are for the more technically savvy so if you aren't some one like that expect to run in to difficulties and have to do some deep research in certain cases. But this is a great community here at xda and we are all willing to help as much as we can but patience is a must.
Click to expand...
Click to collapse
:good:
Flashing kernels made for 7.1.1 on 7.0 FW.
954wrecker said:
You might want to read the kernel threads for help. Seems like if it was a kernel issue like you claim then someone else might have noticed it. Sounds like user error to me
Click to expand...
Click to collapse
Normal, helpful, response(don't be discouraged by some).
J4DedPrez said:
Thanks brain.
Click to expand...
Click to collapse
Douche response.
Migdilu said:
Wow, smartass answer for someone who can't flash a kernel without breaking the camera.
Actually, the answer is the solution you need, search and read.
Click to expand...
Click to collapse
Obvious observation.
J4DedPrez said:
Thank you friend, sometimes being nice and giving the simple solution is the simplest method.
Click to expand...
Click to collapse
Hypocrisy.
Hi all !
This discussion might be related with my issue explained here:
https://forum.xda-developers.com/oneplus-5/help/camera-flashlight-youtube-t3886260
but only thing is I never flashed custom kernels, issue appears after a official update !
Any opinion, ideas ?
Thanks