Related
We got HC 3.1 on the dell streak 7 and the lcd density was too low making everything small. I bumped it from 120 to 190 and rebooted and was shocked.. it was a different UI! It was like GB. Setting the LCD Density to 160 and below gave us the HC UI 170 and higher gave us the GB UI
http://www.youtube.com/watch?v=T8m_Qawds9o
Get out our forum
Nice find...but really get out our forum
Interesting
Sent from my Xoom using XDA Premium App
bwcorvus said:
Get out our forum
Nice find...but really get out our forum
Click to expand...
Click to collapse
hahah you know you love me BW Besides you wouldnt want me telling everyone here you're also an op on the Asus transformer channel would you? hahaha
graffixnyc said:
hahah you know you love me BW Besides you wouldnt want me telling everyone here you're also an op on the Asus transformer channel would you? hahaha
Click to expand...
Click to collapse
What can i say, i get around...
trader!!!!
Old news. This circulated round when the SDK was previewable.
What file did you modify to manually change the LCD density?
This has been known since the SDK... yet Engadget is reporting on it again
Please forgive my pure "noob" question...
Please forgive the pure "noob" question I am about to ask but does this mean that Honeycomb is not really a Full OS and just a build up on Gingerbread?
Im not sure if that even makes any sence but the one reason I bought my Xoom (which I am excitedly waiting to have shipped to me) is because of the Honeycomb Tablet "Optimized" OS otherwise I would have just bought a Galaxy Tab...
Just-in-time said:
trader!!!!
Click to expand...
Click to collapse
Is that supposed to be "traitor"?
I have yet to find a way to change the density on the xoom, anyone try this yet?
yiannisthegreek said:
Please forgive the pure "noob" question I am about to ask but does this mean that Honeycomb is not really a Full OS and just a build up on Gingerbread?
Im not sure if that even makes any sence but the one reason I bought my Xoom (which I am excitedly waiting to have shipped to me) is because of the Honeycomb Tablet "Optimized" OS otherwise I would have just bought a Galaxy Tab...
Click to expand...
Click to collapse
Gingerbread and honeycomb are separate. Both are self contained OS. For all practical purposes...In the world there is a kernel that is the operating system and everything else (drivers, interface and on is just additions to be able to use the kernel). Just as windows 7 is not vista or XP, they are separate. Combined all together is the OS.
So what makes GB so special and better than HC?
One was designed for small devices GB and HC is still young but made for tablets. they both serve a different purpose. Each one is seperate and one is not better then the other. For instance HC on my Htc evo would not make any sence. Screen is to darn small. you could do it...but it would not(IMO) be practical. I want my tablet not to make phone calls, yet gingerbread could run a tablet, very well I might add. Ice cream from google is the merging of tablet and phone android OSs to a single codebase. There is still much work needed on HC that will be done and the Gingerbread, froyo, Eclair have been around longer so the have a bigger user base.
antiochasylum said:
I have yet to find a way to change the density on the xoom, anyone try this yet?
Click to expand...
Click to collapse
Check the market for an app called "LCD density changer"
Sent from my HTC HD2
..fully working Honeycomb? What do you think? Is a fully working Honecomb ROM possible? May it be 3.0 or 3.1 with all those nice honeycomb-native-apps working?
fattymcdirty said:
..fully working Honeycomb? What do you think? Is a fully working Honecomb ROM possible? May it be 3.0 or 3.1 with all those nice honeycomb-native-apps working?
Click to expand...
Click to collapse
Ha? We have two out already and only zoom has it out really...for the new version. Everybody is working with the prerelease sdk. Those in the development section ARE honeycomb and it cannot yet be full driver ready till the release of source or until new release gets ported over. If you mean from Barnes and noble, I do not know. I am running leaked transformer version and it is smooth as it can be.
life64x said:
I am running leaked transformer version and it is smooth as it can be.
Click to expand...
Click to collapse
Which one is that? I thought that all those Honeycomb images out yet for the Nook aren't smooth at all and have compatibility issues with many apps. And The tablet versions from some apps (like GMail) aren't even working...
fattymcdirty said:
Which one is that? I thought that all those Honeycomb images out yet for the Nook aren't smooth at all and have compatibility issues with many apps. And The tablet versions from some apps (like GMail) aren't even working...
Click to expand...
Click to collapse
I forgot to mention it is on my transformer...not nook I was running leaked 3.1. I found that both of the nook honeycombs where semi solid with for me just to test honeycomb. I knew off the bat they are pre-production HC and I treated them as such. Cm 7 for nook is solid and been very content with it. The reason why a lot of apps have fc is the simple fact there was really no production sdk for development till recently. And how do you develop when you dont have the right environment. I want honeycomb bad...but if it is not there, it is not there...what I want is the new kor-el chip tablet...but I gotta wait till end of year for that. For now, honeycomb is just a toy on the nook and I would not really depend on it...that is my opinion, there are others whose it daily and more power to them. It will take a developer to port it for the nook most likely and that will be off in the near, medium or far future...I do not know.
I know we are all waiting for 3.1 but I was wondering if Icecream sandwich will also run on the current honeycomb tablet when it comes out. I have been searching quite a bit on the internet and cant really find an answer to this question. But I bet some people here will know the answer
"Know" the answer, no. Nobody except Google "knows" the answer to that question. HOWEVER, ICS is the unification of tablet and phone versions of Android, designed to run on both platforms, so it's extremely likely it WILL run perfectly fine on the A500.
Assuming Acer release it for us, which they'd better.
I DONT THINK SO,
so if u want that, just pray so bootloader being unlocked ... so dev can make ICS for iconia
interqd said:
I DONT THINK SO,
so if u want that, just pray so bootloader being unlocked ... so dev can make ICS for iconia
Click to expand...
Click to collapse
Why do you say this?
FloatingFatMan is most likely correct with his assessment.
Well, the real question (until unlocked bootloader) isn't so much "can it run" as "will Acer push it out to the A500". The A500 appears to be, at its core, very similar to what we could call a reference Honeycomb design, so unless Google goes out of their way to make things difficult, ICS should be an easy upgrade from HC. It'll come down most likely to device drivers - A500 using a different audio chip, and not certain of whether the mSD card slot is controlled directly from the Tegra2 or another controller chip (if the latter, another driver.)
I'll admit I'll feel a bit better about Acer's commitment to the Android environment if the A501 gets released quickly, and of course even more better when they push 3.1 out, and ecstatic if they'll just unlock the bootloader and get rid of the worry factor entirely.
blazingwolf said:
Why do you say this?
FloatingFatMan is most likely correct with his assessment.
Click to expand...
Click to collapse
its from my past with android device .. my htc desire,
till now official gingerbread not released for it, only the leaks and ports
1 gb ram, dual core 1ghz CPU wat else do u need to run Ice cream sandwitch.
Sent from my A500 using Tapatalk
interqd said:
its from my past with android device .. my htc desire,
till now official gingerbread not released for it, only the leaks and ports
Click to expand...
Click to collapse
so based just of my retired htc evo then it will def be coming my evo had 2.1 ota 2.2 and now an offical ota for 2.3
I'm confused. I have a rooted a500 running Honeycomb 3.2 and I don't think i have a locked bootloader. The rooting process was super simple and i have no problem doing nandroid backups or installing new ROMs.
Am I missing something? Did later/earlier models come with a locked bootloader?
Probably, yes, it's just a matter of time. This is possible in two cases:
1. Google - as they promised - will publish full ICS source code, so we could build it.
2. Google will provide source code to some similar Tegra2 tablet vendor, and we'll rip their binaries and put them on our A500s.
The possibility of at least one of the case happening is quite high.
Bootloader is irrelevant. Even though it's encrypted and has some checks (defeated by itsmagic), it's not locked down to the extent we can't run custom kernels. And the only point of bootloader is to load a proper (i.e. from the correct partition) chunk of code in the memory and run it.
That is, unless Acer will release newer tablet revision with updated firmware (which disallows EUU/nvflash-based downgrades) and locked bootloader. But that'll be different hardware. I know my UID (thus, SBK) and no software upgrades could possible change this, so my tablet is safe.
Im sure our device will support ICS
If not officially from Acer...it will be from our great developer here
trevoryour said:
I'm confused. I have a rooted a500 running Honeycomb 3.2 and I don't think i have a locked bootloader.
Click to expand...
Click to collapse
Technically, it's "locked", but the protection was relatively lax and were defeated by sc2k's itsmagic.
OTA 3.2 upgrade introduced new bootloader, which has stronger protection, but, luckily, we can downgrade back using EUU service software (which is, technically, just an SBK calculator and nvflash).
Google said they were about to publish the source code, "soon"... Let's wait
Okay, so we've already seen Ice Cream Sandwich running on the Nexus S, but that was decidedly... unofficial. We've just heard straight from Google's Gabe Cohen that the Nexus S will definitely be getting ICS. In fact, both he and Matias Duarte think most Gingerbread devices will see an upgrade, saying: "Currently in the process for releasing Ice Cream Sandwich for Nexus S. Theoretically should work for any 2.3 device." It's hardly a surprise and there's no specific word on timing just yet, but hopefully it won't take long to move that vanilla Android device up to something with a breaded exterior.
Click to expand...
Click to collapse
Source : Engaget
So, Theoretically HC could be upgrated in ICS
Wait and see
May be this os is made natively for phone... besides who needs a full new os, a few feature from it will do me good like the swipe to close apps in background, i really like it
jodiac said:
May be this os is made natively for phone... besides who needs a full new os, a few feature from it will do me good like the swipe to close apps in background, i really like it
Click to expand...
Click to collapse
ICS is for both phones and tablets, but looking at its specs one gets the feeling that it just brings HC to the phones much more than improving the HC itself. I just wonder how the phones that are not intended for ICS would handle the UI. Sacrificing screen area for navigation while you have a perfectly good hardware buttons seems stupid.
Sent from my A500 using XDA Premium App
More than likely, Yes
http://www.engadget.com/2011/10/20/asus-says-eee-pad-transformer-tablet-will-get-ics-upgrade-som/
as others have said if ACER does not the dev community will. I have a feeling they are already working on it at acer, my guess is that since google kept 3.0 so walled off they have clear upgrade paths for 3.0 to 4.0 set for all manufactures. 3.0 is the Redheaded stepchild of android versions it exists only because it was required so that we didint have tons of android 2.3 tablets, 4.0 is what 3.0 should of been
tkolev said:
ICS is for both phones and tablets, but looking at its specs one gets the feeling that it just brings HC to the phones much more than improving the HC itself. I just wonder how the phones that are not intended for ICS would handle the UI. Sacrificing screen area for navigation while you have a perfectly good hardware buttons seems stupid.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
much like for Honeycomb now, if you dont like the buttons, with root you can use Honeybar to hide it.
qwertylesh said:
much like for Honeycomb now, if you dont like the buttons, with root you can use Honeybar to hide it.
Click to expand...
Click to collapse
I know you can hide it, the question is if the OEMs will go that way with the older phones which will receive the update or not.
Sent from my A500 using XDA Premium App
tkolev said:
I know you can hide it, the question is if the OEMs will go that way with the older phones which will receive the update or not.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
I am pretty sure the OEMs will be hiding the soft buttons and map them to the hardware buttons instead. It remains to be seen how they implement the context-sensitive soft-button, there's plenty of ways of implementing that and undoubtedly different OEMs will go different ways.
Is there anyone work in progress for Chrome os porting to iconia a500?
We already have web browser! No need for another one! (Yes I'm talking about Chrome OS)
OrionBG said:
We already have web browser! No need for another one! (Yes I'm talking about Chrome OS)
Click to expand...
Click to collapse
my thoughts exactly. i dont understand the attraction to chome os on a tablet that already has a chrome based browser plus the most powerful mobile os ever made on top of an amazing cpu+gpu. whatever floats your boat i guess
How about now as nobody seems to dev for it any longer where Android is concerned....
HarshReality said:
How about now as nobody seems to dev for it any longer where Android is concerned....
Click to expand...
Click to collapse
There are still devs working on A500, JB, ICS, more JB, but, what more do you need developed? What needs do you find not satisfied with the current offerings?
Ahoy mateys. I've been a longtime Android user (October 2009) and have never been much for running the stock OS on my devices.
Currently I've been running CM7 and loving it on the KF. Been keeping tabs on the ICS port over, just waiting for the sound issues to be hammered out as I use the device mostly for watching videos via RockPlayer.
Lately I've been thinking about trying to port over Honeycomb to the KF, as it might be simpler given that it's been around longer. I know that it's somewhat futile given the state of the 3.0 kernel being needed for HW acceleration. But it seems like it could be worthwhile just to test it and see what might happen. Give it more tablety goodness if anything!
I'm a programmer by trade and am majoring in CS. Not much dev experience on Android aside from writing games. But I've built Gentoo for my machines, so I've got some kernel knowledge. What do you guys think?
Regards,
-Free
P.S. I don't have 10 posts so this is in General.
freeqaz said:
Ahoy mateys. I've been a longtime Android user (October 2009) and have never been much for running the stock OS on my devices.
Currently I've been running CM7 and loving it on the KF. Been keeping tabs on the ICS port over, just waiting for the sound issues to be hammered out as I use the device mostly for watching videos via RockPlayer.
Lately I've been thinking about trying to port over Honeycomb to the KF, as it might be simpler given that it's been around longer. I know that it's somewhat futile given the state of the 3.0 kernel being needed for HW acceleration. But it seems like it could be worthwhile just to test it and see what might happen. Give it more tablety goodness if anything!
I'm a programmer by trade and am majoring in CS. Not much dev experience on Android aside from writing games. But I've built Gentoo for my machines, so I've got some kernel knowledge. What do you guys think?
Regards,
-Free
P.S. I don't have 10 posts so this is in General.
Click to expand...
Click to collapse
Personally, I think it's a good idea, and that you should do it. You'll probably get a lot of people saying there's no point cause ICS is what honeycomb should've been. I've never used honeycomb before, so I don't know how different it is from ICS but I'm sure there are some.
I think you should do it to give this device and its users another ROM choice, with a different android version. Or even just for the fact that you might want to use it, do it for yourself and post it here just to see if people want it. I'd try it out, even if ICS is out and stable haha
Sent from my HTC Glacier using Tapatalk
Personally, I think it's a good idea, .... I've never used honeycomb before...
Click to expand...
Click to collapse
Huh?
Why would you encourage someone to work on something when you yourself don't know what the differences are between them??
ICS is Honeycomb just taking to what was its planned completion. With many Honeycomb devices moving to ICS I don't see the point.
That would be doing a lot of work, just to end up with an in between OS with all the new support going to ICS which is what everyone that can get it wants.
Also, for someone with no Android programming experience, you most likely would be a lot better of working with apps before tackling a whole OS.
krelvinaz said:
Huh?
Why would you encourage someone to work on something when you yourself don't know what the differences are between them??
ICS is Honeycomb just taking to what was its planned completion. With many Honeycomb devices moving to ICS I don't see the point.
That would be doing a lot of work, just to end up with an in between OS with all the new support going to ICS which is what everyone that can get it wants.
Also, for someone with no Android programming experience, you most likely would be a lot better of working with apps before tackling a whole OS.
Click to expand...
Click to collapse
I'd like to check it out. It's not like I'm telling him that he needs to do this, he asked what people thought of the idea because he was interested in doing it, and I voiced my opinion.
Though I do agree that it might be easier to work with apps and then maybe work on a ROM, but hey, if he's willing to attempt it and learn how everything works, why stop him? The more devs, the merrier lol
Isn't the problem with porting honeycomb is that it was never truly open source?
My understanding is there was never a source release for honeycomb
Sent from my SPH-D700 using xda premium
[email protected] said:
Isn't the problem with porting honeycomb is that it was never truly open source?
Click to expand...
Click to collapse
Yea, that is, AFAIK, why there was never a CM8. I don't think it would be worth OP's time to try to reverse-engineer a Honeycomb tablet and shoehorning it into the KF.
However, the OP might want to donate some of their time to the ICS port
It is open source after all...
[email protected] said:
Isn't the problem with porting honeycomb is that it was never truly open source?
Click to expand...
Click to collapse
I believe Google released the source for Honeycomb when they released the source for ICS
Sent from my Kindle Fire using Tapatalk
Hit up this Google announcement, they did indeed release the source.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
Click to expand...
Click to collapse
groups.google dot com/forum/#!topic/android-building/T4XZJCZnqF8
The only thing that I really want to know is if there is a significant driver difference between ICS and Honeycomb. If there is, then there is a reason to try to port 3.0 over because it would have more driver support. There are 3.0 devices out in the wild. If there isn't a driver difference between 3.0 and 4.0, then it's futile and all efforts should be spent on 4.0.
theholyfork said:
I believe Google released the source for Honeycomb when they released the source for ICS
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Indeed.
And when they released the source for ICS, they elaborated on why they included Honeycomb in the Source tree: To essentially display the hacks they were forced to use to push Honeycomb to market. Honeycomb was never AOSP'd because it wasn't reliable for wider use.
Based upon the fact that Google was basically too ashamed to release Honeycomb to AOSP, I don't think it would make much sense to target a broken platform (Honeycomb).
IMO, if you're going to spend time trying to work on getting a more tablet-oriented version of Android running, it's probably going to be *easier* to work with ICS than Honeycomb. Moreover your contributions could assist the greater KF community in getting a stable base of ICS for all.