Develop Bugs

[UPDATED 04/29][DEV - Camera ( camcorder improvement ) ] Camera tests

Hi,
Here is a "test" package for camera under android.
IMPORTANT : this thread will only deal with XDANDROID Rom. Cyanogen's mod or any else might not work if camera have not been enabled in userland (checkered camera screen).
Current working devices are :
-Diamond
-Rhodium
-Raphael
-Blackstone
-Topaz
This package allow camera to be used for picture but video will fail (bug fixed, will soon publish libs).
I need some people to test it (I've tested it but when you are working on something for a long time, you sometimes need external testers...because you know where it may bug and you don't really want that so you avoid those use cases...)
1/ MAKE A BACKUP of the system.ext2, rootfs.img and data.img files so that you can revert back to normal state if something goes wrong
2/ See intructions in the 22/01/2011 update.
3/ If you have a CMDA rhodium, add the following content to the startup.txt file :
Code:
board-htcrhodium.is_cdma=1
This is a quick hack to detect CDMA board till I make it as the other board do.
4/ Replace the kernel + modules with the ones provided in the latest update.
Any feedback is welcome. If you're experiencing problems, please attach a dmesg log and logcat log so that I can analyze them. If I don"t have those files, I probably won't be able to do anything to help you.
THIS THREAD IS FOR PEOPLE WHO KNOW HOW TO USE ANDROID AND ADB. Others, wait for the final release in the common tree.
Source tree : http://gitorious.org/~jbruneaux/linux-on-qualcomm-s-msm/linux-msm-home-work (lot of changes almost every days as used as a gateway between computers)
[23/02/2011] :
* New kernel for rhodium only. This is an attempt to fix the pink screen problem.
Link to the package : http://www.4shared.com/file/OMMJkB4Q/kernel_modules_02232011.html
[29/04/2011] :
* New libraries for camcorder to enable the hardware codecs for video recording.
These libraries will make camcorder use the hardware accelerated codecs for qualcomm hardware. That will make quite good quality videos (much more than the software codec actually used) and will also make sound recording work with video.
Link to the libraries : http://www.4shared.com/file/fLEiesLy/libomx_xdandroid.html
Please also patch your froyo.user.conf with those two lines :
Code:
mount --bind /sdcard/lib_camera/libOmxCore.so /system/lib/libOmxCore.so
mount --bind /sdcard/lib_camera/libmm-omxcore.so /system/lib/libmm-omxcore.so
Note that these libraries are to be used with the official xdandroid FROYO build (FRX05 or later) and the official kernel/modules.
Don't use the kernels / libraries (except the 29/04/2011 camcorder libs) from this thread, they are now included in the offical release.
Once again : if you have a crash or a bad behaviour, please make a dmesg log + logcat log ! I can't work without these files. Thanks
PLEASE, READ CAREFULLY BEFORE POSTING AND CHECK FOR ANSWERS IN THE POSTS !
IMPORTANT : If the camera does not work, first, try to find the solution by yourself in this thread, then send me dmesg log + logcat of the boot and camera start.
Thanks to bzo for its modified libGLES_qcom and its work on rhodium (working hard on camera). Thanks to everyone who helped me with testings and logs.

Awesome... I was hoping this would make its way out into the wild soon!

Hi,
before release, i wanted to make clocks working without rpc calls, that's why it took longer. Now, the code is "cleaner" and should work for any device (with small adjustments for amss and memories configuration).
Jerome

Testing on Fuze.
Edit: Does not work, Haret freezes on boot..

i encounter this when playing around with angry bird.
Code:
msm_proc_comm_wince: DEX Code not match! a2m[0x8a], m2a[0x0], a2m_num[0x7b5], m2a_num[0x7b5]

whooooopieee! trying it out

Haret does not boot with included kernel...

test diam100:
tried this on a donut version. Camera aint working. hehehe. but it has green crash on it.

Great one. works great. the bad thing is, hardware buttons wont work after sleep on diam100. I don't know why. can anyone with diam100 comfirm on this?

everything copies successfully except gralloc.msm7k.so. The folder is unwriteable through ssh. Any suggestions for getting it moved?
it says it's a read-only file system. do I need to be in a different mode other than through adb in order to mount the file as rw?

Great! I hopefully it will work on TP2 also

This is GREAT NEWS! Yes I hope once things are ironed out it will be easy to run it on my Rhod400!

Try sudo command.

u need to mount -o remount,rw /system to make it writable

Amazing ! ^^ It works fine for me !

lorikitty said:
everything copies successfully except gralloc.msm7k.so. The folder is unwriteable through ssh. Any suggestions for getting it moved?
it says it's a read-only file system. do I need to be in a different mode other than through adb in order to mount the file as rw?
Click to expand...
Click to collapse
The lib_inst.sh contains a line to enable read/write access to rootfs so that gralloc can be overwritten
Have your tied using this script ?
Testing on Fuze.
Click to expand...
Click to collapse
Package was not designed to run on fuze but should not make your system crash or freeze...
i encounter this when playing around with angry .
Click to expand...
Click to collapse
I don't know if it's related to my kernel. Can you send the full dmesg + logcat if you've got the problem again. Also, it might come from the modded libGLES_qcom.so. What device are you using ?
I'm currently modifying blackstone files. I will need someone to test it but he must be patient because it may fail a few times before it runs (memory layout is written in a more "tweakable" way, but it may need some adjustement.
Blackstone sensor is not the mt9t013 as in diamond but mt9p012. Anyway, liboemcamera.so seems to know this sensor and it should work. I'm also looking at the CDMA diamond to make it work with camera (mainly memory configuration to do).
Will try to put a package for theses devices before xmas.

