Related
If anyone has questions or concerns regarding the CyanogenMod 10 please ask here and stay away from the development section for these posts, as it has over 3000 posts.
To start off please read the CM10 faq on the first Page of the CM10 thread before asking any questions here or in the official thread. Thanks
Sent from my HTC One X(L/AT&T)
So, does (or will) the camera app in CM10 have the same burst mode that the Sense camera has? Can you take AS MANY photos AS QUICKLY? Will those photos be similar quality? Will we be able to pull stills from previously recorded video? Or take Hi Res stills while shooting HD video?
I read the last 15 pages of the development thread and didn't see any of this being discussed.
Thanks a bunch!
Billy
Sent from my Nexus 7 using Tapatalk 2
Burst mode is a sense cam feature only, because there is no sense in cm those features will not be there. Your best bet is if you want sense cam but asop feel go with clean rom or tn rom, they can desense the launcher but keep the apps but you will be on ics. But i will say the cm cam is alot faster then it used to be and is still a good camera.
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
PaKMaN787 said:
To start off if you want the video camera and/or audio fixes, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
yungskeeme said:
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Click to expand...
Click to collapse
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
PaKMaN787 said:
To start off if you want the video camera and/or. music workarounds, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
PaKMaN787 said:
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
Definetly hit or miss. Heard it was fixed in the 8/28 but no music so I guess I'll stay on 8/22 and deal with it. Heard someone say they flashed AOKP ICS rom and reflashed CM10 and it was fixed.
bstephens2u said:
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I'll do a little poking around and see if I can get this working (I probably won't) and I'll let you know if I do!
tropazr said:
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
Click to expand...
Click to collapse
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Is wake locks an issue with cm10 so far or just a few users isolated type instance? I was getting massive wake lock for alarmmanager that I do not get on CleanRom.
anyone else getting bad battery life with this ROM? currently running the 8/29 nightly.
Right now im at 33% battery with 11h on the battery but only 1h45min screen time. I also have GPS on and brightness around 1/2..which could possibly be the problem.
JeepFreak said:
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
toptalent said:
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Click to expand...
Click to collapse
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
h8rift said:
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
Click to expand...
Click to collapse
Wooooooooooot!! And would it just be TeamDouche in general that deserves the donation? Or was somebody specific working on this?
Thanks H8!
Billy
Sent from my Nexus 7 using Tapatalk 2
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
Click to expand...
Click to collapse
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
toptalent said:
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
Click to expand...
Click to collapse
I'm not entirely sure if something is being worked on but I think you should flash CR4.0 as it is definitely working and is 4.0.3 base which is what h8rift said to flash.
Sent from my HTC One X(L/AT&T)
May I ask what is the right procedure to flash CM10? In the zip there is a boot.img. Do we need to manually extract and flash it with fastboot?
I ask this because some people (including me) can't make LTE to work in CM9/10. Some say by flashing CleanROM 4.0, full reset then flash CM10, LTE will be the default. This trick does not work for me. What is the mechanism of this trick? What stays after full reset? All I can think is the boot image. But even manually flashing CleanROM's boot.img then flash CM10 does not work for me. Changing build.prop (ro.ril.def.preferred.network and ro.telephony.default_network as suggested at code.google.com/p/cyanogenmod/issues/detail?id=1623 , sorry can't link external) of course does not work either.
I know #*#*info*#*# can change the preferred network type, but it does not stick after reboot, which renders this approach useless.
Thanks.
I was running CM10 back in the day when it was not yet officially hosted by the CM team and I I went back to stock since there were a couple issues with the video recorder and other things. I see now that CM10 is officially being hosted by the CM team but they are still nightly, but I still would like to give it another go around. I was just wondering if there what are the major issues with the ROM right now (if any)?
The first posts don't really tell much except "it's a major work in progress" and the official change log might as well be gibberish to me, and I'm definitely not about to go through all 500+ pages, so if someone would give me a brief summary of what is/isn't working it would be much appreciated!
brob925 said:
I was running CM10 back in the day when it was not yet officially hosted by the CM team and I I went back to stock since there were a couple issues with the video recorder and other things. I see now that CM10 is officially being hosted by the CM team but they are still nightly, but I still would like to give it another go around. I was just wondering if there what are the major issues with the ROM right now (if any)?
The first posts don't really tell much except "it's a major work in progress" and the official change log might as well be gibberish to me, and I'm definitely not about to go through all 500+ pages, so if someone would give me a brief summary of what is/isn't working it would be much appreciated!
Click to expand...
Click to collapse
Its definitely daily driver ready. Just some wake locks making it not have as good battery life as sense. But everything else works great. The build bot has been broken since 10/12 so when the next official nightly comes out, it should have a bunch of new things... Maybe new kernel?
Sent from my HTC One X using xda app-developers app
ethantarheels123 said:
Its definitely daily driver ready. Just some wake locks making it not have as good battery life as sense. But everything else works great. The build bot has been broken since 10/12 so when the next official nightly comes out, it should have a bunch of new things... Maybe new kernel?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sweet, I might just have to flash it again since I usually have a charger handy with me so battery life isn't a huge a concern. I'm sort of confused by what you mean about the next official nightly... I thought nightlys were released every... well night?
brob925 said:
Sweet, I might just have to flash it again since I usually have a charger handy with me so battery life isn't a huge a concern. I'm sort of confused by what you mean about the next official nightly... I thought nightlys were released every... well night?
Click to expand...
Click to collapse
The night lies have been down because some changes were made to the code upstream that causes the Evita build to fail. They're working on the kernel fixes to get the night lies to compile again but apparently its very involved.
Sent from my One X using Tapatalk 2
There was an experimental one posted today
my wifi doesn't crap out on the experimental nightly which was my only issue with 10/12
One should always read at min the last 10 pages of a thread of a Rom you might flash, an really it's expected of anyone.
WR
Sent from my HTC One X
Just a heads up dont know if anyone else is having this problem.
I rooted my 2.2 with the new 2.2 root instructions and downloaded the latest (10/25:experimental[cm-10-20121025-EXPERIMENTAL-evita.zip ]) cm10 build, everything works great, even wifi, except MOBILE data. I'm on straight talk, and man im getting slow speeds, nothing changed to APN, i think its a radio problem. anyone got any suggestions? I attached the radio link, which radio should i flash?
http://forum.xda-developers.com/showthread.php?t=1694012&page=99
Um I'll update all this later as im doing it mobile lol
Bugs:
GPS still being douchy meaning it still not working
WiFi stays on searching for networks
Install: must be on at least ICS rom
Wipe data
Flash Rom + 4.2.x gapps
Reboot
Wait 5 mins enjoy.
Source:
Proton kernel source is still same kernel source which is why WiFi doesn't work :/
LUKE I AM YOUR SOURCE LOL
Downloads:
v5:
recording both ffc n rear fixed 100%
fix camera
fixed playback 100% (because i can )
battery isn't draining (fixed deep sleep)
fixed wifi enough to turn on for temp fix
smaller size of rom
misc changes
link :
v5 is beast
v4 *beastflood*
changelog:
video playback fixed.
camcorder fixed *ffc doesn't record right*
updated to tonights changes
deep sleep issue fixed.
bluetooth issue fixed.
wifi still not working.
etc...lol
link:
I am number 4
V3:
Changelog :
TBD
Link:
http://d-h.st/HaA
v2: it's called beastmode edition but idk why lol jk
changelog :
to make this quicker on myself it has the same bugs fixed as 4.1.2
but the wifi doesn't work on this lol
everything else works and you will need 4.2.1 gapps
fixes battery issues. ( put this here just because that was the biggy)
link:
Yankee doodle went to town and brought back an updated lol
v1:
Because I could lol
Link:
http://codedgraphx.info/tka/sgs4g/jellybean/cm10.1/cm-10.1-20130116-UNOFFICIAL-galaxys4gmtd.zip
sent from my batcave in space! lol
My views on Q's in Dev thread lol
I guess screenies too lol
BTW you guys should thank hechoen without him pushing me last night I wouldn't of tried again and fixed the phone.apk issue lol
@hechoen there it is released!
Lol we now have 4.2.1 before s2 lol
sent from my batcave in space! lol
Edit: Didn't read OP correctly lol
The ROM is working fine so far other than WiFi... I also problem with device settings, but you know that already.
Erik, I wanted to say thanks (already hit the button lol). You never gave up on this phone and now we are on par (in terms of updates) with many popular phones out there. Sure its great to develop on a popular device like the S3, but it is even greater to develop on a phone that is so old and archaic now. I really think that we need more devs like you, people who don't give up on the forgotten. You did what nobody thought could. Not only did you give us a daily driver for Jelly Bean, but now you give us Android 4.2.1... You are the best!
There are other links? low speed download
webxs said:
There are other links? low speed download
Click to expand...
Click to collapse
Do you see other download links in the posts? If there was mirrors, they would listed. This is hosted by one of our members on his own webserver for free just to help out and this was just released, so everyone is downloading at the same time. Don't be so impatient to run a alpha ROM where half the stuff doesn't work and you can't use as a daily phone ROM.
eeeit... Erickmm congratulations you always forward takes this device, why not buy a smsung s2 hercules are in offers, you will be well received...lol
webxs said:
There are other links? low speed download
Click to expand...
Click to collapse
I will say this once and once only. It seems that since Erik is doing roms for other devices as well and is "VERY" popular, this I know cause I looked at the stats on my site which all his files are hosted on, the download speeds are getting bogged down. Unfortunately, there is nothing I can do to fix this. I have made a suggestion to Erik to host on other sites as well, mainly goo and mediafire, and use my site as a mirror. Maybe if there are more mirrors, then it won't get bogged down as much. So, I'll just leave it at that and for now, you'll just have to deal with the slow speeds until Erik decides what to do. Just to give you an idea of what's going on here, I'm gonna show you the stats just for this month alone.
Code:
Jan 2013 HTTP usage codedgraphx.info 179.36 Gig
Day All Traffic (Megabytes) HTTP Traffic
1 11038.48 11038.48
2 13269.43 13269.43
3 11693.21 11693.21
4 10452.60 10452.60
5 11378.55 11378.55
6 13586.09 13586.09
7 11872.08 11872.08
8 14547.27 14547.27
9 11609.46 11609.46
10 13572.19 13572.19
11 11127.03 11127.03
12 10059.93 10059.93
13 15044.09 15044.09
14 11383.62 11383.62
15 9385.89 9385.89
16 3644.03 3644.03
About 95-99% of that is Erik's stuff. So, I'll leave it up to Erik on what he wants to do. He is more than welcome to continue using my site to host his files. With all that said, I'm sorry, but it just seems my site's host just can't handle Erik's popularity.
I'm a nub. What exactly does bln borked mean?
If only wifi, gps, and call worked... I would love this phone again. I'm hating this phone so badly lol
sungersoo said:
I'm a nub. What exactly does bln borked mean?
If only wifi, gps, and call worked... I would love this phone again. I'm hating this phone so badly lol
Click to expand...
Click to collapse
BLN means Backlight Notification. It turns your capacitive buttons into LED notifications. You need an app to control these features.
Seems like 4.2 is really a monster for battery (not a placbo but the truth) on this phone, just 30 minutes and 20% gone (on my second charge)
Sent from my SGH-T959V using xda premium
daothanhduy1996 said:
Seems like 4.2 is really a monster for battery (not a placbo but the truth) on this phone, just 30 minutes and 20% gone (on my second charge)
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Idk man, I used it for a day and found it hard to notice any difference.
I flashed it yesterday and tested a few things (maybe half an hours worth). My battery was fully charged. Fell asleep. When I woke up the battery was dead. I don't know how long it lasted, but with no use it shouldn't have died that quickly.
Sent from a hole in the time/space continuum.
Maybe you have some mediaserver action running?
Got any corrupt music files?
I think this is big problem about battery.
WiFi stays on searching for networks
You can test after turn off WIFI.
What do you think?
Re: [4.2.1]CyanogenMod 10.1 v1[UNOFFICIAL][BETA]
Second time this is a Dev thread I regret opening tbh this rom isn't a DD yet plus its a beta build only released so you guy can play with it that's it .
Its not ready to be used daily and without logs it'll never get there.
sent from my batcave in space! lol
Re: [4.2.1]CyanogenMod 10.1 v1[UNOFFICIAL][BETA]
Erickmmm... PM
Enviado...:thumbup:
OK people. I'm posting this with Erik's permission. Since I've already played with CM 10.1 on my tab, I know a little of what's to be expected and how some of the things work. With that said, here's something to keep in mind...
READ ME:
# CM 10.1 is based on Android 4.2.1. Any and all proprietary applications that you have installed outside of CM should be updated to their 4.2.1 counterparts. Do not use the 4.1 versions of proprietary applications, else you will experience difficulties.
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal. For us SGS4G users, since we don't have nightlies yet, the updater is totally useless. Do not even attempt to try and use it.
# You do not need to wipe when updating to 10.1 if coming from an earlier CM version. However, as we mentioned in the weekend's PSA, users updating (instead of wiping) will experience a conflict in the application data for the Clock app. You are advised to clear this apps data on first boot of 10.1.
# Another item to note is that the support for the 10.0 feature that allowed for an expanded number of targets on the pattern lockscreen is not in 10.1. If you use this lockscreen, disable it before updating from 10.0.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0. Credit to post from CyanogenMOD team (G+ https://plus.google.com/+CyanogenMod/posts/9X561GFMxL5)
Now with that said, the only way we will get this to be a daily driver is to HELP the devs by providing logs of what's going wrong. Without logs, the devs can't fix things. Once we get things ironed out and get the major things working properly, then maybe we can submit to the CM Team for our device for nightlies. Until then, if you want to help get this moving, then quit complaining and provide logs. Otherwise, Erik won't support this project at all and may request this thread to be closed or worse, deleted. So, come on guys, let's try to get this project rolling. I for one would love to see our device get some 4.2.1 love.
GFX.myst. said:
Now with that said, the only way we will get this to be a daily driver is to HELP the devs by providing logs of what's going wrong. Without logs, the devs can't fix things. Once we get things ironed out and get the major things working properly, then maybe we can submit to the CM Team for our device for nightlies. Until then, if you want to help get this moving, then quit complaining and provide logs. Otherwise, Erik won't support this project at all and may request this thread to be closed or worse, deleted. So, come on guys, let's try to get this project rolling. I for one would love to see our device get some 4.2.1 love.
Click to expand...
Click to collapse
Now hating to derail thread, but is there a good primer out there or forum post on the best way to get logs or a suggestion on what to submit, what to filter out, how to filter, etc. There a zillion "log" apps. Is one better than the other? I don't mind testing, but I admit, I get lost sometimes in the "post a log" thing and sometimes the log is so long, I'd hate for a dev to have to sift through tons of crap just to find the 1 line that is the key, so anything that can be suggested on what to submit, etc, would be helpful, for me at least and maybe some others.
erikmm said:
Its not ready to be used daily and without logs it'll never get there.
l
Click to expand...
Click to collapse
I am not sure how to get logs... I went to the terminal emulator or what ever and typed in "logcat" then copied this. I am not sure if this is what you need or not. Please help me help you? Also when you get a text, the quick actions bellow the message preview are cut off.
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
well cyanogenmod 11 resumes cm11 for our phone :angel:
cm-11-20141027-EXPERIMENTAL-taoshan.zip
Is stable ?
davidhor21 said:
Is stable ?
Click to expand...
Click to collapse
same issue with FXP 343 no signal (blinking signal icon)
well i played the ROM a bit some bugs are fixed like front camera (video mode)
well i reverted back my old ROM
ehehe its nice to see cyanogemod continue CM11
waiting tomorrow for nightly release.. i hoped signal is fix.
thats nice.
@varun.chitre15 is this coming from you? or just CM it self?
Pleasee!!
which bugs have this android version ?? and if someone could tell me out into a stable version for the Xperia l ?
Milleto05 said:
which bugs have this android version ?? and if someone could tell me out into a stable version for the Xperia l ?
Click to expand...
Click to collapse
try it by yourself
Joel16 said:
@varun.chitre15 is this coming from you? or just CM it self?
Click to expand...
Click to collapse
It's an experimental build triggered by me.
There is one more coming in few hours, I need you all to test that new one and check if the recently introduced 'No signal' problem is fixed.
It's working for me. Poland, both 3g and 2g.
Sent from my C2105 using XDA Free mobile app
cm
Hello, haw can i make incoming call glowdots background transparent?
varun.chitre15 said:
It's an experimental build triggered by me.
There is one more coming in few hours, I need you all to test that new one and check if the recently introduced 'No signal' problem is fixed.
Click to expand...
Click to collapse
I understand that you had been busy with android One devices and recently Xiaomi Mi3 device. I am not sure congrats be enough for I believe that it needs more recognition !
I checked them all out and that's greatest work but sadly couldn't test it due to unavailability of Android One in Europe.
I understand how much effort and work is required and one single mistake in code can increase errors by many folds. I know it's already a tough job to code and with all the nagging and hate you got for some xperia L users must be very disheartening.
Even if you discarded Xperia L out of further development, I wouldn't have blamed you for all many greedy users did to you.
With all that going on, it's very good to see your support and love for the Xperia L once again which obviously has kept me & many others away from the thought of selling it away.
I hope you continue to work for Android projects as a whole and wish you every luck to make all your work to further success.
P.S: Xperia L Users
Never ask for ETA or when any bug would be fixed and whine like a bit**. He got a life and he does everything for free. You do owe him for using his works but he doesn't owe you at all even if you make a donation.
He gives you time from a lot of his hobbies, family, friends and I'm sure a lot more to bring you his ROMs. He is as human as you , maybe more if you can't see that he has cutting his time from his life and giving it to you to make some Roms and kernel for you.
Instead of being thankful and grateful, don't be a **** to trouble him.
He deserves every support and thank for his each work and you shouldn't take that away from him.
I hope this comes to you as some insight how hard it is to be in his shoes and you should respect that regardless of if he decides to quit development for Xperia L or any device.
@varun.chitre15, Thank you very much for your hard work on our Taoshan.
Long life to the development Taoshan. !!
varun.chitre15 said:
It's an experimental build triggered by me.
There is one more coming in few hours, I need you all to test that new one and check if the recently introduced 'No signal' problem is fixed.
Click to expand...
Click to collapse
Thanks, will try this one ASAP
Ok phone 2g/3g works
varun.chitre15 said:
It's an experimental build triggered by me.
There is one more coming in few hours, I need you all to test that new one and check if the recently introduced 'No signal' problem is fixed.
Click to expand...
Click to collapse
Dirty flashed cm-11-20141028-EXPERIMENTAL-RIL-taoshan over FXP341, also flashed Thunderzap. Data connection works correctly (E, 3G and H+ tested).
Sent from my C2105 using Tapatalk
I tested EXPERIMENTAL-RIL, and everything works perfectly for me
Meanwhile, is there any updates to hwcomposer? those graphical bugs are annoying
any nightly updates ?
I am using the nightly for three months now and I am satisfied.... The experimental is going to be nightly soon? or stable perhaps?
Sent from my C2105 using XDA Free mobile app
maa chuda