Database Develop

Android 2.3 port from Nexus S to Galaxy S?

Hey guys,
what do you think, is it possible to port the Android 2.3 Gingerbread from Nexus S to our Samsung Galaxy S. Because it has a similar hardware!
/Discuss

You're fast , just wanted to ask this. Hope some legend dude will do this.

Theoretically it should be very simple to port the software. The only difference I can see from a hardware perspective is the NFC chip which simply needs to be disabled in software, and the missing search button which will need to be mapped to a menu long-press.
I did some work on the NITDroid project back when I had an N900, and neither of these is particularly difficult to do.

For nexus S info:
http://googleblog.blogspot.com/2010/12/introducing-nexus-s-with-gingerbread.html
http://www.google.com/nexus/#!/tech-specs
http://www.google.com/phone/compare/?phone=nexus-s&phone=samsung-galaxy-s

will the iNAND be a problem?

Supercurio says the devices use different types of memory.
Might be a bit of a problem

i can't see any reason we will have issues bringing it to the galaxy s line, especially if its the same SoC... and hardware, gps might be different, but thats a huge bonus anyways

Arkanius said:
Supercurio says the devices use different types of memory.
Might be a bit of a problem
Click to expand...
Click to collapse
yea the Nexus use the 16gb iNAND...

Since Samsung closely helped Google at making the hardware, hopefully we might have a quick 2.3 Samsung version for our devices
Which will then be easier to bring down to stock with the Cyanogen team progress

It must be far easier than a sense port or even cyanogen port.
Sent from my GT-I9000 using XDA App

One thing that also caught my eye was, that the video recording isn't HD... probably to not throw away boatloads of RAM for the camera...

Arkanius said:
Since Samsung closely helped Google at making the hardware, hopefully we might have a quick 2.3 Samsung version for our devices
Which will then be easier to bring down to stock with the Cyanogen team progress
Click to expand...
Click to collapse
I wouldn't bet on that. If Sammy released 2.3 in short order for the SGS it would cannibalize Nexus S sales. The aftermarket community is still the best bet.

binary110 said:
i can't see any reason we will have issues bringing it to the galaxy s line, especially if its the same SoC... and hardware, gps might be different, but thats a huge bonus anyways
Click to expand...
Click to collapse
GPS is the same! Both using A-GPS Chips. The NFC Software must be Disabled, Bluethooth Updated to 3.0, Nexus S has only 2.1 and Video Recording Updated to 1280x720, Nexus S had 720x480
Arkanius said:
Supercurio says the devices use different types of memory.
Might be a bit of a problem
Click to expand...
Click to collapse
Thats the biggest problem, I think. SuperCurios Tweet to iNand Tweet
Leandros

This a premature thread. Once a dump or aosp is released only then can we begin to do something about it. Till then this is a discussion thread and not related to development. IMHO

What about rfs? Im sure google is not using it. We will have to work that out as well.

2.3 SDK is out so I see no problem in getting gingerbread.
Whether as a port from the NS or a homebrew I don't really care.
All I want is the integrated SIP client. Been missing this since switching from my Nokia e90 Communicator to Android 1 year ago.
I am interested how the nexus S fares against a hacked Galaxy S, don't think it will be any faster!

Mycorrhiza said:
2.3 SDK is out so I see no problem in getting gingerbread.
Whether as a port from the NS or a homebrew I don't really care.
All I want is the integrated SIP client. Been missing this since switching from my Nokia e90 Communicator to Android 1 year ago.
I am interested how the nexus S fares against a hacked Galaxy S, don't think it will be any faster!
Click to expand...
Click to collapse
Everything is virtually the same.

I call up one the powers of the all powerful XDA to port the N:S for all the SGS's that are out there, so we can forget about samsung roms and use a normal google one

The Nexus S doesn't seem to support an external sd card. Likely another problem?

bigriot said:
The Nexus S doesn't seem to support an external sd card. Likely another problem?
Click to expand...
Click to collapse
Maybe... but I can live without an external SDCARD for now...

wifi only gtab

so i just got one as a present. rooted it in seconds but now what? from what ive read here there are no custom roms yet for this version PLUS the bluetooth keyboard i got with it cant even pair because the wifi only has different btooth capabilities apparently? i feel like i have a paper weight! lol unless i overlooked something what are the flashing options for the wifi only gtab?

nevermind. will be returning. hell my phone has more capabilities then this tab. very disappointing sam SUCK.
/thread

