Sounds like they did a good job with optimizing broadcast batches so as to cut down on battery life and also cut down on memory requirements for the system and phones like ours with low RAM.
It sounds like a great fit for this phone. Does anyone know if CM or other solo developers plan to bring KitKat to the MPQ?
Thanks
Yes, in due time.
Patience. Don't ask for ETA's.
Looks like Motorola has updated their software upgrade page for the Moto X to say that it is receiving Kit-Kat, but Photon Q's page has an ambiguous "Future plan coming soon". I doubt we'll get an official update, but personally I care more about the Play Services updates. Most of the Kit-Kat features (besides some IR stuff) seem like they are already in CM.
Solust said:
Looks like Motorola has updated their software upgrade page for the Moto X to say that it is receiving Kit-Kat, but Photon Q's page has an ambiguous "Future plan coming soon". I doubt we'll get an official update, but personally I care more about the Play Services updates. Most of the Kit-Kat features (besides some IR stuff) seem like they are already in CM.
Click to expand...
Click to collapse
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
pujdo1 said:
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
Click to expand...
Click to collapse
Google has been releasing updates fairly fast, so some device manufactureres deciced to skip some of them and move to the latest version available to keep up with development.
Though I am not avare of any Motorola produced device that was receveing long term updates, they abandon it soon (more-less) after release.
Even nexus devices fall under 18-month update policy: http://www.phonearena.com/news/Goog...Galaxy-Nexus-will-not-get-Android-4.4_id48950
However, there are other factors regarding samsung galaxy nexus: "While Google clearly states the 18-month rule for dropping Galaxy Nexus support, it is also likely that the company was forced to take this step because Texas Instrument, which manufactured the processor for the device, has shut down its mobile phone business."
Agreed. Better battery life and less RAM usage on 4.4 would make it a welcome improvement for the Photon Q LTE. I would also like to see Miracast (Widi) working properly. At 1.9 Ghz on the Wheatley gov with it's dual Core, thanks to Dev's like Argggh, if we had 4.4....it would be another year before I even thought about getting a new phone. May be an GS5 by that time, or the Nexus 6.
If not by moto is it possible to compile it from source? Like cm, or would it be dependent on moto proprietary 4.3 stuff?
Sent from my XT897 using XDA Premium 4 mobile app
T-Mobile Moto X has got KitKat leaked update yesterday. It's too fast and will be the first non nexus to receive KitKat.
Sent from my XT897 using XDA Premium 4 mobile app
CM-11.0 is in development, but I'd not expect that to be stably useable in a month.
It can boot and the graphics seems to be fine, but no audio, camera and wifi yet, at this moment...
kabaldan said:
It can boot and the graphics seems to be fine, but no audio, camera and wifi yet, at this moment...
Click to expand...
Click to collapse
Hah, I saw the branches... good work!
I was going to try compiling it but ran into build errors, haven't put much effort into it lately. Good to know it can be built and boots! :good:
pujdo1 said:
i dont think that Motorola will make another update for our photon q and even if so, why should they update it to android 4.4 instead of 4.2 or 4.3 ?
Click to expand...
Click to collapse
Because there is probably no upgrade path in the coming year for the Photon Q. Slates don't count. So it should get the latest and greatest until a successor is planned.
Do somebody hear something about CM11 on our phone ? recently do a terrible silence in this matter
niko99 said:
Do somebody hear something about CM11 on our phone ? recently do a terrible silence in this matter
Click to expand...
Click to collapse
...you must be patient
aosp from arrrghhh works good...but without sd card and keyboard backlight
CornholioGSM said:
...you must be patient
aosp from arrrghhh works good...but without sd card and keyboard backlight
Click to expand...
Click to collapse
The SD card is kind of a critical one... And I'm not sure what is missing :/
As for keyboard backlight, I've ported this to other ROM's like AOKP - and it is NOT going to be a straightforward task on AOSP - probably not worth the effort.
Hoping to get the SD card fixed, that is annoying!!
arrrghhh said:
The SD card is kind of a critical one... And I'm not sure what is missing :/
As for keyboard backlight, I've ported this to other ROM's like AOKP - and it is NOT going to be a straightforward task on AOSP - probably not worth the effort.
Hoping to get the SD card fixed, that is annoying!!
Click to expand...
Click to collapse
Yeah, it was fun booting your build up just to see^^
Only problem I had was finding a working GApps....could load your build fine but if i tried to load any of PA's GApps or some others(like the one you have listed in your thread) I would just get constant bootloop. Anyway, looking forward to CM 11! Thanks for the update Skrillax :good:
slimbrady said:
Yeah, it was fun booting your build up just to see^^
Only problem I had was finding a working GApps....could load your build fine but if i tried to load any of PA's GApps or some others(like the one you have listed in your thread) I would just get constant bootloop. Anyway, looking forward to CM 11! Thanks for the update Skrillax :good:
Click to expand...
Click to collapse
there is already working CM11
http://forum.xda-developers.com/showpost.php?p=47954424&postcount=348
- GSM SIGNAL / CALLS / CALL BACK working
- KEYBOARD BACK LIGHT working
- SD CARD Working
- CAMERA with recording wideo working
- GSM DATA working
- GAAPS / STORE etc working
- WIFI working
- SMS / MMS ( for GSM users look bottom)
- ROOT etc working
- HDMI out working
- MEDIA DOCK working
What dont work
- camera button (but work if you start manual camera apk )
For GSM user there is needed to change in bulid.prop like below
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
telephony.rilV7NeedCDMALTEPhone=false
regards
niko99 said:
there is already working CM11
http://forum.xda-developers.com/showpost.php?p=47954424&postcount=348
- GSM SIGNAL / CALLS / CALL BACK working
- KEYBOARD BACK LIGHT working
- SD CARD Working
- CAMERA with recording wideo working
- GSM DATA working
- GAAPS / STORE etc working
- WIFI working
- SMS / MMS ( for GSM users look bottom)
- ROOT etc working
- HDMI out working
- MEDIA DOCK working
What dont work
- camera button (but work if you start manual camera apk )
For GSM user there is needed to change in bulid.prop like below
ro.telephony.gsm-routes-us-smsc=0
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
telephony.rilV7NeedCDMALTEPhone=false
regards
Click to expand...
Click to collapse
Hrmm nice, i'll give it a whirl. This site turned me into a real rom junkie lol
Is SMS working now?
ZenInsight said:
Is SMS working now?
Click to expand...
Click to collapse
Yes, but if you are gsm user you need to edit build.prop like i wroted
Related
Is there any major milestone that must be overcome in order for the cyanogenmod team to officially support the HOXL? Are we just waiting for ROM cooks to take initiative? I know S-off is nice to have, but I don't believe it's a requirement.
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
jordanetodd said:
No but kernel source would be required for jelly bean at the very least. And probably a little more developer interest.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Seems like ther'es been a fair amount of work as far as ROMS and mods and things go, but the Kernel source is the reason that there are working JB roms for the GS3 and we don't even have CM9 fully working yet....
I believe the developer interest come from a few factors.
1) There are few developers that get paid nothing and porting CM9/10 is a lot of work.
2) There are hundreds of devices how do you pick which one gets the CM9/10 .... sales.
The HTC One XL is a nice device but as a LTE device and from HTC it is likely not the strongest selling phone in North America
shorty6049 said:
what's the deal with developer interest on the One X ? Is this not a popular phone or is it that most developers bought an international version?
Click to expand...
Click to collapse
There's definitely more people on the One X international version. People will find that most phones with kernel source available and unlocked bootloader will draw more developers... But in this case quantity =/= quality. I've had several android phones over the years and yes, while it's nice to have a giant land of developers with pages and pages of roms to look through, they lose their luster to mediocrity. You'll find some of the best devs who weren't discouraged by the locked down devices such as this one, and as a result, the product (ROM, kernel, etc) will always be top-notch. And a smaller, more intimate dev community encourages more interaction and community support, making the overall experience that much better.
I think we already have pretty solid support, given that there's still no kernel source available.
We have great Sense-based ROMs (the CleanROM family, amongst others) as well as pretty-solid alphas of CM9 and AOKP. Personally I've been very tempted to try either CM9 or AOKP, but I haven't made the plunge yet. A friend of mine is using CM9 has his daily driver without issue.
I believe the team working on CM9 has plans to incorporate their currently-unofficial branch into being officially a part of CM9 (or CM10) once kernel source is released and the remaining issues are resolved.
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
pearlbrian said:
Functioning CM9/10 is all i really want on this device. I don't need anything flashy. Just give these awesome devs the source kernel HTC!!!
Click to expand...
Click to collapse
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
stnguyen09 said:
The major milestone is kernel source. Without it, the devs can't squash some of these remaining bugs on our device. Without that, we won't get merged into the main branch (afaik). As to why there are more people on the international version, just look at what you just said. The INTERNATIONAL version. It's available on more carriers and yes, it is a heck of a lot easier to develop for since they didn't have to waste time trying to figure out how to unlock the bootloader (which makes them at least a month of ahead of us in terms of development) and they have source.
Trust me, once we have source, development will skyrocket.
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
Our CM9 port is totally functional! Though...not 100%...but from what I've seen it's good enough for a daily driver. I'm running AOKP M6.2 and it's perfectly usable.
Click to expand...
Click to collapse
Sorry, i didn't mean functional. I meant, like you said, 100%.
pearlbrian said:
Sorry, i didn't mean functional. I meant, like you said, 100%.
Click to expand...
Click to collapse
yeah, my issue is that the few things that ARENT working are the things I want the most. Frustrating that this is as good as it can get unless HTC releases that source (which it's sort of staring to look like they may get away with not doing at all)
I think source will come. It's just sad that i have JB running on my old as bones Captivate while my shiny new one x is stuck with Sense :crying:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
kleeman7 said:
AOKP is great, very little doesn't work. It even has NFC. I have been using it for about a week. Very stable.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
SkizzMcNizz said:
If you connect your tablet through the wifi hotspot on your phone then you wouldn't need bluetooth right?
Click to expand...
Click to collapse
Not quite sure what you mean,
The tablet would get Internet from my phone, then I'd use the tablet to stream music to my stereo via bluetooth
shorty6049 said:
what on AOKP doesn't work currently? I'm trying to decide whether to switch back to something like CleanROM DE or over to AOKP right now.
I just got a nexus 7 and was planning on using it as a nav/media player in my car , mounted in front of the existing stereo. What I'd like to do is use my phone as a wifi hotspot (triggered by a NFC tag in the car) and then stream music through the tablet via bluetooth.
Click to expand...
Click to collapse
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
stnguyen09 said:
From the AOKP thread:
What doesn't work:
Tethering (coming soon)
Panorama mode in Camera app
2G/3G switch (needs kernel source)
Same multitouch bug as CM (needs kernel source) <- When you have multiple touch points active and you remove one, the phone loses track of all of the others
Face Unlock
Other things may come up too depending on your specific situation (especially if you don't clear dalvik and cache or don't factory reset).
Click to expand...
Click to collapse
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
shorty6049 said:
Edit- I was looking at the wrong AOKP thread.
(for whatever reason, android beam doesn't seem to be working when I try it on milestone 6.2 though) I touch the phone to the tablet (both with NFC and android beam turned on) and nothing happens.
Tried it with a photo open as well to see if you needed content to beam . No luck
Click to expand...
Click to collapse
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
I got it to work using CleanRom (not a photo, it told me it didn't support receiving large files) . I might flash something new tonight... I really just want something that does wifi tether (which I'll have to read into more... I feel like it's tougher to get that feature working on this phone than it was on my Evo) and NFC (so I can automatically turn on tethering when I get in the car) . I'm alright using a sense-based ROM if I have to since anything is pretty fast on this phone and cleanrom is relatively AOSPish
stnguyen09 said:
I don't think beam can actually send photos, only links and contact information. SBeam on the SGSIII can send files and such because it uses Wifi Direct to transfer files. Try sending a web page or a contact card between your devices and see if that works? I've never used NFC yet so I'm just going by what I read.
Click to expand...
Click to collapse
Sending Photos only works on JB. With ICS you can you can send contact info and Youtube links. Works between CM9 on One X and my N7 running JB.
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.
maybe....
http://au.ibtimes.com/articles/5034...veals-android-4-kitkat-os-11.htm#.UicpuH-I68A
here's a quote from the article:
Android 4.4 KitKat Features
Google hasn't revealed any features yet of the upcoming Android 4.4 KitKat but instead, the company said: "our goal with Android KitKat to make an amazing Android experience available for everybody."
With this statement from Google, it is expected that KitKat will become accessible to Android-running devices with lower RAM such as 512MB and older Android version such as 2.3 Gingerbread. This optimisation has been rumoured to be included in Android 5.0 Key Lime Pie.
Click to expand...
Click to collapse
What...
http://signatures.mobile-overload.com/wp-content/uploads/2013/07/sig-cm-5.png
I would not hold my breath.
Sent from my SCH-I545 using XDA Premium HD app
lol no. Unless if it was created by an awesome person here, but there's no point in that. This phone is long dead, earlier this week I finally moved on, and oh my gosh, its been great having a Nexus 4 over this phone that was out-dated before it was even released back in Spring 2011.
Nope
You'll probably never see a KitKat version on the Charge. The main reason is the same that you never saw ICS or JB on the Charge. The code for the radios was never released. I've tried JB on the Charge, it runs well; however the camera and data don't work. Also, while I still use the Charge as my primary phone, there's not many of us left.
ICS and all versions of JB work fine on this phone already... we are just missing the radios.
I doubt anyone cares about this phone anymore anyways...
10amla said:
You'll probably never see a KitKat version on the Charge. The main reason is the same that you never saw ICS or JB on the Charge. The code for the radios was never released. I've tried JB on the Charge, it runs well; however the camera and data don't work. Also, while I still use the Charge as my primary phone, there's not many of us left.
Click to expand...
Click to collapse
I'm inclined to agree, though it would be awesome to be proven wrong!
JihadSquad said:
ICS and all versions of JB work fine on this phone already... we are just missing the radios.
I doubt anyone cares about this phone anymore anyways...
Click to expand...
Click to collapse
Yeah not many folks left that's for sure... still a few that care though
dwitherell said:
I'm inclined to agree, though it would be awesome to be proven wrong!
Yeah not many folks left that's for sure... still a few that care though
Click to expand...
Click to collapse
I agree with both assessments. Thanks for all the work you've done on Tweaked, Dwith. My wife and I love it on our charges.
P.S. One problem I had with Tweaked Lite, when I installed it, it didn't install file manager(I think that's what it's called on stock) and when I went to select a sound(not ringtone) for a ringtone it would show and error. I went to tweaktools and installed the file manager and it works fine. Not sure why it wouldn't work with my other file management programs.
10amla said:
I agree with both assessments. Thanks for all the work you've done on Tweaked, Dwith. My wife and I love it on our charges.
P.S. One problem I had with Tweaked Lite, when I installed it, it didn't install file manager(I think that's what it's called on stock) and when I went to select a sound(not ringtone) for a ringtone it would show and error. I went to tweaktools and installed the file manager and it works fine. Not sure why it wouldn't work with my other file management programs.
Click to expand...
Click to collapse
Yeah I am not a fan of MyFiles, and for better or worse the call to that for ringtone selecting is hardcoded... at least tweaktools brings it back quick enough - forgot about that tbh, sorry for the troubles!
dwitherell said:
Yeah I am not a fan of MyFiles, and for better or worse the call to that for ringtone selecting is hardcoded... at least tweaktools brings it back quick enough - forgot about that tbh, sorry for the troubles!
Click to expand...
Click to collapse
I agree with your take on MyFiles, one of the first thing I did was replace it with something else(currently FX File Manager). I wasn't a big deal, I had planed on copying my few ringtones to system anyway.
while I agree that the we are more likely to see Republicans and Democrats agree on something, would still be interesting to see if this holds true. I really would not be surprised though, if older devices do get upgraded to the latest OS - that could mean larger revenues for Google. more folks would be able to use their apps, services, etc. without having to get a new device.
however, after then, they could see how slow their device is, and then they decide to upgrade. but still, worth keeping an eye on.
Google and Verizon both agreeing to do this? Hell will freeze over first.
Sent from my SCH-I510 using xda app-developers app
From my understanding of several stories posted from Android sites since KitKat was announced, It sounds like either Google is going to update phones to KitKat silently like they have been doing everything else without the help of Samsung or Verizon or perhaps we just get these features without ever actually upgrading to KitKat
Hangouts is supposed to be replacing the stock Messaging app-If Google can do that then why would they need anything from Samsung/Verizon??
http://www.androidpolice.com/2013/1...msmms-integration-video-sharing-capabilities/
http://mobilesyrup.com/2013/10/08/h...uts-will-almost-certainly-integrate-with-sms/
4.4 "Google Experience" Launcher Launcher could be released from the Play Store (which would replace touchwiz??)
http://www.androidpolice.com/2013/1...re-some-things-we-are-expecting-to-see-in-it/
The truth of the matter is this. The Motorola Droid 1, a phone I bought as a media/mp3 player for 50 bucks and fixed up, is working better than a phone I paid 300 new and had nightlies and better support. I loved my charge, the battery sucked. And the phone I use now is the Verizon note 2 and sprint note 3 as a business phone since I now work for the sprint corporation. Do I miss my charge? Yes. Do I wish it had some cyanogenmod support being a phone 1 1/2 years newer than the droid 1? yes. As soon as I can learn how to make a rom for the charge, I plan to make an ics or jb nightly that will support a wifi only support on this relic. It was my first 4g phone. I have it in my desk and feel sad since it helped me achieve so much.
asacado said:
The truth of the matter is this. The Motorola Droid 1, a phone I bought as a media/mp3 player for 50 bucks and fixed up, is working better than a phone I paid 300 new and had nightlies and better support. I loved my charge, the battery sucked. And the phone I use now is the Verizon note 2 and sprint note 3 as a business phone since I now work for the sprint corporation. Do I miss my charge? Yes. Do I wish it had some cyanogenmod support being a phone 1 1/2 years newer than the droid 1? yes. As soon as I can learn how to make a rom for the charge, I plan to make an ics or jb nightly that will support a wifi only support on this relic. It was my first 4g phone. I have it in my desk and feel sad since it helped me achieve so much.
Click to expand...
Click to collapse
That's exactly what I was thinking - even if the radios weren't released, having the phone to use over wifi would be good enough for me. I guess that's the question - would it be possible to work up a kitkat ROM that was just purely wifi?
zereoue said:
That's exactly what I was thinking - even if the radios weren't released, having the phone to use over wifi would be good enough for me. I guess that's the question - would it be possible to work up a kitkat ROM that was just purely wifi?
Click to expand...
Click to collapse
I've seen an ics rom that was floating around, but support for this phone was always limited. It came and went faster than any other phone I saw. Hell, the bionic I owned had support and nightlies all the way up to the day I got the note 2. I digress. I am looking into it as soon as I can get a linux kitchen set up.
asacado said:
I've seen an ics rom that was floating around, but support for this phone was always limited. It came and went faster than any other phone I saw. Hell, the bionic I owned had support and nightlies all the way up to the day I got the note 2. I digress. I am looking into it as soon as I can get a linux kitchen set up.
Click to expand...
Click to collapse
I am learning how to build for android. Starting with the fascinate since there is a lot of support so I can gain familiarity and then I'm going to do a build for the charge. I intend to only use it as a media device. I can't promise or guarantee anything but, I will try my best to deliver a bootable kitkat rom. This is all pretty difficult. We shall see what happens.
pyroman512 said:
I am learning how to build for android. Starting with the fascinate since there is a lot of support so I can gain familiarity and then I'm going to do a build for the charge. I intend to only use it as a media device. I can't promise or guarantee anything but, I will try my best to deliver a bootable kitkat rom. This is all pretty difficult. We shall see what happens.
Click to expand...
Click to collapse
I have a Fascinate as well, but haven't installed any of the KK offerings for it yet. I did notice that when updating the Fascinate to KK you have to flash a 4.1 or 4.2 rom first, to get the file system setup, right? Then flash the 4.4 rom. Would the steps be the same for the Charge?
zereoue said:
I have a Fascinate as well, but haven't installed any of the KK offerings for it yet. I did notice that when updating the Fascinate to KK you have to flash a 4.1 or 4.2 rom first, to get the file system setup, right? Then flash the 4.4 rom. Would the steps be the same for the Charge?
Click to expand...
Click to collapse
AFAIK you shouldn't have to flash any rom first.. I could be wrong. I don't keep up with all the fascinate development. I did flash a 4.4 rom in the past from cm10.1.
I have a build enviroment set up and I am running into problems building cm11 for the fascinate. I think by the errors that I need to increase the system partition. Because the build always fails at making the system.img. The build guides make it seem like you should run into no errors at all.
I'll start building for the charge soon. I'm too much of a noob to actually develop for it right now, but I think I can atleast boot it once I figure out how to build it.
pyroman512 said:
AFAIK you shouldn't have to flash any rom first.. I could be wrong. I don't keep up with all the fascinate development. I did flash a 4.4 rom in the past from cm10.1.
I have a build enviroment set up and I am running into problems building cm11 for the fascinate. I think by the errors that I need to increase the system partition. Because the build always fails at making the system.img. The build guides make it seem like you should run into no errors at all.
I'll start building for the charge soon. I'm too much of a noob to actually develop for it right now, but I think I can atleast boot it once I figure out how to build it.
Click to expand...
Click to collapse
not sure if I mentioned this earlier, but it could be the fact that the charge is based on RFS system (GB 2.3). I believe android went EXT4 with ICS and higher. there are some kernels that can convert the Charge to EXT4 - so not sure if that would help ya.
Does anyone think that android 5.0 will come to our phones? or are Google Motorola and Verizon going to be an ass and say no. I'm willing to help any development.
We're not going to get official support for 5.0 if that's what you mean. As for custom ROMs, I'm sure it will happen eventually.
Once Android 5.0 L is officially released, we intend to bring this latest upgrade to many of our other Motorola devices, as well. This includes Moto X (1st and 2nd Gen), Moto G (1st and 2nd Gen), Moto G with 4G LTE, Moto E, Droid Ultra, Droid Maxx and Droid Mini. We're still working out the details on timing and the upgrade depends on our partners' support so stay tuned to our software upgrades page for the latest and greatest.
Click to expand...
Click to collapse
http://www.motorola-blog.blogspot.hu/2014/10/nexus-6-from-google-and-motorola-more.html
...and it begins...Took less than a day for someone to ask. It's not even released yet. Coming to the Razrs? Not a snowball's chance in hell. Unofficial, maybe? These things are at EOL and they received a barely functioning official KK update.
Sent from my HTC6525LVW using Tapatalk
Moto kind of hinted at the possibility of having other devices on Lollipop, but I'm not holding my breath this time.
derpyherp said:
Does anyone think that android 5.0 will come to our phones? or are Google Motorola and Verizon going to be an ass and say no. I'm willing to help any development.
Click to expand...
Click to collapse
We're not even going to get KK 4.4.4 officially. The only way we have that is via custom ROMs like CM11.
Those of us in the soak test were told that this latest OTA (.15 release) was the FINAL release for this phone. No more updates. That came straight from a Motorola person in the private soak test forums.
So, don't hold your breath for an "official" Lollipop release. As others have stated, you might see it via Cyanogen or some other custom ROMs, but that will only be for those who have unlocked bootloaders. Those who have already upgraded to the latest OTA without unlocking are screwed forever.
Besides, CM11 for this phone has just recently become completely stable. L isn't even out yet.
here's is how its going to go down.
L comes out nov 3.
cyanoagen inc /PA will merge the code to their repos; take about a month before the first nightly comes out. cm11 is EOL as they move to Lollipop.
gummy slim and others will take the cm base and fork to get their ROMs running too.
then dhacker epinter etc. our great maintainers will port to our devices; first nightly will be for the very brave.
about 2-3 months of bug fixes until it becomes usable.
give or take by feb we have a daily driver of android L
question is with the f* ups of jjbl and kkbl which kernel will be supported to L, i'm sure cm will use a custom kernel just like it did with cm11 before the moto kk ota.
paranoid android to make l for msm8960 unified
just saw a reply from cj360 he will be working on l for msm8960 devices jbbl and kkbl. he said dont hold your breath ait will take a while
Gr8 stuff so far!
I'm enjoying my recently renewed phone anyways!
Btw, this L inspired Nova Pro customizable theme rocks and ART runtime is superb!
Sent from my Razr HD, Unlocked KKBL, latest CyanogenMod CM11 KK 4.4.4 ROM, ART runtime.
Yeah, it's actually available right now.
Check dhacker29's twitter, he has links up.
Flashing soon
the build
cartpig said:
Yeah, it's actually available right now.
Check dhacker29's twitter, he has links up.
Flashing soon
Click to expand...
Click to collapse
I flashed the build from the 14th i have no issues besides the power menu and lack of options, it doesnt have root DO NOT get the one from the play store get supersu 2.1.6 flash recovery. if you get anyother it will soft brick or cause fc issues. The wifi activity arrows are out of line. I will provide the zip. Its smooth no battery life issues its absoultley flawless..
GOOD JOB dhacker29 WE ALL OWE YOU SO MUCH FOR DOING THIS!!!
derpyherp said:
I flashed the build from the 14th i have no issues besides the power menu and lack of options, it doesnt have root DO NOT get the one from the play store get supersu 2.1.6 flash recovery. if you get anyother it will soft brick or cause fc issues. The wifi activity arrows are out of line. I will provide the zip. Its smooth no battery life issues its absoultley flawless..
GOOD JOB dhacker29 WE ALL OWE YOU SO MUCH FOR DOING THIS!!!
Click to expand...
Click to collapse
No, it has issues. Blue-tooth is wonky and Netflix and Google Play Movies won't work (you can't watch anything).
DHacker told me via Twitter that it's due to the DRM libraries. He hasn't figured out the right combination yet to get it working,
But, other than that, it works well.
11/16 has the battery percentage in the notification icon.
11/17 apparently has radio issues. Some people have reported that it works for 5 minutes and then the radio dies. A reboot fixes it for about 5 minutes, and then it dies again. Might want to stay away. I'm going to test it, and if I see the same issues, I'll go back to 11/16.
On the 11/16 build, here's what happens on my xt926M:
Phone > Recents > View full call history (bottom of screen) > Dialer fc's.
Haven't upgraded to the 11/17 build yet, as I don't want to run into any radio issues that I'm reading about here.
Not_A_Dev said:
On the 11/16 build, here's what happens on my xt926M:
Phone > Recents > View full call history (bottom of screen) > Dialer fc's.
Haven't upgraded to the 11/17 build yet, as I don't want to run into any radio issues that I'm reading about here.
Click to expand...
Click to collapse
There's a thread in the dev section that's already dedicated to reporting performance, bugs, etc on the new LP builds....
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
There's a thread in the dev section that's already dedicated to reporting performance, bugs, etc on the new LP builds....
Click to expand...
Click to collapse
Thanks. Just posted my impressions of running the 11/16 build on that thread.
So here's a question (and I'm being serious when I ask, not trying to be snotty):
What about L is everyone so looking forward to that you all need it so bad? Xposed doesn't work on it, and if you're running a custom ROM you're already more than likely modified beyond anything that "Android L" is going to give you...
Other than "material design" and "ART" (along with being near impossible to root without an unlocked bootloader) I haven't even read up on what is so special about L that everyone is creaming their pants over it. Please someone enlighten me to the goodness of L other than "it's Google's lastest software".
EDIT: An acceptable answer would be to get off of the botched up KK Moto gave us... twice... Thus why I am sporting DU now - never going back.
LifeAsADroid said:
So here's a question (and I'm being serious when I ask, not trying to be snotty):
What about L is everyone so looking forward to that you all need it so bad?
Click to expand...
Click to collapse
For me - in short - battery life. If Android 5.0 hadn't come along soon, I would have downgraded to JB any day now, because that was the perfect OS for my XT926M. For me, KK just does not run right on this device. Why LP? The promise of "Project Volta" and whatnot. Of course, running a pretty much pre-alpha early version of CM 12, battery life is actually worse than it was on KK. I'll chalk it up to the fact that LP still needs development for this device, in hopes of having good battery life, hopefully by next February. Material Design is also pretty to look at.
Not_A_Dev said:
For me - in short - battery life. If Android 5.0 hadn't come along soon, I would have downgraded to JB any day now, because that was the perfect OS for my XT926M. For me, KK just does not run right on this device. Why LP? The promise of "Project Volta" and whatnot. Of course, running a pretty much pre-alpha early version of CM 12, battery life is actually worse than it was on KK. I'll chalk it up to the fact that LP still needs development for this device, in hopes of having good battery life, hopefully by next February. Material Design is also pretty to look at.
Click to expand...
Click to collapse
Lol I will totally agree with you on the battery life thing! I thought my phone was on its way out with how fast the stock KK versions were draining my battery. Constantly had to keep the phone on a charger when I was in one place. I will say that the battery life on DU was one of the things that really caught my attention from the start. Phone makes it through the day, can make it through the night if I forget to charge it overnight, and no more does the phone heat up to 125-140F. Highest I've seen, even with charging, screen on, streaming movies or TV over LTE, has been 98F. Night and day compared to the stock KK ROMs Moto vomited at us. I'd be surprised if other custom KK ROMs for our phones didn't have much improved battery life over that failed attempt at a PR stunt giving us stock KK.
I have to really give major props to the developers of the DU ROM which I ran for a solid 2 weeks, just prior to upgrading to 5.0 They have actually made KK a bearable OS on this device with which I could get 2 full work days out of the XT926M - battery-wise - with moderate use. Still, the MAXX battery is a beast, and less than 2 days should not be acceptable. Under JB that was the case. If LP doesn't deliver soon, I am definitely going back to JB. And right around next March, my contract for this device is up anyway.
+1 for dirty unicorn dev
Not_A_Dev said:
I have to really give major props to the developers of the DU ROM which I ran for a solid 2 weeks, just prior to upgrading to 5.0 They have actually made KK a bearable OS on this device with which I could get 2 full work days out of the XT926M - battery-wise - with moderate use. Still, the MAXX battery is a beast, and less than 2 days should not be acceptable. Under JB that was the case. If LP doesn't deliver soon, I am definitely going back to JB. And right around next March, my contract for this device is up anyway.
Click to expand...
Click to collapse
I was looking for the official firmware and found an unofficial cm build. I don't know who the developer is, if it's working, something's broken, etc.
Just wanted to let everyone know. If the developer stumbles upon this and don't want it to be posted here, just let me know and I will remove it.
Download: check thread
This is a build from @vache . given the date, I'd assume this is a build that doesn't have nfc and the wonky display.
dictionary said:
This is a build from @vache . given the date, I'd assume this is a build that doesn't have nfc and the wonky display.
Click to expand...
Click to collapse
As I said I have no clue.
Probably best to remove the link as he is collaborating now with someone else and I think they would prefer peoples first experience with something they have built to be slightly more positive.
Sent from my XT1562 using Tapatalk
ephumuris said:
Probably best to remove the link as he is collaborating now with someone else and I think they would prefer peoples first experience with something they have built to be slightly more positive.
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Yeah, that would be an unstable and broken early test build (not intended for public consumption). We'll have something more usable ready for you all to try soon.
Sneak Preview
For the impatient, here is a more usable preview build:
http://www.mediafire.com/download/hc19wc76a7y8374/cm-12.1-20150916-UNOFFICIAL-lux.zip
There's still a lot of work to be done, but at least the core functionality should work in this build (booting, WiFi, NFC, camera, GPS, audio, etc.). I'm not looking for bug reports at this point. Don't be surprised if you find something that doesn't work. One known issue is that AudioFX is broken right now.
But if you like living on the edge and want to try something new, you can flash it if you like. Use my TWRP build (originally mentioned in my kernel thread) to flash this ROM. The TWRP currently on vache's thread will have issues, so you must use mine.
squid2 said:
For the impatient, here is a more usable preview build:
http://www.mediafire.com/download/hc19wc76a7y8374/cm-12.1-20150916-UNOFFICIAL-lux.zip
There's still a lot of work to be done, but at least the core functionality should work in this build (booting, WiFi, NFC, camera, GPS, audio, etc.). I'm not looking for bug reports at this point. Don't be surprised if you find something that doesn't work. One known issue is that AudioFX is broken right now.
But if you like living on the edge and want to try something new, you can flash it if you like. Use my TWRP build (originally mentioned in my kernel thread) to flash this ROM. The TWRP currently on vache's thread will have issues, so you must use mine.
Click to expand...
Click to collapse
Super Excited (doing a nandroid right now but i am going to check it out)
belkre said:
Super Excited (doing a nandroid right now but i am going to check it out)
Click to expand...
Click to collapse
It works well enough. Loving the LED settings. No it's not multicolored, before people ask, but you can set different lengths and durations. Battery didn't seem as good, and felt a little more choppy at times, but this is why I'm assuming they didn't release lol. Not complaining. Just super excited to see some development.
dictionary said:
It works well enough. Loving the LED settings. No it's not multicolored, before people ask, but you can set different lengths and durations. Battery didn't seem as good, and felt a little more choppy at times, but this is why I'm assuming they didn't release lol. Not complaining. Just super excited to see some development.
Click to expand...
Click to collapse
yea i am finding it totally usable but i can see lots of *****ing if this was a more official release
squid2 said:
For the impatient, here is a more usable preview build:
http://www.mediafire.com/download/hc19wc76a7y8374/cm-12.1-20150916-UNOFFICIAL-lux.zip
There's still a lot of work to be done, but at least the core functionality should work in this build (booting, WiFi, NFC, camera, GPS, audio, etc.). I'm not looking for bug reports at this point. Don't be surprised if you find something that doesn't work. One known issue is that AudioFX is broken right now.
But if you like living on the edge and want to try something new, you can flash it if you like. Use my TWRP build (originally mentioned in my kernel thread) to flash this ROM. The TWRP currently on vache's thread will have issues, so you must use mine.
Click to expand...
Click to collapse
Thanks for your work @ squid2.
I know it's an earlier version, but I will spend a feedback, do not know if it's the same with you.
Tested the ROM on my device, everything seemed to work fine, except the SIM. He was not recognized, tried flashing another modem, but did not work well.
In today posted in another post version, the SIM worked, but not WIFI.
Hi guys,
I made a PAC build for lux available here : http://moto.shreps.fr/?dir=Moto X Play (lux)/rom/pac
Based on the latest work with @squid2 and @vache
If some of you want to try and report back, would be great !
I think I will open the dedicated thread tomorrow or this weekend
bononi said:
Thanks for your work @ squid2.
I know it's an earlier version, but I will spend a feedback, do not know if it's the same with you.
Tested the ROM on my device, everything seemed to work fine, except the SIM. He was not recognized, tried flashing another modem, but did not work well.
In today posted in another post version, the SIM worked, but not WIFI.
Click to expand...
Click to collapse
I'm in Canada, and my Sim works fine. It takes a very long time to pick it up though.
@squid2 @vache @Shreps
Is there any way you can enable dual sim in these ROMs straight out the gate? I don't have a second Sim to test at the moment, but that would be awesome.
dictionary said:
I'm in Canada, and my Sim works fine. It takes a very long time to pick it up though.
@squid2 @vache @Shreps
Is there any way you can enable dual sim in these ROMs straight out the gate? I don't have a second Sim to test at the moment, but that would be awesome.
Click to expand...
Click to collapse
The Canadian model is single sim only I believe.
squid2 said:
The Canadian model is single sim only I believe.
Click to expand...
Click to collapse
Technically true. If you look inside the sim slot, you'll see the pins are there for dual sim. On the ejector tray, the second sim slot is covered by a dummy piece of plastic. There are also reports of people flashing a dual sim ROM and it working.
@vache I'm testing the SOKP right now WiFi works but camera and layers doesn't ,on RR WiFi doesn't
Edit:the device is flying zero lags overheating issues
What does layers mean? And the last line zero lags is good. But do you mean there are overheating issues? Or no overheating issues?
Sent from my XT1562 using Tapatalk
ephumuris said:
What does layers mean? And the last line zero lags is good. But do you mean there are overheating issues? Or no overheating issues?
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
Layers is an alternate theme engine.
Ahh thanks for that been out of the CM scene for a while.
Sent from my XT1562 using Tapatalk
ephumuris said:
Ahh thanks for that been out of the CM scene for a while.
Sent from my XT1562 using Tapatalk
Click to expand...
Click to collapse
It's actually a stock Android theme engine. If I remember correctly, it was introduced by Sony into aosp, and it's baked into factory ROMs like on the n9. The layers app just makes things easier to manage it all, because the average Joe has no knowledge that it even exists.
XMoDuLeSx said:
@vache I'm testing the SOKP right now WiFi works but camera and layers doesn't ,on RR WiFi doesn't
Edit:the device is flying zero lags overheating issues
Click to expand...
Click to collapse
Where do you've found the sokp build?