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.
Related
This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire HD
CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 6 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery.
2. Do a Nandroid backup!
3. WIPE (wipe data/factory reset + wipe cache partition)
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://mirror.teamdouche.net/?device=ace
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
reserved
10 char 10 char
I bow down to Kali and all of team douche. Christmas is here early this year.
Sent from Cyanogenmod for Desire HD
Nightly !!!! YES...Cyanogen cannot be matched.
rixsta said:
Nightly !!!! YES...Cyanogen cannot be matched.
Click to expand...
Click to collapse
What does this mean exactly ? its updated nightly ? or ... haha
a nightly-build contains all the newest changes which come step-by-step.
all the changes will be offered in a new release candidate if there are stable and harmonize.
so if you always want the newest fixes, patches and so on..you have to flash the nightly-builds. but there is no guarantee that it is stable.
if you want a stable build you have to wait for the rc
sorry for my bad english
rixsta said:
Nightly !!!! YES...Cyanogen cannot be matched.
Click to expand...
Click to collapse
That's right. Although it would be awesome if another team were to try.
mero01 said:
What does this mean exactly ? its updated nightly ? or ... haha
Click to expand...
Click to collapse
Team Douche do work on the rom every day. You can see what commitments they make to the code on the git hub. Every night an automated build bot compiles the code into a flashable rom. As stated in the op, these are experimental builds which add new features but may be quite buggy. In my experience with the nexus one they are usually very stable apart from the odd annoying glitch.
Most importantly for bleeding edge lovers like myself you get to check out new features before, often weeks before, people using the stable branch.
Sent from Cyanogenmod for Desire HD
dr.m0x said:
Team Douche do work on the rom every day. You can see what commitments they make to the code on the git hub. Every night an automated build bot compiles the code into a flashable rom. As stated in the op, these are experimental builds which add new features but may be quite buggy. In my experience with the nexus one they are usually very stable apart from the odd annoying glitch.
Most importantly for bleeding edge lovers like myself you get to check out new features before, often weeks before, people using the stable branch.
Sent from Cyanogenmod for Desire HD
Click to expand...
Click to collapse
But, now Cyanogen has got all organised, at this stage in the cycle i.e prior to release of the stable version it tends to mainly be bug-fixes rather than additional features so in my experience these late nightly release are often better than the RC's on which they are based
dr.m0x said:
That's right. Although it would be awesome if another team were to try.
Team Douche do work on the rom every day. You can see what commitments they make to the code on the git hub. Every night an automated build bot compiles the code into a flashable rom. As stated in the op, these are experimental builds which add new features but may be quite buggy. In my experience with the nexus one they are usually very stable apart from the odd annoying glitch.
Most importantly for bleeding edge lovers like myself you get to check out new features before, often weeks before, people using the stable branch.
Sent from Cyanogenmod for Desire HD
Click to expand...
Click to collapse
Oh thank you for that . Sounds great going to give it a go
Can you post a link to the github thread or update post ? would like too see all the next features n whatnot cant seem to find it
thanks
ghostofcain said:
But, now Cyanogen has got all organised, at this stage in the cycle i.e prior to release of the stable version it tends to mainly be bug-fixes rather than additional features so in my experience these late nightly release are often better than the RC's on which they are based
Click to expand...
Click to collapse
Good point. Until Cyanogenmod 7 (Gingerbread) we probably won't see any new features.
Can't post link to git hub right now but google "cyanogenmod git hub" should take you right there.
Sent from Cyanogenmod for Desire HD
Thats actually pretty insane, NIGHTLY UPDATES . what more could you ask for ... iv been waiting for updates on other roms for weeks now...
The ROM is great but it drains the battery too quickly. Can someone help me on this.
Great to get nightlies, new to Android but well used to this from XBMC, open source ftw.
lisboapcs said:
The ROM is great but it drains the battery too quickly. Can someone help me on this.
Click to expand...
Click to collapse
Would have to disagree, took mine off charge this morning and used it throughout the day heavy enough including FM Radio, PowerAMP, browser, some apps and watching TV on the journey home and battery is at 51% now.
hi i'm new to Android and have a few questions. Just flashed this rom and it looked amazing except that I didn't have market or any other apps. Is it just me (do those apps fall under the Google stuff mentioned earlier? And is it possible to get my contacts from leedroid (just switched after full wipe) also would it help if I flashed the "normal" CM and install the nighty Rom s update ?Anyone can help me? Thx in advance
Sent from my Desire HD
deadcookie said:
hi i'm new to Android and have a few questions. Just flashed this rom and it looked amazing except that I didn't have market or any other apps. Is it just me (do those apps fall under the Google stuff mentioned earlier? And is it possible to get my contacts from leedroid (just switched after full wipe) also would it help if I flashed the "normal" CM and install the nighty Rom s update ?Anyone can help me? Thx in advance
Sent from my Desire HD
Click to expand...
Click to collapse
yup market, gmail, maps etc come under the GAPPS package which you have to flash after flashing cyanogen mod.
If you sync your contacts to your gmail then it should be restored after entering your account details with the new rom
And it doesn't matter if you install the normal CM and then install the nightly, you can just jump straight into the nightly if you want. As previously stated, normal is a stable release whereas nightly is untested but usually stable.
deadcookie said:
hi i'm new to Android and have a few questions. Just flashed this rom and it looked amazing except that I didn't have market or any other apps. Is it just me (do those apps fall under the Google stuff mentioned earlier? And is it possible to get my contacts from leedroid (just switched after full wipe) also would it help if I flashed the "normal" CM and install the nighty Rom s update ?Anyone can help me? Thx in advance
Sent from my Desire HD
Click to expand...
Click to collapse
yes you need to get the google addons for theDHD its HDPI-20101114
http://goo-inside.me/google-apps/
but if you downloaded the rom from rom manger it asks you if you want the google add-ons after the rom as well.
when you install google add-ons sould get your contacts back
only need to do full wipe if you coming from a different rom, eg leedroids rom, if already using CM 6.1 rc2 or rc1 just need to flash the nightly over it.
Thx a lot you both saved my day
Sent from my Desire HD
So any one care to comment what extra feature or u got repair on this NB ? Cop are to the RC
Tis exciting!
Yes! Nightly builds. I have been missing those. Even considered switching back to N1 just for my Nightly fix (and trackball).
Sent from my CM powered Desire HD
Well I'm running nightly build 6 and being on such a low build number got me all hot and bothered. No issues to report so far.
Sent from Cyanogenmod for Desire HD
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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.
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
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
For TW 4.1.2 is the most current, but developers are working on 4.3. Otherwise, I would flash an AOSP ROM & I've had good luck on those too.
DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
Gummy and SlimKay have full GPS and Bluetooth capabilities. The unofficial CM builds are FAR more stable than the official ones, so if you must use CM, go with an unofficial like Mastamoon or KitKang.
HOWEVER... every custom rom has issues with a 'kill signal' with Bluetooth, so if you use BT, you need to make sure you power down the other device, before you try to turn off BT on your phone; that will send the signal to your device and unpair the two. Otherwise, your phone won't be able to reconnect to BT on that device and you'll have to reboot. It's a known bug and people are working on it.
I used Gummy all December and now I'm running SlimKat... they're stable for daily use. I'd recommend a custom kernel with Slim, though... I'm using Lean Kernel.
DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
Take a look at this it was just released
http://forum.xda-developers.com/showthread.php?t=2591895
beepea206 said:
Gummy and SlimKay have full GPS and Bluetooth capabilities. The unofficial CM builds are FAR more stable than the official ones, so if you must use CM, go with an unofficial like Mastamoon or KitKang.
Click to expand...
Click to collapse
Why would an unofficial cm be more stable? From reading the descriptions, it's just cm with a couple of visual tweaks, no?
lexluthor said:
Why would an unofficial cm be more stable? From reading the descriptions, it's just cm with a couple of visual tweaks, no?
Click to expand...
Click to collapse
Recent CM nightlies are highly unstable and there's often they'll put out a build with a commit they later revert. The unofficial builds vary... some don't release every night (avoiding those bad commits), others cherry-pick and are able to avoid commits they don't think are necessary (and are what often wonk up a build). Basically, they're more fine-tuned for our specific device (the CM builds are just pushed out auto-build) and tend to perform better.
If you look at the feedback in the 'official' thread, then compare that to the unofficial threads, you'll see far more issues in the official one. Could be more noobs going to CM's official builds because it's considered safer, but I've seen some veteran flashers have the same issues, so I'm inclined to believe it's due to how they push out nightlies.
... but that's just my observation. Take it for what it's worth.
beepea206 said:
Recent CM nightlies are highly unstable and there's often they'll put out a build with a commit they later revert. The unofficial builds vary... some don't release every night (avoiding those bad commits), others cherry-pick and are able to avoid commits they don't think are necessary (and are what often wonk up a build). Basically, they're more fine-tuned for our specific device (the CM builds are just pushed out auto-build) and tend to perform better.
If you look at the feedback in the 'official' thread, then compare that to the unofficial threads, you'll see far more issues in the official one. Could be more noobs going to CM's official builds because it's considered safer, but I've seen some veteran flashers have the same issues, so I'm inclined to believe it's due to how they push out nightlies.
... but that's just my observation. Take it for what it's worth.
Click to expand...
Click to collapse
That's a reasonable explanation. I'm on CM11 official nightly. I usually read the changelog before I update. I did do a full wipe before updating originally and I've been running very well. I've had 1 random boot in about a week and the camera froze the system once. I had many more random reboots on TW. It's incredibly fast and I've got no lag (that was a bad problem for me on 4.1.2).
Nice one... checking the changelog and/or Gerrit commits is a good practice, IMO. I only flash a nightlie if I find some commits I think would make the rom run better for me... most are small things like language tweaks and updates to other device repos, so flashing the newest version isn't always necessary.
Regarding the random reboots, you probably have the same modem issue I do. There was a recent update to the device RILs that completely resolved the modem 'freakout' i kept having; I believe they used the updated device files from the 4.3 stock builds pushed out, so it made the device more compatible with the 4.3 and 4.4 roms.
DatacomGuy said:
Is 4.1.2 the latest VZW published version?
I'd like to get to 4.3 or 4.4.. what is the most stable ROM that i can flash that won't cause me to lose any features like GPS or Bluetooth?
Click to expand...
Click to collapse
if you like touchwiz, MOAR and Wicked Sensations roms (4.1.2) are pretty good. I'm on cm10.2 (4.3.1) with xposed framework and it's running perfectly. I'm staying away from kitkat cause of all the bluetooth issues.
Can we start a list of sorts with Roms that work with the new bootloader?? so far i read that Dhacker29 has a few test builds of cm11 . i have one installed right now and it has some bugs but works and is faster than my hd has ever been . i can run this game i like and before it couldnt play without lagging now it runs crazy fast . anyway thank you Dhacker29 for the recovery and rom. i was reading another site and someone mentioned another dev that had a test build out for the new recovery but i cant for the life of me find or remember who it was. also how can i tell if a rom will work without trying to install it. i read that the kernel had to be 3.5 and newer or some shshhsh. anyway thanks in advance to anyone that responds
I second this. Was actually thinking of suggesting the same thing. Might help keep people from flashing the JB kernel Roms and asking what they did wrong. Least maybe a bit more.
>.>
almost forgot
heres a link to Dhackers Test rom that im using . it has a few minor bugs but all the hardware works soo
http://androidhosting.org/Devs/Dhacker29/msm8960/cm-11-20140619-UNOFFICIAL-RAZR-HD_M-KITKAT-TEST.zip
i hope its ok to do this anyway Thanks Dhacker29!!!!
http://androidhosting.org/Devs/Dhacker29/msm8960/
here's the whole directory with all his builds and where I think he adds them
I believe there is a PACMan Alpha out as well. Has the same bugs as CM11
cmh714 said:
I believe there is a PACMan Alpha out as well. Has the same bugs as CM11
Click to expand...
Click to collapse
i would love to have pacman rom on here!! i read that you cant downgrade your bootloader is this true or is that only apply to locked bootloaders?
JohnnyMcG said:
Can we start a list of sorts with Roms that work with the new bootloader?? so far i read that Dhacker29 has a few test builds of cm11 . i have one installed right now and it has some bugs but works and is faster than my hd has ever been . i can run this game i like and before it couldnt play without lagging now it runs crazy fast . anyway thank you Dhacker29 for the recovery and rom. i was reading another site and someone mentioned another dev that had a test build out for the new recovery but i cant for the life of me find or remember who it was. also how can i tell if a rom will work without trying to install it. i read that the kernel had to be 3.5 and newer or some shshhsh. anyway thanks in advance to anyone that responds
Click to expand...
Click to collapse
Any stable builds? Maybe some that use stock and then tweak it out.
i think you can install the stock files and then root and use a root app manager to remove all the bloatware from your phone. there is even a thread that tells you all the apps you can get rid of without jacking anything up. here you can check it out
http://forum.xda-developers.com/showthread.php?t=2756195
spapesh said:
Any stable builds? Maybe some that use stock and then tweak it out.
Click to expand...
Click to collapse
after root you can download xposed installer and then download one of the customizing modules and you can then change your icons in the status bar. nav bar, even alter the way your toast messages come in . anything you can think change the color of your wifi and 4g icons or change them to something entirely diff . here check that out too . you probably already know all this already but just in case.
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
JohnnyMcG said:
i think you can install the stock files and then root and use a root app manager to remove all the bloatware from your phone. there is even a thread that tells you all the apps you can get rid of without jacking anything up. here you can check it out
http://forum.xda-developers.com/showthread.php?t=2756195
Click to expand...
Click to collapse
This is what I did. I was already running stock KK before rooting/unlocking. Still running it now but I removed a lot of crap. I'm looking forward to at least a few stable ROMs to try out on this phone, but I'm cool with this for now.
Sent from my DROID RAZR HD using Tapatalk
Does anyone know if the available KK-bootloader roms work on xt925? I know the ROM unification for a lot of devices have taken place. I am not sure this also happens with the new KK-bootlader, or if we are back on the old xt925 vs xt926 compatability devide...
Thanks in advance.
idless said:
Does anyone know if the available KK-bootloader roms work on xt925? I know the ROM unification for a lot of devices have taken place. I am not sure this also happens with the new KK-bootlader, or if we are back on the old xt925 vs xt926 compatability devide...
Thanks in advance.
Click to expand...
Click to collapse
not sure . you can ask Dhacker29 he is the one that made the recovery I think. or you can post your question in this thread and you might get a better response
http://forum.xda-developers.com/showthread.php?t=2776515
Here is a Gummy rom that supports the 3.4 kernel.
https://mobile.twitter.com/dhacker29/status/480220911225036800
Source: http://forum.xda-developers.com/showpost.php?p=53609374&postcount=2913
So far I know of these Roms that are being developed to run on 3.4 kernel
CM11 Unofficial: http://androidhosting.org/Devs/Dhacker29/msm8960/
PAC-man Alpha 1: http://forum.xda-developers.com/showthread.php?t=2683962&page=3 I read mention that this works but I've not tested it myself
Gummy Rom Nightly: https://mobile.twitter.com/dhacker29/status/480220911225036800 <-- using this right now. Seems pretty good.
full list like CM11 unofficial http://androidhosting.org/Devs/Gummy/moto_msm8960/NIGHTLY/
NexesqueKK 0.01: http://www.droidrzr.com/index.php/t...2-droid-nexesque-for-razr-hd-beta-442-builds/ I saw on DroidRZR.com that there was a test for the 3.4 kernel but my attempts to flash it failed
Beanstalk Nightly (Kitstalk): http://www.droidrzr.com/index.php/topic/35880-rom442kit-katunofficalxt926-beanstalk/ flashed the 6-23 one on my phone.. Seems to be working
wow
I thought I was decent at finding info online but i couldn't find any of those threads except for the pacman alpha but for the life of me I can't find where to download the alpha build I can find the nightly n the 4.3 but alas no alpha maybe its under one of the devs tabs instead of the pacman tab idk anyway thanks a lot for all the great info
Jaysp656 said:
Here is a Gummy rom that supports the 3.4 kernel.
https://mobile.twitter.com/dhacker29/status/480220911225036800
Source: http://forum.xda-developers.com/showpost.php?p=53609374&postcount=2913
So far I know of these Roms that are being developed to run on 3.4 kernel
CM11 Unofficial: http://androidhosting.org/Devs/Dhacker29/msm8960/
PAC-man Alpha 1: http://forum.xda-developers.com/showthread.php?t=2683962&page=3 I read mention that this works but I've not tested it myself
Gummy Rom Nightly: https://mobile.twitter.com/dhacker29/status/480220911225036800 <-- using this right now. Seems pretty good.
full list like CM11 unofficial http://androidhosting.org/Devs/Gummy/moto_msm8960/NIGHTLY/
NexesqueKK 0.01: http://www.droidrzr.com/index.php/t...2-droid-nexesque-for-razr-hd-beta-442-builds/ I saw on DroidRZR.com that there was a test for the 3.4 kernel but my attempts to flash it failed
Beanstalk Nightly (Kitstalk): http://www.droidrzr.com/index.php/topic/35880-rom442kit-katunofficalxt926-beanstalk/ flashed the 6-23 one on my phone.. Seems to be working
Click to expand...
Click to collapse
Gummy rom tested on my xt925. Stuck at unlocked bootloader sign. I don't think xt925 is supported yet.
Yeah I don't know if any have xt925 support or not. Hopefully they will include them eventually.
Gummy Rom
I recently tried Gummy Rom for 3.4 kernel. It was pretty good, but had trouble with bluetooth freezing the phone and wifi dropout at times. It has great progress, and appreciate those who are working on it. :good:
I have installed dhacker's 4.4 cm build from 24/6. Happy to report that it boots - and so far, at least - works great. This is on an xt925! It's the first 4.4 bootloader rom other than moto that I have got to actually boot up on this phone.
I installed gummy and have been using the auto updater running nightlies right now I'm running 6-24 build . it seems like the the previous ver. had fixed the screen dimming issue but it seemed to come back on this ver. but rarely happens I haven't tied Bluetooth yet and the popping/static sound issue is still there but other than that I like the rom . thanks for
Sent from my DROID RAZR HD using Tapatalk
In droidrzr forums there is an Unofficial Omni Rom for kitkat bootloader..
btw, for xt925, dhacker says that we only need the new bootloader (maybe installing the leaked soak test from France we can use the newest roms)