im on blacstone.maybe i could help.i saw you modified gralloc that have dynamic memory allocation from standard pmem to 3D pmem.im using qcom library for OpenGL ES 1.1-CM GL_RENDERER Q3Dimension MSM7230 01.02.08 0 4.0.0.Im testing 3D library to get better fps

xUmaRix said:
im on blacstone.maybe i could help.i saw you modified gralloc that have dynamic memory allocation from standard pmem to 3D pmem.im using qcom library for OpenGL ES 1.1-CM GL_RENDERER Q3Dimension MSM7230 01.02.08 0 4.0.0.Im testing 3D library to get better fps
Click to expand...
Click to collapse
I've used libGLES_qcom from bzo, just some memory size stuff modded. For camera, right now, I don't care about fps, but I will care when camera will work for almost every devices. Winmo can use more than our 7 & 8 mb of gpu memories, so I think we can make linux to do the same.

-UPDATE-
Add support for Diamond CDMA, Raphael (all models) and blackstone. Need some (patient) testers.
See first post

cool upload the library i can help testing for blac100.Normal qcom library use MSM7500 OpenGL ES 1.0-CM same as in winmo.I could play HomeRun battle 3D smoothly using MSM7230 OpenGL ES 1.1-CM.maybe MSM7500 need opengl patch

[FAQ][DEV] BT, WiFi and MAC Address on HD2

