Related
I just received my Droid Bionic from eBay which i paid 100 for which i think is a steal.. runs great and fast compared to my incredible 2.. should i stay stock or is 10.1 worth the jump.. opinions please... or is there a better option out right now.. please help
Sent from my DROID BIONIC using Tapatalk 2
miguel11691 said:
I just received my Droid Bionic from eBay which i paid 100 for which i think is a steal.. runs great and fast compared to my incredible 2.. should i stay stock or is 10.1 worth the jump.. opinions please... or is there a better option out right now.. please help
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
As someone who has owned the Bionic since launch, and just jumped to CM 10.1 a few days ago, I'll chime in here. It's a much better phone since CM 10.1. That said, be prepared for issues initially. I had a lot of problems and was ready to give up - until I did a factory reset on the CM 10.1 ROM. If you decide to make the switch, you can root, install SafeStrap, and flash CM 10.1 and Gapps with confidence, as long as don't mind doing a factory reset and rebuilding everything. Since the phone is new to you, that shouldn't be much of a deterrent.
I personally would recommend making the plunge.
Thanks a lot... is there any thing not working... i heard the camera is fixed...
Sent from my DROID BIONIC using Tapatalk 2
miguel11691 said:
Thanks a lot... is there any thing not working... i heard the camera is fixed...
Sent from my DROID BIONIC using Tapatalk 2
Click to expand...
Click to collapse
Yep, camera works fine. Check out the last page or two of the post related to the ROM you intend to flash to see what kind of issues people are working. From the Official CM 10.1 ROM:
WHAT'S NOT WORKING (NOTE: I expect to be able to fix all of these issues, it's just taking some time):
Gallery / Media FC see top of the post for FIX.
HDMI
Dock/Dock Settings
Some random reboots being looked at.
Ratamacue said:
As someone who has owned the Bionic since launch, and just jumped to CM 10.1 a few days ago, I'll chime in here. It's a much better phone since CM 10.1. That said, be prepared for issues initially. I had a lot of problems and was ready to give up - until I did a factory reset on the CM 10.1 ROM. If you decide to make the switch, you can root, install SafeStrap, and flash CM 10.1 and Gapps with confidence, as long as don't mind doing a factory reset and rebuilding everything. Since the phone is new to you, that shouldn't be much of a deterrent.
I personally would recommend making the plunge.
Click to expand...
Click to collapse
What did you mean when you said you had to reset on the CM ROM? Does the ROM still stay on the phone after the reset? Also, what did you have to do to rebuild everything?
I have another post asking for advice on rooting and ROMs. If you could help me out too, that would be great. I am interested in CM.
CycoPuppet said:
What did you mean when you said you had to reset on the CM ROM? Does the ROM still stay on the phone after the reset? Also, what did you have to do to rebuild everything?
I have another post asking for advice on rooting and ROMs. If you could help me out too, that would be great. I am interested in CM.
Click to expand...
Click to collapse
After installing the CM 10.1 20130326 NIGHTLY for the first time on a newly rooted Bionic, the phone was extremely unstable. A factory reset made all that go away. I elected to download all my apps again for a fresh start. Right now, it's working well.
Ratamacue said:
After installing the CM 10.1 20130326 NIGHTLY for the first time on a newly rooted Bionic, the phone was extremely unstable. A factory reset made all that go away. I elected to download all my apps again for a fresh start. Right now, it's working well.
Click to expand...
Click to collapse
Indeed... I'm in the latest and everything seems stable minus the speakerphone bug... Its the only thing not working for me
Sent from my XT875 using Tapatalk 2
miguel11691 said:
Indeed... I'm in the latest and everything seems stable minus the speakerphone bug... Its the only thing not working for me
Sent from my XT875 using Tapatalk 2
Click to expand...
Click to collapse
All the early bugs have been fixed with the exception of the speaker phone. I stepped away for Icarus and now I am back
Sent from my XT875 using xda app-developers app
:thumbup:
Hey guys and lads
Today my nook arrived and I was happy to flash CM 10.1 on it.
Everything went well and it was running smooth'n fine!
But for some reason I made the decision to update it over the tablet itself... To some stable m1 update.
after that everything went down.
Wlan connection was horrible, everything seemed laggy and the display wasn't reacting in some cases.
I can still open stuff and the keys are working, but the display itself isn't reacting (cant power it off, lol)
I wiped everything and reflashed the rom, but still got these problems.
What happened? Do I need to trim it?
edit:
Managed to start the device in "safe mode", there everything worked smooth and the display reacts again!
Could reboot it now and suddenly everything works again.
Still im concerned if everything is okay now.
Please help me out here, thanks!
If you went from CM10.1to M1 (which is CM10.2), you need to update the gapps also. You need 20130813.
Sent from my BN NookHD+ using xda premium
ok thank you bro,
Can u tell me if i need to trim my device?
ok thank you bro,
But still, why did my display and perfomance drop out so hard?
Now everything is fine, but I want to know if need to fix something.
Do I need to trim my device?
riboswitch said:
ok thank you bro,
Can u tell me if i need to trim my device?
Click to expand...
Click to collapse
I have no idea. If it is working ok now, I would think not.
Sent from my BN NookHD+ using xda premium
leapinlar said:
I have no idea. If it is working ok now, I would think not.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
CM 10.2 is based on Android 4.3 while 10.1.3 is still Android 4.2.2. -- I would recommend doing a full wipe / factory reset between CM installations with (rather) big version number changes like that. Of course this only applies if you didn't already do a factory reset in the first place.
You should also consider that an M1 Snapshot is not really a stable release. It's more stable than a nightly, but not as stable as a RC release or a a real stable release. Why the M1 shows up as an update on my Nook is a question that I've asked myself before, too. Especially when I consider that I've set up the update service to only show stable releases.
leapinlar said:
If you went from CM10.1to M1 (which is CM10.2), you need to update the gapps also. You need 20130813.
Sent from my BN NookHD+ using xda premium
Click to expand...
Click to collapse
LEECH666 said:
CM 10.2 is based on Android 4.3 while 10.1.3 is still Android 4.2.2. -- I would recommend doing a full wipe / factory reset between CM installations with (rather) big version number changes like that. Of course this only applies if you didn't already do a factory reset in the first place.
---------- Post added at 01:01 PM ---------- Previous post was at 12:55 PM ----------
http://wiki.cyanogenmod.org/w/Ovation_Info
You should also consider that an M1 Snapshot is not really a stable release. It's more stanle than a nightly, but not as stable as a RC release or a a real stable release. Why the M1 shows up as an update on my Nook is a question that I've asked myself bevore, too. Especially when I consider that I've set up the update service to only show stable releases.
Click to expand...
Click to collapse
Ok thank you sir
Yes it's akward that it shows nightly builds instead of the stable version
Well today (after 3 days or so) my device was lagging again, atleast the display wasn't reacting.
Had to reboot to safe mode and then reboot again. Now it works like a charm, but this is pretty strange.
Any solutions for me? I still dont get when i need to trim or what the risk is, since I hot the "bad" eMMc.
riboW
push.
Is my problem a sign to do a trim?
I upgraded my P1000 from cm-10.1-20131117-NIGHTLY-p1.zip to cm-11-20131210-NIGHTLY-p1.zip
After the update it was kinda working fine. Gapps did not work yet since I did not upgrade that yet, so I installed pa_gapps-full-4.4-20131126-signed.zip.
And rebooted.
That's where the trouble started.
Apps crashed and the P1000 did not startup fine.
I decided to do a full wipe, cleared all caches and re-flashed the P1000.
I does not start anymore (stays on the CM11 boot screen).
What did I miss?
It's not your fault.
It's many different but similar errors in past few days on experimental CM11 builds.
Read http://forum.xda-developers.com/showthread.php?t=2560605 for example.
MarviXDA said:
It's not your fault.
It's many different but similar errors in past few days on experimental CM11 builds.
Read http://forum.xda-developers.com/showthread.php?t=2560605 for example.
Click to expand...
Click to collapse
Thanks,
It seems I updated to CM11 a bit to early, having confidence
If there is someone having a glorious idea...I'm open to those, hehe....
I flashed back to cm10... Maybe it was a bit too early to go to CM11....
This thread can be closed
brenzef said:
I flashed back to cm10... Maybe it was a bit too early to go to CM11....
This thread can be closed
Click to expand...
Click to collapse
Your original problem was using PA GAPPS full. Its to big for the /system partition. You should use one of the BaNkS Gapps versions instead. CM11 runs extremely well on SGT 7, especially after switching to ART.
ulev said:
Your original problem was using PA GAPPS full. Its to big for the /system partition. You should use one of the BaNkS Gapps versions instead. CM11 runs extremely well on SGT 7, especially after switching to ART.
Click to expand...
Click to collapse
That was a very good tip!!!!!
THANKS, upgraded to CM11 with BaNkS Gapps.
+1
brenzef said:
That was a very good tip!!!!!
THANKS, upgraded to CM11 with BaNkS Gapps.
+1
Click to expand...
Click to collapse
Glad I could be of help.
Hey guys, I'm not sure specifically who to ask here so I thought I'd just start a thread for it:
I would LOVE to see a version of Philz Touch Advanced CWM recovery available for our Nook devices, but alas compiling from github is beyond me
Here's Phil's developer info post on how to do it: http://forum.xda-developers.com/showthread.php?p=39433612#post39433612
Hopefully someone on here will be able to make this work as It would make flashing rom's/mods SO much easier!! While it works fine, booting from an SD card every time you want to flash something is just ball ache lol
Anyway, I hope this is something that is within the realms of possibility!
Thanks in advance!!
enigma1981 said:
Hey guys, I'm not sure specifically who to ask here so I thought I'd just start a thread for it:
I would LOVE to see a version of Philz Touch Advanced CWM recovery available for our Nook devices, but alas compiling from github is beyond me
Here's Phil's developer info post on how to do it: http://forum.xda-developers.com/showthread.php?p=39433612#post39433612
Hopefully someone on here will be able to make this work as It would make flashing rom's/mods SO much easier!! While it works fine, booting from an SD card every time you want to flash something is just ball ache lol
Anyway, I hope this is something that is within the realms of possibility!
Thanks in advance!!
Click to expand...
Click to collapse
Post this in Q&A Thread or General.
This is for active developments.
Hate to bump/necro this, but would anyone be kind enough to build this?
Been looking for a touch cwm for the nook HD+ off and on for a while and this is as close as I've seen.
twiztid_ said:
Been looking for a touch cwm for the nook HD+ off and on for a while and this is as close as I've seen.
Click to expand...
Click to collapse
Rhyang built TWRP 2.7.1.0 for the HD+ here. It is a good recovery with touch support.
Tzul said:
Rhyang built TWRP 2.7.1.0 for the HD+ here. It is a good recovery with touch support.
Click to expand...
Click to collapse
Thanks, was looking for CWM since its what I use for all my recovery, but I'll check it out.
Never really gave TWRP a fair chance, since cwm has worked with no real issues.
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]