Sorry to hear that, he only keayboard working with the P1010 is the Freedom Pro with SSP profile and it works great! the problem is due to the lack of HID profile in Froyo, as far I know this was added in 2.3, and the devices pre-gingerbread that has it is thanks to the manufacturers, like Archos (Awesome custom suport for codecs and profiles).
At first I was feeling the same (Poor bluetooth support and no ad-hoc), but the little guy has grown on me, the p1000 is no option for me as I already have Phone, and planning on buying an Acer Iconia for in house use and leave the P1010 for the outside.

[Q] Captivate ROM supporting Bluetooth MAP Profile?

Hi All!
Has anyone ported/incorporated support for the BlueTooth MAP profile into any stable Captivate ROMs?
I see that the Galaxy SII Skyrocket supports MAP (according to their marketing literature), but I'd hate to have to spend the $$$ to upgrade my hardware for a function that seems (to me) like it's purely a software function.
There's nothing wrong with my 1.25 year old Captivate, other than a slight lust for tighter integration with the Ford Sync system in my 2011 Taurus.
Thanks!
Sean

alphaschnitz said:
Hi All!
Has anyone ported/incorporated support for the BlueTooth MAP profile into any stable Captivate ROMs?
I see that the Galaxy SII Skyrocket supports MAP (according to their marketing literature), but I'd hate to have to spend the $$$ to upgrade my hardware for a function that seems (to me) like it's purely a software function.
There's nothing wrong with my 1.25 year old Captivate, other than a slight lust for tighter integration with the Ford Sync system in my 2011 Taurus.
Thanks!
Sean
Click to expand...
Click to collapse
RemICS does. 4.0.4 version.

Bluetooth Low Energy (BLE) Support?

I noticed that patches seem to have been made to CM11 for the rest of the Moto OMAP4 lineup (spyder, utms_spyder, maserati) to turn on Bluetooth LE support, but it does not seem to have made it to the Bionic. Has anybody built a ROM to test this on our devices?
http://forum.xda-developers.com/showthread.php?t=2583274
http://review.cyanogenmod.org/#/q/owner:"Lucian+Cristian"+status:merged,n,z

BLE is Bluetooth 4.0 functionality. The Bionic's hardware only supports up to Bluetooth 2.1, IIRC, so no, it wouldn't be possible.

TechnoMonkey76 said:
BLE is Bluetooth 4.0 functionality. The Bionic's hardware only supports up to Bluetooth 2.1, IIRC, so no, it wouldn't be possible.
Click to expand...
Click to collapse
I initially got a bit tripped up. I confused the WL1271 with the WL1271L since I could only find product sheets on the later.
However, I'm not totally convince that this is really is a WL1271. The iFixit teardown SAYS that it is a WL1271 with a nod to Chipworks, of course the actual pictures (once found in high enough resolution) seem to indicate a WL1285C printed on the chip. For example:
http://www.anandtech.com/show/4910/motorola-droid-bionic-review-dual-core-with-4g-lte/3
I'll see if I can dig in a little bit, and figure out if it is really a WL1271, or if it is a WL1285C with 5GHz disabled.
OK, on my Bionic:
"/sys/class/bluetooth/hci0/hci_version" is equal to 6, which according to hci.c in the Linux BlueZ source means "Bluetooth 4.0"
So it sure seems that with the current Bluetooth firmware ( TIInit_10.6.15.bts ) that the Bionic supports Bluetooth 4.0, and presumably BLE once the minor build change I linked to in my prior post is applied.

guyincog said:
I initially got a bit tripped up. I confused the WL1271 with the WL1271L since I could only find product sheets on the later.
However, I'm not totally convince that this is really is a WL1271. The iFixit teardown SAYS that it is a WL1271 with a nod to Chipworks, of course the actual pictures (once found in high enough resolution) seem to indicate a WL1285C printed on the chip. For example:
http://www.anandtech.com/show/4910/motorola-droid-bionic-review-dual-core-with-4g-lte/3
I'll see if I can dig in a little bit, and figure out if it is really a WL1271, or if it is a WL1285C with 5GHz disabled.
OK, on my Bionic:
"/sys/class/bluetooth/hci0/hci_version" is equal to 6, which according to hci.c in the Linux BlueZ source means "Bluetooth 4.0"
So it sure seems that with the current Bluetooth firmware ( TIInit_10.6.15.bts ) that the Bionic supports Bluetooth 4.0, and presumably BLE once the minor build change I linked to in my prior post is applied.
Click to expand...
Click to collapse
Interesting, il see if I can build up a BLE Cyan-Fox rom for the bionic within the next week and if everything works it may be worth sending a patch to gerrit for the CM builds.