I hope all this is just a little bit interesting for some developers because I can't do any further investigations on ANDROID because my device is broken. At the moment it's on the way and I hope I will get a change of my broken HD2. I have summarized some more or less insteresting facts and I hope someone of you will think about all this informations and can work with them.
First at all: I'm not a developer but I have done some search on ANDROID and logged and logged and logged it again. All this is just a collection of facts and results of compare log files.
When you disassemble some Files within Android, you will see that something will not work because it can't. Let me start with the init.rc what is missing or might be wrong:
1. MISSING FOR BLUETOOTH:
Code:
# create mountpoints
mkdir /mnt_data/download 0777 root system
2. WRONG?
Code:
chmod 0666 /dev/ttyHS1
chown root radio /proc/cmdline
chmod 666 /proc/cmdline
There is no ttyHS1 device within the ANDROID. Can't find it.
3. NOT SURE
rfkill is seems not working. Recommendation on the website:
http://www.gitorious.org/openaos-te...5f360fec4c21c1e06d145a5fe?diffmode=sidebyside
Code:
chmod 0666 /sys/devices/platform/wifi_bt/bt_enable 0
write /sys/devices/platform/wifi_bt/bt_enable 1
but based on ANDROID Developer FAQ it should be:
Code:
chmod 0666 /sys/modules/board_[platform]/parameters/bluetooth_power_on
write /sys/modules/board_[platform]/parameters/bluetooth_power_on 1
and this MUST also done after the change:
Code:
on property:persist.service.bluetoothd.enable=0
write /sys/modules/board_htcleo/parameters/bluetooth_power_on 0
...depend of the settings it also could be:
Code:
write /sys/devices/platform/wifi_bt/bt_enable 0
on property:persist.service.bluetoothd.enable=1
write /sys/modules/board_htcleo/parameters/bluetooth_power_on 1
...depend of the settings it also could be:
Code:
write /sys/devices/platform/wifi_bt/bt_enable 1
Also interesting is the command write which is used a lot of times by the init.rc. I don't know where this command is located. But if you open a SHELL on Android and try to "write" something you will see that this command is not available. Can someone explain how this will work when this command is not available????
4. WRONG!
Code:
chmod 666 /dev/uinput
chmod 666 /etc/bluez/audio.conf
chmod 666 /etc/bluez/hcid.conf
chmod 666 /etc/bluez/input.conf
On the one hand this path is not existing and on the second hand the hcid.conf is also not existing. If you take a look only within /etc you will see that /etc/bluetooth is only existing.
5. BT INITIALIZATION
Code:
service hciattach /system/bin/brcm_patchram_plus --enable_hci –enable_lpm --baudrate 3000000 --patchram /etc/firmware/bcm4329.hcd /dev/ttyHS0
user bluetooth
group bluetooth net_bt_admin
disabled
This is also not working at all. If you try to run this command via the shell nothing will happens. And if you need to load the firmware into the device you need also setup this device by nvram.txt which you can see within the bluetooth.c file. The nvram.txt is important to get a valid MAC Address from the hardware. If you take a look into the source code of the BCM4329 you will see additional informations about this.
The second problem is the value of 3000000. This is to small. If you want to work with head set than a value of 4000000 is minimum required. From my point of view this initialization should be:
Code:
service hciattach /system/bin/logwrapper /system/bin/hciattach -s 57600 /dev/ttyHS0 any 4000000 flow
The value 57600 is the minimum value for initialize bluetooth and it could be that this value will downsize the standby drain. Not sure, just an idea.
Why? Lets take a look into the main.conf or hcid.conf:
Code:
# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true
# Remember the previously stored Powered state when initializing adapters
RememberPowered = true
This was the reason why I think the initialization speed "...-s 57000 /dev..." should be lowerd down which might also solve the battery drain issue. Again, not sure - just an idea.
Btw, if you open the ADB shell and try hciconfig, hciattach or hcitools non of this are working because there is no Bluetooth Adapter even if you have BT enabled. This tools are requried for BT analyse, test and command options. You can call each of the files within the Shell but whatever you try to do you it will fail because BT is not enabled. Try to run rfkill which could initiate a reset on the BT device. If you try to rfkill ttyHS0 which is the BT adapter on HD2 device this will not work. From my point of view all this problems are not only related to the kernel.
6. TAKE A LOOK INTO THE init.htcleo.rc
Code:
# Make sure we startup btld before hcid
# Set target address to emulator host loopback IF
# Limit baudrate to 460800 to ensure reliable uart operation
service btld /system/bin/logwrapper /system/bin/btld -hwtun 10.0.2.2 -hb 460800 3000000 -lpm 1
# service btld /system/bin/logwrapper /system/bin/btld -lpm 1 -hb 3000000
Not sure what will run first. The init.rc or the init.htcleo.rc. If the init.rc will run first this could be also a problem. Btw, the first value is 460800. From my point of view this is too much for initialization.
7. WiFi INITIALIZATION
Just an example but if you do a Google search for "BCM4329 nvram.txt" you will get more than 3 links. Let me show here an example:
http://android-wifi-tether.googlecode.com/svn-history/r465/trunk/res/raw/tether_edify
Search for Value 4329 and you will see SAMSUNG Device bla, bla – don't know from top of my head:
Code:
!file_exists("/sdcard/android.tether/bcm4329.bin") && ( module_loaded("dhd") || log(insmod("/lib/modules/dhd.ko", "firmware_path=/system/etc/wifi/bcm4329_mfg.bin nvram_path=/system/etc/wifi/nvram_mfg.txt"), "Loading dhd.ko module<br>(bcm4329_mfg.bin from /system/etc/wifi/)"); );
Hmm... That was the reason why I grabbed the SAMSUNG i9000 from a friend of me and double checked the device. If you take a look into the /etc/wifi you will see the nvram.txt. I'm not sure how this will be loaded into the device but the i9000 has the same BCM4329 Chipset.
Now let us take a look into the wifi.c for QUALCOMM devices which is also valid for the HD2:
http://gitorious.org/linux-on-qualc...f8dffe668c0448/libhardware_legacy/wifi/wifi.c
Code:
Line 61: Take a look. Nothing of this is existing on the HD2
Line 71: there is no wlan.ko on the HD2
But now, where the hell the MAC Address is stored for the WIFI Adapter? Just take a look at this location:
Code:
sys/module/board_htcleo/parameters/bdaddress
or use this:
Code:
/system/sysroot/module/board_htcleo/parameters/bdaddress
If you check this file you will see there your current MAC Address of the WIFI device. The stupid MAC for the BT device seems not stored on the device. And this is the point where I guess to need the fu***ing nvram.txt.
I have done a search for some BCM files and found something interesting which is attached as "Broadcom Files.7z." There are some (!) more or less firmware files within (?) and also the famous nvram.txt
For additional informations about WiFi and more just open the wifi_suplicant within the /system/bin directory with a simple text editor and browse down to the end. There you will see also a lot of interesting settings for the WiFi environment.
8. W.t.F. IS THIS STUPID NVRAM.TXT?
Download attached Broadcom.7z and check the txt file within. If you open the file you will see the nearly same content as within the
Code:
/etc/calibration
file.
But this file you can ignore on your HD2 device. Delete it, rename it – do whatever you want and you will see no changes on the device. The more interesting thing is within
Code:
/sys/calibration
Huhhhh...! The same file but less values. But where does it come from??? Currently I don't know.
It seems that the nvram.txt is as same as like a BIOS for the device. The BCM4329 is a BT AND WiFi Chip within one CHIP. It might be wrong but I guess this is the easy explanation for this.
And because of this the thing can't work. First it needs to load the BIOS (nvram.txt) and then it needs the OS for it (BCM4329 Firmware).

Okay here is something by reading and following your examples:
sys/module/board_htcleo/parameters/bdaddress
That lines exists in the current NAND Android roms, but this line:
/system/sysroot/module/board_htcleo/parameters/bdaddress
doesnt exist, not in Rafs rom or in imilka's 0.1 GB sense rom.
But here is my key interest: "bdaddress" is where the BLUETOOTH MAC Address is!
Another interesting thing, in imilka's 0.1 GB Sense rom, I can change this to whatever I want and it Sticks till I reboot, but in Rafs it does not.
Key Question, How do we make this file KEEP the changes we make to it??? I know its a dirty fix but none the less its a FIX!! So anyone got a clue?!??

