Droid Turbo 2 Marshmallow Source Kernels Now Available - Droid Turbo 2 General

Not a whole lot of news, but for whatever it is worth.
http://www.androidheadlines.com/2016/01/droid-turbo-2-marshmallow-source-kernels-now-available.html

That's interesting, does this has happened before? As long as I'm aware, they never release, sources for droids, but I'm not 100% sure, are they gonna let unlock the bootloader on droid turbo 2??

Jaocagomez said:
That's interesting, does this has happened before? As long as I'm aware, they never release, sources for droids, but I'm not 100% sure, are they gonna let unlock the bootloader on droid turbo 2??
Click to expand...
Click to collapse
If you read the article, it explains that it is to give app developers a head start. And yes with Android being open source, the nearly always release the kernel source to keep things in line with AOSP.. Usually the Kernel Source comes within days to a few weeks after the firmware pushes to phones.

Related

[Q] Gingerbread question

Just curious: As an EVO user, I've had Gingerbread on my phone for about two months now, but there isn't a 2.3 Epic ROM to be found. Is there really no work being done for 2.3 for the Epic yet? Forgive me if there's something I don't understand, I'm obviously not a dev and don't fully understand what goes into building something like that.
Thanks!
Search next time there are at least a dozen pointless threads asking this exact same question and getting the same answer. NO, the source code literally dropped less than a week ago and no other phone is even vaguely similar to ours with source to build drivers from.
Where is the TROLL SPRAY?
Sent from my SPH-D700 using XDA App
Oh I'm sorry, you guys are so right. I'm such a douche bag. Obviously if I use the search function and look for Gingerbread and 2.3 I get TONS of results that... oh, wait... I get nothing. Interesting as that's THE SAME THING I GOT LAST NIGHT WHEN I SEARCHED!
Still, I do appreciate your answer 063... glad the source finally dropped. Yet another reason why I would never personally buy a Samsung device, but for my wife it's fine.
WrlsFanatic said:
Still, I do appreciate your answer 063... glad the source finally dropped. Yet another reason why I would never personally buy a Samsung device, but for my wife it's fine.
Click to expand...
Click to collapse
Not to sound troll-y, but source for our froyo update dropped a couple days before the update itself. HTC doesn't do that very often.
Short answer: We're working on it. Expect to see some early testing builds here in the next week or two.
The source for 2.2.1 was released for epic, not 2.3/2.4
Sent from my SPH-D700 using XDA App
nullghost said:
Not to sound troll-y, but source for our froyo update dropped a couple days before the update itself. HTC doesn't do that very often.
Short answer: We're working on it. Expect to see some early testing builds here in the next week or two.
Click to expand...
Click to collapse
Oh, interesting. I assumed he meant that the source for 2.1 only now FINALLY dropped... but it was 2.2, huh? Interesting. Well, I would commend them if their update weren't bricking phones. Maybe they SHOULD wait until they are 100% certain that the release is solid before dropping the source on the world.

Kernel sources

