Related
Hello Everyone! This is a movement/project to get MHL going on CM10 ROMs. I have started tearing into it as some of you may have seen on some other threads, but I am just a noob
I would love some help on this. I am not good with programming or working with source so i have posted my changes on pastebin. Reason for that is so that you guys (and gals) can help out! If you know what you're doing and can build with some changes you make yourself, please go ahead and do so, but keep me informed. If you are not as savvy with this stuff like me, you can still help by searching through the code and trying to see what is missing or out of place! Thank you to all that help out. Post any news or questions here!
Pastebin ==> http://pastebin.com/u/slingerdroid
Attached log files from attempting MHL use on AOSP and actually doing it on Sense 3.6.
Big Thank you to SirGatez
cslingerland said:
Hello Everyone! This is a movement/project to get MHL going on CM10 ROMs. I have started tearing into it as some of you may have seen on some other threads, but I am just a noob
I would love some help on this. I am not good with programming or working with source so i have posted my changes on pastebin. Reason for that is so that you guys (and gals) can help out! If you know what you're doing and can build with some changes you make yourself, please go ahead and do so, but keep me informed. If you are not as savvy with this stuff like me, you can still help by searching through the code and trying to see what is missing or out of place! Thank you to all that help out. Post any news or questions here!
Pastebin ==> http://pastebin.com/u/slingerdroid
Click to expand...
Click to collapse
Hawtness. Will def jump in wherever I can.
What is MHL.
Sent from my ADR6425LVW using xda app-developers app
merlin66676 said:
What is MHL.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Mobile High-Definition Link. Basically, the HDMI over USB protocol that the Rezound supports in Sense but not AOSP.
place holder. so tapa can have this in my recent. going to work on this more tonight. thank you op
shrike1978 said:
Mobile High-Definition Link. Basically, the HDMI over USB protocol that the Rezound supports in Sense but not AOSP.
Click to expand...
Click to collapse
Sense 3.6 only. The Sense 4.x builds do not support MHL.
To the OP, thank you guys so much for attempting to make this work. You guys keep breathing life into this device. Your work is VERY appreciated!
Sent from my ADR6425LVW using xda premium
synisterwolf said:
place holder. so tapa can have this in my recent. going to work on this more tonight. thank you op
Click to expand...
Click to collapse
let me know what you find or if i can help
Question. I don't have CM10 installed right now but you guys have tried adding "ro.hdmi.enable=true" to the build.prop? Worth a try.
Flyhalf205 said:
Question. I don't have CM10 installed right now but you guys have tried adding "ro.hdmi.enable=true" to the build.prop? Worth a try.
Click to expand...
Click to collapse
yeah its already there
Flyhalf205 said:
Question. I don't have CM10 installed right now but you guys have tried adding "ro.hdmi.enable=true" to the build.prop? Worth a try.
Click to expand...
Click to collapse
I thought thus was used for HDMI only and not the mhl connector.
Cm10 trys to output video to USB when connected to the mhl device. It just doesn't know how. Someone posted a logcat and it shows its passing the information to com.android.athome.mediaroute.provider
But errors right there. Unless I'm looking at the wrong error. But I need to look at it some more. Couldn't do much at work today. :/
Sent from my iPhone...
synisterwolf said:
I thought thus was used for HDMI only and not the mhl connector.
Cm10 trys to output video to USB when connected to the mhl device. It just doesn't know how. Someone posted a logcat and it shows its passing the information to com.android.athome.mediaroute.provider
But errors right there. Unless I'm looking at the wrong error. But I need to look at it some more. Couldn't do much at work today. :/
Sent from my iPhone...
Click to expand...
Click to collapse
I've been reading a lot and CM10 seems like it has problems with MHL anyways. You say it tries to push it through USB but just doesn't know how to. That would be kernel issue would it not?
I will be able to start testing when I get my MHL adapter back tomorrow. I got a lot of free time to test since I'm done updating recoveries for now
EDIT: I reading more and saw where one guy somehow changed his refresh rate to [email protected] inside of the kernel. So is it somewhere in there most likely???
im also good to test. might be sending the phone in though so sooner rather than later would be good. It seems that everything starts with the ActivityManager file... i could be wrong though.
Flyhalf205 said:
I've been reading a lot and CM10 seems like it has problems with MHL anyways. You say it tries to push it through USB but just doesn't know how to. That would be kernel issue would it not?
I will be able to start testing when I get my MHL adapter back tomorrow. I got a lot of free time to test since I'm done updating recoveries for now
EDIT: I reading more and saw where one guy somehow changed his refresh rate to [email protected] inside of the kernel. So is it somewhere in there most likely???
Click to expand...
Click to collapse
Kernel is built with HTC source. I would think it would carry over but I'm no way a kernel dev. The jar file posted in the other thread might be needed but I haven't had time to look at it yet. As it sits now the phone doesn't know how to pass the information from the screen to the USB mhl to the TV. I think the reason why screen says source and just black is because its getting some sort of output.
Sent from my iPhone...
synisterwolf said:
Kernel is built with HTC source. I would think it would carry over but I'm no way a kernel dev. The jar file posted in the other thread might be needed but I haven't had time to look at it yet. As it sits now the phone doesn't know how to pass the information from the screen to the USB mhl to the TV. I think the reason why screen says source and just back is because its getting some sort of output.
Sent from my iPhone...
Click to expand...
Click to collapse
I think the real issue is as I discussed else where (where I posted the logs in CounterShrike) and the issue is that the kernel has everything it needs to utilize MHL hardware and the HDMI out driver is functioning (but separate from the actual media pipeline. The pipeline portion that MHL require to function (the middleman that takes the graphics, sound and sends them to MHL hardware) does not seem to be in our sources (not the kernel, but the libraries) because it is proprietary. I am going to experiment with trying to hack the display middleman into AOSP and see if it works, with any luck it will be drop in and won't require anything HTC specific.
In Stock once the MHL cable is connected an HDMI broadcast is sent and picked up by the DisplayListener which responds by handshaking and configuring the MHL/HDMI output of the device before handing off to the AudioListener which does the same. AOSP is not performing any of this short of identifying the MHL cable is connected and rotating the home screen for display (it also appears any portrait app besides the home screen stays in portrait mode regardless of MHL cable connected)
This is an issue affecting many MHL capable devices, NOT just the Rezound. I have read MHL does work on some AOSP devices but I have not been able to locate any source to specific roms capable of it (which could help us). I think our best bet is a hack until we can get/find proper source.
Once we can get the DisplayListener and AudioListener to handshake with MHL/HDMI hardware like Stock we can identify what else we may need to fix if we are still without picture and or audio.
synisterwolf said:
Kernel is built with HTC source. I would think it would carry over but I'm no way a kernel dev. The jar file posted in the other thread might be needed but I haven't had time to look at it yet. As it sits now the phone doesn't know how to pass the information from the screen to the USB mhl to the TV. I think the reason why screen says source and just black is because its getting some sort of output.
Sent from my iPhone...
Click to expand...
Click to collapse
Hmm..That is true. Should be taken from original source unless Chad has modified a file which I doubt that is the case.
EDIT: Or what he said above This guy has his MHL fix in his kernel at https://github.com/ZenArcade/Infusion-GB-Z/commit/e70be75f5e709ef17df9dd2705bee1b810e0a2b6
waiting for a reply back from meetmhl on exactly what files are used in the api. Hopefully it's something as simple as missing a lib.
SirGatez said:
I think the real issue is as I discussed else where (where I posted the logs in CounterShrike) and the issue is that the kernel has everything it needs to utilize MHL hardware and the HDMI out driver is functioning (but separate from the actual media pipeline. The pipeline portion that MHL require to function (the middleman that takes the graphics, sound and sends them to MHL hardware) does not seem to be in our sources (not the kernel, but the libraries) because it is proprietary. I am going to experiment with trying to hack the display middleman into AOSP and see if it works, with any luck it will be drop in and won't require anything HTC specific.
In Stock once the MHL cable is connected an HDMI broadcast is sent and picked up by the DisplayListener which responds by handshaking and configuring the MHL/HDMI output of the device before handing off to the AudioListener which does the same. AOSP is not performing any of this short of identifying the MHL cable is connected and rotating the home screen for display (it also appears any portrait app besides the home screen stays in portrait mode regardless of MHL cable connected)
This is an issue affecting many MHL capable devices, NOT just the Rezound. I have read MHL does work on some AOSP devices but I have not been able to locate any source to specific roms capable of it (which could help us). I think our best bet is a hack until we can get/find proper source.
Once we can get the DisplayListener and AudioListener to handshake with MHL/HDMI hardware like Stock we can identify what else we may need to fix if we are still without picture and or audio.
Click to expand...
Click to collapse
I believe this rom has working MHL. https://github.com/rascarlo/platfor...jb-ras-mr1/core/java/android/hardware/display
Very good work cslingerland and Flyhalf205. Could one of our AOSP devs check this code out and see if compiling it into the ROM resolves our MHL problems? I do not currently have a development environment setup Someone would likely beat me to having a compiled library ready. I would have to D/L some source first as I haven't done any kernel dev work since Gingerbread. Thanks!
FYI, HDMI/MHL has nothing to do with USB, they just share a connector (it can do USB or MHL, not both).
SirGatez said:
Very good work cslingerland and Flyhalf205. Could one of our AOSP devs check this code out and see if compiling it into the ROM resolves our MHL problems? I do not currently have a development environment setup Someone would likely beat me to having a compiled library ready. I would have to D/L some source first as I haven't done any kernel dev work since Gingerbread. Thanks!
Click to expand...
Click to collapse
i would, but that is the very reason i started this thread. i dont know exactly what files we need and what ones need to be modified.
i was hoping some dev would have more knowledge to be able to look at it and know
Im running the Malaysk ROM for RK3188 on my Eonon GA5153F
Since flashing the Malaysk ROM my bluetooth settings keep reverting to default, carkit device name etc.
Even if I manage to change them and even hold the settings for a coupe of boots on rare occasions they always revert to carkit and the default pin.
This problem has repeated over 2 versions of the ROM and posting in the Malaysk RK3188 thread brought nothing useful in the way of info.
Anyone have any ideas or suggestions how to sort this out, its very annoying and I desperately need bluetooth handsfree back for work purposes.
Dont know if its relevant - I also have the GA5153F and although everything was fine with Malaysks 4.4. ROM - when i updated to his 5.1 version - bluetooth did not work until I changed the bluetooth adapter in Factory Settings to the non "b" version (same model number) since then it works great.
Yep, youll get nothing with the wrong adapter set.
Unfortunately this is a different fault.
Anybody?
I know others have suffered this problem, doesnt anyone have any other suggestions?
mindriot said:
Anybody?
I know others have suffered this problem, doesnt anyone have any other suggestions?
Click to expand...
Click to collapse
Get a Parrot BT. I am using a MKI9200. It is simple to install and call quality is 100x better.
m00n61 said:
Get a Parrot BT. I am using a MKI9200. It is simple to install and call quality is 100x better.
Click to expand...
Click to collapse
Im sure it is, but it doesnt help solve the real fault with the kit Ive already purchased, fitted, and seriously need to function as I regularly need to take calls when driving, Im a courier.
Frankly I didnt have any call quality issues when it was working, its the total lack of function thats a bit of an issue!
Is this a hardware fault? Is it a Rom fault? IS it a media board fault? IS it as simple as a file somewhere being over written or with bad permissions?
Non b worked for me but now I have no wifi
Sent from my SM-N915T using XDA-Developers mobile app
mindriot said:
Im sure it is, but it doesnt help solve the real fault with the kit Ive already purchased, fitted, and seriously need to function as I regularly need to take calls when driving, Im a courier.
Frankly I didnt have any call quality issues when it was working, its the total lack of function thats a bit of an issue!
Is this a hardware fault? Is it a Rom fault? IS it a media board fault? IS it as simple as a file somewhere being over written or with bad permissions?
Click to expand...
Click to collapse
It is essentially a manufacturer (software) issue. Malaysk has mentioned somewhere that Chinese developers messed up the BT stack. You must understand that these units use a plethora of BT boards from various suppliers AND in various HW revisions. Nobody will work on a universal BT service that accommodates all these boards. Your best bet, if you want to use the on-board BT, is to find a ROM that works, through trial and error, and stay with that one.
m00n61 said:
It is essentially a manufacturer (software) issue. Malaysk has mentioned somewhere that Chinese developers messed up the BT stack. You must understand that these units use a plethora of BT boards from various suppliers AND in various HW revisions. Nobody will work on a universal BT service that accommodates all these boards. Your best bet, if you want to use the on-board BT, is to find a ROM that works, through trial and error, and stay with that one.
Click to expand...
Click to collapse
Thanks I am aware of the hardware diversity. It is frustrating that these companies have a weak attitude to stability. However the original rom had functional Bluetooth, and the Malaysk rom is supposed to be based upon it, thats what is also frustrating.
I tried posting in the Malaysk thread but it was largely ignored, scoffed at and lost in all the noise.
Anyone else?
In my quest for the best combination of features, in light of interchangeable PX5 SOMs, I may want to transfer the BT module that works best to the HU with the best screen. I'm not worried about the soldering and of course the BT selection needs to adjust in the factory settings. Is there a known reason why this would or wouldn't work?
Which by module is "best".
marchnz said:
Which by module is "best".
Click to expand...
Click to collapse
I'm sure that's a controversial question. When I first got an Oreo HU it had a BC6 BT module, and my boss said it sounded very good. Presently I'm running an Oreo SOM in a KSP HU, with an SD-968 module. At least I think it's an SD-968; I lost the MCU configuration, but it functions when set to SD-968 and I recall that's what it was. Maybe I'll know for certain the next time I open the HU. Anyhow this HU got a poorer critique when used on a call. It's all very uncertain since there are so many other factors, the MCU, the amplitude of the MIC input, the HU circuitry, the quality of the phone's connection, and maybe the ROM has an effect also. Perhaps I'll get around to doing a careful study.
Update:
The HU with "good" BT has a short red wire antenna connected to the BT card, which is vertical. This gives me something to try on the HU with "bad" BT. The symptom is, while making a call, the sound fades out a lot, it is not a steady consistent connection. I don't think it's the phone's connection doing this.
xdamember2 said:
I'm sure that's a controversial question. When I first got an Oreo HU it had a BC6 BT module, and my boss said it sounded very good. Presently I'm running an Oreo SOM in a KSP HU, with an SD-968 module. At least I think it's an SD-968; I lost the MCU configuration, but it functions when set to SD-968 and I recall that's what it was. Maybe I'll know for certain the next time I open the HU. Anyhow this HU got a poorer critique when used on a call. It's all very uncertain since there are so many other factors, the MCU, the amplitude of the MIC input, the HU circuitry, the quality of the phone's connection, and maybe the ROM has an effect also. Perhaps I'll get around to doing a careful study.
Update:
The HU with "good" BT has a short red wire antenna connected to the BT card, which is vertical. This gives me something to try on the HU with "bad" BT. The symptom is, while making a call, the sound fades out a lot, it is not a steady consistent connection. I don't think it's the phone's connection doing this.
Click to expand...
Click to collapse
Interesting write up. I would have thought that the md725 be a contender, because it is the integrated BT/wifi chip, which is connected directly to the SOM via USB. Seems the developers have a very poor BT implementation.
Agree multiple factors from mic to module.
Recently I bought comfast CF-WU725B USB card, to see if It can be used instead of integrated BT/WIFI unit.
Mine MCU has md725, so as a BT HF unit it's useless!
Lot of "hishes", echoes, and sound quality like, when you will be almost to far from receiver.
But the problem is that when I plug this card to USB port in some time unit will freeze, and only reboot helps.
I can tell that drivers are get loaded, cause card LED start's to glow.
But when I disable BT from Factory Settings I get no BT, no WIFI and when I connect this card to USB its drivers aren't loaded (no LED light on card).
Is there anyone here that tested this card with success?
silo said:
Recently I bought comfast cf-wr302s USB card, to see if It can be used instead of integrated BT/WIFI unit.
Mine MCU has md725, so as a BT HF unit it's useless!
Lot of "hishes", echoes, and sound quality like, when you will be almost to far from receiver.
But the problem is that when I plug this card to USB port in some time unit will freeze, and only reboot helps.
I can tell that drivers are get loaded, cause card LED start's to glow.
But when I disable BT from Factory Settings I get no BT, no WIFI and when I connect this card to USB its drivers aren't loaded (no LED light on card).
Is there anyone here that tested this card with success?
Click to expand...
Click to collapse
Have a look at this thread
What chipset does the sd-968 have? I know the md-725 is a rtl8723bu
Any source to buying a md725 type1 board? I'm afraid my unit has a type2.
Regards.
Pachis83 said:
Any source to buying a md725 type1 board? I'm afraid my unit has a type2.
Regards.
Click to expand...
Click to collapse
I only found a type 1 by buying a GS xtrons board, desoldering and transplanting into my JY board, replacing the type 2.
suspect it's a matter of factory configuration of type 1 and 2 by the OEM but haven't been able to validate yet.
marchnz said:
I only found a type 1 by buying a GS xtrons board, desoldering and transplanting into my JY board, replacing the type 2.
suspect it's a matter of factory configuration of type 1 and 2 by the OEM but haven't been able to validate yet.
Click to expand...
Click to collapse
It's a problem then... I was expecting to be able to buy a usb dongle from aliexpress with type 1 RTL chip :crying:
@marchnz regarding this post https://forum.xda-developers.com/showpost.php?p=75868058&postcount=219 , could it be a solution to modify the sh file forcing goccsk to be used?
Regards.
P.D. Could it be a type 1 module? https://www.aliexpress.com/item/RTL...150Mbps-100-Original-and-New/32843823199.html
P.D. 2: Found!!! https://es.aliexpress.com/item/RTL8...U-V1-2-13-4-12-2mm-WIFI-GSPI/32471521628.html
Exactly as the one shown in the first post. I will buy one and let you know.
I havent given up yet, but havent found a supplier.
---------- Post added at 04:16 PM ---------- Previous post was at 04:11 PM ----------
Pachis83 said:
It's a problem then... I was expecting to be able to buy a usb dongle from aliexpress with type 1 RTL chip :crying:
@marchnz regarding this post https://forum.xda-developers.com/showpost.php?p=75868058&postcount=219 , could it be a solution to modify the sh file forcing goccsk to be used?
Regards.
P.D. Could it be a type 1 module? https://www.aliexpress.com/item/RTL...150Mbps-100-Original-and-New/32843823199.html
P.D. 2: Found!!! https://es.aliexpress.com/item/RTL8...U-V1-2-13-4-12-2mm-WIFI-GSPI/32471521628.html
Exactly as the one shown in the first post. I will buy one and let you know.
Click to expand...
Click to collapse
I have previously seen these, your pic is a type 2 but a type 1 is needed. Type 1 appear to have "GOC-MD725" stamped on them - let me know how you get on, if it works or not.
See my thread: https://forum.xda-developers.com/an...ment/md725-type-1-type-2-module-swap-t3795575
marchnz said:
I havent given up yet, but havent found a supplier.
---------- Post added at 04:16 PM ---------- Previous post was at 04:11 PM ----------
I have previously seen these, your pic is a type 2 but a type 1 is needed. Type 1 appear to have "GOC-MD725" stamped on them - let me know how you get on, if it works or not.
See my thread: https://forum.xda-developers.com/an...ment/md725-type-1-type-2-module-swap-t3795575
Click to expand...
Click to collapse
Yes, my fault, I though the type 1 was the one with the white back side.
I will try to search for GOC-MD725 and let you know.
Regards.
Pachis83 said:
Yes, my fault, I though the type 1 was the one with the white back side.
I will try to search for GOC-MD725 and let you know.
Regards.
Click to expand...
Click to collapse
The module is made by "goodocomm" - www.goodocom.com
I couldn't find email contact details. Perhaps someone here might try.
marchnz said:
The module is made by "goodocomm" - www.goodocom.com
I couldn't find email contact details. Perhaps someone here might try.
Click to expand...
Click to collapse
Update: I have been in touch with Goodocomm, they have advised "next week" and hope to secure a number of modules which I would then offer to members.
- M
im interested in buying one.
marchnz said:
Update: I have been in touch with Goodocomm, they have advised "next week" and hope to secure a number of modules which I would then offer to members.
- M
Click to expand...
Click to collapse
Great to know that.
Finally my unit has type 1 module, it's running Oreo and working ok.
Even I removed 7floor hardware mod and now using Wadzio modded bios, everything runs ok.
Thanks for your support anyway marchnz.
Regards.
Pachis83 said:
Great to know that.
Finally my unit has type 1 module, it's running Oreo and working ok.
Even I removed 7floor hardware mod and now using Wadzio modded bios, everything runs ok.
Thanks for your support anyway marchnz.
Regards.
Click to expand...
Click to collapse
where did you get module?
silo said:
where did you get module?
Click to expand...
Click to collapse
It was a mistake, my unit always had a type 1 module.
Regards.
Pachis83 said:
It was a mistake, my unit always had a type 1 module.
Regards.
Click to expand...
Click to collapse
So did you find someone that would sell you one of these modules in the end? I'd still like to get hold of one as I had the um02wbs-8723bu-v1.2 which I removed and replaced with a USB MD-725 Type 2 (this was before Oreo was out).
bjt2 said:
So did you find someone that would sell you one of these modules in the end? I'd still like to get hold of one as I had the um02wbs-8723bu-v1.2 which I removed and replaced with a USB MD-725 Type 2 (this was before Oreo was out).
Click to expand...
Click to collapse
No, I didn't find anyone. My unit had Type 1 from factory, I was mistaked thinking it was a type2 one.
Hi there,
At 4pda, they are writing, that some PX5 units have troubles with WiFi/USB below 0°C.
It looks like my Witson unit (MX2 MCU, PX5, Android 8) suffers from exactly this problem. The last days we had warm temperature and USB and WiFi worked perfectly.
Now I went outside and the issues are back. It's 0°C now here!
Can anyone confirm this issue?
At 4PDA, they suggest a fix by adding a screw-whole + screw to better fix the proccessor unit:
https://4pda.ru/forum/index.php?s=&showtopic=883219&view=findpost&p=77467642
It looks like the processor unit is only fixed by 2 and not 3 screws and especially the two most outside pins, which are responsible for wifi and usb suffer from loosing contact with cold temperature.
I'm keen on trying to hardware fix. But I'd like to know if someone has experience with this?
Christian
Seems like a easy issue to check for and then apply if your unit has this issue. You might help others by testing the solution and posting result/images.
marchnz said:
Seems like a easy issue to check for and then apply if your unit has this issue. You might help others by testing the solution and posting result/images.
Click to expand...
Click to collapse
I now read the whole post in an ugly into german translated version.
The theory with the processor unit is not confirmed, the people over there discuss about powering issues for the usb ports, temperature-related problems etc. No finally confirmed fix seems availbale yet.
As my unit is less than two weeks old, I am claiming warranty. At least I purchased trough an UK dealer with paypal, so first I hope for a replacement.
If I don't make progress with that, I'll open the unit and look for the issue.
If someone elso would have a confirmed working fix, I'd try it.
BR
Christian
gforums said:
I'm keen on trying to hardware fix. But I'd like to know if someone has experience with this?
Click to expand...
Click to collapse
There's another thread where a few of us have been researching this problem. The fix is posted HERE. There's no need to open the unit.
There's links in that thread to the 4pda forums where they explain what the issue is also. Long story short, it ends up being a manufacturing defect relating to the USB host controller. Newer versions of the board don't have this problem. But I can confirm the above fix does work like a charm, I've tested it several times.
Hazard15301 said:
There's another thread where a few of us have been researching this problem. The fix is posted HERE. There's no need to open the unit.
There's links in that thread to the 4pda forums where they explain what the issue is also. Long story short, it ends up being a manufacturing defect relating to the USB host controller. Newer versions of the board don't have this problem. But I can confirm the above fix does work like a charm, I've tested it several times.
Click to expand...
Click to collapse
Hi there, will comment in the thread you linked. I have running that fix with tasker already but still have partial drops of the host controller. I'm also working on a tasker task to switch WiFi on as soon as it gets off.
gforums said:
Hi there, will comment in the thread you linked. I have running that fix with tasker already but still have partial drops of the host controller. I'm also working on a tasker task to switch WiFi on as soon as it gets off.
Click to expand...
Click to collapse
If anyone is still interested in a hardware fix, my KSP units have a 5-pin IC for USB current limiting and I found if the part is cooled, the USB will not turn on when it wakes up. I replaced one with a TPS2001DDBVT, same package and pinout but better specs. It passed the bench test. I haven't gotten around to installing the HU yet.
Update: I installed the unit with replaced ic, and it behaved differently, though not yet correctly.
It's worth noting, a Dasaita HU which has not exhibited the low-temperature wifi issue has the same USB hub chip, but a different (much larger) crystal attached.
I installed the newer usb hub chip as mentioned in the other thread. No more low temperature problems, however if I reboot the unit via software (with a rooted app), the wifi does not come on. One must reboot with the reset hole. Do not try this while driving.
xdamember2 said:
If anyone is still interested in a hardware fix, my KSP units have a 5-pin IC for USB current limiting and I found if the part is cooled, the USB will not turn on when it wakes up. I replaced one with a TPS2001DDBVT, same package and pinout but better specs. It passed the bench test. I haven't gotten around to installing the HU yet.
Update: I installed the unit with replaced ic, and it behaved differently, though not yet correctly.
It's worth noting, a Dasaita HU which has not exhibited the low-temperature wifi issue has the same USB hub chip, but a different (much larger) crystal attached.
Click to expand...
Click to collapse
Hello
Can you make a photo of crystal and send it here?
Dasaita change something in board design (usb hub for sure) and currently doesn't exhibit cold temp bug.
Info confirmed with my friend with new unit.
I have older unit (from September) with older usb hub and need to make an upgrade.
mahtew said:
Hello
Can you make a photo of crystal and send it here?
Dasaita change something in board design (usb hub for sure) and currently doesn't exhibit cold temp bug.
Info confirmed with my friend with new unit.
I have older unit (from September) with older usb hub and need to make an upgrade.
Click to expand...
Click to collapse
Thanks for the info and question, I will send a picture, I can also compare to an earlier model, that's much easier than trying to trace the current circuit.
mahtew said:
Hello
Can you make a photo of crystal and send it here?
Dasaita change something in board design (usb hub for sure) and currently doesn't exhibit cold temp bug.
Info confirmed with my friend with new unit.
I have older unit (from September) with older usb hub and need to make an upgrade.
Click to expand...
Click to collapse
Here is a picture
mahtew said:
Hello
Can you make a photo of crystal and send it here?
Dasaita change something in board design (usb hub for sure) and currently doesn't exhibit cold temp bug.
Info confirmed with my friend with new unit.
I have older unit (from September) with older usb hub and need to make an upgrade.
Click to expand...
Click to collapse
Hi
I have the same problem on my Dasaita bought on september 2018!
which upgrade do you suggest? hardware or software?
the problem occurs only with the dab module connected to the cable with 2 usb, while the single USB cable, which I connected the 4G wi-fi router, always works.
If I will installed the hal9k ROM, could I fix the problem?
thanks
Alexander_Kwame said:
Hi
I have the same problem on my Dasaita bought on september 2018!
which upgrade do you suggest? hardware or software?
the problem occurs only with the dab module connected to the cable with 2 usb, while the single USB cable, which I connected the 4G wi-fi router, always works.
If I will installed the hal9k ROM, could I fix the problem?
thanks
Click to expand...
Click to collapse
I'm going for HW repair. I've ordered GL852 sop28 from ALiexp (0,55+3,4USD shipping).
Dasaita knows about problem with GL850, but they proposed to replace chip by myself or to send them SOM board and wait till they resend it back. well, i'm definitelly not happy with their response.
I hope that replacing USB hub will solve at least one other problem - random unmounting usb drives and problems with copying files from usb to sd-card.
mahtew said:
I'm going for HW repair. I've ordered GL852 sop28 from ALiexp (0,55+3,4USD shipping).
Dasaita knows about problem with GL850, but they proposed to replace chip by myself or to send them SOM board and wait till they resend it back. well, i'm definitelly not happy with their response.
I hope that replacing USB hub will solve at least one other problem - random unmounting usb drives and problems with copying files from usb to sd-card.
Click to expand...
Click to collapse
How could I know if I have GL850 or GL852?
Alexander_Kwame said:
How could I know if I have GL850 or GL852?
Click to expand...
Click to collapse
You need to open-up your HU to check. Also there is a thread on xda regardig WiFi/BT issues;
https://forum.xda-developers.com/showpost.php?p=78295553&postcount=123
https://forum.xda-developers.com/showpost.php?p=78204931&postcount=70
and I think that you can check a type of the hub with app USB HUB
mahtew said:
You need to open-up your HU to check. Also there is a thread on xda regardig WiFi/BT issues;
https://forum.xda-developers.com/showpost.php?p=78295553&postcount=123
https://forum.xda-developers.com/showpost.php?p=78204931&postcount=70
and I think that you can check a type of the hub with app USB HUB
Click to expand...
Click to collapse
Ok. I'm going to check the chip model.
I haven't problems with the Wi-Fi or BT.
when the temperature is low the DAB module connected to the double USB cable doesn't work, everything else are fine.
could I have your same problem?
I changed the gl850 ssop28 with the better version gl852g. Now I have no real problems anymore with my xrc unit. There is a software fix in hal9k 3.1.1 in the mod settings but it was only working when it was not to cold. I had in cold days allway to wait and reboot the system ...
crazybird82 said:
I changed the gl850 ssop28 with the better version gl852g. Now I have no real problems anymore with my xrc unit. There is a software fix in hal9k 3.1.1 in the mod settings but it was only working when it was not to cold. I had in cold days allway to wait and reboot the system ...
Click to expand...
Click to collapse
Change the chip is simple?
Which are items do you suggest?
There is a tutorial?
Thanks so much
Alexander_Kwame said:
Change the chip is simple?
Which are items do you suggest?
There is a tutorial?
Thanks so much
Click to expand...
Click to collapse
No, it's not really easy, but without no skills before I did it. I just watch some desoldering and soldering videos and tried a bit with an littel another broken board with a ssop8 socket on it. I desoldered a lot and soldered a lot on it and then I change the chip on my mainboard.
Videos
I used a soldering iron beacuse I din't had a hot air station.
crazybird82 said:
No, it's not really easy, but without no skills before I did it. I just watch some desoldering and soldering videos and tried a bit with an littel another broken board with a ssop8 socket on it. I desoldered a lot and soldered a lot on it and then I change the chip on my mainboard.
Videos
I used a soldering iron beacuse I din't had a hot air station.
Click to expand...
Click to collapse
Judging from the comments you've bought this right? https://www.aliexpress.com/item/10P...96-43df-b7c8-2d03f857b97b&transAbTest=ae803_5
I might give that a shot.
Bose321 said:
Judging from the comments you've bought this right? https://www.aliexpress.com/item/10P...96-43df-b7c8-2d03f857b97b&transAbTest=ae803_5
I might give that a shot.
Click to expand...
Click to collapse
Yes, I did. It's my picture at the feedbacks.
For me was it a good shot.
Hi.
My cust-Android board is connected to a touch screen via a USB port. This touch screen fails to respond inrregularly on bi-monthly basis, which induces a great deal of agnoy for the testing process, and the product will be rolled off the manufacture lines in less than 5 months.
Currently the most troubling aspect of this whole ordeal is that we still couldn't quite decide if it's the fault of the onboard driver, the particular AOSP build we customized, schematics design for the board, which isn't done by us and the custom-designing studio vehemently denies any possible errors citing past experiences, or the cap-touch screen manufacture.
We are trying to narrow down the problem. As a group of people with mostly top-level software experience, I wanna know how to devise a plan to test this.
As of now we have installed a little robotic arm and have it touches on random places on the screen. But I'm less versed on the hardware/driver. How should I proceede? With limited knowledge, I understand frequent handshakes take place between the host side of the USB (which of course is our board) and the client side of the USB (which is the touch screen), is there and way we can document everything USB related and output to a log file on a laptop? Something like the adb logcat magic.
Can someone please help?
RagaePrince said:
Hi.
Can someone please help?
Click to expand...
Click to collapse
Hey.. whats the deal, no one?
I just want to monitor the usb connection, handshakes and/or keep-alive signals will be fine?