First of all there is a WRONG that is big like an house
the init.rc "syntax" is not shell syntax.
so as example, command "write" will not work in shell... but only in init.rc
I see also a lot of confusions about stock froyo/gingerbread stuff and sense stuff.
Example: Sense uses it's own stuff for BT so a clean init.rc for sense is really different from the one for a non-sense build.
Also some stuff/commands needs to be changed/replaced to have them working with our hd2 kernel.
I have no time now but really this posts is about 30 different things that cannot be explained all togheter.
My suggestion is to google for "android init syntax" and start from there understanding all the android boot process and the android init syntax.

About the wifi mac address.
The wifi mac address is "read" from the libhardware_legacy.so
normmaly this lib reads the mac address in /etc/calibration
this file is a "kernel" file so you are not able to change it.
You can use a modified libhardware_legacy.so that reads the mac address in /system/etc/calibration so you can change it, as I did on my builds where you can change the wifi mac address.
Unfortunately the modified libs causes other issues like gps not working.
---------------------------------------------------------------------------
About the problem that you cannot write permanetly the changes on stuff inside the folders
/
/etc
/proc
/sys
and so on.. this is because those folders are the "kernel" that normally is read-only
you can make it write enabled but it's not a safe way to proceed...

so is there a chance to fix the issue with the bluetooth mac?!
would be important for me
(can't use my parrot car kit with my wifes hd2 because of the same mac adress )

rafpigna said:
First of all there is a WRONG that is big like an house
the init.rc "syntax" is not shell syntax.
so as example, command "write" will not work in shell... but only in init.rc
I see also a lot of confusions about stock froyo/gingerbread stuff and sense stuff.
Example: Sense uses it's own stuff for BT so a clean init.rc for sense is really different from the one for a non-sense build.
Also some stuff/commands needs to be changed/replaced to have them working with our hd2 kernel.
I have no time now but really this posts is about 30 different things that cannot be explained all togheter.
My suggestion is to google for "android init syntax" and start from there understanding all the android boot process and the android init syntax.
Click to expand...
Click to collapse
Thanks mate! The problem is that I have no clue how to do it but I hope someone outside who has more experience with all this knows what to do.
Btw, I have had also tried to do a simple test with this "write" command by fill a line within /etc/test and also /proc/test which fails. Usually I added some lines into the init.rc to see if this will work.
But I'm not sure if I have had something wrong.

rafpigna said:
About the wifi mac address.
The wifi mac address is "read" from the libhardware_legacy.so
normmaly this lib reads the mac address in /etc/calibration
Click to expand...
Click to collapse
Sorry, but this is not true. Check this:
http://developer.android.com/reference/android/net/wifi/WifiInfo.html
If you check this from Android SDK you will see that the wpa_supplicant is responsible for this. And this would be O.K. if you also check the BCM4329 source code.
First the CHIPSET will be initiated and prepared by the firmware and the nvram.txt and after that the wpa_supplicant do the rest.
How this exactly will work - sorry, too less coding knowledge
A good thing is it to compare the MAC & BT issue with the i9000 devices and Sony X10. The Sony X10 has the same QUALCOM chipset as the HD2.

Here are the files from the original Desire HD 1.8x.
The initrd.zip contains is the original file and the initrd~.7z is the extracted who is interested to read and compare.

see this http://gitorious.org/linux-on-wince...mmit/ce69804632e64b397758c1c9835f06efd0c8cb54
in file arch/arm/mach-msm/board-htcleo.c i see from markinus some changes to file bdaddress.but it is not in the main git tree we use for hd2 kernel
maybe someone kernel developer can see it and make a kernel for testing;

clio94 said:
see this http://gitorious.org/linux-on-wince...mmit/ce69804632e64b397758c1c9835f06efd0c8cb54
in file arch/arm/mach-msm/board-htcleo.c i see from markinus some changes to file bdaddress.but it is not in the main git tree we use for hd2 kernel
maybe someone kernel developer can see it and make a kernel for testing;
Click to expand...
Click to collapse
Looks good, but this is not valid for HD2. This is HTC Tattoo. If you check this code you will see "akm8973".
Damn!

http://nagaraj-embedded.blogspot.com/2011/02/guide-on-adding-wifi-drivers-on-android.html
and
http://www.jetdroid.org/forum/viewtopic.php?f=78&t=456&start=20#p4502
Can someone double check this???? From my point of view this looks quite good...

MrT69 said:
Sorry, but this is not true. Check this:
http://developer.android.com/reference/android/net/wifi/WifiInfo.html
If you check this from Android SDK you will see that the wpa_supplicant is responsible for this. And this would be O.K. if you also check the BCM4329 source code.
First the CHIPSET will be initiated and prepared by the firmware and the nvram.txt and after that the wpa_supplicant do the rest.
How this exactly will work - sorry, too less coding knowledge
A good thing is it to compare the MAC & BT issue with the i9000 devices and Sony X10. The Sony X10 has the same QUALCOM chipset as the HD2.
Click to expand...
Click to collapse
I'm wrong?
Sorry to say, I'm not an andorid guru but maybe I have a little bit more knoledge and trust me in our case, at least with our builds, the mac address is read from the calibration file.
So how is possible that in my builds you can change the wifi mac?
I just take yor desired wifi mac, write it in the /system/etc/calibration file and replace the libhardware_legacy.so that will read from that instead of /etc/calibration
MrT69 said:
Thanks mate! The problem is that I have no clue how to do it but I hope someone outside who has more experience with all this knows what to do.
Btw, I have had also tried to do a simple test with this "write" command by fill a line within /etc/test and also /proc/test which fails. Usually I added some lines into the init.rc to see if this will work.
But I'm not sure if I have had something wrong.
Click to expand...
Click to collapse
Already said... init.rc syntax is not shell syntax!!!
Anyway.. I still miss the purpose of this thread....

Just the first two google search links appearing with a simple "android init.rc" search
http://www.androidenea.com/2009/08/init-process-and-initrc.html
http://elinux.org/Android_Booting
Read that and something will be clearer.

rafpigna said:
I'm wrong?
Sorry to say, I'm not an andorid guru but maybe I have a little bit more knoledge and trust me in our case, at least with our builds, the mac address is read from the calibration file.
Click to expand...
Click to collapse
It might be that I have had something missunterstand but I only want to say by default (!) the MAC Address is not read from the calibration file by ANDROID. Of cause I have had tested your solution and it's working.
So how is possible that in my builds you can change the wifi mac?
I just take yor desired wifi mac, write it in the /system/etc/calibration file and replace the libhardware_legacy.so that will read from that instead of /etc/calibration
Click to expand...
Click to collapse
I know that the MAC Address could be changed within this way. I hope you don't understand it within the wrong way but from my point of view this is only a patch solution. Because of the fact that the BT & WiFi Chip is ONE (!) chip within HD2 there must be an other solution to read and get the MAC address for WiFi AND BT.
Already said... init.rc syntax is not shell syntax!!!
Click to expand...
Click to collapse
I only was asking why and where it was not working. In the mentime I know it because of your feedback. But I have add some lines into the init.rc and the files and changes was not written to the device. That was the reason why I was asking.
Anyway.. I still miss the purpose of this thread....
Click to expand...
Click to collapse
Hope to find some people who will help to fix all this issues and on the second hand I hope to find a solution for the BT and WiFi MAC to get it from the device.

It is proper time to make an open discussion about the 2.2.1 rom and more tweaks closer to HD2 reveal in the community.

MrT69 said:
I know that the MAC Address could be changed within this way. I hope you don't understand it within the wrong way but from my point of view this is only a patch solution. Because of the fact that the BT & WiFi Chip is ONE (!) chip within HD2 there must be an other solution to read and get the MAC address for WiFi AND BT.
Click to expand...
Click to collapse
maybe this is wrong but it is extremely good that in sense roms,you can change at any time wifi mac address.in my city municipality have free wifi hotspot but after sometime reads your wifi mac address and cut the connection for a time.so with dynamic wifi address i can be almost all time everywhere online and this saves me from a slow (because i live in a small greek city and 3g connection is not everywhere) data edge connection.

[q] [language support] how to get android bangla font supported

Dear Everyone
As a Bangladeshi and Android user, many others like me facing the below problem since the day android comes out. People who wants to browse a website written in complex scripts such as uni-code support can never get the solution (properly). For that reason we are unable to read online newspaper those are in bangla.
We know we have some great dev, the can sort out this issue for us ? It must have a way to do so. Currently Opera giving a solutions - Using bitmap fonts for complex scripts. It works flawlessly also though become horrible when the article is big. Click here to see the whole procedure.
Then one of Bangladeshi guy named Mehedi did some tricks like below which didn't work -
Steps to be followed:
1. Get Solaimanlipi or Lohit fonts. (other unicode ones should do too)
2. Rename the font (one that’s chosen) to DroidSansFallback.ttf
3. Put the font into the SDCARD root.
4. Open terminal (oh! forgot to tell, you neet to be root)
5. Type the following and hit ENTER
su
6. Wait till $ sign turns into #
7. type the following and hit ENTER (mounting the system partition)
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
8. Then the following and hit ENTER
chmod 4755 /system/fonts/DroidSansFallback.ttf
9. in following line we will overwrite the existing font with the one from SDCARD
dd if=/sdcard/DroidSansFallback.ttf of=/system/fonts/DroidSansFallback.ttf
10. Once typed the above, hit ENTER
11. REBOOT immediately using the following:
reboot
Click to expand...
Click to collapse
This problem is still out there which need your kinds input. So far, Tibetan, Arabic, Hebrew,Hindi and few more languages were proved successful.
Or if i'm not updated and somebody have the solutions please share it with us.

[Attention] Google
Google should have built-in support in their android phone for this language. Bangla is currently stand at no 7 in the top natively language.
Recently a day has been selected for the International Mother Language by UNESCO,which has been commemorated in Bangladesh since 1952, when a number of students including the students of the University of Dhaka were killed by the Pakistani police in Dhaka during the Bengali Language Movement protests.
I have expecting built-in bangla in android very soon, apple already did the job.

This is a big problem almost everywhere........language problems can be best handled by Google if you can provide your query to them

I will bro...

Bump
Sent from my Wildfire S using Tapatalk 2

cleansafi said:
Dear Everyone
As a Bangladeshi and Android user, many others like me facing the below problem since the day android comes out. People who wants to browse a website written in complex scripts such as uni-code support can never get the solution (properly). For that reason we are unable to read online newspaper those are in bangla.
We know we have some great dev, the can sort out this issue for us ? It must have a way to do so. Currently Opera giving a solutions - Using bitmap fonts for complex scripts. It works flawlessly also though become horrible when the article is big. Click here to see the whole procedure.
Then one of Bangladeshi guy named Mehedi did some tricks like below which didn't work -
This problem is still out there which need your kinds input. So far, Tibetan, Arabic, Hebrew,Hindi and few more languages were proved successful.
Or if i'm not updated and somebody have the solutions please share it with us.
Click to expand...
Click to collapse
I use SonyEricsson Xperia Neo and cool cuz Bangla Language is pre-build in Any sony Device wheather its Android or not.

[PX5][MD725] Solution for the bluetooth echo v2

Hi,
I release final solution for the bluetooth calls echo issue. Solution is for the PX5 units. For now it works only with MD725 module.
Donate to me
If you want to use this solution in your custom ROM, please put my "Donate to me" button in a noticeable place.​
Changelog:
26.08.2017:
-Added patched version of sdsdk
-Fixed problem with auto connect after sleep
24.08.2017:
-Added libgnustl_shared.so to zip archive because not all ROMs have it.
Click to expand...
Click to collapse
All needed files are available in the attachment
!! You have to be rooted in order to use this solution for the bluetooth echo !!​
1. Copy gocsdk, sdsdk, libf1xaec.so, libgnustl_shared.so and f1xaec.ini files to your SD card
2. Install a file manager (like ES File Explorer) which supports exploration of Android system dirs.
3. Go to /system/bin directory
4. Find gocsdk file and rename it to gocsdk_backup
5. Copy gocsdk file from your SD card to /system/bin
6. Set permissions (access rights) to 777 for /system/bin/gocsdk
7. Find sdsdk file and rename it to sdsdk_backup
8. Copy sdsdk file from your SD card to /system/bin
9. Set permissions (access rights) to 777 for /system/bin/sdsdk
10. Copy libf1xaec.so to /system/lib directory
11. Set permissions (access rights) to 777 for /system/lib/libf1xaec.so
12. Copy libgnustl_shared.so to /system/lib directory
13. Set permissions (access rights) to 777 for /system/lib/libgnustl_shared.so
14. Copy f1xaec.ini to /system/etc directory
15. Set permissions (access rights) to 777 for /system/etc/f1xaec.ini
Now it is very important to figure out what binary is used by your Head Unit. It can be either sdsdk or gocsdk. Right now rules of choosing binary by a Head Unit are unknown - probably it depends on MCU.
16. Install a terminal emulator (like Termux)
17. Execute command ps | grep gocsdk and ps | grep sdsdk
18. Remember what process is running (gocsdk or sdsdk) (if execution one of these commands gave you more lines of output, it means that this binary is used by the Head Unit)
19. Open /system/etc/f1xaec.ini
20. If your Head Unit is using sdsdk, change value of the streamDelay parameter to 280
21. If your Head Unit is using gocsdk, change value of the streamDelay parameter to 210
22. Restart Head Unit.
Click to expand...
Click to collapse
gocsdk and sdsdk are taken from HA 20170726 rom. If someone of you would have a problem on newer firmware, then we will consider update of binaries.
Short info: libf1xaec.so is a shared library containing implementation of webrtc algorithms with my patches and adjustments for RK3688 SoC. Do not worry - any viruses or other spyware are not included .

I'm sorry and I personally disagree with what was done by XDA moderators, I hope the manufacturer will listen to you.
In any case thank you for all the hard work you have done.

I also disagree.. I will donate back. The donation is a thank you for all the hard work.
So thank you.

hi,
thank you for the refund, but i sent it to you back, it is for your hard work as write Nomader0, thank you

Joining the others here in what they say, I will also donate again. - your work is worth it regardless of this isolated fix.
Looking forward to what happens here, and to see what you can achieve with the manufacturers...

We have so many great people here . Guys, thank you very much for all your messages and donations - I really, really appreciate that . Now I see that is worth to sitting even 3 months in the car D) just to read such good words.
So, there is no time to wait. Please read the first post and enjoy .

