Database Info

KitKat for the Charge?!?!?!?

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.

KitKat?

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

Andorid Lollipop!!

Hi guys! I already asked this question but....why a smartphone as S PLUS received Android lollipop and Kernel 3.4.105 and the S advance is stop to KitKat and kernel 3.0.101? Thi our smartphone has absolutely no developer able to do it?:crying::crying:

giovibob said:
Hi guys! I already asked this question but....why a smartphone as S PLUS received Android lollipop and Kernel 3.4.105 and the S advance is stop to KitKat and kernel 3.0.101? Thi our smartphone has absolutely no developer able to do it?:crying::crying:
Click to expand...
Click to collapse
bcz S plus has qualcomm snapdragon Soc (easily available sources ) and our crap has novathor which has no source ...so don't expect any new update for our device...even present source builds are not bug free for i9070 .
this thing made clear many times by many devs
so don't create new thread for this thye of Qs...we have Q&A thread plus search option.

This is amazing news. Although, I'm not sure whether this is going to affect our device or not. It's not that the devs are unable to pull this off, I think it's more of a matter of the practical aspect since most people follow the natural course and update their dated hardware. Nonetheless we can just hope that our device is not forgotten.

Team Canjica not give more support for janice, so no lollipop for S Advance
Janice sources are horrible, could compile lollipop, but with many bugs

uncreator said:
This is amazing news. Although, I'm not sure whether this is going to affect our device or not. It's not that the devs are unable to pull this off, I think it's more of a matter of the practical aspect since most people follow the natural course and update their dated hardware. Nonetheless we can just hope that our device is not forgotten.
Click to expand...
Click to collapse
It's sad to say but it's already forgotten

I say too that our janice is forgotten...But remember this: never say never, although i think that janice can't run lollipop.We already experience lags on jb, cm.If we had 1gb ram,then was other story...but still hard to build lollipop without sources.
We won't get more performance using lollipop, we will get a slow device.
Why you really wants lollipop? Just for the look, isn't it? You can make a theme like that and that's it.
I know that is not allowed,but if anyone need that novathor sources which chinese guy posted on xda few months ago and know how to adapt them for lollipop (if is possible) tell me...i still have them in my pc and I'll never delete them.
What is the rom which is trully fast and smooth ? The answer is GIINGERBREAD. Yeah, it is outdated, but consume less ram, and that we need, free ram.

Force said:
What is the rom which is trully fast and smooth ? The answer is GIINGERBREAD. Yeah, it is outdated, but consume less ram, and that we need, free ram.
Click to expand...
Click to collapse
Have you tried Vanir? I use it for like 6 months now and don't even think about anythink else. Fast, no fancy colorful stuff jumping at me from every menu, good battery life, what more can you want?
In a day or two I'll also put here the kernel I use with Vanir along with my new governor, if you're interested.

mkaluza said:
Have you tried Vanir? I use it for like 6 months now and don't even think about anythink else. Fast, no fancy colorful stuff jumping at me from every menu, good battery life, what more can you want?
In a day or two I'll also put here the kernel I use with Vanir along with my new governor, if you're interested.
Click to expand...
Click to collapse
I'm using first or second version of Vanir and I'm satisfied and i never updated. I installed many apps and became little slow. Gingerbread still better for ram management i think.
Why i use vanir ? Because i see that on this rom the camcorder isn't so darker like other roms, at least for me (after changing exposure). Although i record videos rarely, when i want to do it i don't want darker videos...
I'm interested in your kernel, and i think not just me
PS: i use just vanir and sami os

Should we have hopes for a custom rom for the Mate 7

