Hello,
Since the desire is pretty much the same as the Nexus one, I was wondering if anyone had any luck getting the wireless N driver working on the desire yet? or getting the desire notification led working with more colors ;<
thedt said:
Hello,
Since the desire is pretty much the same as the Nexus one, I was wondering if anyone had any luck getting the wireless N driver working on the desire yet? or getting the desire notification led working with more colors ;<
Click to expand...
Click to collapse
I'm not sure you're able to get wireless N on the Desire, since it doesn't have the N-wireless hardware, does the N1 really have it? :S
And the led thing, how many colors does it have? Green, Orange and red(?)?
The only possiblities would be green and orange and a mix of both, but both at once isn't allowed.
As for Wireless N, you'd have to find out if they share the same chipset. If they do then it is of course possible, but good luck finding anyone to port the driver from the Nexus to the Desire.
It's integrated in the snapdragon right?
that's the same as the nexus one..
As far as I know they have the same shipset, so we are supose to get Wifi N as soon as HTC wants to launch Froyo or a minor uptade.
=)
Sweet
Bonus.
I didn't know either had Wifi N until this thread. Now jsut to wait on someone to port it from the Nexus, or HTC to give us froyo.
alias_neo said:
Bonus.
I didn't know either had Wifi N until this thread. Now jsut to wait on someone to port it from the Nexus, or HTC to give us froyo.
Click to expand...
Click to collapse
Desire uses same hardware as the HD2, which has Wifi N. On the HD2 it can be enabled via the registry.
According to the kernel there is a controller for a blue led, but it might not be connected to anything.
Code snip for proof:
Code:
static struct microp_led_config led_config[] = {
{
.name = "amber",
.type = LED_RGB,
},
{
.name = "green",
.type = LED_RGB,
},
{
.name = "blue",
.type = LED_GPO,
.mask_w = {0x00, 0x02, 0x00},
},
{
.name = "button-backlight",
.type = LED_PWM,
.mask_w = {0x02, 0x00, 0x00},
.led_pin = 1 << 2,
.init_value = 0xFF,
.fade_time = 5,
},
};
is it shure that the Desire will get Wireless N with the update to Froyo?
This would be great! Than I can set my router to N only.
ardsar said:
Desire uses same hardware as the HD2, which has Wifi N. On the HD2 it can be enabled via the registry.
Click to expand...
Click to collapse
Yeh, Android is never as simple though, with no "registry" and most surely no driver capable of Wifi N, it wo't be quite as simple for us.
deovferreira said:
According to the kernel there is a controller for a blue led, but it might not be connected to anything.
Code snip for proof:
Code:
static struct microp_led_config led_config[] = {
{
.name = "amber",
.type = LED_RGB,
},
{
.name = "green",
.type = LED_RGB,
},
{
.name = "blue",
.type = LED_GPO,
.mask_w = {0x00, 0x02, 0x00},
},
{
.name = "button-backlight",
.type = LED_PWM,
.mask_w = {0x02, 0x00, 0x00},
.led_pin = 1 << 2,
.init_value = 0xFF,
.fade_time = 5,
},
};
Click to expand...
Click to collapse
well GPO stands for General Purpose Output. It could be for an external component or just not used for anything. Maybe the camera flash?
Vieze Fur said:
is it shure that the Desire will get Wireless N with the update to Froyo?
This would be great! Than I can set my router to N only.
Click to expand...
Click to collapse
Nope, nobody has officially ever mentioned it, it's possible HTC may not want nor intent to give the update with Wifi N at all.
BCM4329
http://www.broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM4329
This chip also has FM Tx, so I want radio transmitter now for car stereo.
-------------------------------------
Alias::NeO on HTC Desire
it would be just awesome...
alias_neo said:
well GPO stands for General Purpose Output. It could be for an external component or just not used for anything. Maybe the camera flash?
Click to expand...
Click to collapse
It's not for the camera flash, that uses a different controller. I'm not sure what the purpose is yet, I'm sure someone will find out , maybe me when I have some free time.
alias_neo said:
Nope, nobody has officially ever mentioned it, it's possible HTC may not want nor intent to give the update with Wifi N at all.
Click to expand...
Click to collapse
We can use the nexus driver if they don't give us one.
In that case what is stopping us from testing it with the current froyo ports?
-------------------------------------
Alias::NeO on HTC Desire
alias_neo said:
In that case what is stopping us from testing it with the current froyo ports?
-------------------------------------
Alias::NeO on HTC Desire
Click to expand...
Click to collapse
Chipset documentation, probably, fm tx isn't implemented in the kernel.
Sorry, I meant the WiFi N using nexus driver. Trying to discuss too many things at once. I wasn't clear.
-------------------------------------
Alias::NeO on HTC Desire
alias_neo said:
Sorry, I meant the WiFi N using nexus driver. Trying to discuss too many things at once. I wasn't clear.
Click to expand...
Click to collapse
That's ok. We need the kernel source, I don't think google has published the froyo kernel source yet. And then someone to backport the module, I could probably do it the interface hasn't changed much.
deovferreira said:
That's ok. We need the kernel source, I don't think google has published the froyo kernel source yet. And then someone to backport the module, I could probably do it the interface hasn't changed much.
Click to expand...
Click to collapse
If they share the same chipset as the nexus then wouldn't it be possible to get N on the current roms, since nexus roms can currently do it (cyanogens) wouldn't it just be compiling the driver for the desire kernel?
thedt said:
If they share the same chipset as the nexus then wouldn't it be possible to get N on the current roms, since nexus roms can currently do it (cyanogens) wouldn't it just be compiling the driver for the desire kernel?
Click to expand...
Click to collapse
Yes, but if the driver interfaces changed you still have to do some backporting work.
Related
I've been hearing great stuff about Bluetooth 4.0 LE ((B)LE), like paring heart-rate sports gear almost without battery draining.
Afaik Bluetooth 4.0 doesn't necessarily mean LE functionality, and the only mention thus far I could find was APT-X is included.
Right now I'm confused on whether or not this is supported on the One X. Does anyone know?
Here's a link with a chart that should explain compatibility between new Bluetooth devices, but I really don't get it
And what about NFC implementation? I haven't seen any mention of Sense 4 using it, while Sony's Experia S has those coins with nice software implementation to let the phone know it's next to your bed and needs to be quiet, is in your car and needs navigation etc.
http://www.cellular-news.com/story/53379.php
According to this site it is Smart Ready. As I understand it: It should be ready for the LE-devices.
NFC ist atleast in the Settings:
Look at 2:40: http://www.youtube.com/watch?v=a-478p9v7T8
Thanks for those links Noneus! Seems like the device is BLE ready while Android 4.0.3 isn't. I really hope xda devs can help with this into the One X roms, however, I guess the wait is for nvidia to update their drivers mostly right?
Sent from my HTC Desire using xda premium
Not necessarily. Most of the time the OS is lacking the Bluetooth features. Not the driver.
Here is a good diagram: https://sites.google.com/a/android.com/opensource/projects/bluetooth-faq
From http://developer.android.com/sdk/android-4.0-highlights.html :
Android 4.0 also introduces built-in support for connecting to Bluetooth Health Device Profile (HDP) devices. With support from third-party apps, users can connect to wireless medical devices and sensors in hospitals, fitness centers, homes, and elsewhere.
Click to expand...
Click to collapse
This look promising, thanks! Will take a closer look as soon as I get back from work!
The HQ for bluetooth 4.0 fix on GS3
there is a lot of information on this thread that may or may not be helpful to you even tho its mostly directed towards the gs3
http://forum.xda-developers.com/showthread.php?p=35322649#post35322649
hope it helps
Hi all,
The black HTC one X has a different Camera.apk which has only Grid in the interface options, a measure taken probably because it is illegal to turn off the shutter sound in the camera. (From what I know). Comparing them side to side, the black version also "stutters" less when moving around, but also, both the colours and the screen seem to have a better contrast.
These are the photos, included is the different software number. I saw this model in two different stores.
Can anyone perhaps upload the black camera.apk? I think it fixes some of the issues the white one has. Are there any roms based on this version?
All the best.
Must be regional as your version numbers all differ a great amount from mine.
Also, I have a white one with the ability to toggle shutter sound. A black one from a friend also has that option.
Also, why on earth would it be illegal to turn off shutter sound?
Kernel 3.0? It's a custom ROM...
Mine is black and I don't have any deferent camera.
krogoth said:
Kernel 3.0? It's a custom ROM...
Mine is black and I don't have any deferent camera.
Click to expand...
Click to collapse
no its not a custom kernel
maybe its a One XL?
krogoth said:
Kernel 3.0? It's a custom ROM...
Mine is black and I don't have any deferent camera.
Click to expand...
Click to collapse
Custom ROM in a store? Sure.
Zulake said:
Also, why on earth would it be illegal to turn off shutter sound?
Click to expand...
Click to collapse
Privacy laws in some countries.
Sent from my HTC One X using xda app-developers app
xchasa said:
Privacy laws in some countries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
That's just retarded imo. I mean, normal camera's and such don't have shutter sounds aswell.
This is probably an unreleased FW version on the phone used on display models? I think HTC probably pushed a non-consumer version of the 3.0 kernel for best performance? better performance = more sales. I'm not sure.
ThatNerdGuy said:
This is probably an unreleased FW version on the phone used on display models? I think HTC probably pushed a non-consumer version of the 3.0 kernel for best performance? better performance = more sales. I'm not sure.
Click to expand...
Click to collapse
Okay now this thing has got me interested as well :-/
i think its the One XL so hold your horses
interesting how the settings icon of the camera is red/orange when pressed
mine is green
Duh... it's one xl, with a stock software version 1.81.841.1.
I've got international black one X and trust me, there is an option to turn of the shutter sound.
hamdir said:
i think its the One XL so hold your horses
Click to expand...
Click to collapse
You're right. This is the XL. A simple google search of the FW number revealed the XL FW page. And for a second there I thought the 3.0 kernel release was imminent.
Baseband was the giveaway...
It could be the One XL, I didn't know they look alike so much. I'll double check when I go back to make sure.
Posting two photos of One X versions with different menu colours, red and yellow/orange, both of them display models.
htckt said:
It could be the One XL, I didn't know they look alike so much. I'll double check when I go back to make sure.
Posting two photos of One X versions with different menu colours, red and yellow/orange, both of them display models.
Click to expand...
Click to collapse
It wasn't that hard to identify XL or X,
Go About - Hardware information, Processor: Quadcore = X, Dual core = XL.
krogoth said:
Mine is black and I don't have any deferent camera.
Click to expand...
Click to collapse
You guys are funny. The phone itself is exactly the same. In the last stage of assembly it's put in to either a white or grey body. There's no h/w or s/w differences between the colors. You can buy a different colored body on eBay and change the color and nothing will change with the internals.
ThatNerdGuy said:
This is probably an unreleased FW version on the phone used on display models? I think HTC probably pushed a non-consumer version of the 3.0 kernel for best performance? better performance = more sales. I'm not sure.
Click to expand...
Click to collapse
This sounds like BS if you ask me. Why would HTC include kernell 3.x, still use old HTC API and Android 4.0.3... While they have A 4.0.4 TEST rom out which uses the new HTC API...
And from the SW version it is 100% a One XL!
Sent from my HTC One X using xda app-developers app
xchasa said:
Privacy laws in some countries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I heard in radio that it's illegal to turn off shutter sound in phones, and that is only in Japan or somewhere there.
The best is the reason. Guys loves to take photos of strange girls on the street, specially when they have very short skirt. Problem is that the guys taking photos of what is under this short skirt. Therefore is better when it's making sound also.....
This is a example: http://www.youtube.com/watch?v=CDFSLCNSJLM
Another example is sleeping girlfriends/wives, or using a camera when cameras
are not permitted.
Sent from my HTC One X using xda app-developers app
I have read that gnex has hardware that supports Bluetooth 4.0, is there a rom or kernel that has enabled it to work or is it even possible?
Thanks in advance
Sent from my Galaxy Nexus using Tapatalk 2
I'm sorry man but i think it's impossible according to the samsung specs, it only has bluetooth 3
http://www.samsung.com/hk_en/consumer/mobile/mobile-phones/smartphone/GT-I9250TSATGY-spec
Thanks. The reason I ask is that I saw this on Wikipedia. It states that it is Bluetooth 4.0 hardware compatible. 2nd reason is I bought those Bluetooth speakers with Bluetooth 4 and apt-x support. I just want to maximize it to it's full potential.
Sent from my Galaxy Nexus using Tapatalk 2
mrm43 said:
Thanks. The reason I ask is that I saw this on Wikipedia. It states that it is Bluetooth 4.0 hardware compatible. 2nd reason is I bought those Bluetooth speakers with Bluetooth 4 and apt-x support. I just want to maximize it to it's full potential.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes. The hardware is bluetooth 4.0 compatible but there's no software support yet. Star the issue to add your vote! ->
http://code.google.com/p/android/issues/detail?id=33371
travellers trolloca
Wait wait wait, one moment, i don't understand. The hardware inside GNeX is bt4 but it has driver that doesn't support that but only bt3, is this what are you saying? It sound really strange to me, maybe that statement on wiki means that GNeX can use other hardware with bt4 even if it's bt3 but not at full power, am i wrong?
[email protected] said:
Wait wait wait, one moment, i don't understand. The hardware inside GNeX is bt4 but it has driver that doesn't support that but only bt3, is this what are you saying? It sound really strange to me, maybe that statement on wiki means that GNeX can use other hardware with bt4 even if it's bt3 but not at full power, am i wrong?
Click to expand...
Click to collapse
It'll be clearer if you check out the link in my previous post. Gnex contains a Samsung SWB-B42 BT 4.0 Dual Band Wlan FM Tx/Rx chip so the hardware is there. The thing is the driver that is currently installed on our gnex only has BT3 coded in. And even if the driver utilizes the phone's BT4.0 capabilities, Android in itself doesn't have native APIs to allow developers to take advantage of the new features.
Sorry if i didn't read the whole link but i was at work so, you can understand... Thank you for the very clear explanation, however it's really really strange this behaviour by google...
Will Google/Android ever get BT4/BLE working on the GNex? Or shall we move on to another device if we need/want it?
Is there any way to make this tablet to support this kind of wifi -n?
I have a router TP-Link WDR4300 dual band, and the 2.4Ghz band is detected ok, but the 5ghz don´t show up.
The motorola Atrix, have support for 5Ghz..
tux_topo said:
Is there any way to make this tablet to support this kind of wifi -n?
I have a router TP-Link WDR4300 dual band, and the 2.4Ghz band is detected ok, but the 5ghz don´t show up.
The motorola Atrix, have support for 5Ghz..
Click to expand...
Click to collapse
The hardware doesn't support it, no real way to add it unless you change the WiFi module out for one that does, then you'll maybe need to build a kernel to support the new WiFi module.
Tapatalked from my HTC DNA - PAC
pio_masaki said:
The hardware doesn't support it, no real way to add it unless you change the WiFi module out for one that does, then you'll maybe need to build a kernel to support the new WiFi module.
Tapatalked from my HTC DNA - PAC
Click to expand...
Click to collapse
While searching, found this: http://forum.xda-developers.com/showthread.php?t=1675547
I know different devices, different hardware, and different OS... but are you sure that can´t be the same problem?
Of course, already search those files, but culdn´t find them....
Thanks for the answer!!
tux_topo said:
While searching, found this: http://forum.xda-developers.com/showthread.php?t=1675547
I know different devices, different hardware, and different OS... but are you sure that can´t be the same problem?
Thanks for the answer!!
Click to expand...
Click to collapse
No, that addresses an issue of a device having 5 GHz but losing its use after an update, the a100 never had 5 GHz support, period. The hardware just isn't there. The note is also a newer device, so 5 GHz support is more likely, the a100 is at least a couple years old now, when 5 GHz support was costly and not deemed required, now its cheaper and more cost effective to use existing chips supporting it vs having chips made without it.
And Acer is nothing if not corner cutting cost effective computer builders.
Tapatalked from my HTC DNA - PAC
Is it true that Galaxy Nexus Hardware don't support Bluetooth LE on Android 4.3 like Nexus 4? If not, how to check it supports LE ?
Ashutos1997 said:
Is it true that Galaxy Nexus Hardware don't support Bluetooth LE on Android 4.3 like Nexus 4? If not, how to check it supports LE ?
Click to expand...
Click to collapse
Same here, could someone confirm Galaxy Nexus is now supporting bluetooth smart ?
Just done some web search and found this, which seems to confirm Bluetooth smart support : http://androidtelegraph.com/galaxy-nexus-bluetooth-sig-certification-hints-android-4-3/
But I just want to be sure before buying this : http://www.zephyranywhere.com/products/hxm-smart-heart-rate-monitor/
Regards
No Bluetooth 4.0, the gnex was being recertified for 3.0.
Beamed from my Maguro.
Mach3.2 said:
No Bluetooth 4.0, the gnex was being recertified for 3.0.
Beamed from my Maguro.
Click to expand...
Click to collapse
Oups... you're right. That's bad considering the bluetooth Galaxy Nexus chip is compatible with 4.0 : http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182/2
Wow... Really!? I am blown away by this revelation... The GNexus has BLE hardware (BT 4.0) but the 4.3 update doesn't add compatibility? That is so so crappy...
lahma69 said:
Wow... Really!? I am blown away by this revelation... The GNexus has BLE hardware (BT 4.0) but the 4.3 update doesn't add compatibility? That is so so crappy...
Click to expand...
Click to collapse
Hopefully the devs will be able to hack it
lahma69 said:
Wow... Really!? I am blown away by this revelation... The GNexus has BLE hardware (BT 4.0) but the 4.3 update doesn't add compatibility? That is so so crappy...
Click to expand...
Click to collapse
Apparently the issue is not with the chip, it's with the kernel. In order to have BLE you need to have the kernel bumped up to 3.4. From what I've read there are instability issues on the GNex with 3.4, possibly due to the fact that TI isn't doing anymore work on the OMAP processor line. So unless google figures out a way to release a stable, then we're out of luck. Or if a kernel developer figures out a way, but from what I understand it's a bit of an undertaking to accomplish.
Is it possible for the debs to actually make it work. If it's I would jump on that.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
joedeveloper said:
Apparently the issue is not with the chip, it's with the kernel. In order to have BLE you need to have the kernel bumped up to 3.4. From what I've read there are instability issues on the GNex with 3.4, possibly due to the fact that TI isn't doing anymore work on the OMAP processor line. So unless google figures out a way to release a stable, then we're out of luck. Or if a kernel developer figures out a way, but from what I understand it's a bit of an undertaking to accomplish.
Click to expand...
Click to collapse
Hmm... I hadn't heard any of that info. I guess I just assumed that any devices that have BT 4.0 hardware, and get a 4.3 update, would support BLE. When you are saying 3.4, I assume you mean 4.3? Don't the new stock 4.3 images for the nexus devices come with an updated kernel for 4.3? Hopefully this gets worked out...
Ah... I know what you mean by 3.4 now... You are referring to the kernel version.
There is always a weak link, if the OMAP is really not compatible with Kernel 3.4 then it'll be very hard if not impossible for the devs to fix....
lahma69 said:
Hmm... I hadn't heard any of that info. I guess I just assumed that any devices that have BT 4.0 hardware, and get a 4.3 update, would support BLE. When you are saying 3.4, I assume you mean 4.3? Don't the new stock 4.3 images for the nexus devices come with an updated kernel for 4.3? Hopefully this gets worked out...
Ah... I know what you mean by 3.4 now... You are referring to the kernel version.
Click to expand...
Click to collapse
Yep it's all about the kernel... hmm.
This is a very bad news, because klp will maybe requiring a newer kernel for new functionality or battery management...which meens no more update for gnex. Deception... Come on nexus 5
Sent from my Galaxy Nexus using xda premium
Judge584 said:
This is a very bad news, because klp will maybe requiring a newer kernel for new functionality or battery management...which meens no more update for gnex. Deception... Come on nexus 5
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Buy CyanogenMod will support gnex and will bring CM 11 / 5.0 for gnex
joedeveloper said:
Apparently the issue is not with the chip, it's with the kernel. In order to have BLE you need to have the kernel bumped up to 3.4. From what I've read there are instability issues on the GNex with 3.4, possibly due to the fact that TI isn't doing anymore work on the OMAP processor line. So unless google figures out a way to release a stable, then we're out of luck. Or if a kernel developer figures out a way, but from what I understand it's a bit of an undertaking to accomplish.
Click to expand...
Click to collapse
Well, that was my speculation earlier in the thread :]. Thing is that a module could be included in whatever kernel there is. Google Glass for instance uses the same chip and CPU as GN, but was certified for BT 2.1 only in April. Why are they're not bringing BLE on there is a mystery, because it's certainly a type of device which would benefit a lot from that functionality.
It may also be that Broadcom doesn't release the proper support for it. Chip vendors can be show stoppers because of politics (they develop new chips all the time, remember).