I am wondering if any of you smart folks are working on a ported HC 3.2 from Samsung Galaxy 10.1 update.
If u wanted a galaxy tab maybe u should go buy one.
Thestock acer rom is better any day.
Plus everything works.
The same isnt true on ports of other devices.
Just keep your panties on 3.2 is almost ready from Acer
Sent from my unknown using Tapatalk
Moved to Q&A
I changed from Samsung Galaxy S2 to Samsung Galaxytab 7.7 3G.
In xda-developers forum there are many Roms (Custom and Stock) for the S2 but only a few for the Galaxy Tab 7.7.
What is the reason for this?
Will there be more roms if ICS for Galaxy Tab 7.7 is out?
I dont understand why there are only a few roms for this really great TAB
I think because it is such a new product and also development is focussed on ICS and there is a fair amount of work to port from CM9 from other devices and build a working rom with no issues.
It is close though! I can't wait.
The custom tweaked and stock v3 is soon to be released and if anything like v2 it will be even better and run very well.
Lets support our devoted devs!!!
The answer probably is:
GS II sold a ton of devices (10 millions at least) and was brought to Us early
GT 7.7 is selling few devices and in Us came only trough verizon few time ago
Sent from my Nexus One using XDA
Galaxy Tab 2 (7.0)
Galaxy Tab 2 (10.1)
Galaxy Note 10.1
Galaxy Tab 7.0 Plus
Galaxy S II
Galaxy S II (LTE)
Galaxy Note
Galaxy S Advance
Galaxy Ace 2
Galaxy Beam
Galaxy Ace Plus
Galaxy Mini II
Galaxy S DUOS
Galaxy Music
Galaxy Chat
Source
Nice list.
I have two devices on it.
scottx . said:
Nice list.
I have two devices on it.
Click to expand...
Click to collapse
I have three :victory:
Wohoo!!... I want to see both of my devices with Jelly Bean
Pfff need jb for my siii
Sent from my GT-I9300 using xda app-developers app
what's the big difference between ICS and JB?
I had an N7 and the only difference I can find is Google Now (which did nothing for me on my tablet)
Also, what will we lose?
I know flash is not present but can still be loaded on, although not seen anyone say it works, but not looked that hard.
BBC iplayer?
anybody knows when is the update?
im waiting the update to my GT 3110
im from portugal, i dont know if the update out at same day for all...??!?!?
great thread
i am waiting for jb for my GT 3110 too, does anybody know when we will get the update?
I hope the "official" update for the Galaxy Tab 2 with have these issues fixed that the currently leaked versions have....
-portrait only home screens
-mike not working in some apps
-battery percentage on notification bar
rudeguy said:
what's the big difference between ICS and JB?
I had an N7 and the only difference I can find is Google Now (which did nothing for me on my tablet)
Click to expand...
Click to collapse
Butter. Really, most of the differences are not changes you can see. They cleaned up the code and are compiling it with a newer toolchain. It helped optimize things more and provides for a more fluid interface.
I have an unlocked version. According to the TmoNews article, the unlocked versions should see the update first as they they have to go through carrier testing.
Hopefully the Tab version will come out quickly, then we'll just have to wait for AT&T to muck around with uit for 6 months before the rest of the devices get it.
There's a video with all changes uploaded in youtube, I can't post it 'cause I'm a new member but is there, the google event release of jb almost 3 months ago.
Sent from my GT-I9300 using xda app-developers app
Alhamdulillah, can't hardly wait..
The update is still not available yet for my country, so I have installed my own with germany version
JB is great..
http://www.sammobile.com/2013/03/18...roid-5-0-for-the-galaxy-s-iii-galaxy-note-ii/
* End at Android 4.2.2 update.
GT-I9080 – Galaxy Grand
GT-I9082 – Galaxy Grand DUOS
GT-I8190 – Galaxy S III mini
GT-I8730 – Galaxy Express
GT-I9100 – Galaxy S II
GT-I9105 – Galaxy S II Plus
GT-I9260 – Galaxy Premier
GT-N7000 – Galaxy Note
GT-S6310 – Galaxy Young
GT-S6312 – Galaxy Young DUOS
GT-S6810 – Galaxy Fame
GT-S7710 – Galaxy X Cover 2
To get Android 5.0.
GT-I9300 – Galaxy S III
GT-I9305 – Galaxy S III LTE
GT-I9500 – Galaxy S 4
GT-I9505 – Galaxy S 4 LTE
GT-N5100 – Galaxy Note 8.0
GT-N5105 – Galaxy Note 8.0 LTE
GT-N5110 – Galaxy Note 8.0 Wi-Fi
GT-N7100 – Galaxy Note II
GT-N7105 – Galaxy Note II LTE
GT-N8000 – Galaxy Note 10.1
GT-N8005 – Galaxy Note 10.1 LTE
GT-N8010 – Galaxy Note 10.1 Wi-Fi
Remember this is an pre-list. (Samsung could still change devices!)
Do not ask for other devices, if we know more we will tell you.
* List is not complete yet!
It must be a fake news .
* End at Android 4.2.2 update.
GT-I9080 – Galaxy Grand
GT-I9082 – Galaxy Grand DUOS
GT-I8160 – Galaxy Ace 2
GT-I8190 – Galaxy S III mini
GT-I8350 – Galaxy Beam
'GT-I8350 – Galaxy Beam'
'i8530 ' not 'i8350'
Galaxy Beam still at android 2.3.6 .and getting 4.2.2 is RIDICULOUS !!!!!
bykevin said:
Galaxy Beam still at android 2.3.6 .and getting 4.2.2 is RIDICULOUS !!!!!
Click to expand...
Click to collapse
The Galaxy Note N7000 and the S2 i9100 were also at 2.3.5/6 and got ICS, JB and both are probably getting 4.2.2 .
Awesome!
i hope Samsung will not wait until 5.0 is out but upate to 4.2.2 first .
Can Someone Confirm how Samsung does at the last updates ?
Greetz Steyen
It'll be amazing if Samsung release android 4.2.2 for galaxy note 10.1 users before summer and it improves the good performance we can get for the quad core processor.
If you look at comments on Google code, you'll see that Bluetooth remains broken in 4.2.2. This is totally unawesome and Google seems unable or unwilling to fix their code.
mke1973 said:
If you look at comments on Google code, you'll see that Bluetooth remains broken in 4.2.2. This is totally unawesome and Google seems unable or unwilling to fix their code.
Click to expand...
Click to collapse
Totally fixable issue. I'm currently using cm10.1 which is 4.2.2 and typing on a Bluetooth keyboard.
Sent from my GT-N8013 using xda app-developers app
quinman22 said:
Totally fixable issue. I'm currently using cm10.1 which is 4.2.2 and typing on a Bluetooth keyboard.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
The BT issue is especially pervasive with any type of audio headsets (many can't establish any connection with audio BT), although some users are reporting that other BT devices will connect but then disconnect, requiring a reboot to be usable again. I hate to see what Android merged into Chrome will look like. Google's size may not really improve its products. Google is also terrible at interacting with its customers. So many times they never respond to bug reports on Google Code even if a multitude of users confirm its existence. They're morphing into a new version of MS.
mke1973 said:
The BT issue is especially pervasive with any type of audio headsets (many can't establish any connection with audio BT), although some users are reporting that other BT devices will connect but then disconnect, requiring a reboot to be usable again. I hate to see what Android merged into Chrome will look like. Google's size may not really improve its products. Google is also terrible at interacting with its customers. So many times they never respond to bug reports on Google Code even if a multitude of users confirm its existence. They're morphing into a new version of MS.
Click to expand...
Click to collapse
I am begining to love the Nexus concept. It's where all the major bugs in Android get found, which make the system unusable for Nexus users - before Samsung release a fixed and tested version a few months later!
So much for the Google Android purists -LOL!
curious, I have bt working on my cheap ainol tablet running 4.2 (own build) audio no issues at all,
maybe its a chipset issue, got a link to the bleating (I mean google code bugreports?)
fards said:
curious, I have bt working on my cheap ainol tablet running 4.2 (own build) audio no issues at all,
maybe its a chipset issue, got a link to the bleating (I mean google code bugreports?)
Click to expand...
Click to collapse
I think Google isn't adequately beta testing, asuming the Nexus aficionados who buy the devices for "native" Android are geeky enough to tolerate bugs. However, the Bluetooth bug has been draging on for 5 months and tempers are flairing, especially since Google isn't responding. Other manufacturers that are putting an interface on top of Google's code seem to be putting out better products at the moment.
mke1973 said:
If you look at comments on Google code, you'll see that Bluetooth remains broken in 4.2.2. This is totally unawesome and Google seems unable or unwilling to fix their code.
Click to expand...
Click to collapse
they never do fix they code, hence the jellybean resource hog problem/ OTG problem.
What is the Bluetooth problem about ?
Don't notice any problem in the note
Sent from my SGH-I747M using Tapatalk 2
klau1 said:
What is the Bluetooth problem about ?
Don't notice any problem in the note
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
You are on Jellybean 4.1.2 if you're on the updated sock ROM. Google put out an increnental update last fall with the Jelly Bean designation 4.2, this update has killed Bluetooth. Most Nexus device users, who are the consumers who've gotten this update are reporting that audio Bluetooth is completely dead and that other Bluetooth devices may connect briefly but then disconnect and the device must be rebooted. Google has been silent on this issue in the Google Code forums and 2 subsequent updates, 4.2.1 and 4.2.2 have not fixed it. Users in the Google Code forums are frustrated as this problem has existed for almost 5 months and Google is dead silent on the issue.
Also, Goog hasn't implemented BTLE, which means there's a TON of devices like Nike's FUEL band that can't be made to work with any Android device. Almost every Android device made since the middle of last year has a BT4+LE chipset but can't use it except by bringing in a third party library - and since there's different chipsets, it's a pain to support all the different devices - so no one supports any of them.
mke1973 said:
You are on Jellybean 4.1.2 if you're on the updated sock ROM. Google put out an increnental update last fall with the Jelly Bean designation 4.2, this update has killed Bluetooth. Most Nexus device users, who are the consumers who've gotten this update are reporting that audio Bluetooth is completely dead and that other Bluetooth devices may connect briefly but then disconnect and the device must be rebooted. Google has been silent on this issue in the Google Code forums and 2 subsequent updates, 4.2.1 and 4.2.2 have not fixed it. Users in the Google Code forums are frustrated as this problem has existed for almost 5 months and Google is dead silent on the issue.
Click to expand...
Click to collapse
Wow, what a fail for Nexus.
What's the point of trading off immensely useful micro SD slot for useless pure android experience?
Sent from my SGH-I747M using Tapatalk 2
klau1 said:
Wow, what a fail for Nexus.
What's the point of trading off immensely useful micro SD slot for useless pure android experience?
Sent from my SGH-I747M using Tapatalk 2
Click to expand...
Click to collapse
Speculation is that the strategy on dropping the micro sd is to ultimately drive more users to Google cloud storage (and ultimately fees for Google). Given the shift of responsibility for Android development to the manager for Chrome, tech publications see Google merging Android into Chrome. I suspect that it will be a mess. The big question is whether Google code writing and beta testing will improve. I'm not going to hold my breath.
Based on past experience on the time Sammy takes to update. Let me guess, our key lime pie will be ready in 2015?
salmonsushi said:
Based on past experience on the time Sammy takes to update. Let me guess, our key lime pie will be ready in 2015?
Click to expand...
Click to collapse
lmao true
--->Samsung Galaxy S4 Gets apps to sd support official
Let there be light! i hope this leads to support for the note too. Or at least a hacked official support to the note 10.1
-------->BOOM:good::fingers-crossed::laugh::victory:
That and 4.2 on the new tabs. Let's hope Samsung doesn't forget what a great and unique tablet they've got with the Note 10.1!
I shudder to think that Windows might catch up. Urghhh!!!!!
Sent from my GT-N8000 using Tapatalk HD