Its still kind of early to loose hope I guess, but since everything is opensource with this phone (downloadable on Huawei's site), should we be hoping for a custom rom for the Mate 7? I'm scared it won't get popular enough for a developer to make one, even though it is an amazing phone.

Maan
I was hoping for some love from cynogen.

Extornia said:
Its still kind of early to loose hope I guess, but since everything is opensource with this phone (downloadable on Huawei's site), should we be hoping for a custom rom for the Mate 7? I'm scared it won't get popular enough for a developer to make one, even though it is an amazing phone.
Click to expand...
Click to collapse
I don't want to sound pessimistic, but the phone is already more than 3 month old. I think they're will be no international custom rom for this phone. But i will be happier if I'm proven wrong.

Custom ROM's would be nice, but I'm afraid we'd lose the fingerprint scanning ability and what not.
You'll never know though! Personally, I can't wait to get mine in a few days (shipping from HK is a *****), I miss xposed framework.

When you open the boot loader and it rootest, then does the here.
http://forum.xda-developers.com/mate-7/themes-apps/xposed-modules-t2957769

I hope for CM.

Extornia said:
Its still kind of early to loose hope I guess, but since everything is opensource with this phone (downloadable on Huawei's site), should we be hoping for a custom rom for the Mate 7? I'm scared it won't get popular enough for a developer to make one, even though it is an amazing phone.
Click to expand...
Click to collapse
What for ?
What's problem with EMUI 3.0 ?"?!??!

We just need lollipop base, EMUI is just fine. I would like to see some camera improvement, 4k support, better gpu thermal throtling... No need for custom rom if you ask me...

Mr.Nice.ba said:
We just need lollipop base, EMUI is just fine. I would like to see some camera improvement, 4k support, better gpu thermal throtling... No need for custom rom if you ask me...
Click to expand...
Click to collapse
no we don't need lolipop sht.. it is worse.. 4.4.2 is best..

Probably a better outlook for the HAM7 than the HAM2.
Why the negativity? 3 months, really?
Newer android doesn't necessarily mean better, if it ain't broke?
The HAM2 was stuck on 4.2.x since its release. It got one update (4.4.2 on their Chinese portal). The HAM7 might get an update too, but there are 3 model versions out there so far (one that works in NA only), and they aren't interchangeable (different radios), so hopefully XDA has a Chinese translator for when they do update. Don't see why they wouldn't post at least an official update to 5.x.x somewhere down the line.
Are they going to do to HAM7 what they did to the HAM2? 'Here's some free phones and source, develop'. :cyclops:
Rumour mill: There's supposed to be a proper North American model released sometime.

Official Nougat 7.0 soak test starts in Brazil

Motorola has finally started the Nougat soak test in Brazil. Let's hope it won't take too long for them to release the final version. However, the screenshots say it's Android 7.0 and not 7.1. Also, to make us believe it's really happening, we can have a look at the comments posted below the post. Few comments say they have received it and it's working smooth as of now.
Source: http://www.androidpit.com.br/teste-nougat-moto-x-force-e-style-comecarao-em-breve
Update 1: Motorola send out soak test invitations to US users
Update 2: Android Headlines reports Moto X Style Is Receiving Android 7.0 Nougat In India
Update 3: Moto X Style and X Pure Nougat update spotted on GFXBench (Yes, again. The last time it was spotted on 7.1 was in last week of December.)
Update 4: A user on reddit who is located near Chicago states he received the Nougat update.

Soak test is going on in India also.

This is a good news !!!!!!

soak test is only available for limited users and if anyone who will break their rules will be out of the soak test permanently so don't expect that someone might just end up sharing the files !! all we need to do is just wait for that moment when it gets as stable as a daily driver and we all are good to go
its most likely 7.0 but i hope we get a 7.1.1 or 7.1.2

Why not get it now?
Google "AICP clark"
I've been running it since Dec 2015 on Republic Wireless with no problems.

I got bored waiting for official nougat and went to AICP 7.1
It's pretty good, can't see myself going back to stock tbh

Put me down for Dirty Unicorns. Last things for me were camera functioning well (which it seems to be if using OpenCamera) and torch working well (which it seems to be improved).

Sagar_1401 said:
its most likely 7.0 but i hope we get a 7.1.1 or 7.1.2
Click to expand...
Click to collapse
no chance for that

iks8 said:
no chance for that
Click to expand...
Click to collapse
Doesn't matter so much. We're interested in the N blobs, i think they are the same between 7.0 and 7.1. this will at least mean better custom ROMS

josdehaes said:
Doesn't matter so much. We're interested in the N blobs, i think they are the same between 7.0 and 7.1. this will at least mean better custom ROMS
Click to expand...
Click to collapse
Even on this forum not everyone is interested with custom roms. I used to mod my phones a lot but thoose were crapy low end devices and custom roms were really adding some performance but with this phone I don't see a reason to install custom rom. Even on my old moto e I went back to stock after trying few roms, moto software is really well made imo, so it's sad that their updates are way slower than they used to be and that they relase already obsolete software ;\.
btw from my expierience there is always something broken in custom roms, and if it's not broken now it will be in next relase xd

iks8 said:
Even on this forum not everyone is interested with custom roms. I used to mod my phones a lot but thoose were crapy low end devices and custom roms were really adding some performance but with this phone I don't see a reason to install custom rom. Even on my old moto e I went back to stock after trying few roms, moto software is really well made imo, so it's sad that their updates are way slower than they used to be and that they relase already obsolete software ;\.
btw from my expierience there is always something broken in custom roms, and if it's not broken now it will be in next relase xd
Click to expand...
Click to collapse
I'm with you here. I have no desire leave the stock ROM for any reason other than updates. It's been bug-free and smooth sailing for me with Motorola's software ever since 2015, no doubt because they stick to AOSP.
The only way I'd be interested in a custom ROM is if the developers were on a very long release cycle where they spent months ironing out every tiny bug before tinkering with new things, similar to how OEMs approach stock ROMs. That seems rare these days, though I don't follow things too closely anymore. "Man this ROM is amazing... except, oh yeah, Bluetooth breaks and requires a reboot... oh, and calls drop a lot... and, uh, call volume randomly goes to max/silent for no reason... oh yeah, and MMS just doesn't show up sometimes, and the camera crashes every 3rd open requiring another reboot" seems to be the way of the world, and I don't have patience for it. Putting up with random bugs can be worth it if it frees you from TouchWiz or Sense or LG UI, but when the stock ROM is already AOSP and fast/fluid, I don't see the point.

http://www.androidauthority.com/moto-x-style-pure-edition-nougat-758023/

I have to agree that stock rooted ROMs are my way of going now. Of course that also means I won't buy from makes like Samsung who overburden their ROMs with too much frill. Besides, with manufactures like one plus, the is really no reason to revert.

good news

ptn107 said:
Google "AICP clark"
I've been running it since Dec 2015 on Republic Wireless with no problems.
Click to expand...
Click to collapse
I'm on RW too. Are you using a certain version that's working good? I just don't wanna messed up my service, but would love to try 7.1.1.
Sent from my SM-P600 using XDA-Developers Legacy app

Official Android 7.0 Nougat out for Moto X Style (Pure) in India and Brazil
AsquareX said:
Motorola has finally started the Nougat soak test in Brazil. Let's hope it won't take too long for them to release the final version. However, the screenshots say it's Android 7.0 and not 7.1. Also, to make us believe it's really happening, we can have a look at the comments posted below the post. Few comments say they have received it and it's working smooth as of now.
Saw the same on another website this morning. I wonder how long after the soak test that it will be released in the US?
Click to expand...
Click to collapse

About time. I see that the Android O developer preview is out and we don't even have 7.0 yet. Grrr!

strafer69 said:
About time.
Click to expand...
Click to collapse
not really, it's way too late imo. Start of soak test doesn't mean a lot, I guess in some regions you will have to wait like more than month since now, I guess everyone willl get it in may as it was said before, that's way too long for not so old flagship phone... We should have 7.0 already and 7.1 in may but it's not going to happen ;\ shame on you moto

iks8 said:
not really, it's way too late imo. Start of soak test doesn't mean a lot, I guess in some regions you will have to wait like more than month since now, I guess everyone willl get it in may as it was said before, that's way too long for not so old flagship phone... We should have 7.0 already and 7.1 in may but it's not going to happen ;\ shame on you moto
Click to expand...
Click to collapse
Not Moto's fault. Blame it all on Lenovo, as the Moto's work force is pretty much non-existent.

Rmsalt said:
AsquareX said:
Saw the same on another website this morning. I wonder how long after the soak test that it will be released in the US?
Click to expand...
Click to collapse
Honestly, a while... It usually goes Brazil, India, Europe, then US and UK (sometimes US/UK flip-flop). To be honest, Lenovo doesn't see the US as a major market, these phones are not carrier subsidized so their market penetration is minimal at best. US is always the last to get Moto (Lenovo) updates in the last 12-18 months. Not likely to see that change anytime soon. Each region will have it's own beta if history repeats, we are at minimum 2-3 months out in the US.
Click to expand...
Click to collapse