Related
The New BT STACK(BCHS) has Release at 31 May 2006 , Can anybody find the setup file ?
the old BCHS ver.107 ( 1107 ) , See:
O2 MINI NEW BLUETOOTH STOCK.
The New one is ver.1740 , Description :
Release Description BCHS 15.1.0
Thanks !!
ps: Sorry !!! It's " Stack " , Not " Stock " ...
The Release File contains:
The 15.1 serie contains the following new features:
- The Phone Book Access Profile has been added
- The device side of the HID-profile has been added
- In the AV, FTC, OPC, BPP, CM and SC it is now possible to cancel an
action started by:
AV_CONNECT_REQ
FTC_CONNECT_REQ
OPC_CONNECT_REQ
BPP_CONNECT_REQ
CM_SDC_SEARCH_REQ
CM_SDC_UUID128_SEARCH_REQ
SC_BOND_REQ
Besides the new features a number of bugfixes has also been addressed in this release.
Below a short description of the content of the bugfixs that has been solved in this release is listed.
Release 15.1.0
--------------
Introduction
------------
The 15.1.0 release contain a number of bugfixes and improvments as liste
above.
And more old Release.......
link doesnt work....
Link brings up error "you dont not have the authorization to download this content"
I am very interested in seeing this!
It is a stack, you ...!
Hey Chatty,
i'm interested to see whether or not this updated version of the bluetooth stack (that i'm already using) has any of the bugs fixed that the original had.
If you looked at the old stack and the amount of attention it got maybe you should just let people follow what interests them and if you dont like it ... DONT READ IT!
People have the right to read what they want and say what they want! But they should be able to do it with out have someone personally attack them, ESPECIALLY IF THAT PERSON HAS NOTHING CONSTRUCTIVE TO ADD TO THE CONVERSATION!
Anyway
enjoy your night Chatty and relax a little!
we love ya anyway
Nice edit Chatty!
The Release File :
The 15.1 serie contains the following new features:
- The Phone Book Access Profile has been added
- The device side of the HID-profile has been added
- In the AV, FTC, OPC, BPP, CM and SC it is now possible to cancel an
action started by:
AV_CONNECT_REQ
FTC_CONNECT_REQ
OPC_CONNECT_REQ
BPP_CONNECT_REQ
CM_SDC_SEARCH_REQ
CM_SDC_UUID128_SEARCH_REQ
SC_BOND_REQ
Besides the new features a number of bugfixes has also been addressed in this release.
Below a short description of the content of the bugfixs that has been solved in this release is listed.
Release 15.1.0
--------------
Introduction
------------
The 15.1.0 release contain a number of bugfixes and improvments as liste
above.
Bugfixes
------------------
D-0095 Fixed problem in ./common.h with endian dependend macro's for
bytestream manipulation. The macros have been made endia
independent.
D-0307 Linux: Using BCHS in the Linux Kernel mode, the scheduler did
not correctly clean up the timed event queue upon shutdown.
D-0419 Linux: Using BCHS in the Linux User mode, the scheduler did
not correctly clean up the timed event queue upon shutdown.
D-0578 Linux: In the Linux kernel port, it must be possible to
specify an alternate panic handler, such that special
platform/application specific handling can be performed
instead of the default BCHS sched_panic() function.
D-0717 Linux: The Linux userspace USB driver must support the new
kernel-driver interfaces for Reset and EnterDFU.
D-0797 Linux: The Linux kernel USB driver supports a
non-documented customer-supplied "extra" interface to augment
the standard USB driver
D-0804 Linux: It is now possible to setup maximum number of
outstanding ISOC frames in the USB driver at runtime, instead
of having to define it at compile time.
D-0805 Linux: The Linux kernel USB driver is slow due to inefficient
URB usage pattern and too many payload copying.
D-0863 Linux: The Linux kernel driver will sometimes crash when being
unloaded.
D-0879 Linux kernel: Crashes/oopses have been seen to occur when
loading/unloading the USB driver multiple times.
D-0888 Linux: If the Linux kernel BSL (PAN) network interface was
loaded, but not configured (ie. not connected), the module
would crash on unload/unregister.
D-0901 Linux kernel: The USB driver must support the UsbDrv_Reset()
API call required by the USB interface.
D-0904 Linux kernel: The USB driver keeps too much track of the
outstanding URBs.
D-0959 All demo applications: Added "-A <bluetooth-address>" command
line argument for all demo applications. This option can be
used to skip device inquery in the demo application.
D-1017 Linux: The verify_area() Linux kernel API function has been
deprecated since at least Linux version 2.6.11 and completely
removed from at least version 2.6.14. The function access_ok()
should be used instead.
D-1082 Fixed problem in ./common.h with endian dependend macro's for
bytestream manipulation. The macros have been made endia
independent.
D-1100 OBEX/Common: Corrected miscalculation of unicode string length
D-1107 Linux USB: Fixed a problem in the Linux USB driver where a
transfer buffer was allocated based on a predefined value
instead of the value defined by the device
D-1155 BPPS: Support for mandatory features has been completed,
including status and referenced object channel has been
included.
D-1235 Linux USB: Fixed a problem in the Linux USB driver where URB's
could be leaked.
D-1238 Linux: The USB-driver can now handle a warm-reset so it is
possible to use USB ROM devices.
D-1239 Bootstrap: now possible to also use bootstrap when using USB.
A new Library is created for use with USB. The library name
is bccmd_boot_strap_usb.lib for windows and
libbccmd_boot_strap_usb.a for Linux. The old
bccmd_boot_strap-library still contains the serial boot strap
implementation.
D-1254 HFG: Disabling of status indicators using the AT+CMER is now
implemented.
D-1259 HFG: The actual status indicator values are now stored in the
HFG separately for each connection.
D-1265 Linux: The default BCHS sched_panic() now generates a kernel
stack dump when using the Linux kernel BCHS port.
D-1269 In BCHS version 15.0.0 the OBEX profiles writes the total file
size erroneous. This has now been fixed
D-1277 PAN DEMO: updated to prompt user for passkey instead of using
a fixed value.
D-1284 SBC: An overflow could occur in the decoded SBC sound
D-1432 samples, if the sound was played with maximum amplitude at the
time of encoding
D-1293 OBEX/FTC,OPC: The FTC and OPC profiles has had a general code
cleanup.
D-1297 OBEX/OPC: The prim->bodyType in the opcPutReq library function
is only assigned a value if the bodyType in the lib call is
not NULL. I.e. the bodyType contains garbage when arriving in
OPC profile resulting in a crash when OPC pfree it. This has
when fixed so the library set it to NULL.
D-1298 BPP: Could not initiate two requests on different channels at
the same time. This is now fixed.
D-1299 HFG: If the connection was disconnected during a service
search, it was not possible to initiate any further connections
from the HFG since service search resources were not released.
D-1300 Build: Problem compiling without
EXCLUDE_EXCEPTION_HANDLER_MODULE but with ENABLE_SHUTDOWN has
been solved.
D-1305 JSR82: Cancelling an inquiry through the JSR-82 layer led to a
delayed access violation in some cases, because a timed event
was not cancelled. The timed event is now removed when an
inquiry is cancelled.
D-1306 HFG: Fixed problem with Ring request
D-1310 OBEX/FTP: The FTP client API have been updated so the Get and
Put signal describes the new interface
D-1313 Linux: It is now possible to use bootstrapping when running in
the Linux User to kernel mode split.
D-1329 Changed the page scan mode to HCI_PAGE_SCAN_MODE_MANDATORY.
D-1339 Build: The WIN macro has been replaced by the build-in _WIN32
D-1340,D-1341 macro for windows builds. WIN is no longer needed.
D-1344 AV: Avoided AV forcing link to active in case of sniff request
by remote device.
D-1345 DUNC demo app.: Added menu item for hanging up a call and
updated the AT command call setup sequence
D-1350 SC: The SC module does not called sc_db_write() if the peer
device updates a link link which already exits. This has been
fixed so the sc_db_write() function is called when the link
key is updated.
D-1351 SC: If a peer device initiates a connection while the local
device is in high security mode, the class of device parameter
in a SC_BOND_IND msg is zero. A fixed has been made so this
parameter is valid in this situation.
D-1357 BCCMD: Removed memleak in SetPcmChannel
D-1360 VDP-Demo: SD_IFACEQUEUE added to tasks.c
D-1361 VDP-Demo: Alignment set to 8 byte
D-1364 Optimized the HID parser.
D-1365 HFG: When an incoming connection from a headset is initiated
at the same time of a connect request from the application it
is possible that both connections will fail.
D-1367 VDP demo: In order for properly interfacing the external video
library demuxing functions, BCHS libraries and the demo
application must be built using the same alignment as the
external library alignment. Instructions on how to do so has
been added in the demo description.
D-1371 HFG: Fixed handling of AT+CHLD=? in profile and Demo app.
D-1372 VDP Demo: ScPasskeyResSend updated to use proper result format.
D-1373 JSR82: An ill-behaved, threaded Java program could cause rfcomm
packets from the JSR-82 layer to arrive out-of-order. A message
queue has been added to handle this.
D-1374 VDP-Demo: If multiple media packets were sent in the same l2cap
packet then a temporary buffer was freed, causing an error.
This pfree has been removed.
D-1376 OBEX/OPC: If the OPC put an object which need to be spilt up in
multiple OBEX packets, the OPC is some cases keeps sending the
OBEX headers(name, type length).
D-1379 DUNC demo app.: Added response to port negotiation.
D-1380 CM: Under rare condition the Connection Manager could restore
its local queues when it is not allow to. The consequences of
this are that it can send more than one signal to the lower
layer and in worst case a dead lock could happen.
This has been fixed.
D-1381 JSR82: The inquiry procedure of the JSR-82 layer requests names
for all found devices. This has been changed to only request
names when requested from application layer.
The inquiry is now usable for selectService implemented in
upper layer.
D-1382 TCS: The SDP record of the TCS GW contained an incorrect value
of the protocol descriptor list. This incorrect value
(UUID TCS-BIN) has been changed to the correct value
(UUID TCS-BIN-CORDLESS)
D-1389 BPP: Removed potential memory leak when sending document to
printer, by pfreeing printContent.
D-1410 JSR-82: The inquiry procedure may cause a segmentation fault
if no device names are fetched during this. The event
responsible is now properly cleaned up.
D-1411 HFG-Demo: Cleaned up the handsfree demo application and removed
some macro re-definitions.
D-1416 OBEX/OPC: If the OBEX clients (FTC, OPC, BIPC) is release while
setup an OBEX connection their could go into a state where it
has not possible to make a new OBEX connection. This has now
been fixed.
D-1417 OPC: Removed potential memory leak when putting an object to
the server, by pfreeing the object received by the application.
D-1418 OPS: If an OBEX PUT packet includes a type header the OPS
profile did write an invalid byte into the OBEX PUT packet,
which made the rest of it invalid. This has now been fixed so
an invalid byte is not put into the OBEX PUT packet.
D-1420 HFG: HfgAtCmeErrorSend has been added to the Hfg-lib file.
D-1421 HFG: Library function HfgAtCopsSend now returns the correct
structure.
D-1423 BPP: Added description of docTypeLength and printContentLength
in API.
D-1424 HF: Fixed compilation problem when ADVANCED_HF was deined and
new SCO interface is used.
D-1426 BPPS: Activation issue for the BPPS profilemanager solved.
D-1428 BCSP: Fixed problem in BCSP where it was not possible to
initialise BCSP multiple times.
D-1429 Linux kernel: The USB driver should adjust the SCO packet size
after the VOICE_SETTING in usr_config.h.
D-1435 DUNC: Corrected 'maxMsgSize' assignment in the DUNC_STATUS_IND
primitive
D-1438 Handsfree: Fixed interoperability issue with some car kits that
does not follow HFP specification
D-1440 HFG: Fixed problem with incoming and outgoing connection at the
same time
D-1444 AV: Update of the AV API document so it now also states that
the AV profile supports video streaming
D-1445 AV: The description of the roleType parameter in the
AV_STATUS_IND message was wrong. This has been corrected so
the description matches the parameter
D-1446 HIDH Demo: The second parameter of the
HidhConnectAcceptReqSend(...) call in the HIDH demo is invalid.
D-1447 Handsfree: Updated default values for eSCO connections.
D-1456 AVRCP: Update of AVRCP API description, particularly connection
establishment issues.
D-1457 Build: It is now possible to compile BCHS with the
EXCLUDE_BCHS_L2CA_MODULE and/or EXCLUDE_BCHS_RFC_MODULE
compiler defines.
D-1463 BCHS: BCHS has been updated to support RFCOMM so it may be used
together with the 21d Firmware version
D-1467 AVRCP: Prevented forcing connection out of low power mode when
low power was changed by remote device
D-1473 Build: Problem compiling without
EXCLUDE_EXCEPTION_HANDLER_MODULE but with ROM_BUILD_ENABLE
has been solved.
D-1476 HFG: Transmission of callheld status indicator from the HFG is
added.
D-1477 HFG: Fixed the supported features written in service record.
D-1478 BPP-Client: Added description of
BPP_CONNECT_IND and BPP_CONNECT_RES which was missing in the
API documentation (bchs-api-023_obex_bpp_client_api)
D-1482 HFP: PICS document has been updated
D-1488 Corestack: Fixed an issue where the max_frame_size field of an
RFC_START_CFM contained the locally requested value and not the
negotiated value.
D-1489 TCS-Demo: Fixed the GW part of TCS demo application. The GW did
not respond with an alert message due to an imporperly set
variable.
D-1491 FTS: Added low power mode control.
D-1494 HFG: Updated HFG to mutually exclude RING and audio connections
for HSP according to ESR1 E2112.
D-1500 JSR82: For short local names, the JSR-82 layer would read
outside of the string, due to an incorrect cast. The name is
now copied properly.
D-1501 BPP: Made sure that BPP can be activated in NULL state.
D-1502 BPP: Only perform one SDC attribute search during BPP connect.
D-1503 BPP: Fixed problem with handling channels disconnecting in
random order in BPP.
D-1505 The following two compiler defines is added to usr_config.h:
PAGE_SCAN_TYPE
INQUIRY_SCAN_TYPE
These defines allow the customer to select which Page Scan Type
and Inquiry Scan Type BCHS is using.
D-1506 SAPS: Added Bluetooth address of remote device for incoming
connections to the SAPS_CONNECT_IND.
D-1507 BPP: Removed possibility of getting an incorrect structured
OBEX packet on the BPP Object Channel.
D-1509 TCS: Added support for the Samsung SIT105EW access point in the
terminal part of TCS
D-1515 HF: Updated API document with some missing lib. functions.
D-1516 CM: Added more error code mappings from HCI-error codes to
BCHS error codes.
D-1518 Optimized the HID parser
D-1519 HFG: Updated API document with some missing lib. functions.
D-1521 JSR-82: L2CAP connections may leave remaining data when Java
application is closed. This caused new connections in a new
Java application to fail. This data is now cleared.
D-1524 BPP: Corrected the security setting for BPP Object Channel to
none.
D-1525 Obex/Push App: Removed the references to C-code files in
profile_mangers etc. directories and insert the use of
libraries instead.
D-1526 BPP: Corrected the requested max OBEX packet size for BPP Job
and Status Channel.
D-1527 BPP: Added description of channelId and ConnectionId to
documentation of BPP_DISCONNECT_IND.
D-1530 BPP: Added extra security so BPP only accepts incoming Object
Channel connections from a connected printer.
D-1532 HFG: Fixed handling audio request when signals are crossing
D-1533 SC: The cod is zero in the SC_PASSKEY_IND and SC_BOND_IND in
the scenario where:
A successful bond has been made between dev 1) and dev 2).
If dev 2) debonds dev 1) and dev 1) afterwards initiate a
connection to dev 2) then dev 2) will initiate a new bond
sequence against dev 1) and in this case the SC_PASSKEY_IND
will popup with a cod=0 at dev 1).
This has been fixed now by adding a read to the SC_DB if cod=0.
D-1534 HFG/HF: Fixed error in SCO negotiation if application specified
eSCO parameters
D-1535 Changed default sniff mode parameters to 40 in order to follow
the BT spec.
D-1544 BIP: Optimized the BIP code and removed some bugs.
D-1545 AV,FTC,OPC,BPP,CM,SC: A new feature was been made which allowed
the application to cancel a:
AV_CONNECT_REQ
FTC_CONNECT_REQ
OPC_CONNECT_REQ
BPP_CONNECT_REQ
CM_SDC_SEARCH_REQ
CM_SDC_UUID128_SEARCH_REQ
SC_BOND_REQ
D-1547 OBEX/SYNC: Who header length corrected from (10 to 9) in the
obex-sync-server.
D-1548 The compiler define DEFAULT_LINK_SUPERVISION_TIMEOUT has been
added to usr_config.h.
This allows to adjust the default link supervision timeout for
all new ACL links created.
D-1550 OBEX/SYNC: Who header length corrected from (10 to 9) in the
obex-sync-server.
D-1552 SBC:When the SBC decoder decodes an audio signal, encoded with
max amplitude, the output signal occasionally drops to zero at
the peak values. This has been fixed now by fine tuning the
final scaling boarders.
D-1555 BPP: Fixed converter error in BPP related to getEvent,
getJobAttributes, and cancelJob, so it does not forget the
number zero.
D-1559 BCHS: Removed the use of put_message_in, put_message_at and
cancel_timed_message. These functions are planned to be removed
from the BCHS scheduler in the future (date of removal has not
been fixed yet)
D-1560 FTC: In BCHS 15.0.4 FTC always request the link to go to
ACTIVE mode even if it is already in this mode. This has been
change so FTC only request to go to ACTIVE mode if the link is
not in this mode.
D-1561 BPP: Now possible to cancel a job without getting a
disconnection in BPP.
D-1563 CM: In the situations where a peer device releases its L2CAP
connection before it has been configured, the connection
Manager (CM) could go into a state where it keeps rejecting
incoming connection attempts. This has now been fixed
D-1565 TCS: Lib functions has been updated to use bchs_msg_transport
which makes it more easy to split applications from BCHS.
D-1566 Linux: The library: sc_db-file was not built for Linux. This
has now been fixed.
D-1571 HIDD: The device side of the HID profile has now been
implemented conforming to the specifications.
D-1573 Handsfree: Memory leak when a AT command is not encoded as it
should has been fixed.
D-1576 API document updated with additional description, including
examples of how to use library functions.
D-1577 API documentation is updated with additional information on new
library functions and example on how to use all library are
added.
D-1578 PAN: Now only possible to build PAN for HCI and not RFC,
because PAN is only to be runned on HCI-builds.
D-1579 JSR-82: If the JSR-82 layer received a disconnect from the
remote device on an L2CAP connection while sending data,
it could enter a state where it would stop responding to any
signals sent to it. This issue has been cleared up.
D-1581 Handsfree: The body and the data fields are now switched so
that the contents are according to the API document.
D-1583 Handsfree: Length value of the body and the data fields is now
corrected so that the 0-terminations is also included.
D-1584 HFG: Format changed for CIND response, so that the call_setup
element is closed properly.
D-1585 HFG Demo App: OK is now send after HFG demo app has all +CLCC
results to HF.
D-1587 SDP: The SDP layer now does full comparison for 128bit UUIDS,
allowing searches for non-bluetooth (e.g. JSR-82 Java)
applications.
Note: This fix has only been applied to HCI builds.
D-1588 AV: When unregistering the service record when running as
SINK the wrong service record was used. This has now been fixed
D-1595 BCSP: Added init of timer ID to avoid cancelling already
expired timers
D-1597 HF: Fixed problem with string handling for +CLCC. and +CNUM.
D-1600 obex/fts: The connection-ID was wrongly set to 0xFFFFFFFF when
a connection was terminated. This has now been fixed so the
correct connection ID is returned.
D-1605 Handsfree: In the unsolicited +CLIP message send form the HFG a
needed space is added after the ":" so that the message now is
+CLIP: xx, where xx is a number.
D-1606 Handsfree: In different unsolicited message send form the HFG a
needed space is added after the ":" so that the message now
is +CLIP: xx, where xx is a number.
D-1608 Handsfree: The support AT-functions are corrected so that they
are according to the AT specification format.
D-1611 Handsfree: The errors in the function HfSendHfCmeeInd have been
corrected. It is not able to handle a space after :
(example:+CME ERROR: 32) and the digits send in the error code
are not mixed up any more so that a received code is send
corecltly to the app.
D-1613 Handsfree: Implemented signal interface is corrected so that
COPS function will work in HF and HFG API is updated for
HFG_COPS_RES.
D-1614 Linux kernel: The USB driver should have the functionality to
bring the interface into DFU mode.
D-1615 Changed default sniff mode parameters to 40 in order to follow
the BT spec. in the
bchs-api-005_connection_mgm_api documentation
D-1618 HF: Function HfSendClccInd is now able to handle space after :
D-1620 Linux: The userspace part of the USB driver does not support
entering DFU mode or USB reset.
D-1622 Phone Book Access Profile is implemented according version 1.0
of the specification.
The profile has two modules:
PAC is the client side e.g. Car kits
PAS is server side e.g. Mobile phones.
D-1628 BCHS has now been updated to support the BC3MM AV-router
v1.2.2 solution.
D-1630 SPP: Made API for changing low power mode on SPP connections
D-1632 SBC: The SBC decoder has undergone a minor optimization round
to improve the general decoder MIPS performance.
D-1634 CM: If the Connection Manager(CM) receives an incoming L2CAP
connection while the local message l2cap_connect_accept_req is
stored on a local queue, the CM will reject the incoming L2CAP
connection.
This has been changes so if a l2cap_connect_accept_req message
is stored the incoming L2CAP connection is also stored. In this
way the CM will not reject it.
D-1636 BPP: A cancel connect attempt can no longer result in a
BPP_CLOSE_SEARCH_IND.
D-1637 BPP: Made sure that the abort timer is cancelled if a
disconnection happens simultaneous.
D-1641 BPP: Fixed problem with uninitialised memory when using Object
Channel.
D-1642 FTS now sends CmModeChangeReq (for LINK_STATUS_CONNECTED)ONLY
once on rx of CM_DATA_IND while NOT in LINK_STATUS_CONNECTED
and obex is connected.
D-1644 FTS now sends CmModeChangeReq (for LINK_STATUS_CONNECTED)ONLY
once on rx of CM_DATA_IND while NOT in LINK_STATUS_CONNECTED
and obex is connected.
D-1647 Linux: The Linux userspace UART driver now correctly perform
the pthread shutdown sequence.
D-1648 In BCHS 15.0.5 FTC will request the link to go to ACTIVE mode
even if it is already in this mode. This only happens if FTC
receives a FTC_CANCEL_CONNECT_REQ in connected state.
This has been change so FTC only request to go to ACTIVE mode
if the link is not in this mode.
D-1649 Linux USB: A memory leak has been found in the Linux userspace
USB driver in the UsbDrv_Rx() function, where the rx-queue
element itself was not freed after the data has been send to
the stack.
D-1655 Linux user: The USB driver does not use the correct pthread
shutdown sequence.
D-1659 PAC: Added handling for low power mode and cancel connect.
D-1664 HIDH: solved free of non allocated data
D-1665 SPP Demo App: mapping between client and instance number made
more intuitive
D-1672 SAP: Updated Service record for SAP server to be compatible
with WinCE devices
D-1673 FTC: FTC accidently uses more than one timer to control
lowpower. This has been fixed so FTC only use one timer to
control this.
D-1674 HIDH: When calling HIDHConnectReqSend(..) with SdpInfo as a
NULL pointer undefined Memory access is read. This has now been
fixed.
D-1677 HFG: New signal "HFG_STATUS_INDICATOR_SET_REQ" is created to
enable the application to update the actual status indicator on
all link at the same time and in any state of the HFG.
D-1679 AV: Av app. will now receive a negative connect confirm also
when a cancel connect arrives too late to make actual cancel -
when the connection establishement is done but has not yet been
reported to app.
D-1680 An incorrect offset calculation that caused searches for more
than one 128 bit UUID to fail has been fixed.
Note: This fix has only been applied to HCI builds.
D-1681 HIDH: When HIDH luses the connection and should automatically
reconnect. If the reconnect fails, a HIDH_CONNECT_CFM is send
to the application instead of a HIDH_DISCONNECT_IND. This is
Fixed.
D-1682 HIDH: A problem in the HIDH package fragmentation routing which
did not work for packages larger than the MTU size has been
fixed.
D-1685 OBEX: Optimize the OBEX profiles so the clients release the
connection and the servers send a response code with error, if
the peer device sends an OBEX packet larger than agree on.
D-1688 TCS: Doing shutdown the tcs_deinit function did not pfree the
payload in a CM_L2CA_CONNECTIONLESS_DATA_IND_T message, causing
a potential memory leak. This has now been fixed.
D-1691 HIDH: Problems with Connect Accept and Reconnect Flag and
Virtual Cable Flag are True and Normally Connectable Flag is
False. This has been fixed.
D-1694 HIDH: Fixed a memory leak in HIDH which occured when packages
bigger that the MTU size was send. The user payload was then
not free'ed. This is now free'ed.
D-1704 OBEX documentation: Added connected state to the sequence
overview diagram.
D-1740 CM: In BCHS 15.0.6 TCS_IFACEQUEUE were hardcoded into the
Connection Manager (CM). If TCS_IFACEQUEUE were removed from
the bchs_task.h bchs could not compile.
This has now been fixed.
quite list there! will be interesting to see what the possibilities for the magician shall be!
Thanks for the heads up and i look forward to reading more
now to wait for the cab file...
The most important question for me: Will the modem work now?
Good!
Only two questions:
1) When it can be downloaded? From where?
2) That HUGE list of improvements it's really confusing. What is this new stack going to do respect the previous? It's worth install it?
Really thanks to people like wensonlau that discover interessant unpgrades to the magician
Cheers, MocciJ
still no working download to this hotly anticpated release?
What a pity... no one got access.
Was hoping this would make my Magaician work better with my Pioneer Bluetooth head unit....damn dissapointed it hasn't emerged.
UP
where?
I didn't say, I uploaded it. I just meant to put this thread to the top.
Can Anybody please tell me if this works fro Prophet (Xda neo), too ?
I have some Problems with my HT-820....
@meisterlampe2000: just try the older version and you'll know. Or just read the thread about the old version. How to find it? Use the SEARCH function!
SO kind of you !
I`ve read everything now, didn`t expect a different answer from you !
I hope to find a Link to that new Stack soon - Would be nice to listen to Music withoput interruptions.
THX
Couldn't help just being the first;
Over the wire version just appeared on my A101
Version 2.1.8 - February 16th, 2011
External keyboard layouts: various country layouts are now supported using Settings > Language and keyboard > Select external keyboard layout setting (qwerty us/uk, azerty french, qwertz deutch, latin america spanish, russian, japanese).
Proxy: http proxy settings have been enabled for the browser in Settings > Wireless & network > wifi proxy settings.
Network shares: introduce an option to enable/disable network share scanning per Wi-Fi Access Point in Wi-Fi authentication dialog box
Battery: improve robustness of battery charge status for hard drive based A70it
Sound: fix sound level saturation causing loss of audio when playing on speaker
Music: fix some MP3 files have bad sound after seeking
Video: make some high level H264 HD files play correctly
Video: fix black screen on video player resume from suspend for MPEG4 files
USB host: fix NTFS UTF8 support
Wi-Fi: fix network disabled occurring after several suspend/resume loops
Wi-Fi: prevent false state information reported when authenticating/enabling Wi-Fi
Multimedia library: avoid deletion of multimedia files happening sometimes on SDCard
nice
any information about better flash support?
Nice very nice!
czesiu said:
nice
any information about better flash support?
Click to expand...
Click to collapse
From Bragon on archosfans.com:
"We are still continuing the long certification process with a scaling partner of Adobe going through all the 2200 tests. Note that the flash plugin that will be used is the one available on the android market. Acceleration is provided outside the plugin. We have now a good user experience on the internal experimental firmware that we use for the certification. All these modifications will be made available soon in a 2.2.x firmware release."
vertig0730 said:
From Bragon on archosfans.com:
"We are still continuing the long certification process with a scaling partner of Adobe going through all the 2200 tests. Note that the flash plugin that will be used is the one available on the android market. Acceleration is provided outside the plugin. We have now a good user experience on the internal experimental firmware that we use for the certification. All these modifications will be made available soon in a 2.2.x firmware release."
Click to expand...
Click to collapse
http://forum.archosfans.com/viewtopic.php?p=328657#p328657
I'm find the wifi improvements pretty useful; after a couple of hours of use it's very stable indeed.
A welcome change over the last firmware.
Upgrading now. Hope this will indeed solve my WiFi issues!
i use this firmware for testing
the keybaord layouts are very great
it is possible to use azerty touch with qwerty kb
cajl said:
i use this firmware for testing
the keybaord layouts are very great
it is possible to use azerty touch with qwerty kb
Click to expand...
Click to collapse
Before I decide to upgrage this new firmware. Please kindly let me know.
In Setting -> Language and keyboard -> Select external keyboard layout menu. Have Thai (ไทย) language yet ?
Thank you in advance.
jakkrith said:
Before I decide to upgrage this new firmware. Please kindly let me know.
In Setting -> Language and keyboard -> Select external keyboard layout menu. Have Thai (ไทย) language yet ?
Thank you in advance.
Click to expand...
Click to collapse
Nope don't think so. I see some russian character and some chineese But not the ones you post in your question.
wdl1908 said:
Nope don't think so. I see some russian character and some chineese But not the ones you post in your question.
Click to expand...
Click to collapse
Thank you very much for your quick reply.
I have problem with external usb keyboard. I could not type in Thai language.
Hope Archos Developer team will add Thai language for external keyboard layout in next version.
Just finished installing the new firmware... I will be able to test the wifi proxy when i get to the office.
I've been looking for this....
Sent from my A101IT using Tapatalk
minxwin said:
Just finished installing the new firmware... I will be able to test the wifi proxy when i get to the office.
I've been looking for this....
Sent from my A101IT using Tapatalk
Click to expand...
Click to collapse
Sorry about your (our) luck. Proxy does not work.
Yah! Just tested the proxy settings. I can input the proxy address and save it but unable to enable it. Even thou I checked the "Enable Proxy" then save.
The Proxy module will close but when I checked again the "Enable Proxy" is not enabled again.
Whats up with this?
Anyone know how to fix this???
As per flash thread. If the acceleration is handled by archos firmware why the heck can archos not include the tweaks now and include flash when certified.
Keeps archos in good books with adobe and we get acceleration.
Seems like an ideal solution seeing as certification to include flash is taking months
mr-mac said:
As per flash thread. If the acceleration is handled by archos firmware why the heck can archos not include the tweaks now and include flash when certified.
Keeps archos in good books with adobe and we get acceleration.
Seems like an ideal solution seeing as certification to include flash is taking months
Click to expand...
Click to collapse
Really? You think Adobe would allow them to put it in their when we can get Flash from the market? Your kidding right?
Flippin camera!
With with the camera flipped=no mod in the local.prop file, the camera image now rotates backwards as you rotate the tablet. Anyone else?
no video preview / App movies with rotten t
Working great on A70 but I think one of my favorite apps stop working. The movie app with rotten tomatoes wont play any of the preview videos.
"Sorry video cannot played" can some one corfirm that and if only me..... any solutions? Thank you.
Btw IMBD video previous are working find.
Can anyone confirm if the 2.1.08 FW fixed some of the USB host issues?
I should mention I have an A101 and a 70it 8G.
I had rolled back to 2.1.71 because of wifi issues on both devices associated with 2.2.03 and .04, I had hoped the rollback would also resolve some USB issues, no joy there.
Hello XDA developers,
As you know, Atmel maXTouch touchscreen controllers are used in a large percentage of Android phones and tablets out there.
I wanted to let you know that the latest patches for the official Atmel maXTouch Linux driver are available on GitHub. This will allow you to get the latest up to date changes before they make it into the mainline kernel.
On GitHub, search for user "atmel-maxtouch"
Happy hacking
Best regards,
Sherif
Product Marketing Manager - Atmel
thank u for ur valuable information, well can u pls post what are the latest changes and updates. that will help the devs much more.
Hi showlyshah,
The latest updates include the following:
- Support for Atmel's mXT224E, mXT768E, and mXT540E chipsets
- Support for both protocol A and protocol B reporting
- Support for kernel 3.0 in addition to kernel 2.6.35
More details are available on GitHub in the release notes.
Regards,
Sherif
Is https://github.com/atmel-maxtouch the correct URL?
Unfortunately, if it is, the drivers in this repository are structured completely differently from the ones included in many vendor source drops, and unfortunately this causes great negative impact on their usefulness.
See, for example:
https://github.com/Entropy512/linux_kernel_sgh-i777/tree/master/drivers/input/touchscreen - This includes the mxt224 drivers as implemented by Samsung on their device (Galaxy S II)
https://github.com/atmel-maxtouch/linux/tree/master/drivers/input/touchscreen - mxt224_u1.c is completely missing, indicating that the driver here is incomplete or structured very differently from the one used by Samsung, making it very difficult to use. Also, the few files there that do pertain to Atmel MXT such as atmel_mxt_ts.c in there appear identical to the mainline Linux repo.
Entropy512 said:
Is https://github.com/atmel-maxtouch the correct URL?
Unfortunately, if it is, the drivers in this repository are structured completely differently from the ones included in many vendor source drops, and unfortunately this causes great negative impact on their usefulness.
Click to expand...
Click to collapse
But it's not Atmel who are to blame. Atmel are doing a great job working directly with upstream so that all the users of mainline linux can benefit. I have been using the drivers from the vanilla kernel for quite a while on both my tegra tablet (with chromium kernel) and galaxy s2, and they work just fine, supporting multitouch in xorg in ubuntu.
The problem is OEMs who do crap like hardcoding/hacking drivers instead of using platform data, use machine-specific hacks, custom interfaces and a lot of copy-paste. That's the essence of modern consumer electronics business - no one cares for quality, only about releasing early.
Entropy512 said:
Unfortunately, if it is, the drivers in this repository are structured completely differently from the ones included in many vendor source drops, and unfortunately this causes great negative impact on their usefulness.
See, for example:
linux_kernel_sgh-i777/tree/master/drivers/input/touchscreen - This includes the mxt224 drivers as implemented by Samsung on their device (Galaxy S II)
atmel-maxtouch/linux/tree/master/drivers/input/touchscreen - mxt224_u1.c is completely missing, indicating that the driver here is incomplete or structured very differently from the one used by Samsung, making it very difficult to use. Also, the few files there that do pertain to Atmel MXT such as atmel_mxt_ts.c in there appear identical to the mainline Linux repo.
Click to expand...
Click to collapse
I think you're looking at the unchanged mainline branch: the driver releases are as tags.
The advantage of these drivers is that they are generic for all chips in the maxtouch series. mxt224_u1.c is just a renamed atmel_mxt_ts.c, it contains lots of mxt224 specific configuration and it's unlikely that it will go upstream.
You will also find some user-space tools for extracting config files in a format the kernel driver can load, on the same github account.
Missed the tags, thanks for the additional info!
I'll look into maybe playing with this when ICS time rolls around. It's getting late in the game to do a major driver rework on the Gingerbread kernel I maintain.
sherifhanna said:
Hi showlyshah,
The latest updates include the following:
- Support for Atmel's mXT224E, mXT768E, and mXT540E chipsets
- Support for both protocol A and protocol B reporting
- Support for kernel 3.0 in addition to kernel 2.6.35
More details are available on GitHub in the release notes.
Regards,
Sherif
Click to expand...
Click to collapse
Hi Sherif,
I found the project in Github, but am not able to find the the release notes. Does this driver support the Atmel mXT336S at this time?
Thank you
Hi omaha64,
Support for mXT336S is in progress.
Regards,
Sherif
Question,
I am trying to back-port the 2.6.35.7 driver to 2.6.32. I have mostly succeeded, but probe() fails because of missing platform_data. Digging through the driver code, I found the platform data structure in include/linux/i2c/atmel_mxt_ts.h:
Code:
struct mxt_platform_data {
unsigned long irqflags;
u8(*read_chg) (void);
};
So I assume that in my board file (where my i2c_board_info arrays live) I would want to create a static instance of the above struct and store a pointer to it in the .platform_data member of the i2c_board_info struct, right? But what is the preferred initialization, and what is read_chg supposed to actually do? What's the consequences of just setting it to NULL? (I know it won't crash because the driver checks it before calling it)
Need atmel mxt224 driver for Windows embedded compact 7
sherifhanna said:
Hello XDA developers,
As you know, Atmel maXTouch touchscreen controllers are used in a large percentage of Android phones and tablets out there.
I wanted to let you know that the latest patches for the official Atmel maXTouch Linux driver are available on GitHub. This will allow you to get the latest up to date changes before they make it into the mainline kernel.
On GitHub, search for user "atmel-maxtouch"
Happy hacking
Best regards,
Sherif
Product Marketing Manager - Atmel
Click to expand...
Click to collapse
Hi,
Can you please send me the multi touch driver for ATMEL MXT224(Stream interface PDD layer) for Windows Embedded compact 7.
Thanks in Advance,
Rag
Android Driver Initialization
Hi,
I would like to use MaxTouch mxt224 on a TI am335x-evm board running Android ICS, I'm looking for documentation on how to initialize mxt224 driver from board's configuration file. Can someone help me?
Thanks.
ceskobassman said:
Hi,
I would like to use MaxTouch mxt224 on a TI am335x-evm board running Android ICS, I'm looking for documentation on how to initialize mxt224 driver from board's configuration file. Can someone help me?
Thanks.
Click to expand...
Click to collapse
.
I don't know if there's such documentation to tell you how to initialize. At least a sample exists; look here:
arch/arm/mach-exynos4/mach-nuri.c
The values in "mxt_init_vals" come from Atmel's mxt224 datasheets/manual, so you'll have to find those. I would be surprised if you could not find these by Googling. When I was trying to get the mxt224 to work on an Omap4 board, I had to hack up the driver a little to handle the reset going to the IC, and to handle the /READY line from the IC to the host. Also, for ICS, you will need to have an IDC file in your root file system. Just Google for "Android Input Device Configuration File" (I'm new here and cannot post links yet).
Without that IDC file, Android considers the touch device to be a pointing device (like a mouse).
Good luck
Atmel Mxt768e Driver details
Hi Sherif & All,
Can you please share the atmel MaxTouch mxt768e driver link, I would also request you to share the driver which has the implementation for fIrmware upgrade.
Thanks,
Balaji S
Is there some place I can learn to understand and modify these? I've never done driver development before. Before I waste any time with this, can someone confirm if the input lag in most devices is because of filtering in the driver or because of the Atmel hardware?
KurianOfBorg said:
Is there some place I can learn to understand and modify these? I've never done driver development before. Before I waste any time with this, can someone confirm if the input lag in most devices is because of filtering in the driver or because of the Atmel hardware?
Click to expand...
Click to collapse
I don't think you'll be able to find a single place that describes the driver. Luckily, these drivers are small, the mxt224 is just a single C file. I've looked at the mxt224/mxt336, so the following info is specific to those. Some high level info for you to get started:
* The driver allows the exchange of "objects" between the touch IC and the host processor. To understand what the objects are, you'll need to find the datasheets/manual for the chip you're using. Just try Googling for it. Objects from the host to the IC are typically configuration data, and objects from the IC are probably touch data
* In the case of the mxt224/336, the driver needs the I2C driver
* The driver has a structure that needs to be setup from your board file (example arch/arm/mach-omap2/board-???.c). This structure has some configuration data needed by the driver
* Typically, there's a reset line that has to be pulled high on the board. May need pinmuxing to set the functionality of the pin correctly.
* The IC will also have a /CHG line that will go low when it has data to send to host. You will need to set up pinmuxing for this pin as well.
* The driver has an interrupt routine handling the /CHG line. When a touch/drag happens, objects will be sent to the driver to process. The driver formats the data and forward that up to the user space via the input subsystem.
* If you're doing this for Android, you'll need an .idc file in your root file system. Info: {link removed because I'm new. Just google Android IDC }
* The driver will look for a config file in /system/vendor/firmware, upon starting up
I can't comment too much on the lag you're talking about because I don't know the nature of the lag you're seeing. But I can tell you that the Atmel touch IC needs a "tuning" process where the internal parameters have to be adjusted to operate properly.
If you find more info on this subject, please post it here.
omaha64 said:
I can't comment too much on the lag you're talking about because I don't know the nature of the lag you're seeing. But I can tell you that the Atmel touch IC needs a "tuning" process where the internal parameters have to be adjusted to operate properly.
If you find more info on this subject, please post it here.
Click to expand...
Click to collapse
The "lag" is because the touchscreen does not recognise fast taps. You must press and hold your finger on the screen for several milliseconds before it actually recognises a touch. If it was purely a latency, then even a fast tap would be recognised after a delay. In this case, only a continuous press of a minimum duration is recognised. This makes the screen unresponsive and useless for games that need taps.
Is this something that can be resolved in the driver? I have a feeling this is coded in the firmware blob that gets uploaded to the touchscreen on initialisation.
KurianOfBorg said:
The "lag" is because the touchscreen does not recognise fast taps. You must press and hold your finger on the screen for several milliseconds before it actually recognises a touch. If it was purely a latency, then even a fast tap would be recognised after a delay. In this case, only a continuous press of a minimum duration is recognised. This makes the screen unresponsive and useless for games that need taps.
Is this something that can be resolved in the driver? I have a feeling this is coded in the firmware blob that gets uploaded to the touchscreen on initialisation.
Click to expand...
Click to collapse
I believe that if the issue you're describing is due to the IC's noise rejection algorithm, then you may be able to alter that in the driver. There are params in the chip such as number of valid ADC samples for the touch to be recognized as a true touch, that you can play with. But I don't know if you can change these parameters on the fly, or has to be done at start up. I haven't played with these params. See if you can grab hold of a "Protocol Guide" for the touch controller that you're working with. That shows all the params that you can change. In fact, you may be able to alter some of these params without having to touch the driver; search for mxt_app in github. I've used mxt_app to load configuration and change T9 object before, but that's the extent of my use of it.
Thanks for your help. Time to start reading. Some of the mach-* initialisation params can be changed at runtime such as the Vitalij value.
What is the real world best case input latency of these controllers? Can the Galaxy S2's touchscreen actually be made as good as the iPhone 5 or are the iPhone controllers simply superior?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Android 4.1.1 OS, Google Play Store pre-installed;
Build in Bluetooth
Wifi 802.11 b/g/n
Rockchip RK3066 Dual core, up to 1.6Ghz, Quad core Mali400 GPU
Support XBMC
Aluminum Case
Dimensions: 3.82 in x 1.54 in x 0.39 in (9.7 cm x 3.9 cm x 1.0 cm)
Weight: 1.41 oz (40 g)
Operating Language: South Africa Dutch, Amharic, Indonesian, Catalan, Czech, Danish, German, English, Spanish, French, Croatian, Italian, Latvian, Lithuanian, Hungarian, Malay, Dutch, Dona-Norwegian, Polish, Portuguese, Romanian, Slovak, Slovenian, Finnish, Swedish, Swahili, Tagalog, Vietnamese, Turkish, Zulu, Greek, Bulgarian, Russian, Serbian, Ukrainian, Hebrew, Arabic, Farsi, Hindi, Thai, Korean, Japanese, Traditional Chinese, Simplified Chinese
Support OTG
Supports external 3G network card
Support UBS HDD, up to 2TB
Support some USB camera, video (eg. with Skype)
Support Wireless Keyboard/Mouse 2.4GHz
Audio Formats: MP3 / OGG / WMA / WMAPRO
Video Formats: MKV, TS, TP, M2TS, RM / RMVB, BD-ISO, AVI, MPG, VOB, DAT, ASF, TRP, FLV etc. full formats
Video Codecs: Mpeg 1 / 2 / 4.H.264, VC-1, Divx, Xvid, RM 8 / 9 / 10, VP6
Picture Formats: JPEG
Subtitle Formats: SubRip [.srt]
Output Resolution: 1080P
HDMI: 1.3 and 1.4
USB: USB 2.0 + Mini USB
Video Output: HDMI
Audio Output: HDMI
Other Interface: 1 x HDMI interface / 1x USB interface / 1x OTG interface / 1x Expansion card interface / 1x Mini USB interface
Power Input: 5V 2A
Android Market Download: Yes
Compatible Application: Youtube / Facebook / Google play
Packing List:
1 x Google TV player
1 x 5V 2A EU plug adapter
1 x HDMI cable (20cm)
1 x OTG cable (10cm)
1 x USB cable (60cm)
1 x English user manual
ROM
[2012-11-29] iMito_MX1_V411_121129 Stock Firmware
how to root?
új firmware telepítése (HU)
hogyan rootoljuk? (HU)
[2012-12-13] iMito_MX1_1080P_V411 Beta Firmware rooted
[2012-12-22] Finless ROM 1.5 rooted
MX1 firmwares collection: http://goo.gl/ki6We :good:
How to install firmware?
(source)
Download a firmware (example from http://goo.gl/ki6We)
Download the Rockchip USB driver: RockusbDriver.rar
Download the Flash Tool: flash tool.rar
Installation the Rockchip USB Driver:
You should connect your MX1 to your PC or laptop (note: you must connect the OTG port, not DC 5V charaging port).
Open MX1 settings:
USB - click "connect to pc"
developer options - click "USB debugging"
Storage - click "mass storage"
So your MX1 will recognize your PC or laptop, an installation interface will pop up.
See screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=1635906&stc=1&d=1357914922
Click "Browse" button to select the corresponding system, according to the actual situation of the drive path.
Click on the "Next" button, follow the instruction in the picture, and the installation has been done.
See screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=1635907&stc=1&d=1357914922
Open your download tool "flash tools\RKBatchTool.exe", and choose "update.img".
Then the screen will appear the picture below.
And choose the pre-downloaded new firmware update, follow the picture instruction.
See screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=1635908&stc=1&d=1357914922
Use the USB to micro USB cable to connect your PC and TV (note: you must connect the OTG port, not DC 5V charaging port).
Then open your MX1settings: Settings - Storage - (Menu) USB computer connection - Mass Storage
See screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=1635909&stc=1&d=1357914922
See screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=1635913&stc=1&d=1357914922
Close MX1 setting: settings - developer options - delete "USB debugging".
See screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=1635914&stc=1&d=1357914922
When all of settings you have done, you will see your "flash tools\RKBatchTool.exe" as follow, the tool will recognize MX1 and the purple light will turn on.
See screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=1635915&stc=1&d=1357914922
The last step is to click "update" button.
If all went well, the green light will turn on, you have updated MX1 successfully!
See screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=1635917&stc=1&d=1357914922
After you finish the update successfully, you can check "Setting" - "My device", the build number will change...
The most important: After you flash this firmware, and next time, when we release new firmware, you don't need to flash in this hard way, you can just copy the firmware *.img file, and rename it to "update.img" and paste it to your Micro SD Card, insert the micro SD card to iMito MX1 and then connect MX1 with TV, the system will inform you "there is a new firmware update detected, and if you want to update", just click "yes", and the flash will go by itself.
So enjoy your new firmware, any questions,please feel free to report to us. :good:
Peripherals
Android Control App for MX1/MX2
You can control the iMito with an Android phone.
http://blog.geekbuying.com/index.php/2013/01/11/imito-mx1-imito-mx2-cell-phone-control-app-share/
Product reviews and others
iMito MX TV BOX Review by geekbuying
iMito MX1 - Disassembley and short Test
http://blog.sancho.hu/2013/01/imito-mx1-android-mini-pc.html (HU)
http://pdafanclub.hu/?p=7333 (HU)
Here is a Google+ community where we discuss some tricks and tips, apps and games, feel free to join!
http://goo.gl/Oliw7
ArmTvTech forum:
http://www.armtvtech.com/armtvtechforum/viewforum.php?f=76&sid=8fd1fe8544bfe2a77ae15593a091d247
Q/A
[Q:] When you power OFF device... How do you turn it back ON?
[A:] Ctrl+Alt+Del works on most keyboards, and wireless also. :good:
[Q:] What is the difference between MX1 and MX2?
[A:]
MX1: metal case - MX2: plastic case
MX1: better heat dissipation - MX2: better wifi signal
Both have different Bluetooth chips. Both work on all current ROMs. (source)
[Q:] My stick will not clock above 1.2 GHz, where is the 1.6 GHz?
[A:] In fact it IS a 1.6 GHz processor. It's downclocked to 1.2 because of temperature and stability. However in benchmarks the same hrdware gets more points for CPU performance in the downlclocked MX1 than in the MK808. A better optimized 1.2 is much more effective than a crappy 1.6. (source)
I got mine few days ago. Seems like this stick is getting more and more popular. Everything on this stick is very smooth. HD streaming from my server via WLAN works perfect (1080p mkv files too). Was hoping for more 3D performance but it´s still OK. GTA Vice city runs perfect.
But I am having trouble with gamepads, pretty hard to get them to work correctly. GTA is the only program where the XBox controllers work like they should after I used xpad.ko from the arctools app. USB/BT Joystick center doesn´t recognize any sticks I plug in. Still testing though...
Thanks for the review man!
Do you think this is the best stick available on the market? I'm just starting to research on these, and just curious which one is the best bet in the long run, to be supported with newer roms?
peaceburn said:
Thanks for the review man!
Do you think this is the best stick available on the market? I'm just starting to research on these, and just curious which one is the best bet in the long run, to be supported with newer roms?
Click to expand...
Click to collapse
I´m asking the same question. This seems to be the best one so far?
peaceburn said:
Thanks for the review man!
Do you think this is the best stick available on the market? I'm just starting to research on these, and just curious which one is the best bet in the long run, to be supported with newer roms?
Click to expand...
Click to collapse
agazza said:
I´m asking the same question. This seems to be the best one so far?
Click to expand...
Click to collapse
Well, I would lie if I say it´s the best one because I didn´t test other sticks, only phones. I bought the stick because people who own the 802, 808 or other devices say that the imito is the best stick right now. I took their advice and I am happy with that.
I noticed some issues with the WLAN connection today. To me it looks like the signal is dropping from time to time but gets back up after 2 or 3 seconds and if you search for this issue you will find people who are reporting the same. I do not have this problem with my other devices so it´s the imitos fault I think. The current stable firmware version does not support "true 1080p" output. As far as I found out it´s 720p upscaled to 1080p which makes the picture look a little bit unsharp. There is a custom ROM from a guy named Finless who took the latest beta ROM with true 1080p support and added some stuff and fixes. I think this will improve the stick even more but I will report back after that.
Oh and just to make things clear: I own the imito MX2 not the MX1 - but just the cases differ from those two. The imito MX1 has serious WLAN problems because of the metalcase. It´s nice to see a company noticing their own mistakes and listening to the community, otherwise the MX2 would not exist
Edit: One thing I am not able to check right now is that people are complaining that the rk3066 does not support surround sound output. The signal gets downmixed to stereo regardless of which source. My av-reciever is built into a shelf and for that I have no opportunity to check this myself.
Edit2: Just read my text, hope my english is still okay
There is a rom for the iMito MX1 & MX2: http://www.freaktab.com/showthread....2-Finless-ROM-1-5-Root-debloat-init-d-support
yeah that´s the one I was talking about. I will backup my device and install this rom in about 1 hour
agazza said:
I´m asking the same question. This seems to be the best one so far?
Click to expand...
Click to collapse
doesn't matter which you buy, the moment it arrives there are more and more better on the market.
At the moment there are quadcore processor ones too, and next week on the CES you'll see more of these...
However about imito mx1/2
the wifi and BT driver are not open source, so until Mediatek doesn't release source for these drivers, you'll not have many custom roms.
BUT
1. no need for it, stock rom is fast and snappy
2. if you not willing to use wifi or BT (internet can come through USB-LAN adapter from router), you can use any custom rom made for MK808 devices.
Here is a Google+ community where we discuss some tricks and tips, apps and games, feel free to join!
http://goo.gl/Oliw7
---------- Post added at 04:39 PM ---------- Previous post was at 04:34 PM ----------
sancho1234 said:
More info...
Click to expand...
Click to collapse
For more info post:
MX1 review
http://goo.gl/42ddZ
MX1 latest Stock ROM (29.11.2012)
http://goo.gl/RTu9j
Update
I updated some fields on the 1st page. Thank you for your additions!:good::laugh:
Finless ROM Update 1.5 12/22
FYI, in the second post, I think the date of Finless ROM is in error. The ROM is dated 12/22 (based on 12/12 kernel).
Here is original from Bob at Freaktabs for verification, install instruction links:
http://www.freaktab.com/showthread....2-Finless-ROM-1-5-Root-debloat-init-d-support
Works great on my device.
dgf2002 said:
FYI, in the second post, I think the date of Finless ROM is in error. The ROM is dated 12/22 (based on 12/12 kernel).
Here is original from Bob at Freaktabs for verification, install instruction links:
http://www.freaktab.com/showthread....2-Finless-ROM-1-5-Root-debloat-init-d-support
Works great on my device.
Click to expand...
Click to collapse
:good:Tnx!
Hard MX1 firmwares collection: http://goo.gl/ki6We :good:
wish more people here would jump on this. i have the mx2 and its a decent little device. i am grabbing a usb wifi adapter today and going to push the new drivers to the device when i get home. the internal wifi chip is not all that great. i had a hell of a time figuring out that unless you are within 10-15 feet of the router, it just wont connect. but with a external usb adapter people have reported way better results. so on to that i go! i'll try to post back as i'd love to get a real community of users here at xda instead of reading at the infested websites of armtvtech and freaktab. i feel like my pc got malware visiting those websites lol
I have Deal Extreme SKU 165489. (Jesurun NX003)
Sure looks the same as iMito MX1 (SKU 166114), (Of course I paid $5 more )
Does anybody know if it is really the same? -- e.g. Can I use the same firmwares?
Also, a couple of notes, in case it helps anyone:
I also have the Measy RC11 Air Mouse - Works fine, have never had to reset accelerometer.
ADB runs as root out of the box, so there is no need to root for most changes (such as editing build.prop)
Speaking of build.prop --- When I changed my ro.lcd.density from 160 to 140 (to try to get a more "PC" like experience), it worked, but I lost Movies&TV on Google Play, and several Apps I tried to install reported incompatible (Adobe Reader, for one). I set it back, and both worked again.
Un-powered Mini travel USB hub works fine.
2nd Serial port works as OTG, with the included adapter, so that you end up with 2 full size USB ports.
GE branded generic webcam worked fine as a USB microphone, but when I hit Search with Camera in Google Search/Google Now, it crashes Google Search. I have not installed a camera app to test more.
A RadioShack/GigaWare USB mic/audio device works fine, both as a Mic, and a Audio output device.
My stick will not clock above 1200 MHz - can somebody confirm?
shrewm said:
My stick will not clock above 1200 MHz - can somebody confirm?
Click to expand...
Click to collapse
Yes posted everywhere. A heat sink is needed if you want to go higher. I believe there's a similar device with an oc kernel out there that may come to the MX eventually.
I'd like to see a guide on adding a heat sink.
Hello! I wanted to share my app I have been developing since about 1 year. It is my first big programming project so any suggestion is welcome to improve my coding!
MultiWork (MW) is a LogicAnalyzer tool, there is a hardware side built with a microcontroller and the software side that is the Android app. Now is simply capable of decoding UART and I2C protocols with a maximum sample rate of 40MHz but new protocols will be added and maybe in the future more sample speed and memory to store the data.
The hardware side is USB and battery powered but currently only works only with USB chargers capable of providing 500mA without USB enumeration. I am working on the new hardware and I hope to get it ready in a few weeks.
The app is made with Android Studio but you can download directly the APK I attached. Here is the GitHub Repository
The API used to decode the protocols is available as a separated jar file which source code is here.
Thank you very much and sorry for my bad English!
hi, thanks for your effort of programming this logic analyzer but Do you have English version.that support USBee AX Pro?