So HTC didn't release kernel sources for this device yet right?... I'm planning to build kernels for this device as soon as they are available.
They are going to be blind builds until I manage to get money for the device.
I think they have up to 90 days to release the Kernel sources. Glad to have you aboard.
Finally someone to build a serious tegra3 kernel, welcome to the HTC side
I hope you can fix the idle battery consumption like you did with the Nexus.
Would also be cool if the One X didn't chew through my battery as it does currently, that's my only complaint so far
Just donated to get the party started, now lets push HTC for those sources
heard high praises for what you did to the nexus so i can't wait!
I'm running Franco's kernel on my galaxy nexus and also was running it on my galaxy note. He has the best kernels out there. Great balance of performance with very good battery life.
great i use franco kernel for the gnex good to know to come to tbe one x that's excellent
Sent from my HTC One X using xda premium
wohoo your kernel back in the gingerbread days was awesome on my nexus s
franciscofranco said:
So HTC didn't release kernel sources for this device yet right?... I'm planning to build kernels for this device as soon as they are available.
They are going to be blind builds until I manage to get money for the device.
Click to expand...
Click to collapse
Well before we start cooking kernels' the first thingvto do eould be to get s-off on the device. Franco i know you would be thinking the same. Have you unlocked your device's bootloader yet. And if revolutionary or some other teams make s-off possible, would it be possible to indo the unlocking procedure we did via htcdev.com ?
Sent from my HTC One X
tids2k said:
...would it be possible to indo the unlocking procedure we did via htcdev.com ?...
Click to expand...
Click to collapse
i asume you mean undo, and the answer is yes and no, if revolutionary manages to crack the hboot and provide us with a solution to get a real unlocked bootloader with s-off then you can also reflash a locked bootloader and get s-on back
but htc keeps record of devices unlocked through htcdev.com, so even if send your device to service, they know that the phone was unlocked once. The better question is whether HTC will charge you for repair or not, i have not found a clear statement yet on how your warranty is void after unlocking the official way.
Some say it is void for software issues, but then i think, it's easy to say from HTC point of view to just use software as source for nearly every Hardware fault!
As long as i have no clear statement from HTC (which i'm gonna email them about, right now ) i will wait with the unlock. but not having root, coming from a nexus device kind of sucks
This could be usefull? http://developer.nvidia.com/linux-tegra
Now tegra 3 and 2 support Linux kernel 3.1
Don't forget to go nag HTC on Twitter and Facebook about the kernel sources. The more that nag, the more chance they will comply.
franciscofranco said:
So HTC didn't release kernel sources for this device yet right?... I'm planning to build kernels for this device as soon as they are available.
They are going to be blind builds until I manage to get money for the device.
Click to expand...
Click to collapse
hey welcome to the OneX club!
looking forward to your high quality kernels
Oh yay. I just gave my dad my galaxy nexus and swapped with the HTC one x. I was using your kernal. Your kernal made my phone snappy
Sent from my HTC One X using xda premium
flakz0r said:
Finally someone to build a serious tegra3 kernel, welcome to the HTC side
I hope you can fix the idle battery consumption like you did with the Nexus.
Would also be cool if the One X didn't chew through my battery as it does currently, that's my only complaint so far
Just donated to get the party started, now lets push HTC for those sources
Click to expand...
Click to collapse
Is yours that bad? Mine goes through about 1% over 8 hours idle!!
franciscofranco said:
So HTC didn't release kernel sources for this device yet right?... I'm planning to build kernels for this device as soon as they are available.
They are going to be blind builds until I manage to get money for the device.
Click to expand...
Click to collapse
HTC has been known for not releasing source code in a timely manner.
You will be waiting at least a month before source shows up...
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Why No AOSP ROM?

So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Jess813 said:
So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Click to expand...
Click to collapse
In my experience unless you are using a nexus device aosp roms are never 100% at least not until the phone is at the year/year and a half mark. Now if your talking about camera not working and stuff like that yeah its going to take time especially since only a hand full of devs are working on it in there spare time. On the plus side they will probably have most of the kinks hammered out before L releases and most of the changes and fixes will translate over.
Well what about the HTC M8, the S5, the Note series, the Xperia Z, all those have AOSP roms and most of those have been out less than a year. Again not complaining
Jess813 said:
Well what about the HTC M8, the S5, the Note series, the Xperia Z, all those have AOSP roms and most of those have been out less than a year. Again not complaining
Click to expand...
Click to collapse
We do have aosp roms.....
ThePagel said:
We do have aosp roms.....
Click to expand...
Click to collapse
Correct, but not fully working. Is it because LG is not releasing certain things ?or there's not enough developers with this phone?
Jess813 said:
Correct, but not fully working. Is it because LG is not releasing certain things ?or there's not enough developers with this phone?
Click to expand...
Click to collapse
I would think its because we don't have enough developers committing to the same rom ie we need official cyanogenmod github so the changes eventually end up in one spot that everyone even non g3 users feel comfortable sending a commit to.
ThePagel said:
I would think its because we don't have enough developers committing to the same rom ie we need official cyanogenmod github so the changes eventually end up in one spot that everyone even non g3 users feel comfortable sending a commit to.
Click to expand...
Click to collapse
Dang...this is like LGs biggest hit ever as a device. You would think that Cyanogen would acquire one.
Jess813 said:
Dang...this is like LGs biggest hit ever as a device. You would think that Cyanogen would acquire one.
Click to expand...
Click to collapse
Somebody will send a request to have a rom reviewed to be added to the official git. It will just take the one person and a little time. If you feel strongly about it you could ask one of the devs working on it to send it to the cm team for review but I bet one of them will after the camera is fixed. whoever does will have there name next to 99% of the commits in the official github so that person will have bragging rights.
Tom Marshall was working on it then intervigilium, who yesterday had some activity on his github and finally invisiblek as well, all with cyanogenmod. Not to mention the actual phone 2 of them are using belongs to...think it was Roman from AOKP. You also have the guys here working on it when they have time. My bet would be a few more weeks and it will be up and running properly.
Good to know, I love this phone however but I'm sure with an AOSP ROM it'll fly!!!
Jess813 said:
So I've been rooting since rooting existed on Android, but one thing that I don't understand is how it works, sort of. I know that google has to release the source, and the device has to have an unlocked boot loader. Then what? I know there's 4 variants of the G3 and the T-Mobile is the only one with an unlocked bootloader.
I'm not throwing a brick against the or anything but would like more info on why things like this happen, and I mean why we are not able to get CM on the G3 fully working. Just curious, and yes I did search.
Click to expand...
Click to collapse
coding a new rom takes time and devs work on their own dime as so few here actually donate anything to them. Phones and their hardware are becoming way more sophisticated each year and porting any flavor of rom is no longer something easily done. If people are impatient perhaps they need to open their wallets and give the devs some inspiration.............

Nougat update for Motorola Droid Turbo 2 receives Bluetooth SIG certification

Looks like some good news may really be coming (Nougat)...
http://www.gsmarena.com/nougat_upda...es_bluetooth_sig_certification-news-22523.php
Looks like the Motorola Droid Turbo 2 will soon get Nougat as the Android 7.0 update for the handset (model number XT1585) has been certified by the Bluetooth Special Interest Group (SIG).
Now we will finally get root! Hehe
my2cents said:
Now we will finally get root! Hehe
Click to expand...
Click to collapse
wh
I've come to terms with the likelihood that this phone will never see root. And if it does, there will be little to no development for custom roms or other goodies. I am to the point where I think the glory days of rooting and having cool software hacks that actually improve the phones are behind us. Now my opinion could be, because my last three phones have been locked down on Verizon, and my Razr M once unlocked never had great builds. The builds it did have had issues due to bootloader changes and my lack of willingness to downgrade the bootloader once other changes were made. As I recall. Still excited to see Nougat coming at least.
romma1 said:
I've come to terms with the likelihood that this phone will never see root. And if it does, there will be little to no development for custom roms or other goodies. I am to the point where I think the glory days of rooting and having cool software hacks that actually improve the phones are behind us. Now my opinion could be, because my last three phones have been locked down on Verizon, and my Razr M once unlocked never had great builds. The builds it did have had issues due to bootloader changes and my lack of willingness to downgrade the bootloader once other changes were made. As I recall. Still excited to see Nougat coming at least.
Click to expand...
Click to collapse
Well since Verizon just got rid of 2 year contracts for everyone so no subsidized phones I won't buy another carrier phone. My wife has the pixel xl and loves it. I will be going Google not so much for the unlocked bootloader more for immediate updates. Screw carrier and manufacturer taking forever to update or decide not to update (Droid Maxx 5.1 I'm looking at you).
bigv5150 said:
Well since Verizon just got rid of 2 year contracts for everyone so no subsidized phones I won't buy another carrier phone. My wife has the pixel xl and loves it. I will be going Google not so much for the unlocked bootloader more for immediate updates. Screw carrier and manufacturer taking forever to update or decide not to update (Droid Maxx 5.1 I'm looking at you).
Click to expand...
Click to collapse
Yup. Every single phone I have had has been in the Droid Line (HTC Included). No more!! Not after this phone runs dry.
Is this Bogus?
This has to be bogus, right? Why don't I see this thread on XDA?
http://www.android-nougat.tech/2016/11/motorola-droid-turbo-2-7713.html
my2cents said:
This has to be bogus, right? Why don't I see this thread on XDA?
http://www.android-nougat.tech/2016/11/motorola-droid-turbo-2-7713.html
Click to expand...
Click to collapse
yeah that's a fake website, you can easily tell because none of the other links works (Home, contact us, etc..)
https://twitter.com/Moto_GER/status/826802898512314368
xQrzy said:
https://twitter.com/Moto_GER/status/826802898512314368
Click to expand...
Click to collapse
For F*** sake.
Delayed until May?
Seriously?
Since Lenovo bought moto it's just going downhill.
Top range phone for £500 and need to wait 6 months for update. This is a joke.
TeddyBeers said:
For F*** sake.
Delayed until May?
Seriously?
Since Lenovo bought moto it's just going downhill.
Top range phone for £500 and need to wait 6 months for update. This is a joke.
Click to expand...
Click to collapse
Do You think we will get 7.1.1? LOL, so it is 9 months. This is my first and last Moto.
Xetmes said:
Do You think we will get 7.1.1? LOL, so it is 9 months. This is my first and last Moto.
Click to expand...
Click to collapse
Yeah.
Q4 2018
romma1 said:
Looks like some good news may really be coming (Nougat)...
http://www.gsmarena.com/nougat_upda...es_bluetooth_sig_certification-news-22523.php
Looks like the Motorola Droid Turbo 2 will soon get Nougat as the Android 7.0 update for the handset (model number XT1585) has been certified by the Bluetooth Special Interest Group (SIG).
Click to expand...
Click to collapse
How does the Bluetooth SIG certification affect my phone?
I use Bluetooth with my truck and some earbuds...... I don't see where I would see extra functionality.
Does not affect your phone. It's just a way how info about update leaks. Every phone/update needs to pass certification before is released.
Sent from my Moto X Force