Great! Is there any precautions in install if I already have one of your earlier fix? (testing the old "C" right now)
Is the old gosdk_orig ok, just rename to _backup? The other "sdk" file in the first fix should be taken back to original?

[email protected] said:
Great! Is there any precautions in install if I already have one of your earlier fix? (testing the old "C" right now)
Is the old gosdk_orig ok, just rename to _backup? The other "sdk" file in the first fix should be taken back to original?
Click to expand...
Click to collapse
Nothing special to upgrade from previous solution is needed. Just replace gocsdk from old solution with newer one and follow the README.
Yes, sdsdk can be taken back to original. Name of the gocsdk backup file does not matter - it can be _backup, _orig, etc.
What I observed, Sdsdk* binaries are not executed by Android at all. They are almost the same as gocsdk. The only difference is implementation of the audio pooling.

Hi, I have an xtrons PB7653BAP with the same problem. I tried your solution, but cannot rename or copy in the directory with ES File Explorer. It is read only. How can I change that? Afterwards, how can I set permission codes to 777?
Thanks

clsbuilder said:
Hi, I have an xtrons PB7653BAP with the same problem. I tried your solution, but cannot rename or copy in the directory with ES File Explorer. It is read only. How can I change that? Afterwards, how can I set permission codes to 777?
Thanks
Click to expand...
Click to collapse
you have to be root.
after that use root explorer

