Related
So the blogger over at 'Android and me' has speculated that older devices will not receive the 2.0 update.
This guy has done this before, he also said 1.6 was too big for the G1 OS partition and of course we all know this was wrong.
I want to know what the dev's think, once all the bull**** is striped and the 2.0 source code is at stock for the G1. How large will it be? And how much room will be left over for downloading apps?
Thank you for your time.
And how much room will be left over for downloading apps?
Click to expand...
Click to collapse
Shouldnt be too much of an issue if you are running apsd.
They already have 2.0 running on G1's, i havent used it myself, but it is running, so I presume it fits.
vixsandlee said:
Shouldnt be too much of an issue if you are running apsd.
They already have 2.0 running on G1's, i havent used it myself, but it is running, so I presume it fits.
Click to expand...
Click to collapse
I know, I know... I had 2.0 running for a time and it was great. I used apsd and linux-swap. What i want to know is conclusive evidence that the guy over at Android and me is full of ****.
He always speculates that the G1 will not get updates and is usually wrong. What i am wondering is how large the stock 2.0 for the G1 will be. The Dev's may have an idea.
the guy at androidand me is EXACTLY CORRECT.
What you are failing to see is the guys over there are writing for non-rooted phones. They have said in previous posts that this was a moot point for rooted phones and admitted they were already running the upgraded OS.
Both htc and t-mobile have officially stated that the dream is still getting the 2.0 upgrade. As somebody else said, the point is moot for rooted users because we can always port the newer code to our aging phones, but there's a hitch: the moment htc stops supporting the device, we're on our own.
I've yet to see somebody build the android code for the dream without help from the pre-configurations found in the aosp for dream, and now that the sapphire is officially the adp2, i smell the demise of the dream near.
The biggest enabler of the custom firmware movement was the fact that the dream was also the adp1, so there was a lot of interest on making building the platform easy. We just piggybacked on that.
Take one look at has been accomplished with the hero so far. I still remember the whole "let's make htc give us our hero kernel code" because all thought it would open the door for custom hero firmware. they couldnt have been more wrong. without htc's support, all they got was a fancy linux kernel that they had no idea what to do with, and also discovered how little the kernel had to do with android.
There's now a grand total of two aosp roms for the hero, and they're both so broken that they're really just novelties.
What I'm going at is that once htc drops the dream, people are going to realize knowing linux will only take you so far and you'll have to know android if you plan to get at least a botched android build working on the device.
So eventually, even being rooted will not be enough to ensure continued ability to run the best and latest, unless, ofcourse, we get real devs (again, I'm not claiming to be one myself) in here.
Oh, and.... a bigger android install wont mean less app space... learn to android...
The android system belongs in the 70 mb system partition and, on a factory, official build, doesnt spill into the /data partition where you install your apps. And if you do have root and a2sd, what do you care how big the system is, you can always make your ext bigger, so it should't be a worry for a rooted user.
Really... learn 2 android...
s15274n said:
the guy at androidand me is EXACTLY CORRECT.
What you are failing to see is the guys over there are writing for non-rooted phones. They have said in previous posts that this was a moot point for rooted phones and admitted they were already running the upgraded OS.
Click to expand...
Click to collapse
You know that the guy at Android and Me has been wrong on this exact issue before right?
When 1.6 was still in the pipes he had a pie chart and everything explaining why it was physically impossible for 1.6 to fit on a G1 (non-rooted). Then 1.6 was pushed to everyone....
http://androidandme.com/2009/08/news/t-mobile-g1-owners-dont-expect-any-future-android-updates/
^^
He was using his best guess at the time after speaking with t-mo, htc and the lead developer from google. He also assumed we would get a VERSION of OS 1.6. Everything he stated then seemed logical... don't fault the guy for not predicting the future man.
What it all boils down to is this;
Whether a device will get an update or not has virtually NOTHING to do with the device specifications and/or storage space. There is LOTS of space available on the device, despite what some chicken little's speculate based on a moronic look at the "free space in /system" (which has VERY little meaning). What determines whether a device will get a particular update or not has everything to do with what the MANUFACTURER WANTS TO DO.
In other words, this is *all* in the hands of HTC. Even tmobile has hardly anything to do with this since tmobile themselves don't have the source for the proprietary binaries (which happens to be the stumbling block) -- although tmobile can say "not for ours" if they want, HTC can still build the binaries and/or system image for DREAM/ADP1. Fully in their hands and nobody else's.
Which leads to a couple of options for updates;
1) modify the current state of AOSP to remain compatible with existing HTC binaries,
2) reverse engineer HTC proprietary binaries so they're no longer needed.
I vote for #2. The replicant project seems to have this aim, but I don't know if they are still alive or if they died along with the open android alliance... http://trac.osuosl.org/trac/replicant/wiki
if gingerbread is the future of android devices, it suppose to support hardware capabilities that may not be on the nexus that has been around for a while.
i really wanted to buy a nexus, but it seems that when android 3.0 is out - it should be followed by high end devices by HTC and others.
i really don't know what to do here...
gingerbread is said to launch mid november - not a long time to hold off.
but hey, what do think? wait or buy nexus now?
That is Exactly what I am doing! The desire HD looks wonderful, but i think There will be a VERY nice phone coming on T mobile with new gingerbread already there around Christmas....Just my guess
It seems T mobile and Google have some sort of special deal when it comes to android, like getting stock android phones.....and there MUST be a stock gingerbread phone coming soon!
oronm said:
if gingerbread is the future of android devices, it suppose to support hardware capabilities that may not be on the nexus that has been around for a while.
i really wanted to buy a nexus, but it seems that when android 3.0 is out - it should be followed by high end devices by HTC and others.
i really don't know what to do here...
gingerbread is said to launch mid november - not a long time to hold off.
but hey, what do think? wait or buy nexus now?
Click to expand...
Click to collapse
First, Gingerbread will run fine on a N1. Second, no matter when you buy a phone in a couple months another one will come out that is even better. The N1 has an awesome modding scene though.
First, Gingerbread will run fine on a N1.
Click to expand...
Click to collapse
nobody know that for sure...the minimal requirements may suit the N1 but it may lack the ability to perform certain tasks. we've seen it happen with other phones.
Second, no matter when you buy a phone in a couple months another one will come out that is even better
Click to expand...
Click to collapse
true for most cases. to me nexus is different from others by design. that phone feels right. i really couldn't care less about all these samsungs or motorolas that are out there. and other htc devices seem too big like the desire HD that was mentioned.
basicly, the world need a NEXUS TWO!
So you think Google will develop an OS using their development phone, but not all features of the OS will work on the phone they developed it on? I highly doubt that. Google debunked the minimum requirements roomer for Gingerbread, that was nothing but a site trying to get traffic. Do a little thinking on the subject.
If I were getting a new phone soon though, I would wait till the next gen ones come out. I do love my Nexus though!
the nexus one was a success in regard of telling the world "this is what android can do right now". others did follow and it is biting the market share making other mobile OS look like code accidents.
none the less, why shouldn't gingerbread allow "facetime like" video service for capable devices? the technology for that is in the wild. that is only one example. i am sure there are more features just like that.
at this point, maybe it would be smarter to wait.
oronm said:
the nexus one was a success in regard of telling the world "this is what android can do right now". others did follow and it is biting the market share making other mobile OS look like code accidents.
none the less, why shouldn't gingerbread allow "facetime like" video service for capable devices? the technology for that is in the wild. that is only one example. i am sure there are more features just like that.
at this point, maybe it would be smarter to wait.
Click to expand...
Click to collapse
Whether or not Gingerbread includes a facetime like option is irrelevant to how it will run on the N1. Obviously any phone without a front-facing camera will not be able to do something like facetime. Gingerbread itself will run just fine on the N1. Without going into any technical reasons, just think of this. Of all the Android phones out there right now, the top ones are all in the general vicinity of the N1 in performance. If Gingerbread wouldn't run on the N1, then you cut out these phones too which means only as-yet-unreleased phones would run Gingerbread. So on what basis are you questioning it?
You should probably wait though since you don't seem sure about the N1. The only guarantee you can have is that in a few months from now an even better phone will be released. And then a few months from that once again, and repeat... Dual core snapdragons will start finding their way into phones at some point soon. If you're not rushed then just wait and see what comes out.
Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
This is the development forum. You want the q n a forum.
Sent from my Nexus One
mnv710 said:
Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
Click to expand...
Click to collapse
*sigh*
There is a general section, you know...
mnv710 said:
Gingerbread will most likely be brought to the nexus one but what about 3.0 and beyond? Do you think they will make a new device? Possibly the n2? What about tablets? Will they start a new android line just for tablets. The android phpne market is very spread out right now, phones like the Motorola charm will probobly never see froyo but phones like the Droid x and vibrant have processors that will not become outdated for several years to come. Are company's updating hardware too quickly?
Click to expand...
Click to collapse
The HTC magic, the 2nd ever android phone, got official Froyo. If a phone isn't getting it, its not because it's underpowered (with the exception of the G1).
B3astofthe3ast said:
The HTC magic, the 2nd ever android phone, got official Froyo. If a phone isn't getting it, its not because it's underpowered (with the exception of the G1).
Click to expand...
Click to collapse
Huh? The magic is a G1 less the keyboard. Processor is the same. And I think a rooted G1 can have 2.2.
Sent from my Nexus One using XDA App
HTCinToronto said:
Huh? The magic is a G1 less the keyboard. Processor is the same. And I think a rooted G1 can have 2.2.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The G1 is memory starved. A rooted G1 can have froyo with the proper SPL.
We will get every future Android update.
Gingerbread, Honeycomb, IceCream, Jellybean, K..., L..., Mousse, Pie, Q..., ...
I don't think there needs to be a tablet developer platform designated. Screen resolution differences are something that should be simple enough d'or developers to figure out.
The entire point of a developer platform device is to develop the core OS updates on it, so I fully expect at least another year of official updates for the N1. Especially because we haven't actually seen any faster processor released into the market yet.
The secondary point of a designated developer platform would be to support a core of standard hardware under Android. Smarter OEMs should understand that if they want to have less work to port android to their devices, and to get updates on their devices more quickly, they should try to use hardware components either common to ADP or that have Linux support.
Sure, OEMs can deviate, but anything they include that isn't either compatible with ADP hardware, or already supported in Linux will have to be supported by the company making that handset. So it is up to the consumers to say if they want devices more like the Desire, or more like the X10. Laf!
The Nexus One is the official Google Development phone. Until that changes, we shouldn't have to worry about getting the latest versions first
It is one of the advantages to being a N1 owner.
xPatriicK said:
We will get every future Android update.
Gingerbread, Honeycomb, IceCream, Jellybean, K..., L..., Mousse, Pie, Q..., ...
Click to expand...
Click to collapse
Deserts are my N1's favorite meal!
Android mean Google, then there is no point to buy any phone even if it's amazing, i am with Google devices till they close the company N1 TO N100 i am with Google i just want they put some color in this coming build i feel the stock ROM is black and white
Android 4.0 Source is out! Any chance to get this in the LG Thrill 4G I would definitely be keeping it then.
Sent from my LG-P925 using xda premium
I was wondering the same thing. if this is possible I might not even update it to GB cause it wouldnt make sense. Hopefully its possible.
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
quarlow said:
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
thank your for you input on this matter. Can you please tell me which Galaxy S II is better i777 or the i727 because I am thinking of returning my LG Thrill 4G for the Skyrocket?
The skyrocket has lte actual 4g that if the only difference add far as performance
Sent from my LG-P925 using xda premium
kleeman7 said:
The skyrocket has lte actual 4g that if the only difference add far as performance
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
That's the only difference in data speed. That's also the only area the i727 is better. In EVERY other way the i777 is better.
They have the same screen resolution, but because the 727 screen is bigger, so the pixel density is lower, most people won't notice, but its worth mentioning.
The processor in the 727 is a qualcomm chip oc'd to 1.5 GHz, vs a Exynos chip at 1.2 GHz. People say the qualcomm chip is inferior, and choppy. Most people won't notice it, but it is there. The exynos can be oc'd higher than the qualcomm chip. The qualcomm chip is the reason it won't get i777 or i9100 ROM ports. With the i777 and i9100 running the same chip you can port any i9100 ROM really easy.
I don't know specifics on GPU, but its widely accepted the i777 has better graphics and 3D processing.
The 777 is thinner and lighter.
They both have disabled nfc on board. Att to possibly unlock at a later time, maybe at ICS rollout.
If you have LTE coverage you need to think about the choice, if you don't have LTE, there is absolutely no reason to get the 727. I talked a little about other differences in your other thread.
Sent from my Galaxy S II (i777)
quarlow said:
Its as possible as the source for GB turning into a GB update. That is to say, no its not possible.
LG needs to make the update and bake in the drivers. It took them a few days shy of a year for GB, maybe they can shave that down to 9 months for ICS. So, as Google announces 4.1, start looking for 4.0.
The Galaxy Nexus is not going to provide any ports to the Thrill, or any other device. Its the only device using that CPU/GPU combo. Its the only device to date with its CPU at all (processor in Thrill is different model number 4460 vs 4430, it may as well be entirely different) If ICS is your goal, the Galaxy Nexus is the fastest and easiest way. Otherwise you play the waiting game for the OEM to put out the update, then wait some more for the carrier to bloatify it, then wait some more for the small base of devs to de-bloatify it.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
Did you check the TI site and read the 4460 documentation? The processors are almost identical. The 4460 is just a little more capable. Its still in the OMAP4 family with the exact same architecture. We'll have the LG gingerbread drivers shortly as well as the galaxy nexus ICS drivers which will get us started there. Kernel shouldn't be too big of an issue as again, same architecture on CPU, same exact gpu. Yea its gonna take a lot of time to get everything working but we don't need LG to do it. GB was more of a shot in the dark for this phone than ICS will be. Zero omap4 devices released with GB but it still got ported to a couple Motorola devices. ICS released for two devices, both omap4.
Sent from my LG-P925 using Tapatalk
I said this about GB too. I hope I'm wrong for all of your sake's. When people were saying GB was around the corner (in September), and I said December, people said I was being too cynical. Well ... here we are, December is right around the corner, and the GB port is not flashable in CWM, nor is it complete. I over-cynicized a little, but not much.
I think it's all great on paper, just like building a AOSP GB build for the phone looked simple, did that ever actually get off the ground?
As I look in the past, I use that to forecast the future. My guess is that there is no where near a functional daily use ROM for the Thrill until a ICS build comes from LG (I would guess no sooner than July). If the the Nexus S and Captivate running the exact same hardware (CPU/GPU plus lots of others) both made from the same company, cannot share ROMs with lots of dev support, I just find it hard to believe that a phone with a similar chip, packaged with other chips (WiFi, BT, USB, Power, comination unknown) by another OEM is not going to provide useful drivers for the small dev community here. Again, I would love to be wrong, but ...
To be honest I think the Thrill is more Thrilling (rim-shot) because it's an underdog, and it feels like a start-up, ground-floor opportunity to build and jury rig everything and frankenstein it together. I think it would be fun, and I would have loved to have been involved had I stayed. But, I moved on, as many others have. I can't wait for months for something like this when I will only have that phone for a year. I don't hang on to old tech, I sold my Captivate and it paid for my Galaxy S II, talk about the circle of life.
The Thrill is definately an underrated phone, but it's also not the highest end phone. As I said before, as it stands it's definately the best AT&T phone for less than $100, it's the king of the mid-range offerings. Unless you can get the i777 for $50 or less, like many places have advertised for Black Friday.
I wish everyone the best of luck with the Thrill, but the reality train is leaving the station, and I feel my welcome may just be wearing thin here.
It seems that LG doesnt really care about the consumer because they release a phone and update the firmware when its not even new anymore and its funny because it seems like the Thrill will be getting GB and everyone else will be getting ICS. =(
Demonface said:
It seems that LG doesnt really care about the consumer because they release a phone and update the firmware when its not even new anymore and its funny because it seems like the Thrill will be getting GB and everyone else will be getting ICS. =(
Click to expand...
Click to collapse
it'll be about 3-8 months before other devices will recieve ics. samsung has the same problem. they still haven't updated the charge, fascinate, captivate and infuse.
tampaboy1984 said:
Android 4.0 Source is out! Any chance to get this in the LG Thrill 4G I would definitely be keeping it then.
Sent from my LG-P925 using xda premium
Click to expand...
Click to collapse
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
AeRo0 said:
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
i got so excited when i saw his videos of it on the o3d i almost jumped and threw my laptop!!! hahaha
Trekfan422991 said:
i got so excited when i saw his videos of it on the o3d i almost jumped and threw my laptop!!! hahaha
Click to expand...
Click to collapse
This is after all the reason why I got this phone cuz of the chipset and the fact that ICS is designed for it
Sent from my LG-P920 using XDA App
AeRo0 said:
Yes it will Ricardo from the cyanogenmod team in charge of lg devices posted a video on YouTube showing ICS running on the O3D. He posted on his google + that it took him a couple of hours to get the touchscreen working but it shows you that work has begun and we might see ICS sooner than you think.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
Thats very good news , Hopefully it gets released soon. Instead of using GB I would go straight to ICS when its released. Does anyone have the link to the video because I cant seem to find it.
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
quarlow said:
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
seriously i know your trying to help us keep a grip on our excitement.. but its starting to get annoying seeing your comments pop up here all the time after you switched weeks ago.. and they are all how the thrill has potential but im so happy with my choice... like we cant even get our hopes up because your too afraid of our dreams getting dashed to pieces... we should all follow your example. i know thats not what you mean but it feels that way...
like many others i choose this phone based off the hardware specs... so i will be sticking it out for a few months at least if not for a few years.
we know the decision you made to switch and that you have support for the thrill and knew it to be a good device.. there is no rule about posting in forums for phones you dont have.. but please... please ease back a bit on clarifying all the realities for us...
there is nothing wrong in wishing.. we had no development for ages, it feels like, and now we have some things to look forward too, thats all!
so give us our hopes please... *tears up* its all we have!
quarlow said:
Those types of ports that are half functional are popping up every where for tons of phones.
They will not support some basic phone functions for months. There is no way 3D will work until LG builds the drivers, and they won't release them until they release the full ICS update. Things like WiFi, Bluetooth, GPS, data, etc will all (or mostly) be missing for quite a while. Making ICS run and making a daily driver with ICS are two very different things.
I watched that video, there is already a comporable port running on the i9100. Proof that both using similar but different omap4 processors means nothing. The processor is the most simple basic part of the functionality, its everything else that's going to be hard.
Try to keep some perspective, and realistic hopes.
Sent from my Galaxy S II (i777)
Click to expand...
Click to collapse
He's a legit cm dev. Its NOT a half functional port. Its the beginning of an ICS source build a day after source was released. It took him a few hours to get touchscreen working. Its NOT one of the fake SDK ports that have been floating around. They've already said it will be ATLEAST 2 months before we should even start expecting any updates on cm9. Hows your build of ics going? Your claims on timeline, etc, MUST be based on your own firsthand progress, correct? You are actually contributing something to the community with all your development knowledge, correct?
You claim to be saving us from false hopes. But the way I take that is that you are assuming we as a community are to ignorant and naive to realize the time/process of getting a new OS on a new device. NOBODY here has said we expect this to be a rapid process. We know it takes time.
Hop on your faux white horse and ride back over to your fanboy forum. You've contributed absolutely nothing to this forum and I assume the same is probably true there. But seeing how as you actually have that phone you have a reason to lurk over there.
Sent from my LG-P925 using Tapatalk
Wait wait wait...
You mean AT&T doesn't give super fast firmware updates to their phones?!
Here's what I will say about this phone so far...
I like it. It's treated me better than any Samsung phone I've had. It does everything I need it to.
I can't really remember ever saying "I wish this phone could..." that I wouldn't say about any other phone.
I hear people talk about how fast this phone is and that phone is and how fast the GSII compared to the Thrill. But how much faster is faster? The web browser pops up a second faster? A file is downloaded 10 seconds faster? I don't really think a lot of that is that big of a deal. It almost reminds me of the Crackberry forums when they were talking about not going to Android because the email isn't push (which isn't true) and so you got your emails a whole 30 seconds later. I mean, c'mon, how many of us are in a position where if we don't get that email 30 seconds faster our entire corporation loses billions?
I think it'd be cool to get 2.3 or above right now because there are a couple of games I'd like to play that are on 2.3 or above. But considering I have 25 games already installed and over 1/2 of those I ahven't touched, it's okay.
I've had a few Samsung phones and everyone of them I had had a lot of issues. I went through 8 Captivates. Now I did have to return one Thrill and exchange it but every Samsung phone I've had, I've had to get replaced at least twice. I keep saying I want a Note but then think about how bad I've had it with Samsung phones.
Phone technology is crazy. The thrill came, then the GSII, then the GSII skyrocket and the HTC Vivid, then there are three new Galaxy devices coming to AT&T in the next 2-3 months, and whatever awesome quad core devices, and then pretty soon we'll have the hologram phones in which you tell the phone to contact someone and they pop out of the phone like in Star Wars.
Honestly, I think I need a couple more pairs of shoes more than I need a newer phone.
CallMeAria said:
He's a legit cm dev. Its NOT a half functional port. Its the beginning of an ICS source build a day after source was released. It took him a few hours to get touchscreen working. Its NOT one of the fake SDK ports that have been floating around. They've already said it will be ATLEAST 2 months before we should even start expecting any updates on cm9. Hows your build of ics going? Your claims on timeline, etc, MUST be based on your own firsthand progress, correct? You are actually contributing something to the community with all your development knowledge, correct?
You claim to be saving us from false hopes. But the way I take that is that you are assuming we as a community are to ignorant and naive to realize the time/process of getting a new OS on a new device. NOBODY here has said we expect this to be a rapid process. We know it takes time.
Hop on your faux white horse and ride back over to your fanboy forum. You've contributed absolutely nothing to this forum and I assume the same is probably true there. But seeing how as you actually have that phone you have a reason to lurk over there.
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
I won't get drawn into a pissing contest regarding dev support of the Optimus 3D vs the Galaxy S II (i9100).
But, I will respond.
I'm sorry I over estimated and called that port half functional, you are right: its not a half functional port.
The build status of CM9 for the phone that half the Cyanogen team was given months ago is unknown to me. I made no claims on timelines, just forecasts based on the past and opinion.
There is indeed a very similar ICS ROM built for the i9100 (and by extension the i777) from the source that just dropped, but I cannot comment as to whether or not it was put together by a "legit cm dev."
I am not a developer, no. I am just an observer, an observer that tends to be realistic with expectations, and generally accurate.
I don't accuse the community here of being ignorant or naive. I can see that some people here do have realistic expectations.
I too was once an Aria, Captivate and Thrill fanboy. Today I am a GS II fanboy. I picked my team, as you have too. I don't think there is anyone on xda that isn't passionate about their phone.
I will not dignify further condescending comments from you with a response. This is the last time you will see me on the Thrill forums. Do not take my future lack of response as an admission of your perceived superiority. And do not take my comments to imply I believe I am better than you. I know you built a ROM, and were the first to share how to port O3D ROMs. Just because I never used your contributions I will not be so arrogant to say they don't exist.
And with that, I will be on my way. Again, best of luck to every one with a Thrill.
Sent from my Galaxy S II (i777)
Just checked out the optimus 3d thread about ICS and it seems that Ricardo is getting a lot of progress done and it seems like its getting done quickly. So hopefully it gets released before Christmas
. BTW I know that's still a long wait still but it would all be worth it.
This is a general question from me trying to understand things better. Before the D4 I had a samsung stratosphere. Completely unlocked bootloader with full capability to flash custom ROM/kernel images. Despite this no AOSP ROMs could be build due to lack of driver sources. It was the same situation with the Epic 4G. The Droid 4 on the other hand had the bootloader locked with the key thrown away. Despite this CM9 and other AOSP ROMs are up and nearly fully operational, even with ICS booting on GB kernels. What makes this possible on D4 but not the stratosphere?
My guess is that driver software is available for the D4. This is due to the fact that Motorola uses parts from other OEMs (TI CPU ect) with public drivers. Samsung on the other hand uses their own proprietary parts and keeps the drivers private. Is this an accurate assessment?
It would seem then that the most important thing to making development possible for a phone (apart from popularity) is driver availability, NOT whether or not the bootloader is unlocked. Is that true? Regardless, I will probably steer clear of samsung for future android purchases. HTC still seems best and motorola acceptable. If only HTC still made high end QWERTYs.
Usually devs just pull the proprietary files off the phone and use it in the compile/builds. This has been going on for Motorola phones since the original Droid.
Sounds like no one invested in seeing what proprietary files were needed from the Stratosphere or Epic 4G.
Public AOSP code mixed with copying in private/proprietary files is how most ROMs are made. The higher the user base of a device, the higher the development activity and the larger number of devs finding out what all is needed to be pulled from the stock device to compile a fully functional ROM.
Since some proprietary files are used....you need them for the same version OS you are building, ie...use stock phones ICS drivers for ICS builds or stock phones GB drivers for Gingerbread builds. You can sometimes hack drivers to work but with lots of limitations. Also drivers depend on the kernel so a matching kernel is needed......requiring the device to have the needed kernel level or an unlocked bootloader to be able to replace the stock kernel.
We wont be seeing an unlocked bootloader? Ever?
Sent from my DROID4 using xda premium
twizzles said:
We wont be seeing an unlocked bootloader? Ever?
Sent from my DROID4 using xda premium
Click to expand...
Click to collapse
All signs point to no...we will never see an unlocked bootloader on the current Motorola devices.
With Google owning Motorola Mobility and already replacing MM CEO with one of their own from Google........it's possible future devices may be unlock capable.
Current devices....no, not ever.
The first locked bootloader on a Motorola droid was the Droid 2. It still has not been unlocked, hacked, cracked, etc... How long has it been out?
Motorola released a special Razr Dev model with an unlockable bootloader...retail price, zero warranty, nothing you do on it would transfer over to the normal Razr or Razr Maxx.......so why would anyone buy it? Great PR for them to say "see..we released an unlockable device and no one bought it".
Well that just sucks. Thank you for the info
Sent from my DROID4 using xda premium
I have to say, I don't mind not having an unlocked bootloader. I had the Galaxy Nexus and ran multiple different setups on it. The radio still sucked though. With the Droid 4, I don't feel the need to do a lot of hacking. The phone is well built, radio is awesome, it just works.
GermanGuy said:
I have to say, I don't mind not having an unlocked bootloader. I had the Galaxy Nexus and ran multiple different setups on it. The radio still sucked though. With the Droid 4, I don't feel the need to do a lot of hacking. The phone is well built, radio is awesome, it just works.
Click to expand...
Click to collapse
I kind of agree with you for the most, but still I prefer the option and think we should have it as an option. It's one way to keep a device relevant throughout your 2 year contract. For example....the Droid 3. I have one, bought online day of release. In less than a years time it has become a non-supported, forgotten device from Motorola. The locked bootloader prevents devs from picking apart the Droid 4 leaked ICS kernel and compiling one with Droid 3 specs (less RAM, etc..) and bringing a fully functional ICS build to the Droid 3. Unlocked...that would be possible.
JKingDev said:
This is a general question from me trying to understand things better. Before the D4 I had a samsung stratosphere. Completely unlocked bootloader with full capability to flash custom ROM/kernel images. Despite this no AOSP ROMs could be build due to lack of driver sources. It was the same situation with the Epic 4G. The Droid 4 on the other hand had the bootloader locked with the key thrown away. Despite this CM9 and other AOSP ROMs are up and nearly fully operational, even with ICS booting on GB kernels. What makes this possible on D4 but not the stratosphere?
Click to expand...
Click to collapse
I, as well, went from the Stratosphere to the Droid 4. I love my Stratosphere and still have it, but the lack of development on it is just down right aggravating. That is why I took it upon myself to learn how to compile a kernel to provide everyone with root and recovery for it. Otherwise we wouldn't have the ROMs we have for it now. If it wasn't for the Droid Charge using the exact same dev board as the Strat, I doubt we'd even have that much. I had to take the Charge build of CWM and packed it in a Strat kernel and tweaked the scripts, thank god at least that worked.
JKingDev said:
My guess is that driver software is available for the D4. This is due to the fact that Motorola uses parts from other OEMs (TI CPU ect) with public drivers. Samsung on the other hand uses their own proprietary parts and keeps the drivers private. Is this an accurate assessment?
Click to expand...
Click to collapse
I am not sure about the Motorola drivers, but you are right about Samsung. The first time I compiled the kernel, I was missing 11 modules. I couldn't figure out what I did to keep them from being compiled... and then I learned the sneakiness Samsung uses to get around releasing the source, they compile the kernels for the file system and radios and dynamically link them in the init.rc script. Apparently a lot of them do this, actually.
JKingDev said:
It would seem then that the most important thing to making development possible for a phone (apart from popularity) is driver availability, NOT whether or not the bootloader is unlocked. Is that true?
Click to expand...
Click to collapse
Actually both are true to some extent, with a locked bootloader you are stuck with OEM signed boot images and can't recompile the kernel to your own needs, or compiling one with ro.secure = 0 so you get root access in adb (which is how I rooted the Stratosphere). Then you need the drivers to talk to the hardware too. Without them, you'd need to reverse engineer them or use the currently complied ones (also, like we did with the Strat). Finally, you have to have the source for the RIL (Radio Interface Layer) in Android so Android as an OS knows how to talk to the drivers to make calls, send messages, use data, etc. THIS is where we are currently hung up from using AOSP on the Stratosphere. I know work is being done on the RIL for the Charge and since its the same board, we might get lucky and be able to reuse most (if not all) of the same code and bring new life to it. But, I wasn't getting my hopes up and decided to get a D4 anyway.
JKingDev said:
Regardless, I will probably steer clear of samsung for future android purchases. HTC still seems best and motorola acceptable. If only HTC still made high end QWERTYs.
Click to expand...
Click to collapse
You and me both. I was in love with the keyboard on my HTC Touch Pro 2 and wish they'd release something like that running Android on Verizon with newer hardware. Closest they had to a QWERTY on VZ was the Merge, and they botched that up from the gate. I also have the Rezound and am trying to design a way to attach a sliding keyboard to the back battery cover to give me something closer to what i have been wanting in a phone.
I think us QWERTY loves on VZ are at the mercy of Motorola and Motorola alone with the original Droid line of sliders.
KnightCrusader said:
I, as well, went from the Stratosphere to the Droid 4. I love my Stratosphere and still have it, but the lack of development on it is just down right aggravating. That is why I took it upon myself to learn how to compile a kernel to provide everyone with root and recovery for it. Otherwise we wouldn't have the ROMs we have for it now. If it wasn't for the Droid Charge using the exact same dev board as the Strat, I doubt we'd even have that much. I had to take the Charge build of CWM and packed it in a Strat kernel and tweaked the scripts, thank god at least that worked.
I am not sure about the Motorola drivers, but you are right about Samsung. The first time I compiled the kernel, I was missing 11 modules. I couldn't figure out what I did to keep them from being compiled... and then I learned the sneakiness Samsung uses to get around releasing the source, they compile the kernels for the file system and radios and dynamically link them in the init.rc script. Apparently a lot of them do this, actually.
Actually both are true to some extent, with a locked bootloader you are stuck with OEM signed boot images and can't recompile the kernel to your own needs, or compiling one with ro.secure = 0 so you get root access in adb (which is how I rooted the Stratosphere). Then you need the drivers to talk to the hardware too. Without them, you'd need to reverse engineer them or use the currently complied ones (also, like we did with the Strat). Finally, you have to have the source for the RIL (Radio Interface Layer) in Android so Android as an OS knows how to talk to the drivers to make calls, send messages, use data, etc. THIS is where we are currently hung up from using AOSP on the Stratosphere. I know work is being done on the RIL for the Charge and since its the same board, we might get lucky and be able to reuse most (if not all) of the same code and bring new life to it. But, I wasn't getting my hopes up and decided to get a D4 anyway.
You and me both. I was in love with the keyboard on my HTC Touch Pro 2 and wish they'd release something like that running Android on Verizon with newer hardware. Closest they had to a QWERTY on VZ was the Merge, and they botched that up from the gate. I also have the Rezound and am trying to design a way to attach a sliding keyboard to the back battery cover to give me something closer to what i have been wanting in a phone.
I think us QWERTY loves on VZ are at the mercy of Motorola and Motorola alone with the original Droid line of sliders.
Click to expand...
Click to collapse
Thanks for the replies. It is interesting stuff. And KC I definitely appreciated your work on the Strat. So I guess it really was a question of popularity being the problem for stratosphere. I definitely know it wasnt the most popular device but it also seemed like reverse engineering drivers for the Samsung devices was so much harder. The charge was relatively popular and years later the RIL has still not been successfully reverse engineered. All the moto devices get cracked so quickly. Is it only because they are more popular, or are there other reasons that make them easier to hack? Thats what leads me to think maybe it's samsung's use of proprietary hardware that makes things more difficult. Does that have something to do with it?