Related
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yeah Factory reset is recommended. And its Working great. I must ask you to consider updating to 4.2, 10.1 nightly build. Its literally flawless...
Sent from my SGH-I897
cm10.1 really cool. Waiting for slim android 4.2
Several days ago I did the upgrade to 10.1 from 10 without the factory reset - no problems, but wipe the caches). You need to clear the clock data first and do the upgrade from the boot screen (not the update screen in about phone). Do a backup just in case you have problems.
for further info go to :donandroid.com/how-to-update-cm10-to-cm10-1-with-cwm-recovery-581
ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
+1
Sent From the Land of Defrag
if you do Erase SD Card, does it erase internal storage instead?
I tried the stable version of CM10, and it seemed to work great except for one thing. I could connect to my employer's Exchange server at all. I tried all kinds of things and it just couldn't connect. I took it to the IT guys and they fiddled with it for a while and couldn't get it to work either. A little quality time with Google told me that JB has a bug that sometimes makes it impossible to connect to corporate exchange accounts. I ended up switching to CM9. Do you know whether CM10.1 fixes that? If so I think I'll give it a try.
ppenguinn said:
cm10.1 really cool. Waiting for slim android 4.2
Click to expand...
Click to collapse
Slim 4.2.1 has been available in beta for a week or two now... I've not encountered any problems with beta 2 so far.
http://forum.xda-developers.com/showthread.php?t=2060386
falcon7204 said:
Hi,
I've had my SGH-I897 Captivate (AT&T) for about a year now, and began reading about rooting and ROMs and personalizing it about five or six months later. I got tired of the AT&T bloatware, the Tethering Manager FC after upgrading from Froyo to Gingerbread via Kies Mini, and the general overall disappointing performance of the phone. I flashed my first ROM back in late April, IIRC, which was CyanogenMod 7.1. This opened up a whole new world of possibilities for me, although my first attempt at flashing was not very good and I ultimately had to go back to stock. But I learned a lot, and since then went from there to CM 7.2, 9.1, Andromeda, and finally CM 10. When I began running Jelly Bean on my Cappy, I was awestruck at the cleanliness of the OS - the Roboto font made everything pop, and everything just seemed smoother (although I wasn't running the Project Butter version - this was CM).
Last week I decided to go bleeding edge and flashed the pre-nightly version of CM 10.1 (JB 4.2). As with my first attempt at flashing, this one didn't go well, either because of the pre-nightly state of the ROM or whatever. So I restored my CWM backup and went back to CM 10. Later that week, I checked in CM Updater and lo and behold, there was a 10.1 nightly staring me in the face. So I updated (even though the official instructions said "don't update through CM Updater", but oh well), and my Cappy runs like a new phone. I honestly cannot find any issues with the OS at all. Everything works. (I updated the gapps version to the 1212 version which runs with 4.2.) I feel like CM 10.1 has breathed new life into my old hardware (and no, I'm not on CM's payroll :laugh.
Mind you, this is with the baked-in kernel. I have tried the Semaphore 2.8c kernel, but for some reason it just didn't seem as snappy. I haven't tried any of the other JB kernels for fear I'll brick the thing.
Thanks to pawitp and the entire CM and AOSP teams for putting out such a high-quality ROM. You guys rock!
I'd post this in the developers forum but I'm not up to 10 posts yet.
Click to expand...
Click to collapse
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
thank quá hay :
theoctagon said:
with my last (first) android phone, i came to the conclusion that carriers muck up android with their lockdowns, bloatware, and refusal to update non-flagship devices. i've been through a couple of ROMs (AOKP, PA, and now on CM 10.1 until PA releases their 4.2 build). i may get a new phone eventually, but, for now, my Cappy is kickin' it. it's always funny seeing someone with a newer phone running gingerbread and thinking "ah, i remember that boggy, unhelpful, but full of potential mess of a phone." good luck!
Click to expand...
Click to collapse
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
laughingT said:
CM10.1 is still on nightlies and from what I am reading, there are still some probs with power management and wifi.
CM10.0 stable is smooth with no noticable lag on my cappy. I don't overclock.
overall passmark benchmark performance is slightly better than it was on GB KK4.
the slowness on your son's phone is probably due to something running, perhaps games.
Sent from my SGH-I897
Click to expand...
Click to collapse
So for a stable fast ROM, you would suggest CM 10.0 over AOCP or some of the other 4.1.2 "final" version ROMs like SlimBean?
depends on your personal preference I suppose. you need to get to CM9 at least, preferably 10.0, to flash slim bean, right? So, if it runs well on 10.0, then you could go slim bean
you wrote that you just want the basics, nothing fancy. so, yes, CM10.
Sent from my SGH-I897
daaac said:
Did you have to factory reset? You make me want to try it. I'm on CM10 right now.
Btw. I find kernels have typical been the biggest player in performance for my phone. I always upgrade to semaphone not sure why you had problems with it.
Click to expand...
Click to collapse
Yes, I did. And I didn't really have any problems with Semaphore, it just seemed a little laggy.
RichMD said:
I gave my Captivate to my daughter a while back when I changed to the Note 2. I initially set it up with AOKP milestone 6 (ICS 4.0.4). My son has my wife's old Captivate and I updated it recently to the final Cyanogenmod 10.0 release. My daughter's phone has been having battery problems due to wakelock issues. I have considered updating it to the latest CM 10.0 like my son has but it seems SLOW - maybe all the games he has loaded.
Anyway, neither of them care about running the "latest and greatest". They just want a stable fast phone. I know the typical answer is "personal preference" but they don't try other ROMs. I have wondered if JB 4.2.x would work well on old hardware like the Captivate with limited RAM, etc. Neither of them need a lot of fancy options and don't use bluetooth, etc.
Opinions on solid fast ROMs to try?
Click to expand...
Click to collapse
I would highly recommend Sephhi's [ROM][4.2.1]Captivating (Xperia Themed)
It is CM10 based and is stripped down to run smooth.
http://forum.xda-developers.com/showthread.php?t=2057574
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
BELbX said:
Set today [ROM] [4.2.1] Captivating (Xperia Themed) [9.2] (Lagless bugfixes), Beautiful, smart, but that does not remove the video camera in any resolution, the error does not take off, but simply does not respond to the record button, the camera photographs. What to do?during the call audio output to the speaker, the button to switch to the internal - external speaker does not work. What to do?
Click to expand...
Click to collapse
Try hellybean 4.2. Hellybean came a long way from when i used it a while back! It's a much smaller and light weight package as compared to the xperia one. Barely any issues. Boot times and first boot are quick. Over clocking is fun again too. I thought it was oc'd at first for being smooth. It's so smooth and stable. One or two things, but nothing compared to others. I like the xperia one but it's heavier with more to be worked. It's running better then aokp 4.1 with semaphore.
Sent from my SGH-I897 using xda app-developers app
3g Problem
I just flashed 4.2.1 AoCP 5 and lost my 3G. Anyone know what's up?
I just flashed the latest version of cm10.1 and now i have an R over my signal bar. Can someone tell me how to fix this? This happened once before when i flashed the 12182012 cm10.1 and it took me forever to fix.
Try this: http://forum.xda-developers.com/showthread.php?t=2066275. Try what's in the last post before following the instructions in the OP.
gocool767 said:
I just flashed the latest version of cm10.1 and now i have an R over my signal bar. Can someone tell me how to fix this? This happened once before when i flashed the 12182012 cm10.1 and it took me forever to fix.
Click to expand...
Click to collapse
BigErnM said:
Try this: http://forum.xda-developers.com/showthread.php?t=2066275. Try what's in the last post before following the instructions in the OP.
Click to expand...
Click to collapse
Yea we are in the hundreds of new posts on this one. Would help if some would read before they flash.
Agreed, it's getting ridiculous!
People know this.... 4.2 rom's have data problems. Practically every rom thread discusses this in a high level of detail. There are fixes if you read. Not gonna hand out this answer, as it's been said over and over in the forums. It's a source issue, even nexus devices are experiencing this issue.
Next, 4.2 will completely change your storage arrangement on your device. Legacy/and 0 folders will become dominant due to the multiuser features. Read, and learn what this will do, and how to recover from it if you downgrade back to 4.1. The op's all warn of these issues! :screwy:
Sent from my Nexus 7 using xda premium
annoyingduck said:
Agreed, it's getting ridiculous!
People know this.... 4.2 rom's have data problems. Practically every rom thread discusses this in a high level of detail. There are fixes if you read. Not gonna hand out this answer, as it's been said over and over in the forums. It's a source issue, even nexus devices are experiencing this issue.
Next, 4.2 will completely change your storage arrangement on your device. Legacy/and 0 folders will become dominant due to the multiuser features. Read, and learn what this will do, and how to recover from it if you downgrade back to 4.1. The op's all warn of these issues! :screwy:
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Damn Duck. Even the devices released with 4.2 have problems. How they think gonna be stable on unsupported devices. I have $600 device. I want everything it came with to go faster but not willing to have cutting edge broke ****.
Dog, it took me all of 2 min of reading to know to stay away from 4.2 on our s3 at this time. I agree, the hit or miss on data is to risky, especially when I'm a year and a half from an upgrade!
I'm running stock rooted pure Google 4.2.1 on my Nexus 7, and it is still a WIP. For custom roms, the multiuser partitioning for source/cm based roms is causing headaches. So much is different than 4.1. Simple theme engine themes are borking the devices, as the legacy folder doesn't know where to apply it. Brand new nexus and s**t is broken, how the hell is our s3 gonna be any better running this android version at this time! Hell, cm10 based roms are still lacking full Samsung source coding....
Sent from my Nexus 7 using xda premium
annoyingduck said:
Dog, it took me all of 2 min of reading to know to stay away from 4.2 on our s3 at this time. I agree, the hit or miss on data is to risky, especially when I'm a year and a half from an upgrade!
I'm running stock rooted pure Google 4.2.1 on my Nexus 7, and it is still a WIP. For custom roms, the multiuser partitioning for source/cm based roms is causing headaches. So much is different than 4.1. Simple theme engine themes are borking the devices, as the legacy folder doesn't know where to apply it. Brand new nexus and s**t is broken, how the hell is our s3 gonna be any better running this android version at this time! Hell, cm10 based roms are still lacking full Samsung source coding....
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Glad to see you duck. Haven't heard from you for a while. Hey man. I'm rockin stock deodexed,kerneled, tweaked, themed 4.1.1 with all the 4.1.1-4.2 inverted apps available. **** stable. Everything works. And no hiccups. I'm good to go. Running 1.72/384 with Quad of 6500. If they didn't see my right handed app button wouldn't know I was running TW. Fast and smooth enough for me and I can call home if I need to.
You too, been on eclipse aosp for the longest time. All decked out. Running a mix of Gunthermic's dh inverts, b-boys, and justins. Will be rocking some synergy once I finish up some beta theme testing
When should we expect the release of KitKat for the Relay?
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Nardholio said:
When TeamApexQ deems fit to release it.
Sent from my Amazon Kindle Fire2 using Tapatalk 4
Click to expand...
Click to collapse
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Guiyoforward said:
Nardholio, do you expect any major innovations, and most importantly, any major sources of bugs or instabilities with KitKat?
Thanks!!
Click to expand...
Click to collapse
That's a question we won't really be able to answer until there is more solid information on KitKat generally available.
Looks like CM is setting up the KitKat AOSP code for there builds Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/396000889011326976
Sent from my SGH-T699 using Tapatalk
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
Cyanogenmod Google+ post " Android 4.4 Source
Source is now being pushed to the AOSP trees. Of course, when it is all there we will begin the process of figuring out what changed, needs work, and/or is no longer feasible or needed.*
We are not in a rush to get 4.4 builds out. We are going to continue the process of working on CM 10.2 M1 - getting that out the door and onto your devices. Further, we will 'finish' the 10.2 code base, similar to what we did with 10.1.*
As a friendly reminder, please don't flood us with requests for 4.4 - we all want new and shiny things, but we will not do so at the expense of abandoning the hard work our contributors have put into 10.2.*
Final note, a lot of folks are reading into the "512mb" item on the release notes. No, this does not mean a sudden resurrection of older hardware, there are dependencies beyond the RAM (and CM has enforced that minimum since ICS)."
Sent from my SGH-T699 using Tapatalk
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Nardholio said:
pst @Magamo this thread was best ended with a simple "when I say so" response and nothing more
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
andrewsfm said:
I actually was referring to an official KitKat OTA update from T-mobile.
How long did it take them to release a JB update after it was first introduced?
I have no interest in a CM ROM full of bugs and things that don't work.
Click to expand...
Click to collapse
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Jax184 said:
Given that we never got upgraded to 4.2 or 4.3 by T-mobile/Samsung, I kinda doubt we'll be getting an official 4.4. And our CM rom, which has been built for us by a couple of people working for free, currently has fewer bugs than the official ROMs.
Click to expand...
Click to collapse
4.2 and 4.3 were minor updates with no name change. JB was a major update and they did update to it.
4.4 KitKat being a major update, I've got my fingers crossed considering the wide range of devices that it's being planned for.
Was just hoping to see if there was any news on a KK update for this model.
CM is fun to play with and all, but it's not something I would trust on an everyday phone.
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
onebornoflight said:
I use CM as a daily driver every day, and have been doing so since 10.2 became CyanogenMod official - everything just works. Now I'm not one of those people who demands a LOT of my phone, but I use it in the course of doing my job daily and it performs better, and more efficiently (with regards to battery consumption) than it did on the debloated stock rom, so much so that I deleted my Nandroid of that setup.
Sent from my SGH-T699 using the XDA-Developers app.
Click to expand...
Click to collapse
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
andrewsfm said:
I'm not sure if I fall into the category of demanding alot from my phone, but if there are issues like, Wifi and BT can't be on at the same time, that's not good enough. That's a serious issue. So if I forget to turn one of them off, stuff stops working? That's not okay...
I want my camera to work, for videos and photos. I want the phone to do everything the hardware is supposed to do.
Click to expand...
Click to collapse
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Jax184 said:
The wifi/bluetooth issue isn't that bad. It only falls apart when WiFi is on and connected to a 2.4GHz access point, and bluetooth is on and connected to a bluetooth device. If you have an N wifi access point that operates at 5Ghz, you can just connect to that instead of the 2.4Ghz node and then the two play nice. It's what I do.
Click to expand...
Click to collapse
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
Guiyoforward said:
Awesome! And you want that for free? You don't seem to appreciate a lot the effort that other people are putting into this...
Click to expand...
Click to collapse
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
andrewsfm said:
I would do this if I had a 5GHz AP, but what I'm saying is that I don't want to have to worry about stuff like that.
I don't want anything for free, except a stock KitKat update from T-Mobile/Samsung for the hardware I paid for... At no point did I say I was interested in CM. I've been explaining why I'm not, the whole time.
I started this thread to find out how long historically after the release of a new OS, does it usually take Samsung/T-Mobile to release an OTA?
Click to expand...
Click to collapse
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
chris122380 said:
Normally only after the Samsung high-end phones get the update and they are just barely getting Android 4.3. It also depends if they decide to update this phone at all. I have been asking t-mobile and Samsung that and they keep blaming each other or referring me to the forum for the phone on there websites.
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
andrewsfm said:
I guess Windows has spoiled me, because I don't understand how it's so hard to port Android to each device.
AMD or Intel, they both use the same instruction set, so they work on any x86/x64 processor, and then you install drivers for your hardware peripherals.
Shouldn't Android run on any ARM processor, and then just have drivers that need to be plugged into it for each component of the phone to work?
Apparently it's a lot more complicated than that, but why...
Click to expand...
Click to collapse
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Looks like coding for CM 11 has started. Check out @CyanogenMod's Tweet: https://twitter.com/CyanogenMod/status/397817644650205185
Sent from my SGH-T699 using Tapatalk
Magamo said:
A lot of the complexity comes from the manufacturers of the SoCs not opening up the workings of their drivers to the wider world that makes porting to new devices, and to new versions of Android so difficult. Things work on one kernel, or one interface, and that's it, and we have no way of tweaking it to work in other ways. Back to the subject at hand. I personally suspect that the Relay will get no official update to KitKat. The Relay is over a year old, T-Mobile has been trying to dump it since 2013 began, and they are the only retailer. The 4.1.2 Jelly Bean updates were rolling out to the then mainline Samsung phones within a week of the Relay's release in September 2012, and we didn't get our update (which frankly is a broken PoS, ESPECIALLY when held up against any CM build for the Relay) until March or April of '13, so expect another 6 months before we MIGHT (and likely won't) get an official 4.3 update.
Click to expand...
Click to collapse
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
andrewsfm said:
Ah k I see. The hardware vendors are mostly to blame it seems.
I may try a stable CM11 if that ever sees the light of day, but I won't hold my breath.
I've heard about the official JB ROM being problematic, so I plan to stay on ICS the phone originally shipped with.
I'm just glad to be getting rid of my Droid3 and Gingerbread.
Click to expand...
Click to collapse
True, there have been some bugs. However, I use the official nightly of cm10.2 as a daily driver. I'd rather put up with the MINOR issues that are left (hardware is stable for the most part) than have a manufacturer ROM. IMHO, the stock ROM that comes with the phone is usually full of crap bloat ware that I don't use and takes up space, and a UI that is SEVERELY limited in customization.
Also, the more people participate and report problems, the faster it takes TeamApex to fix and push out. At least team apex RESPONDS to their users. As mentioned before, it can take as long as 6-8 months after an android release for the manufacturer to roll out an update...still full of crap ware that's NOT used and cannot be uninstalled without root privileges or botching up the UI further.
These people who work tirelessly to provide to us, the end user, an updated version of Android, do so out of their own free will, and don't get a penny. These devs are here to proudly share what they have created, and I applaud and give my utmost respect to them.
You don't wanna install aftermarket firmware? Don't want to aid in bug reporting? Fine, put up with the crap that the manufacturer pushes onto you. Plus, Samsung & T-Mobile don't get any more of your hard earn dollars rolling out an Android update for our year-old device. They'd rather you dump it and buy the latest phone. THAT'S THEIR BUSINESS MODEL! So they have no interest in rushing an update to something as "old" as the Relay.
If you want JB or KK and are unwilling to wait for & install after-market firmware, I suggest you pony up the dough and buy a nexus 5. Better still, learn how to dev and make your own version of JB or KK for the Relay. That's the beauty of open source.
Your rant and *****ing about when "they are going to develop Kit Kat" makes you come across as arrogant, snobbish, and child-like.
Sorry for MY ranting, but it's unappreciative asshats like andre that just piss me off.
Sent from my SGH-T699 using XDA Premium 4 mobile app
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
There will be peace in the middle east first. :banghead:
Sent from my SM-N900V using XDA Premium 4 mobile app
Just because they say it could run on lower end phones doesn't mean it will run w/o lag and so on. I heard the chez won't be getting kit Kat so what does that tell you about the older phones.
Sent from my HTC6500LVW using Tapatalk
The only thing that will run on lower end devices is the new launcher and Google apps. The new ui is supposed to be included in the new launcher and make lower end devices feel and look more like newer ones.
Sent from my ADR6425LVW using Tapatalk
lazarus0000 said:
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
Click to expand...
Click to collapse
The problem with an upgrade to any newer OS on the Charge is the radios. I don't see KitKat and an exception.:crying::crying:
Interesting how they had it where you could use Hangouts as your default SMS App with all the Emoji smileys on phones with Gingerbread including the Charge on the leaked version from the Nexus 5. It was fully working and I tried it. However, now that it's released to everybody through the Play Store, the SMS option is for Android 4.0 Only.
just got kitkat on my razr.... wish I knew how to port, b/c then I would attempt to port this great ROM over to the old Charge....
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2284985
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
I think you're on the right track, though I think I'd stick with CM11 rather than CM10.2.
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
pyroman512 said:
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
Click to expand...
Click to collapse
good luck brother... i'd be glad to test for ya.
some tips that you may/may not already know:
my understanding is that OS 4+ require EXT4 rather than RFS, so it might help to start with a kernel that allows this conversion. there are a few floating around that work.
someone (JT) has successfully (and I guess relatively easily) ported ICS and JB to the charge, the key aspects not working though were mobile data and camera.
I'm told the key road block is the RIL for the kernel in order to get those aspects functioning properly.
as for me, I'd be happy with just a working camera, as the Charge is used by my son as a WiFi-only media player/gaming device. he likes to take pictures/videos, so this is the only thing preventing me from converting it the latest JB port.
again, good luck, and let us know how the progress goes!
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
pyroman512 said:
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
Click to expand...
Click to collapse
As a previous owner of a droid charge, I honestly hope I can squeeze some use out of it as a media device.
I'm on Gummy Nightly 4.4.2 and I'm looking for something more stable. Life is a bit hectic right now so I'm not able to constantly flash a new rom.
What has been the best 4.4.2 rom that you've had the most success with?
to each there own .
moderators dont like these types of threads cuz they cause arguments
Beanstalk and Liquidsmooth! Waiting for the Pac-Man release!
If life is to hectic to find a rom I suggest stock.
Sent from my SCH-I535 using xda app-developers app
I'm liking my PA 4.4 pa_d2vzw-4.0-BETA-20131208 that one it seems to be the only one with a functional camera so far.
GlitchMob said:
Whats the most sold KitKat Rom right now?
Click to expand...
Click to collapse
Define "most solid"...
All you are going to get is people's limited opinions. Plus, if someone has only used 1 or 2 different ROMs - vs ALL of the ones available - they really can't comment
hallstevenson said:
Define "most solid"...
All you are going to get is people's limited opinions. Plus, if someone has only used 1 or 2 different ROMs - vs ALL of the ones available - they really can't comment
Click to expand...
Click to collapse
I meant to say "stable" I just want a rom where the basic functions like Camera work and I'm able to use instagram etc without it crashing. Gummy is fine, but not being able to use the camera is a big thing. I would like a multi-window feature that Hyperdrive has, but I'd like to stay at 4.4.2.
Also, no I will never go back to stock. As for those who have used one or two different roms their opinions are still valid. They can say whether it was stable or not.
twistedillutions said:
to each there own .
moderators dont like these types of threads cuz they cause arguments
Click to expand...
Click to collapse
Lol what do all the nerds start typing in caps lock? its a thread dude in the appropriate area.
GlitchMob said:
I meant to say "stable" I just want a rom where the basic functions like Camera work and I'm able to use instagram etc without it crashing. Gummy is fine, but not being able to use the camera is a big thing.
Click to expand...
Click to collapse
A ROM with a non-functioning camera would never even get consideration from me ! Same applies to ROMs with no working data. Does the Gummy thread tell you the camera doesn't work ? I'd hope so !!
For what it's worth, I've tried the following KK ROMs (with my opinion/comments):
Beanstalk (Gideon's build) - good ROM, no complaints that I can recall.
Omni (Gideon's build) - too plain or simple (or boring) for me. Didn't have a few features that I've grown to like (I blame PAC for that !!). It was stable though.
LiquidSmooth (both the LS team version and Gideon's) - my preferred ROM at the moment. Runs fine, everything works, and has many of the features I like. Between two builds a week and a half apart, I see add'l things added too.
ParanoidAndroid (notta's build) - can't recall any details at the moment.
I suggest trying ParanoidAndroid 4.0 BETA. Yes, it is a beta but it is very stable. I have been using it since Notta switched to 4.4.x. The are still working out small bugs (like every other KK ROM), but like I said, it's very stable.
It does not have multi-window. For that I suggest Omni ROM. I've been using that on my ASUS TF300T and it works awesome!
As evident by some above commentary, XDA is not a support site and users are expected to test all Roms to make their own, independent, determinations as to what is stable for them.
Thread closed.