Nomader0 said:
you have to be root.
after that use root explorer
Click to expand...
Click to collapse
OK, thanks for that. Stupid question (I'm not used to Android) perhaps but how to get rooted? Do you mean at the reboot (menu) of the radio?

clsbuilder said:
OK, thanks for that. Stupid question (I'm not used to Android) perhaps but how to get rooted? Do you mean at the reboot (menu) of the radio?
Click to expand...
Click to collapse
ok..
1st, is your unit a PX3 or PX5?
there are 2 ways to root
1. install Malaysks ROM which is rooted
2. use tools like kingoroot etc..

Nomader0 said:
ok..
1st, is your unit a PX3 or PX5?
there are 2 ways to root
1. install Malaysks ROM which is rooted
2. use tools like kingoroot etc..
Click to expand...
Click to collapse
OK, I can manage that. About px3 or 5, no clue; where can I find that? Can you help me on that? I cannot post a link (because I am new), but if you search for xtrons PB7653BAP you will find it; It is a 7" HD Digital Octa-Core 64bit 32GB + 2G RAM Android 6.0 Multi Touch Screen Car DVD Player Custom Fit for BMW E53 / X5.

clsbuilder said:
OK, I can manage that. About px3 or 5, no clue; where can I find that?
Click to expand...
Click to collapse
Settings >> About tablet >> Build number - what is at the beginning of the line?

clsbuilder said:
OK, I can manage that. About px3 or 5, no clue; where can I find that? Can you help me on that? I cannot post a link (because I am new), but if you search for xtrons PB7653BAP you will find it; It is a 7" HD Digital Octa-Core 64bit 32GB + 2G RAM Android 6.0 Multi Touch Screen Car DVD Player Custom Fit for BMW E53 / X5.
Click to expand...
Click to collapse
ok this is a little off-topic.. but here it goes.
99% you unit is PX5. you can go to settings-->about.. and see.. you will also find the word "MTCD" tell me what 2 or 3 letters are next to that... (GS?, MX? KSP?)
this would be you manufacturer..
you will also find the word PX5 somewhere there or PX3..
now if it is PX5 (which probably it is) go to:
https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3598908
and you will find info there on how to install Malaysks ROM.. your unit will be reset. i advise you to install v.2 of the ROM, and not v.3/v.3.5/v4. v2 is the most stable for now.

Hi f1x,
Like everyone I renewed my donation too, you really deserve it.
I am among those who have the new Dasaita unit that uses a new Bluetooth module (SD-968 module) (see attached image)
I launched the two commands: `ps | Grep gocsdk` e `ps | Grep sdsdk`
With the first command (`ps | grep gocsdk`) Terminal Emulator does not return any result (see attached image)
With the second command (`ps | grep sdsdk`) Terminal Emulator returns this result (see attached image):
root 1643 1 35768 10552 do_wait 0000000000 S /system/bin/sdsdk968
root 17880 1643 45060 2900 futex_wait 0000000000 S /system/bin/sdsdk968
[email protected]:/ $
Hope this information can help extend the fix to this new Bluetooth module.
Thank you

Nomader0 said:
ok this is a little off-topic.. but here it goes.
99% you unit is PX5. you can go to settings-->about.. and see.. you will also find the word "MTCD" tell me what 2 or 3 letters are next to that... (GS?, MX? KSP?)
this would be you manufacturer..
you will also find the word PX5 somewhere there or PX3..
now if it is PX5 (which probably it is) go to:
https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3598908
and you will find info there on how to install Malaysks ROM.. your unit will be reset. i advise you to install v.2 of the ROM, and not v.3/v.3.5/v4. v2 is the most stable for now.
Click to expand...
Click to collapse
+ Please check in factory settings what bluetooth module is installed. For now solutions works only for MD725.

apollo1976 said:
Hi f1x,
Like everyone I renewed my donation too, you really deserve it.
I am among those who have the new Dasaita unit that uses a new Bluetooth module (SD-968 module) (see attached image)
I launched the two commands: `ps | Grep gocsdk` e `ps | Grep sdsdk`
With the first command (`ps | grep gocsdk`) Terminal Emulator does not return any result (see attached image)
With the second command (`ps | grep sdsdk`) Terminal Emulator returns this result (see attached image):
root 1643 1 35768 10552 do_wait 0000000000 S /system/bin/sdsdk968
root 17880 1643 45060 2900 futex_wait 0000000000 S /system/bin/sdsdk968
[email protected]:/ $
Hope this information can help extend the fix to this new Bluetooth module.
Thank you
Click to expand...
Click to collapse
my 2nd unit also has sd968. i will try tonight and post my results.. hope f1x can make it work for that too

apollo1976 said:
Hi f1x,
Like everyone I renewed my donation too, you really deserve it.
I am among those who have the new Dasaita unit that uses a new Bluetooth module (SD-968 module) (see attached image)
I launched the two commands: `ps | Grep gocsdk` e `ps | Grep sdsdk`
With the first command (`ps | grep gocsdk`) Terminal Emulator does not return any result (see attached image)
With the second command (`ps | grep sdsdk`) Terminal Emulator returns this result (see attached image):
root 1643 1 35768 10552 do_wait 0000000000 S /system/bin/sdsdk968
root 17880 1643 45060 2900 futex_wait 0000000000 S /system/bin/sdsdk968
[email protected]:/ $
Hope this information can help extend the fix to this new Bluetooth module.
Thank you
Click to expand...
Click to collapse
Yes, now I have all needed info to start work on solution for new bluetooth module. But I will not have possibilty to test it.
I hope I release it still today.

f1x said:
Yes, now I have all needed info to start work on solution for new bluetooth module. But I will not have possibilty to test it.
I hope I release it still today.
Click to expand...
Click to collapse
i can help you any way i can

Linux - capabilities

Hey Gemini-owners,
I am looking to find a suitable device for WLAN engineers, and this PDA seems like the ideal candidate.
Before I recommend this device to my bosses, I need to make one thing sure though, and for that, I need your help.
When running GNU/Linux, can this device's WLAN nic be set to monitor mode?
Could someone please try this out for me? I don't have the device myself, but I'll be happy to help if needed.
Thanks in advance.

Bart.sch said:
Hey Gemini-owners,
I am looking to find a suitable device for WLAN engineers, and this PDA seems like the ideal candidate.
Before I recommend this device to my bosses, I need to make one thing sure though, and for that, I need your help.
When running GNU/Linux, can this device's WLAN nic be set to monitor mode?
Could someone please try this out for me? I don't have the device myself, but I'll be happy to help if needed.
Thanks in advance.
Click to expand...
Click to collapse
I can try it out if you know the debian cmds to set it that way and change it back ? or you might try looking or asking in this forum https://www.oesf.org

bled82 said:
I can try it out if you know the debian cmds to set it that way and change it back ? or you might try looking or asking in this forum https://www.oesf.org
Click to expand...
Click to collapse
Hey Bled82,
Great to get a response so soon!
I'll list the commands here below:
( These commands assume you have sudo rights on the device )
$sudo apt install aircrack-ng ==> I know, it sounds a bit shady, but that's the name of the software suite, nothing I can change about that. :-/
$sudo airmon-ng ==> use this command to see the list of devices airmon-ng can detect. Your wi-fi card should show up in the form of wlan0 or something similar.
$sudo airmon-ng start wlan0
And that's all to it, if all of the above give no errors, then it should be OK.
You should now have an interface called wlan0mon, meaning the change to monitor mode was succesful.
EDIT ** If you want to undo the above commands just type sudo airmon-ng stop wlan0mon ***
Can you try these out?
Thanks in advance!

Bart.sch said:
Hey Bled82,
Great to get a response so soon!
I'll list the commands here below:
( These commands assume you have sudo rights on the device )
$sudo apt install aircrack-ng ==> I know, it sounds a bit shady, but that's the name of the software suite, nothing I can change about that. :-/
$sudo airmon-ng ==> use this command to see the list of devices airmon-ng can detect. Your wi-fi card should show up in the form of wlan0 or something similar.
$sudo airmon-ng start wlan0
And that's all to it, if all of the above give no errors, then it should be OK.
You should now have an interface called wlan0mon, meaning the change to monitor mode was succesful.
EDIT ** If you want to undo the above commands just type sudo airmon-ng stop wlan0mon ***
Can you try these out?
Thanks in advance!
Click to expand...
Click to collapse
Doesn't work out of box on the debian Technical preview 2 , Maybe on the sailfish release it has available currently ? The debian build is still not fully baked FYI .
[email protected]:~$ sudo airmon-ng
Found phy0 with no interfaces assigned, would you like to assign one to it? [y/n] y
ERROR adding monitor mode interface: command failed: Operation not supported (-95)
Found phy1 with no interfaces assigned, would you like to assign one to it? [y/n] n
PHY phy1 will remain lost.
PHY Interface Driver Chipset
ethtool failed...
Only mac80211 devices on kernel 2.6.33 or higher are officially supported by airmon-ng.
[email protected]:~$ sudo airmon-ng
Found phy0 with no interfaces assigned, would you like to assign one to it? [y/n] n
PHY phy0 will remain lost.
Found phy1 with no interfaces assigned, would you like to assign one to it? [y/n] y
ERROR adding monitor mode interface: command failed: Operation not supported (-95)
PHY Interface Driver Chipset
ethtool failed...
Only mac80211 devices on kernel 2.6.33 or higher are officially supported by airmon-ng.
[email protected]:~$

Hi Bled82
That was to be expected, I suppose.
Could I ask for one more test with an external adapter, should you have one?
I believe the Gemini does support external USB-devices, no?

Bart.sch said:
Hi Bled82
That was to be expected, I suppose.
Could I ask for one more test with an external adapter, should you have one?
I believe the Gemini does support external USB-devices, no?
Click to expand...
Click to collapse
Yes it does , I have connected multiple devices and usb hubs that work well in android , mixed results in Debian , which is not a big surprised they are still working to provide a fully baked distro on debian , sailfish 3 is in the works also and looks promising .