For those of you using the stock ROM, what are your plans for migrating once we reach EOL?

As I'm sure we all know here, our beloved Pixel 3 XLs are officially getting dropped by Google in about three weeks. If history repeats itself, though, we will get the Android 12 release in October followed by one last OTA in December. My typical usage pattern with a phone is:
Get the phone and use the stock ROM until the phone reaches EOL.
Once EOL is reached, move to LineageOS.
I know that this is a pattern that some others more or less follow as well, but I was wondering about what variations there are to the pattern. Does anyone here use another ROM? As much as I like LineageOS, I would be more interested in using a ROM that is basically identical to stock Android. I have read about compiling AOSP from source so as to maintain my own ROM that does just that, but from what I understand, that does not work very well for unsupported devices. Does anyone have any suggestions?
Off the top of the head... EOL only means no more official updates or support, ie security fix's...
Your fone working on a custom rom will still work, since you'd think it was the custom rom updated...
If they do stop the fone calling, there's plenty other apks for 'near field' communication
Free wifi calling hint hint..
Pachacouti said:
Off the top of the head... EOL only means no more official updates or support, ie security fix's...
Click to expand...
Click to collapse
Oh yes, I know that functionality-wise the phone will continue working as before. What I want to know is, what are people considering in regards to custom ROMs?
David B. said:
Oh yes, I know that functionality-wise the phone will continue working as before. What I want to know is, what are people considering in regards to custom ROMs?
Click to expand...
Click to collapse
Kl, well, me, I'm wondering this too just now, because I'm stuck with a system-as-root fone thats a pain, and now there's too many different too choose from, and if they're of the best quality, they now have to cover at least 4 different styles of booting alone, I'd watch those for the ones updating quickest
Pachacouti said:
Kl, well, me, I'm wondering this too just now, because I'm stuck with a system-as-root fone thats a pain, and now there's too many different too choose from, and if they're of the best quality, they now have to cover at least 4 different styles of booting alone, I'd watch those for the ones updating quickest
Click to expand...
Click to collapse
Well, LineageOS certainly does that, but at the same time, it also takes them about 6 months to move to a new major release of Android. I was hoping that someone would know of a release that does it just as well, but is a little more flexible with migrating. I haven't found any myself.
I've yet to convince myself which version is for my fone lol
David B. said:
As I'm sure we all know here, our beloved Pixel 3 XLs are officially getting dropped by Google in about three weeks. If history repeats itself, though, we will get the Android 12 release in October followed by one last OTA in December. My typical usage pattern with a phone is:
Get the phone and use the stock ROM until the phone reaches EOL.
Once EOL is reached, move to LineageOS.
I know that this is a pattern that some others more or less follow as well, but I was wondering about what variations there are to the pattern. Does anyone here use another ROM? As much as I like LineageOS, I would be more interested in using a ROM that is basically identical to stock Android. I have read about compiling AOSP from source so as to maintain my own ROM that does just that, but from what I understand, that does not work very well for unsupported devices. Does anyone have any suggestions?
Click to expand...
Click to collapse
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Not at all, they all sound excellent, however, my fone cant write to the actuall system, can mount, but no joy yet doing anything else, and no overlay works so far, the only custom os I could install was a chrooted nethunter, which was pretty lame and useless being my system as root is a pain... so I'm looking..
dcarvil said:
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Click to expand...
Click to collapse
My plan, at least for now, is to ride on stock until the last update is pushed, and then once LOS gets updated to 12, I will migrate. The only problem with this, though, is that it would leave me without security updates from the end of December until either March or April, and I am not sure how I feel about that.
My experience might help...Last year I was using a Motorola 5Plus with Pixel Experience Rom and loved it. My phone was fast, stable and highly compatible to the "Pixel Experience". I had a hardware issue and decided I liked the PE so much, I went ahead and got a Pixel 3xl...I've never had such a seamless transition...was just faster with better hardware but almost no thought changing for different mechanisms of actions...
I'm hoping someone picks up PE and ports it to the 3XL and I'll use that....otherwise, any alternative suggestions for closest to "stock" Pixel would be appreciated...
S
spschneer said:
I liked the PE so much, I went ahead and got a Pixel 3xl...I've never had such a seamless transition...was just faster with better hardware but almost no thought changing for different mechanisms of actions...
Click to expand...
Click to collapse
Yeah I have seen PixelExperience and would really like to use it over LOS if the 3 XL gets support. As far as I know, the 2 XL did not receive support until it's EOL, so there's hope. Is the feature parity as spot-on as is claimed?
David B. said:
Yeah I have seen PixelExperience and would really like to use it over LOS if the 3 XL gets support. As far as I know, the 2 XL did not receive support until it's EOL, so there's hope. Is the feature parity as spot-on as is claimed?
Click to expand...
Click to collapse
For the features and functions I use, it was almost totally seamless...it was less than a typical release level amount of change (e.g.: 10->11 was more than I experienced PE -> P-3xl)
YMMV however...based on what features/functions you use most heavily.
S
spschneer said:
For the features and functions I use, it was almost totally seamless...it was less than a typical release level amount of change (e.g.: 10->11 was more than I experienced PE -> P-3xl)
YMMV however...based on what features/functions you use most heavily.
S
Click to expand...
Click to collapse
Great! I guess it's time for me to start researching building my own image.
"David B said he's gonna research building PE for 3xl....
GREAT...be sure to use the AOSP version ... there are a couple of flavors of PE but IMHO the AOSP version is the closest to the stock 3xl ...
If you don't mind guiding me a little over the rough patches, I'd be willing to help test your creation once you're out of alpha<G>...(my 3xl is my daily driver)... specifically, I'm used to having TWRP available for the maintenance/management of the ROM and if I understand it properly, TWRP isn't used / available for the 3xl ROM's...
Thanks
S.
spschneer said:
"David B said he's gonna research building PE for 3xl....
GREAT...be sure to use the AOSP version ... there are a couple of flavors of PE but IMHO the AOSP version is the closest to the stock 3xl ...
If you don't mind guiding me a little over the rough patches, I'd be willing to help test your creation once you're out of alpha<G>...(my 3xl is my daily driver)... specifically, I'm used to having TWRP available for the maintenance/management of the ROM and if I understand it properly, TWRP isn't used / available for the 3xl ROM's...
Thanks
S.
Click to expand...
Click to collapse
For now, I would like to hold off on it. I don't really see a point in putting effort in to building PE for the 3 XL when we're about two weeks away from the next major Android release, at which point, PE will need reworked by the dev team. If the 3 XL is not picked up by someone else in the modding community at release time, and I've seen some people that think it will be, then I will start researching it.
David B. said:
For now, I would like to hold off on it. I don't really see a point in putting effort in to building PE for the 3 XL when we're about two weeks away from the next major Android release, at which point, PE will need reworked by the dev team. If the 3 XL is not picked up by someone else in the modding community at release time, and I've seen some people that think it will be, then I will start researching it.
Click to expand...
Click to collapse
Sounds like a plan...will keep an eye on development threads for it once it goes out of support.
Even though the last update will be in Dec I'll probably keep using the 3XL until the 7 comes out (or 6a maybe). I just had the battery replaced a couple months ago, and there is nothing wrong with the phone. I usually use devices until EOL hits, and then upgrade when the next OS/phone comes out, so whatever device I'm using at any given time is on the current OS release (IE: 3XL on Android 12 until Android 13 drops, and then upgrade phone to get Android 13).
I would like to use that method, but I think it's too expensive, so I try to settle for "my phone's basically dead."
dcarvil said:
I've already moved to LineageOS, simply to get the monthly security updates. I have not seen any functional loss on LineageOS. If you don't feel you need security updates, just stay on the stock ROM, especially if you think you need any Android 12 features. IMO, new Android features simply add more bloat than I want or need. Your opinion may differ.
Click to expand...
Click to collapse
Does the unlimited Google Photos upload work on LineageOS?
quera said:
Does the unlimited Google Photos upload work on LineageOS?
Click to expand...
Click to collapse
I don't know how to tell if it is still in effect. I see photos counted against my storage allotment, but don't know if that is just for my previous phones, or if it includes the Pixel photos.
My guess is you would have to use the Google Camera and Photo apps to keep unlimited upload, if it can be kept with LineageOS.

Categories

Resources