ddggttff3 said:
Interesting, il see if I can build up a BLE Cyan-Fox rom for the bionic within the next week and if everything works it may be worth sending a patch to gerrit for the CM builds.
Click to expand...
Click to collapse
Sorry, this had dropped off my radar. Did you ever give this a try?

guyincog said:
Sorry, this had dropped off my radar. Did you ever give this a try?
Click to expand...
Click to collapse
Sorry, I have been busy recently and have been unable to make the test build. I will try to get one in the next few days based on CM11.
EDIT: Here is a build with the patch, but I am unable to test as my bionic is being used by a friend atm. please test and report back.
http://pdl.team-eureka.com/other/ddggttff3/cm-11-20140310-UNOFFICIAL-targa.zip

ddggttff3 said:
Sorry, I have been busy recently and have been unable to make the test build. I will try to get one in the next few days based on CM11.
EDIT: Here is a build with the patch, but I am unable to test as my bionic is being used by a friend atm. please test and report back.
http://pdl.team-eureka.com/other/ddggttff3/cm-11-20140310-UNOFFICIAL-targa.zip
Click to expand...
Click to collapse
Cool, I'll spin up a new Slot on my Bionic, and try to spend some time testing this in the next few days.

guyincog said:
Cool, I'll spin up a new Slot on my Bionic, and try to spend some time testing this in the next few days.
Click to expand...
Click to collapse
Just an update, I keep falling behind here. I finally got this installed in an extra slot last night, and verified that my standard Bluetooth 2.x devices are working fine. I should have a chance to grab a BLE device, and give it a test this weekend.

Sorry for a semi-hijack, any one know if there's a chance to get APTX working if this patch works? Or are we pretty much out of luck?

guyincog said:
Just an update, I keep falling behind here. I finally got this installed in an extra slot last night, and verified that my standard Bluetooth 2.x devices are working fine. I should have a chance to grab a BLE device, and give it a test this weekend.
Click to expand...
Click to collapse
Just wondering if you ever got this tested, as this is the last thing that has ever been posted about Bluetooth Low Energy on the Bionic.

New to XDA - excited to learn more about rooting my device, but also keen to learn more about ASHA support

Good day, fine folks at XDA!
My name is Charles Schultz. I picked up my first Android device the summer of 2021, a cheap Umidigi A9. Their support absolutely sucks! However, they also sent me an additional A9 for free, so I am happy to give rooting a try since I have a spare device.
My biggest problem right now is that the A9 does not support ASHA and streaming to my hearing aids (Jabra Enhance Pro). The Jabras seem to only be compatible with devices that have Bluetooth 5.0 and greatere (check), support for BLE (check), and ASHA ( ). From what I have read so far, Android 10 and up provides support for ASHA, so I have to infer that Umidigi has not baked ASHA support into their branded version of Android. I have been asking them for quite some time for help, but Umidigi support is REALLY BAD(tm).
I am an IT professional who tinkers with various languages and feels quite at home with Linux. Rooting an entire Phone OS seems very daunting, but also exciting at the same time. I am anxious to dip my toes into the XDA waters.
Thanks to all of you who help make XDA such a rich resource for the rest of us.

sacrophyte said:
Good day, fine folks at XDA!
My name is Charles Schultz. I picked up my first Android device the summer of 2021, a cheap Umidigi A9. Their support absolutely sucks! However, they also sent me an additional A9 for free, so I am happy to give rooting a try since I have a spare device.
My biggest problem right now is that the A9 does not support ASHA and streaming to my hearing aids (Jabra Enhance Pro). The Jabras seem to only be compatible with devices that have Bluetooth 5.0 and greatere (check), support for BLE (check), and ASHA ( ). From what I have read so far, Android 10 and up provides support for ASHA, so I have to infer that Umidigi has not baked ASHA support into their branded version of Android. I have been asking them for quite some time for help, but Umidigi support is REALLY BAD(tm).
I am an IT professional who tinkers with various languages and feels quite at home with Linux. Rooting an entire Phone OS seems very daunting, but also exciting at the same time. I am anxious to dip my toes into the XDA waters.
Thanks to all of you who help make XDA such a rich resource for the rest of us.
Click to expand...
Click to collapse
Nice intro Charles! welcome to XDA