Related
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
See the 9-11-12 Cyanogenmod Announcement at bottom of post! There are now regular Nightlies you are used to and now the M-Series Roms, I will let the CM Team speak for it themselves as to what it is, see quote and link at bottom of post.
As of 8-18-12, the Verizon Galaxy S III, yes the one with the formerly locked bootloader that everyone loved to hate, has now been accepted into the Official CM10 Jelly Bean Nightly builds. Bookmark THIS PAGE to check for the latest nightlies. Many thanks to everyone involved in getting the d2vzw this far including you, African Canadian Sock Monkey!
Official Announcement from Cyanogenmod 8-18-12
Today we kick off the nightly builds of the CM10 JellyBean code branch, builds will show up later this evening.
CM9 nightly builds for devices that don't receive a CM10 nightly will continue (for the meantime) but we are changing the timing on them to be once a week instead (aka weeklies). This will allow a means for us to test bug fixes and the like as they get merged into the ICS branch - as stated before, the CM9 branch is in an otherwise perpetual code-freeze.
The devices receiving CM10 nightlies this evening include (but aren't limited to):
# The US SGS3 variants
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (Vibrant, Captivate, International, and i9000b)
# The SGS2 i9100g
# P3 and P5 tablets
Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.
Edit d2vzw nightlies will require the insecure bootloader. See http://goo.gl/CST0K
Click to expand...
Click to collapse
Source
I didn't see a thread for this so I figured I would go ahead and create this thread for the discussion and following of the d2vzw Official CM10 Jelly Bean Nightlies. Our maintainer cvpcs has stated that the initial official nightlies may not have all of the fixes such as MMS fix in them until those fixes are merged into the official tree.
YOU MUST BE ROOTED:
I recommend using the Casual app from Adam in THIS THREAD.
YOU MUST BE UNLOCKED:
As stated the official version of CM10 nightlies for d2vzw requires you be on an unlocked Verizon GSIII. As an alternative to the Casual method Adam posted up, you can now unlock your device using a simple one-click app made by fellow dev mmmeff called VZW GS3 EZ-Unlock on the play store.
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
If you would rather not use that app, see THIS THREAD for CWM 6.0.1.2 files and install instructions.
blade7840 said:
Can I use TWRP recovery to flash this Rom?
Click to expand...
Click to collapse
Don't see why not. As usual, make sure you have a nandroid just in case. I previously stated TWRP Data Wipe was broken. Which is only partially true, because it FAILS for a REASON. If it worked it would format our internal sdcard! Proper use of TWRP would be to use the Factory Reset option which should take care of things. The Format Data option would be rather dangerous if it worked. So there you go.. It should work as well as CWM. More of a preference thing. You can find TWRP 2.2.2.0 in THIS THREAD. If you like using mmmeff's EZ-Recovery app and want to flash TWRP 2.2.2.0 using the custom option, use this file.
BECAUSE WE ARE NOW UNLOCKED, WE NO LONGER REQUIRE OR USE ANYTHING KEXEC
* In case anyone is still running CWM 6.0.1.0 from the kexec kernel days it is fine to use still. It functions as a standard custom recovery but had the additional ability to run kexec enabled kernels. So you can continue to use it or upgrade to another version. Because we are unlocked you are free to use any recovery now and Kexec is no longer applied.
So now all you need to do is root your phone, load up those two apps, load the recovery (i recommend the newest TWRP 2.2.2.0), unlock the device, and download and install the latest nightly in recovery.
GOOGLE APPS (including Play Store) ARE NOT INCLUDED IN OFFICIAL CM:
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Google Apps by default.
If you do a complete wipe and install an official CM10 build clean and you still have gapps remaining without having ever installed a gapps package, you likely didn't get a clean wipe. Recommend rebooting and wiping again and re-install.
WILL I LOSE MY IMEI IF I FLASH THIS?:
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Click to expand...
Click to collapse
There is a chance you will lose your IMEI on these devices any time you flash anything. If you are not willing to accept the risk inherent in flashing your device, regardless of what you are flashing or what you are worried about, then DONT FLASH ANYTHING, remain stock, and locked. If you want to read more on the "how to" for IMEI backup and restore, see THIS THREAD for latest IMEI discussions and detailed methods for backup and restore.
CM OFFICIAL NIGHTLIES DO INCLUDE A KERNEL:
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Click to expand...
Click to collapse
Yes. If you want to try custom kernels on CM10, it is of course at your own risk.
Flash, MMS, NFC or Native Tethering work on these builds?
Let's put it this way. They have all worked at some point or another. Then you have the fact that so many people posting here are contaminating the results with comments about unofficial builds and people that are flashing using different methods, etc......There's no good way for me to track and update this portion accurately. If you rely on any single feature to work properly, you are using the wrong ROM. Go back to stock. If you are flashing Nightlies of anykind you should expect things that have worked all along, some days will be broken. So the best thing to do is try it yourself and report here for others to see. These might be official nightlies but it's still very BETA and WIP (Work In Progress) and should be treated as such.
MMS WORKS
I can confirm personally as of the 8-20 build MMS is working and persistent after a reboot!
NFC WORKS
NFC fix found here.
WPA/WPA2 Native Tethering WORKS
You can flash the file in THIS POST to fix native tethering with WPA/WPA2 security intact.
FLASH WORKS
Sideload the newest Adobe Flash app found in THIS THREAD to get Flash on Jelly Bean. Of course you must have "Unknown Sources" enabled in Settings->Security to sideload any apk
If things change, let me know via PM, I'll try to update the OP.
UNOFFICIAL ALPHA BUILD THREAD IS OVER HERE.
In that thread you can find discussion and info on the unofficial alpha builds by people such as cvpcs, invisiblek, dhacker and others who have been part of the efforts to get us to where we are today. Their contributions are invaluable. Those builds right now may actually run smoother and have less bugs because they are UNOFFICIAL which means they can do what's called "cherry picking" and include code that has not been committed into the OFFICIAL builds yet. The official build may or may not have all those features. They are sometimes different ROMs functionally.
Now that we have an Official Nightly build in order to not confuse people please take Alpha Unofficial talk to that thread. Please keep posts here on topic and relevant to the Official Nightly builds. Things that work on those doesn't work on these and vice-versa.
CHANGELOG IS HERE and UnOfficial CM10 Bugtracker is HERE
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
UPDATE, Official Announcement from Cyanogen Mod, M-Series Roms Announcement 9-11-12
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
Click to expand...
Click to collapse
Source
If you need a more general "all things GSIII guide" to bail out of a problem, or to do other things that aren't necessarily CM10 specific, I highly recommend THIS THREAD
So to start it off I'd like to know if anyone is running the cm-10-20120818-NIGHTLY-d2vzw.zip build from early this morning? Does it have the MMS fix? Is it significantly different from the alpha builds we have been running for a couple weeks?
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've unlocked your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Do these include google now, if not where can I get it?
ilogik said:
Do these include google now, if not where can I get it?
Click to expand...
Click to collapse
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Play Store by default.
Click to expand...
Click to collapse
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Immolate said:
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've disabled your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Click to expand...
Click to collapse
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
YES. Op updated.
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Schaweet said:
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
Yeah yeah, acknowledged. I'm sure if you can disable your bootloader, I'll figure out a way.
ive had one random reboot hopefully it was just a once time thing cause im loving this rom..much better than touchwiz
hopefully that flickering thing when texting gets fixed soon cause it gets a bit annoying..(ive also noticed that my widgets flicker)
neyenlives said:
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Click to expand...
Click to collapse
I think he's talking about Google now(voice search assistant), Not Google apps. It should be built into the ROM but you should still flash gapps anyways
Sent from my SCH-I535 using Tapatalk
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ROM comes with a kernel, but you can flash any non-kexec kernel for AOSP ROMs that you want. I'm currently running an AT&T kernel.
Sent from my Galaxy S III
TheBiles said:
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
Click to expand...
Click to collapse
mms is working for me with the latest build:good:
XTRoRDiNAiRE said:
mms is working for me with the latest build:good:
Click to expand...
Click to collapse
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Can I use TWRP recovery to flash this Rom?
TheBiles said:
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Phone number and MIN are blank for me (after a few reboots). Also, the LTE toggle doesn't seem to function properly. Everything else is working flawlessly; this ROM is definitely a daily-driver. Enjoy!
EDIT: I just realized that MMS isn't working for me....I can live without it for now but those that need it, may want to wait for another build.
neyenlives said:
YES. Op updated.
Click to expand...
Click to collapse
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Nice. I was just thinking about flashing this
Sent from my Verizon Samsung Galaxy S 3 running SynergyROM v1.6
WizeGuyDezignz said:
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The IMEI issue from my personal standpoint and based off of the opinions of the smart guys in IRC, is that it is very possibly a hardware design issue. Samsung could have put the EFS data which contains the IMEI in a non-volatile un-changable part of the memory but it looks as though they left it writable. This means we can try to write it back if we lose it but it also means bad data could be written to it thus erasing it.......that's what I have gotten out of it so far. So every time you flash you take the risk. I seriously doubt any fix will ever officially come because as long as you buy the phone and use it in stock form, you would never see the issue. It's an issue that only affects custom flashers, so don't expect to see a fix.
I originally released this rom on 2fastforums.com (http://2fastroms.com/showthread.php?5435-WIP-18-Dec-2012-CM7-Kernel-CM-msm7x30) and now feel it is ready for release on XDA. (Site is currently down for unknown reasons)
CM7 for HTC Merge/Lexikon
Click to expand...
Click to collapse
Code:
Features:
-100% stock CM7 from source
What works:
Almost everything
Click to expand...
Click to collapse
What doesn't work:
MMS on USC?
Jittery Compass
Click to expand...
Click to collapse
Instructions
1) Flash recovery through bootloader or fastboot
2) Boot into recovery and factory reset, also go into mounts and format system
3) Flash Rom
4) Flash GApps
Click to expand...
Click to collapse
Downloads
Recovery: http://d-h.st/users/e334/?fld_id=6766 (Either one will work, I personally prefer v5.0.2.8 Capacitive Touch)
ROM: http://d-h.st/users/e334/?fld_id=6727
GApps: https://www.box.com/s/79bpq0ywdxcf4093t926 (thanks liamf1!)
Click to expand...
Click to collapse
Source
Kernel: https://github.com/jianC/htc-kernel-msm7x30
Lexikon Device Tree: https://github.com/jianC/android_device_htc_lexikon
Lexikon Proprietary Vendor Tree: https://github.com/jianC/android_vendor_htc
Click to expand...
Click to collapse
All my changes are documented on github.
Credits: Cyberblade (CDMA fix), liamf1 (beta tester/helpful feedback) 2fast4u88, Cyanogenmod & Team, Kali-, Neopeek & Team, UnitedDev & Team, and everyone else who contributed.
Please leave any feedback about bugs/problems/glitches/etc and I will try to fix them.
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
faille13 said:
Thank you ;D
Sent from my HTC Merge using Tapatalk 2
Click to expand...
Click to collapse
Nice to see you on here too
Lol yeah, I'm everywhere.
Sent from my HTC Merge using Tapatalk 2
---------- Post added at 01:34 PM ---------- Previous post was at 01:12 PM ----------
I don't get around here too often. I haven't seen a dedicated forum for my merge yet.
Sent from my HTC Merge using Tapatalk 2
GPS problem
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Gytixas said:
How to fix the GPS ?
It won't turn on , I mean GPS icon is not shown in the notifications bar and it searches for the satellites forever .
I use 20130121 version of this mod and gsm mode .
Click to expand...
Click to collapse
Hmm.. i'll look into it.
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Mistake
sorry sorry, GSM works perfect, Just needed to reboot. Thanks a lot. but Bluetooth and GPS doesn't work either. Plz fix these bugs ! Thanks
nikoloz995 said:
I am so happy that new version established but i GSM doesn't work. Please fix the bug
Thanks
Click to expand...
Click to collapse
+1
development of the firmware is?
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
lexikonlover said:
Thank you so much, this is the best rom for this phone (the only working cyanogen). I am happy to report that after a few weeks use it has across the board improved my phones responsiveness, battery life, and usability. However... I have one problem. I live in Alaska and have GCI as a carrier... when I alter my cdma apn info, everything works up to the point I want to change my MCC and MNC... it's defaulting to 310 and 012 respectively. When I leave those values alone it saves the apn... when I alter them, the apn entry disappears! How can I fix this? I I need it to be 311 and 370 but can't get it to save my apn.
If this never works, I don't care, I wil continue using this rom without mobile internet or mms downloads... it's just that good.
Click to expand...
Click to collapse
APN backup and restore app worked for me on US Cellular (backup apn from stock install, then restore to CM7), though I had to switch to GoSMS as a messaging app for MMS to send properly (stock app would receive but not send MMS - SMS worked normally in both). I had no success manually entering the apn info - didn't seem to have any effect when I tried.
@JianC
I found an issue with the 20130121 version from Jan 21 you posted on 2fastroms: If the phone is left on the charger it will charge all the way up, then discharge all the way back to zero while still plugged in. It still displays that it is at 100%, but then abruptly drops to whatever the actual charge level is after a few minutes of use. I've tried wiping battery stats to no effect and it works properly in stock rom. This is the only bug I can't seem to work around... Any fix or suggestions for things to try would be most appreciated! Thanks again for your work on this ROM!
Fixed GPS (and other issues), please see OP!
EDIT: I'll look into the apns issue... I don't use my Merge on CDMA so it's a stab in the dark.
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
jianC said:
The final version of CM7 has been uploaded (charging bug *should* be fixed).. I will not be supporting CM7 anymore but will be working on Evervolv/CM10.1.
Thanks for your feedback and support!
Click to expand...
Click to collapse
CM10.1 availible to test?
DJ_MiX said:
CM10.1 availible to test?
Click to expand...
Click to collapse
Nope, he working on kernel .
http://review.evervolv.com
Sent from my HTC Merge using xda premium
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
linuxsociety said:
If any help with the kernel is needed I will try my best to free up some time and pitch in some help. I have made several kernels for several other devices and the most popular being for the Acer Iconia tablets here on XDA see my signature. Great to see a CM rom for the merge on here though!! GB works fine for me, not that much cool factor from cm 10 or cm 10.1 as I have compiled quiet a few nightlies for the A100.. Other than the Project Butter and the overall UI I could care less about JB/ICS.
Click to expand...
Click to collapse
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
@ everyone: CM9 for the htc merge is here!: http://forum.xda-developers.com/showthread.php?p=44487058#post44487058
jianC said:
@linuxsociety That would be awesome if you could. Elginsk8r and I have already ported the board files but I can't figure out what's keeping it from booting..
Click to expand...
Click to collapse
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
linuxsociety said:
Does it just boot loop or does it go black? does the CM logo appear? Guess there is no logcat output via adb either or you'd probably have nailed it by now. Maybe we will have to get jtag debugging output so we can see exactly what is causing the kernel panic and work from there.
I have just now had time to get on xda and check up on the new status. I will try to clone the git repository and check the kernel .config for the cm10 build. Just a thought but on most devices that have a working kernel with cm9 the exact same kernel + modules work fine with CM10. Have you all tried the kernel from CM9 that was just recently posted on any CM10 builds for the device? Not much has changed between ICS and JB that are dependent on in kernel features or that require bleeding edge mainline kernel and/or proprietary kernel patches. However there is a good possibility that the issue is more to do with the bootloader that is required to chainload the android OS for JB causing CM10 not to boot properly. So updating the bootloader may be necessary for JB/CM10 to boot properly. Nevertheless we need some debugging output in order to pinpoint what exactly is the problem going on. I am going to flash cm9 to my merge now and see how everything goes. I may experiment with the cm9 kernel and a cm10 build if I can find one for the merge. My hardware I have right now would take quiet some time to build JB as I haven't even used this old c2d laptop to build any android roms yet lol. Sorry for such a long posting but hopefully it is of some help in finding the resolution to the problems we have.
Thanks guys!
Click to expand...
Click to collapse
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
jianC said:
The .35 kernel works fine for CM10.0 but I'm having some issues booting cm10.1 with the .35 kernel because of some graphics memory allocation issues. The main issue is that there are a few issues that can't be fully fixed without the 3.0 kernel such as the camera/camcorder, ION support, etc (which is WIP here: http://review.evervolv.com/#/c/6609/ ). I have already tried probing for the UART TX/RX pins on the lexikon motherboard with a bus pirate but I have not found anything to date. I ordered a micro usb breakout board yesterday for USB UART debugging and am going to pick up some resistors from radioshack so we can hopefully get some progress on the 3.0 kernel because it won't boot far enough to adb or dmesg for our purposes. The problem isn't CM10 right now, but the kernel, which would require jtag or uart debugging, as you have mentioned. I hope that we can get the 3.0 kernel booting soon so we can have cm9/10 fully working.
Click to expand...
Click to collapse
This sounds about like the exact same issues that was experienced when I was helping hashcode work on the original kindle fire device and getting it to work with ICS. I 'think' with the HTC it shouldn't be near as hard to resolve the issue to get full hw acceleration, memory mappings camera/gps and all the extra bells and whistles if we make an attempt at backporting the necessary support into the .35 kernel instead of trying to upgrade * to 3.x which will be adding to the work and break more things than it fixes. Since HTC apparently isn't going to be releasing any updates for the device it looks like it is going to be left all up to us to make one of two decisions:
1) backporting kernel - only the few things remaining needed for our current working GB kernel to have full support for ICS/JB roms
OR
2) updating to 3.x.x and merging HTC fixes and 3rd party patches -through several mainline kernel patches and keeping the proprietary htc addins compatible.
My opinion/suggestion:
I'd think of the two options that backporting would be the most logical answer to the equation since we are only missing support for few things and you already have everything working except the camera, ION, BINDER(?), and other >=3.0.0 android patches. Plus the device is pretty well coming to a good place to say cease development work and either enjoy the device or upgrade to something newer. So if we could get JB support or even just ICS working fully I think 99.99% of all owners/users would be more than 99.99% happy!! I know I would be very happy myself!
CyanogenMod 10.2 is a free, community built distribution of Android 4.3 (Jelly Bean) which greatly extends the capabilities of your phone.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a preview build of CM10.2 for the Samsung Epic 4G. It may cause all the things in the disclaimer to happen, or steal your girlfriend while you are busy flashing ROMs.
Please submit a patch to our Gerrit instance if you want to help out.
WARNING: If you are any build prior to the 10/07 CM10.2 build, this will wipe your data due to a resizing of the mtd partitions. If you wish to go back to another ROM, you will need to ODIN back to stock. If updating from a build prior to 10/07, it is recommended to format /system, /data, and /cache AFTER making your backup.
Recommended steps before you install:
1. Install AppBak from Market, run it and save a list of all your apps.
2. Install SMS Backup and Restore from Market, run it and backup your SMS history.
3. Install Call Logs Backup and Restore from Market, run it and backup your call log history.
4. Boot into CWM recovery. Make a full Backup. You will need this backup later if you decide to go back to your previous ROM and data.
5. It is recommended that you wipe data before installing CM10.2 for the first time.
Additional Disclaimer:
Any bug reports coming from an Unofficial CM10.2 build, or a modified/patched Official CM10.2 build (modem patch, kernels, etc.) should be directed to the originating thread. It is hard enough to provide bug support for the official releases without having to worry about bugs that may have been introduced by outside means. Bug reports are very welcome if you can reproduce them after flashing back to an official, stock build. We do want to be able to fix all the things. Thank you.
**Google Apps are not included in these ROMs. You'll need to install those yourself if you want them. Recommended and highly suggested are the 4.3 gapps from goo.im. Any other versions could result in problems.
Preview Builds
cm-10.2-20131125-UNOFFICIAL-epicmtd.zip
Known Issues:
- 3g data mostly working as of 09/13 build. 3g data will reconnect properly after turning wifi off. No need to disable mobile data before turning on wifi. However, I have noticed occassions where 3G will show as connected, but the data connection is not actually active. This can be verified with a terminal app by using the "netcfg" command. If you do not see the ppp0 interface (or just know that your data is not working), a toggle of the mobile data will most likely reconnect your data.
- 3g data partially working as of 08/14 build. Must boot with wifi off. To reconnect to data after turning wifi off, a reboot is necessary.
GPS is working. However, if you are unable to get a lock, toggle the GPS satelites off & on to reset. If possible, use an app like GPS Status to verify.
/system partition has been resized as of 10/07 build - 39MB have been taken from /data, and 21MB taken from /cache, adding 60MB to /system. MAKE BACKUPS and format /system, /data, & /cache before updating.
- /system partition is too small (again), although enough of the gapps package seems to install so there are no major issues (That I've noticed). This will be adjusted in the not-too-distant future.
- Wimax temporarily disabled
Focal has been removed from official builds.
- Focal will take pictures. But it takes a few seconds to save them. And may crash if you take too many. Feel free to check it out anyway.
- Current bluetooth behavior untested.
- Wired headset mic & buttons. (Yeah, Yeah, someday...)
- Probably more.
Previous preview Builds
cm-10.2-20131007-UNOFFICIAL-epicmtd.zip
cm-10.2-20130913-UNOFFICIAL-epicmtd.zip
cm-10.2-20130902-UNOFFICIAL-epicmtd.zip
cm-10.2-20130814-UNOFFICIAL-epicmtd.zip
cm-10.2-20130802-UNOFFICIAL-epicmtd.zip
Be sure to use these gapps. There is nothing on goo.im yet, but these are as close as you can get to being 'official'.
Patches for devs:
- Check gerrit for any unmerged patches. Everything included in this build has been either merged or uploaded for review.
- This patch is also necessary to prevent rild from crashing. Merged.
- Telephony related patches:
http://review.cyanogenmod.org/#/c/47825/
http://review.cyanogenmod.org/#/c/50036/
http://review.cyanogenmod.org/#/c/50035/
mercy
and for isaint too
didhiy said:
mercy
and for isaint too
Click to expand...
Click to collapse
Pretty sure I was first according to the thanks I did as soon as the thread was up I dont have this phone so I decided to let someone else have it .
Any screens?
Sent from my Xoom using Tapatalk HD
Unjustified Dev said:
Pretty sure I was first according to the thanks I did as soon as the thread was up I dont have this phone so I decided to let someone else have it .
Click to expand...
Click to collapse
and thanks for that
audioblivious said:
Any screens?
Sent from my Xoom using Tapatalk HD
Click to expand...
Click to collapse
He had one on cm-10.1 thread and go to youtube there are plenty of videos and reviews.
Well... (sigh) Being unable to debug builds (i.e. not a dev) always means you will not be the first to push it to the public
Anyway, proper good job mate! Still gonna try this out (bugs don't matter, I never get to step on them) but I will try building again, maybe...
Sent from Google Nexus 4 @ CM10.2
CMTeamEpic said:
- Wired headset mic & buttons. (Yeah, Yeah, someday...)
Click to expand...
Click to collapse
I don't use BT or headset much... but you've never let us down - and we appreciate your work!
bypod said:
I don't use BT or headset much... but you've never let us down - and we appreciate your work!
Click to expand...
Click to collapse
Believe me, it does bother me to keep listing that bug.
WARNING: If you are not already on an official CM10, CM10.1, or CM10.2 build, this will wipe your data due to a resizing of the mtd partitions. If you wish to go back to another ROM, you will need to ODIN back to stock. Currently, the partition sizes are the same between CM10, CM10.1, and CM10.2
Click to expand...
Click to collapse
Slightly off: I always see ROM OPs say that we need to Odin to revert the new MTD partition, but for me it never happened that way. When you're on new MTD ROMs like CM10, 10.1, 10.2, just wipe everything and flash the old MTD ROM you want. I don't know if the ROMs themselves have reverted the partition layout to the old one, but at least they boot and work as they would always. Oh, and if you're on a new MTD ROM and willing to nandroid back to an old ROM's backup, just wipe, install the old ROM first (to convert partition), reboot recovery, wipe again and restore nandroid.
Nice work bbelos!
Ever since we got official CM status for our phone, the development continues to amaze me. This is no exception. 4.3 on this phone is going to prevent me from jumping ship until I see something that really wows me.
Sent from my SPH-D700 using xda premium
@bbelos can you do a commit to remove the branches from cm.dependencies since the manifest chooses the correct one
chrishighs said:
Ever since we got official CM status for our phone, the development continues to amaze me. This is no exception. 4.3 on this phone is going to prevent me from jumping ship until I see something that really wows me.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Now we join the (not so long) list of phones whose highest Android version available/installable is 2+ times their initial/release Android version...
HTC Dream (G1) released with 1.0 and ended up in 4.1.1
Nexus One (and some QSD8x50) released with 2.1 and ended up in 4.2.2 (no 4.3 as of yet)
USA Galaxy S family released with 2.1 and ended up in 4.3 (like us )
AndyYan said:
Now we join the (not so long) list of phones whose highest Android version available/installable is 2+ times their initial/release Android version...
HTC Dream (G1) released with 1.0 and ended up in 4.1.1
Nexus One (and some QSD8x50) released with 2.1 and ended up in 4.2.2 (no 4.3 as of yet)
USA Galaxy S family released with 2.1 and ended up in 4.3 (like us )
Click to expand...
Click to collapse
Its just a fact most 2010 samsungs dont give up Fascinate already has 4.3 thanks to me , bbelos , and pawtip. I need to fix the signal now and we are good to go.
The other aries are already working I think
Man, if development doesn't pick up for my Optimus G by time I get back home from tour in a few weeks, I just may have to come back to my Epic and try this out
Unjustified Dev said:
Its just a fact most 2010 samsungs dont give up Fascinate already has 4.3 thanks to me , bbelos , and pawtip. I need to fix the signal now and we are good to go.
The other aries are already working I think
Click to expand...
Click to collapse
Yup, partly because the S5PC110 board is still good to go at this point, and partly because of you guys maintaining it constantly
(BTW I hate mentioning "aries" since it's the codename for Xiaomi MI-2 series, and I HATE XIAOMI AND MIUI, period. "aries" doesn't seem to be the board name then what does it represent?)
---------- Post added at 04:44 PM ---------- Previous post was at 04:38 PM ----------
iamterence said:
Man, if development doesn't pick up for my Optimus G by time I get back home from tour in a few weeks, I just may have to come back to my Epic and try this out
Click to expand...
Click to collapse
Last I checked there was already unofficial CM10.1 for Sprint variant... and I thought that was enough Not having been officially supported really is a bummer though.
Off-topic: for the same criteria I'd like to buy a second-hand T-Mo GS Relay 4G just because it combines E4G's keyboard with MotoX-level interior and bearable community support (unofficial CM10.1 in 3.4 kernel).
I also would like to say thank you to these wonderful devs for keeping our phones relevant while our phone already has almost 4 generations ahead of it!
I remember way back when I was contemplating between buying the Epic vs. the Evo, today I decided to take a quick peak at the Evo forums just to remind myself how lucky we are to have devs who still care about our phone, thank you for that
Why Omni?
Omni is what custom ROMs used to be about – innovation, new features, transparency, community, and freedom. Our goal is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality.
Omni is a chance to get involved, no matter who you are. Developers, whether you’ve been developing apps for a week, or ROM features for 3 years, you’re welcome. Users, we know you want to help out, and now you can – Omni actively encourages bug reports and feature requests, which can be added to our publicly accessible roadmap. What’s the point in giving you a ROM, and forcing you to not tell us about any bugs you find?
We also recognise how people use Custom ROMs – we’re all custom ROM users and developers ourselves – the argument that “nightlies are not for end users” is over-used, and no longer valid. We’ve found that the vast majority of users want to get nightly updates to their ROM. For that reason, nightlies aren’t a playground – nightlies are for new features that are finished. You should be able to expect the same stability and reliability from a nightly as you would from a “release” ROM, and can report any bugs that prevent this from happening.
We know not everyone wants to update their ROM daily, and you are free to update as frequently or infrequently as you like. Omni is about flexibility and giving users what they expect – and we are excited to see where the community goes with it.
Taken from http://omnirom.org/why-omni/
Screenshots and more info are here
BACKUP YOUR PHONE!!!
* Your warranty was void when you started messing around with your phone.
* These builds are unofficial and are unsupported.
* ONLY YOU AND NO ONE ELSE IS RESPONSIBLE FOR ANYTHING BAD THAT MIGHT RESULT FROM FLASHING THIS ROM!
* Finally Blah Blah Blah good luck!
This ROM probably has the same requirements as any other AOSP 4.4 based rom with the 3.4.x kernel.
Nandroid and then a full wipe.
ROM when its up you can Download Here
PA 0-Day Gapps Get it here
if needed SuperSU 1.75
KNOWN BUGS
Probably whatever is wrong with other KitKat 4.4 roms so...you tell me?
This is based on work done by xHausx for the HTC Evo 4g LTE. You can view the original thread HERE
Thanks
Especially xHausx for the device and common repos and for taking the time to help me get the build process running.
intervigilium for kernel and device repos, because without him most HTC devices would still have Sense
XpLoDWilD, pulser_g2 and all of Team OmniROM
CM for the various repos and for all they've done for the community
XDA:DevDB Information
OmniROM, a ROM for the HTC One S
Contributors
mo976, xHausx
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information
Status: Abandoned
Created 2013-10-31
Last Updated 2013-12-03
Reserved
NO SD CARD!!!
A fix is being worked on but... NO ETA's
Looks promising. Cant wait to try it.
Thanks for keeping the One S alive.
Gotta try this! Thanks
Sent from my One S using XDA Premium HD app
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong
nespresso33 said:
HTC evo is a CDMA radio, maybe the process is crashing because we have a GSM radio.
Click to expand...
Click to collapse
yooouuri said:
I dont want to speak for the devs (sorry for that). But if he use the repos for our phone there will be no problem i think? Please correct me if im wrong
Click to expand...
Click to collapse
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.
mo976 said:
I am looking into the possibility that something in one of the config files is looking for CDMA. However all the ville specific stuff is from CM but edited to use omni sources for the build instead of CM and the msm8960 and s4-common repos that I forked are for all of the HTC S4 based devices regardless of radio support and could have just as easily been forked from CM but required to much editing of the various omni dependencies so I used his stuff.
Click to expand...
Click to collapse
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack
Flashalot said:
Cm repo is all messed up for Ville as far as I cab see from the other devs who source build for the one s
Sent from my HTC One S using Prism Pirates ModPack
Click to expand...
Click to collapse
Well I'm trying anyhow after going through the various dependency files just to double check. I'm hoping it was just a bad build or something so I am pulling down the repo from scratch and hopefully will have a new build in a few hours.
Sent from my One S using XDA Premium 4 mobile app
Looking forward to this
And maybe try the 1.20 radio...
First working build is up try it out let me know!
mo976 said:
First working build is up try it out let me know!
Click to expand...
Click to collapse
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.
nespresso33 said:
Thanks to made this rom on our phone.
This build is working, no bootloop, no force close. But there is a big display glitch with red colors. I never saw that bug before.
Click to expand...
Click to collapse
I noticed that but wasnt sure if its a feature or bug...lol it seems to come and go...
If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone
yooouuri said:
If the SD card is fixed, i would love to try this ROM?
Because i cant live without music on my phone
Click to expand...
Click to collapse
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app
mo976 said:
Its very possible that formatting the sd card from inside the ROM would solve the problem I was unwilling to try... If I have the time maybe I will but...
Sent from my One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
I will check if that's whats missing. I am not sure how to disable strict mode by default since its a setting. Lock screen delay should be the same as cm since its the same kernel.
Sent from my One S using XDA Premium 4 mobile app
yooouuri said:
I'll will try.
- Lock screen delay is more than on the CM roms?
- If you open an app, and more to another page inside the app, a red square appears around the screen. (if you unlock your phone for example)
The SDcard partition (i think mmpcblk0p36) is not mounted!
A page with the red square issue!
http://www.droidviews.com/how-to-fix-the-red-frameborder-around-the-screen-of-android-devices/
Click to expand...
Click to collapse
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.
mo976 said:
Strict mode is not enabled so I am not sure what the red box is...I tried to format from inside the rom, that did nothing. All the mount points are correct...so I am looking at other possible causes like recovery etc.
Click to expand...
Click to collapse
Maby a logcat will give the information you'll need?
yooouuri said:
Maby a logcat will give the information you'll need?
Click to expand...
Click to collapse
I understand what it says but...it may as well be Chinese because I am not any closer. I attached if you want to take a look.
Hi !
I have a few questions:
- If I flash this unofficial rom, will it be possible to have official updates without flashing another rom ?
- And also, is it already good for everyday use ?
Thanks !
Atlantic_Rim said:
Hi !
I have a few questions:
- If I flash this unofficial rom, will it be possible to have official updates without flashing another rom ?
- And also, is it already good for everyday use ?
Thanks !
Click to expand...
Click to collapse
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
i_rnb said:
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Ok thanks for reply !
Then I think I will wait for the official release, because I want a fully functional version for my moto G
Iv just finally been able to flash it, been on the latest rom for two days, bugs for me are youtube freezing and the lockscreen unlock, which actually isnt that bad, u wont need latest official release because this rom will always be up to date and when the phone gets abandoned, people like dhacker are hero's for us because they'll keep our phone updated
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
Iv just finally been able to flash it, been on the latest rom for two days, bugs for me are youtube freezing and the lockscreen unlock, which actually isnt that bad, u wont need latest official release because this rom will always be up to date and when the phone gets abandoned, people like dhacker are hero's for us because they'll keep our phone updated
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I know the great job devs are doing for us before the moto G I had a LG optimus L7 and thanks to cyanogenmod I had kitkat on it.
But as far as this phone just came out, I'm asking myself if it's good to avoid my warranty just to have the same version of android ...
(correct me if I say bad words because I have to train my english :laugh: )
Battery life has been better for me and customization, i think im just happy to flash a different rom, been trying for about 2 weeks, or failing more like, ur english is good, good luck to u
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
Battery life has been better for me and customization, i think im just happy to flash a different rom, been trying for about 2 weeks, or failing more like, ur english is good, good luck to u
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks
i_rnb said:
- nope, you won't get official updates.
- it depends on your needs, check the bug list, if it does not bother you then it is okay for your daily use!
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Wrong. With CMUpdater, if you're running an unofficial build, the nightlies (when they appear) will show up. Even if they don't, you most definitely will be able to manually flash the nightlies without wiping.
The one exception will be if you want to switch to the new "corporate" release streams from Cyngn if those ever get turned on for the device. Those will require a wipe - but official nightlies won't.
Entropy512 said:
Wrong. With CMUpdater, if you're running an unofficial build, the nightlies (when they appear) will show up. Even if they don't, you most definitely will be able to manually flash the nightlies without wiping.
The one exception will be if you want to switch to the new "corporate" release streams from Cyngn if those ever get turned on for the device. Those will require a wipe - but official nightlies won't.
Click to expand...
Click to collapse
I am fully aware for that, but I thought he meant Motorola's official stock updates, not CM's official nightlies.
But still, it is risky to flash official nightly updates on an unofficial build.
Anyway, I might be wrong, I came from a device which did not have a official CM build.
i_rnb said:
I am fully aware for that, but I thought he meant Motorola's official stock updates, not CM's official nightlies.
But still, it is risky to flash official nightly updates on an unofficial build.
Anyway, I might be wrong, I came from a device which did not have a official CM build.
Click to expand...
Click to collapse
There could be risks if you flash an unofficial build from someone who is not at all working on merging a device into CM - they often cherry pick all sort of stuff that causes incompatibilities with upstream to the point where the product really shouldn't be called CM. (I've seen lots of "CM" kangs that had all sorts of extra crap added beyond just doing what is required for device bringup...)
dhacker, however, is an official CM maintainer for many devices, so his builds are the ones that are "on track" for official inclusion.
OK, and I've a few questions again :
If I flash updates directly from CM updater, is it like official updates from Motorola ? I won't lose all my data ?
Because I don't want to lose everything every time a new release come out
U dont lose data, only if u do a factory reset, i do a cache and dalvick wipe, never had any problems doing that
Sent from my Moto G using XDA Premium 4 mobile app
will8578 said:
U dont lose data, only if u do a factory reset, i do a cache and dalvick wipe, never had any problems doing that
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK thanks, then I think I will flash the unofficial ROM when I have time
Atlantic_Rim said:
OK, and I've a few questions again :
If I flash updates directly from CM updater, is it like official updates from Motorola ? I won't lose all my data ?
Because I don't want to lose everything every time a new release come out
Click to expand...
Click to collapse
If people had to wipe every time they flashed an updated, nightlies wouldn't be as popular as they are now.
In general:
1) If you're coming from another project (CM to Omni or vice versa, or any of those to/from stock) you'll need to wipe. Titanium Backup and/or even Androids 'adb backup' can save a lot of time here
2) If you're coming from a previous version of the same project (An unofficial CM build to official nightlies, and subsequent nightlies) you should only have to wipe if someone screwed up
2b) You can usually even do version upgrades this way - e.g. CM10.2 to CM11, although of course this device never saw 10.2 except possibly some super-pre-alpha builds
One exception you may see down the line - with the formation of Cyanogen Inc (aka Cyngn), there are now two release streams. The Community stream (classic nightlies and such) and the "Pro" or "Cyngn" or whatever it's called now release stream. The most obvious example of this right now is CM10.2 on the Oppo N1 - you can't transition between this and community builds without wiping to my knowledge. It's not a big issue now but might be something you need to watch out for in the future.
Entropy512 said:
If people had to wipe every time they flashed an updated, nightlies wouldn't be as popular as they are now.
In general:
1) If you're coming from another project (CM to Omni or vice versa, or any of those to/from stock) you'll need to wipe. Titanium Backup and/or even Androids 'adb backup' can save a lot of time here
2) If you're coming from a previous version of the same project (An unofficial CM build to official nightlies, and subsequent nightlies) you should only have to wipe if someone screwed up
2b) You can usually even do version upgrades this way - e.g. CM10.2 to CM11, although of course this device never saw 10.2 except possibly some super-pre-alpha builds
One exception you may see down the line - with the formation of Cyanogen Inc (aka Cyngn), there are now two release streams. The Community stream (classic nightlies and such) and the "Pro" or "Cyngn" or whatever it's called now release stream. The most obvious example of this right now is CM10.2 on the Oppo N1 - you can't transition between this and community builds without wiping to my knowledge. It's not a big issue now but might be something you need to watch out for in the future.
Click to expand...
Click to collapse
Ok thanks for the informations ! After one hour of intense fighting with my computer, I finally unlocked bootloader, rooted, and flashed cyanogenmod I prefer this rom to the stock one, I find it more smooth, and more costumization
i think its ok for daily use. At least i use it everyday.
I posted this question in a couple other places, but no reply.
I have the GPE version of the Moto G, and I want to run the CM11 builds on it.
Will the fact that the GPE version has the ext4 fs on it prevent me from getting these to work?
I know there are recoveries available specifically for the GPE, but will getting the CM11 builds to work be just a matter of changing a few entries in fstab?
And finally, do either of the recoveries allow you ro format /data from either f2fs to ext4 or the other way around?
Thanks/
I've replaced stock Rom (4.4.2 US Global Version) for unofficial CM11 (2014-02-16's release) and for now CM works more stable than stock.
I had few reboots or issue with .flac, in CM's everything is OK, for now of course. Very good stuff even that is only nightly's release.