Related
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveats:
Audio stutters every 10sec. The only fix I've heard is using a kernel from G3rmo (unfortunately it is old), or
Code:
su
kill -9 28
Which kills the [battery] process. I'm sure this will have negative effects on the battery meter/battery life...
SD Card not working...? "Waiting for SD Card" appearing on boot...? Try putting this command in your startup.txt
Code:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
See gummbah30's post reminding us of these commands.
SD Card has partitions? (If you used a non-XDAndroid build the answer is YES) Then you need to add "no_partitions" to your startup.txt. Between the quotes on the set cmdline line. Do not put it on its own line, it goes in between the quotes! Make sure there is one space between each item.
BT might still be flaky
The CSV files from my BLAC100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Keyboard tiny/unusable? Either change the IME (long press on the input box) Get rid of it! I've heard "Hackers Keyboard" is a good alternative - many options. There's also "Better Keyboard", Swype, etc... Side load the APK using AndroidApps, adb install, etc.
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
logcat attached
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
welard said:
just like to say speakers when making a call works........loud rear speakers (speakerphone) don't work nor does sound in touch selection when going threw screen selection and playing music does not work also.....hope this helps
Click to expand...
Click to collapse
Interesting, does any sound work...? Does it play thru the earpiece instead of the rear speaker? What about previewing ringtones? Next time you pull a logcat, make sure to use -v time. Using GetLogs makes it much easier .
Thanks for testing btw. The more the merrier! If we're going to make this change global, we want to make sure no devices are left in the dust. So it's up to you guys to test and ensure that it works properly! If it doesn't, we'll try to fix it.
If anyone feels like hopping on #xdandroid on freenode while testing, that would be great! Thanks again!
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
am20033 said:
i attached the file i found on sd card after pulling the logs with getlogs. i hope this is the file you wanted.
i just added following commands to my startup, because i cant boot without them:
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave
Click to expand...
Click to collapse
Those commands are necessary if you have a SD card that doesn't play nicely. If you need 'em, put 'em in.
Thanks for the logs, I'll pass them on. Anything you can say about 'em? What happened during the logs...? Please be as specific as possible. The more information, the better.
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
arrrghhh said:
Bump...
I made a mistake. Messed up bad folks! I forgot an extremely crucial step... See the first post! Pre-install Prep .
am20033 already has given pretty good feedback, once having done this step. So send it through the ringer guys, c'mon!
Click to expand...
Click to collapse
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
welard said:
wooooow......thats all i can say......loudspeaker in call works perfect.... incall audio perfect.......touchsceen click works well......overall system louder......have not tested music but in (sound settings)....ringtone, media and alarm works well...bluetooth audio headset has lots of background noise u can hear the other person but not very well but audio is rooted to bt headset.....will test further and report back asap......
p.s. there are 5 c.s.v file in window mobile on blackstone....ive re-check and found 5.....if anyone find more please let me know, but far as i know there is 5 not 10.....thanks
Click to expand...
Click to collapse
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
arrrghhh said:
Good deal! Some headsets seem to work better than others - we'll have to work on that once everything has settled. Glad everything else is working well!
As for there only being 5 CSV's, that might be true for Blackstone. What WinMo ROM are you on...? Perhaps some other users can verify. On my RHOD running EnergyROM there's definitely 10 CSV files in \Windows\. I might ask everyone post theirs so we can detect any differences - so if anyone would like to post all the CSV's they have in a zip file here that would be great!
Click to expand...
Click to collapse
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
welard said:
im on window 6.5 kwbr rom,....im not sure if files are different than in the orignal 6.1 for blackstone........thanks
Click to expand...
Click to collapse
Post those CSV's if you could!
arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
hear are my csv's......thanks...
arrrghhh said:
Post those CSV's if you could!
Click to expand...
Click to collapse
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
cbolumar said:
Thank's Arrrghhh , that is my best news today .
I'm a former HD owner and today i have a HD mini Photon , my current Android ROM is working very well .
The only real problem for me is the audio routing . Could you give me some help to test this in Photon? I can try to change my ROM in order to apply your fix. Don't worry if i don't have success doing that , i know devices are not the same and i don't disturb you .
Because this is HD forum if you want you can PM me.
Thank's a lot
Click to expand...
Click to collapse
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
arrrghhh said:
If you're on a native Android device and you're having audio routing problems I would talk to the developer of the ROM. If you re-read the first post, I detail why we have audio routing problems to day, and why this test build fixes those issues.
Your issue is completely different and entirely unique compared to our woes. Sorry.
Click to expand...
Click to collapse
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
cbolumar said:
Thank's arrrghhh , Photon is a WM 6.5 device (maybe the last HTC WM device) and the issue is the same I had in my blackstone for two years. (BT pairing but not audio ) it was my bigger problem there and with photon .... having the same problem..
I'm reading some times the blackstone thread looking for some light about this issue and today i found your thread. Trust me , the issue is the same and the way to resolve it must be similar.
I had success booting android HD blackstone roms in photon (more or less) and i will try to test your build. at the moment the booting animation start well but never end.
I'm changing some modules to obtain a bootable build but i don't know which libs or kernel modules are you changing here.
Thank's
Click to expand...
Click to collapse
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
arrrghhh said:
Oh I see.
Others have this same problem...? I'm wondering if it's your headset, or the port. Do you know how audio routing works on the port for the Mini? Is it a kernel-only affair, or does userland effect it...?
Click to expand...
Click to collapse
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
cbolumar said:
Is a general problem , I don't know if the problem is only in the kernel but i can give you some issues we have with the sound:
- the stereo wired headset sound only works if we use headset with micro , if we use headset without micro the sound is mono.
- The fm radio sound only works if we start de FM radio in WM before run haret , in other case we have only 5 seconds sound in Android FM radio, after 5 seconds the sound stops suddenly.
- the loudspeaker and sound in general in incoming calls is very low.
- The Bluetooth headset and the bluetooth hand free paired without problems but not redirect the sound.
I think the problem is not so different you want fix here in blackstone.
Click to expand...
Click to collapse
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
arrrghhh said:
The fixes here apply to MSM7k devices. I'm not sure what you would need to port it to other devices... pretty sure our kernel would not work on your phone. That's going to be the hurdle. I would encourage you to analyze the userland stuff tho - that certainly might be useful to you.
Click to expand...
Click to collapse
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
cbolumar said:
Thank's arrrghhh , the hD mini have the MSM7227 processor, i will follow here your work.
Click to expand...
Click to collapse
Don't misconstrue, I haven't done any of the actual development on this acoustic code .
See Jerome's tree if you want to see where this all started. A few others have cloned his tree and made some modifications. We're still working out the kinks. Perhaps it can help your port as well...
Like I said earlier, I am betting the userland stuff will work for you folks without a ton of changes (don't know for sure!). The kernel stuff for this new acoustic will need to be ported - our kernel will not work on your device.
Q&A for [4.4.x]Omni Nightlies for Find 7a/7s
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [4.4.x]Omni Nightlies for Find 7a/7s. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I installed the nightly yesterday, got everything working, things have been going great... Except for one thing - my camera isn't working! Stock camera takes an entirely blank image and no file is saved, google camera doesn't take one at all. Anyone have any clues as to why? My searches are coming up empty.
Random freezes while gaming
Everything seems perfect except those random freezes I get while I'm gaming.
I'm on 02.11 , LVM setup, clean install.
Here is the logcat i took right after a freeze if you can get anything from it
Thx,
Hi,
I'd like to use Omni with LVM enabled to unify the partitions, but is it possible to then also use Link2SD and add my external SD card to the storage pool? I have all my music on the ext SD card and my car only sees the primary drive when plugged in.
slikvik said:
Hi,
I'd like to use Omni with LVM enabled to unify the partitions, but is it possible to then also use Link2SD and add my external SD card to the storage pool? I have all my music on the ext SD card and my car only sees the primary drive when plugged in.
Click to expand...
Click to collapse
I have no idea regarding Link2SD, I've never found a valid use case for it for years.
As to the car only seeing the internal drive - that's kind of strange. MTP can access both internal and external storage, and UMS (even if it were working) would only be able to access the external card anyway (due to the internal one being ext4 even in a split configuration...)
Thanks for replying Entropy!
Maybe I could put the question another way if Link2SD isn't adequate....is there a way of including the external SDCard into the unified storage either by the LVM or another app so I just have one large volume?
With regards to the car, all I can say is that with my Nexus 4 it scanned all the music on it fine, but when I upgraded to the FInd 7a (with music on my ext SDCard) it only picks up the few songs on the internal storage. Hence my request above - although given I'd never take out the 64Gb card I'd prefer it to all be unified anyway.
Thanks
slikvik said:
Thanks for replying Entropy!
Maybe I could put the question another way if Link2SD isn't adequate....is there a way of including the external SDCard into the unified storage either by the LVM or another app so I just have one large volume?
With regards to the car, all I can say is that with my Nexus 4 it scanned all the music on it fine, but when I upgraded to the FInd 7a (with music on my ext SDCard) it only picks up the few songs on the internal storage. Hence my request above - although given I'd never take out the 64Gb card I'd prefer it to all be unified anyway.
Thanks
Click to expand...
Click to collapse
Adding the external SD to the LV pool would cause MASSIVE performance issues for the entire system.
Not sure what's going on, unless your car's MTP implementation is semi-broken. I will double check later this week but I'm POSITIVE both external and internal storage appear in MTP.
A while back I read that Omni Rom had integrated a feature like the Nexus 5 had that let you type a name in the phone app, and you would get results back. Is this feature still in the Rom, and how do I enable it if so?
omni rom oppo find 7a
when call in and out,the screen blank and the touch screen not response untill the call been cancel..help please..
Hey all. Just got omni and am really liking it. However im getting significantly worse battery life than before - seems ok when in use just not great in standby. Android kernel is the main culprit according to gsam. Im on the 17/11 nightly if that helps. Any tips welcomed as other than this the rom is great.
krul apis said:
when call in and out,the screen blank and the touch screen not response untill the call been cancel..help please..
Click to expand...
Click to collapse
I have the same problem. As soon as I answer a call, the Screen goes black and stays black until I or the other person end the call.
Then you have to press the Power button two times to turn the screen on. I have checked for any option to enable screen during calls, but haven't found anything useful. The problem also exists with skype video calls.
Balimba said:
I have the same problem. As soon as I answer a call, the Screen goes black and stays black until I or the other person end the call.
Then you have to press the Power button two times to turn the screen on. I have checked for any option to enable screen during calls, but haven't found anything useful. The problem also exists with skype video calls.
Click to expand...
Click to collapse
Did you come from ColorOS 2.0?
There are some issues with proximity sensor when coming from newer versions of ColorOS we haven't had time to investigate. (We're busy with 5.0 bringup at the moment.)
Entropy512 said:
Did you come from ColorOS 2.0?
There are some issues with proximity sensor when coming from newer versions of ColorOS we haven't had time to investigate. (We're busy with 5.0 bringup at the moment.)
Click to expand...
Click to collapse
Thanks Entrophy512..after restore to color os 1.2.7,its back to normal again..
Feature question
First of all I apologize for the noob feature question. I've unfortunately never had the pleasure of using Omni in any of my devices so I don't know if it's there.
My Find7a's hardware keys are shot. They just stopped working one day out of the clear blue. They take like 50 presses to register a hit. I was stock Color OS at the time and did the build.prop hack to get the softkeys. I didn't want to mess around with shipping it back since I don't live in the US and it would be difficult.
I am currently on Gummy ROM, which does have a specific setting for enabling softkeys. Does Omni have this? If so, I can make the jump, since everything else sounds wonderful and the LVM solves my current space crunch for apps better than any partition hacks I've seen before and dit not want to touch.
If it does, would someone be kind enough to point me to the specific place where I can enable them? If/when I do the whole process to do LVM and flash Omni, I will want to enable them with as few presses of Home or Back as possible, since they will be painfully unresponsive (or even totally dead by now, so if there is an adb way to enable it or a way to do it without touching the hardware keys it would be fantastic).
Thank you and I apologize again for the question. I just read about 15 pages of this thread and also searched for "softkeys" and found nothing so I thought I would ask.
el_ochito said:
First of all I apologize for the noob feature question. I've unfortunately never had the pleasure of using Omni in any of my devices so I don't know if it's there.
My Find7a's hardware keys are shot. They just stopped working one day out of the clear blue. They take like 50 presses to register a hit. I was stock Color OS at the time and did the build.prop hack to get the softkeys. I didn't want to mess around with shipping it back since I don't live in the US and it would be difficult.
I am currently on Gummy ROM, which does have a specific setting for enabling softkeys. Does Omni have this? If so, I can make the jump, since everything else sounds wonderful and the LVM solves my current space crunch for apps better than any partition hacks I've seen before and dit not want to touch.
If it does, would someone be kind enough to point me to the specific place where I can enable them? If/when I do the whole process to do LVM and flash Omni, I will want to enable them with as few presses of Home or Back as possible, since they will be painfully unresponsive (or even totally dead by now, so if there is an adb way to enable it or a way to do it without touching the hardware keys it would be fantastic).
Thank you and I apologize again for the question. I just read about 15 pages of this thread and also searched for "softkeys" and found nothing so I thought I would ask.
Click to expand...
Click to collapse
Yes, but I can't remember exactly where. I'm currently not on it at the moment. I think there's a Button in the Settings menu
I cant connect my phone with computer. With color os 1.2.7i i could but now i cant. Only PTP works. MTP doesnt.. I tried many solutions, but nothing..
lazostat said:
I cant connect my phone with computer. With color os 1.2.7i i could but now i cant. Only PTP works. MTP doesnt.. I tried many solutions, but nothing..
Click to expand...
Click to collapse
Worked fine here last time I tried it. I'll try again tonight.
Now it worked. I uninstalled all hidden drivers from system devices and installed again.
I have some questions.
Where is the compass program?
Where is maxx audio?
Where is the "ultra" option in camera?
Where is the app drawer?
Why in antutu scores 41.000 and with color os 1.2.7i scores 45.000? Also i played some games and i have some lag. With color os i didnt.
Pls answer me.
Aosp roms don't have any ColorOS proprietary stuff. Also, benchmarks are unreliable. If you feel a game is lagging, try messing with the Performance settings. I personally find it just as smooth
farenteria said:
Aosp roms don't have any ColorOS proprietary stuff. Also, benchmarks are unreliable. If you feel a game is lagging, try messing with the Performance settings. I personally find it just as smooth
Click to expand...
Click to collapse
Benchmarks are unreliable and rarely mean that much, however in general you will always see AOSP-derivative projects on Qualcomm hardware benchmark a bit lower than official factory firmwares as there are a number of proprietary tweaks that Qualcomm doesn't allow to be put into open source projects.
That said, the reduced bloat in AOSP-derivative firmwares more than makes up for the slight reduction in benchmark epeen size.
Q&A for [ROM][KITKAT][UNOFFICIAL] Cyanogenmod 11 for SM-T800 16gb
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][KITKAT][UNOFFICIAL] Cyanogenmod 11 for SM-T800 16gb. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
installed
Just installed the ROM and it looks great. I did notice the camera app doesnt function. Anyone else with this issue?
other camera apps tested
Tested another camera app and still no dice.
willharrell said:
Tested another camera app and still no dice.
Click to expand...
Click to collapse
Use google camera it works. Available from the play store
Sent from my HTC One_M8 using XDA Premium HD app
jrock60 said:
Use google camera it works. Available from the play store
Sent from my HTC One_M8 using XDA Premium HD app
Click to expand...
Click to collapse
Yes. Google camera works well for me also.
Sent from my C6806 using XDA Free mobile app
There is one Samsung accessibility feature that I really need: you can invert the screen colors (mainly to get white text on black background) and assign this to a triple click of home button. Any chance this can be ported to CM11 build?
(Thanks to the devs for their awesome work.)
Will there ever be a CM11 build for the chagalllte version?
rodrigorajao said:
Will there ever be a CM11 build for the chagalllte version?
Click to expand...
Click to collapse
if someone who owns the LTE version can do it then I guess it can be built... if I had more skills and time I would do that but atm I can't... also would need alot of help because I have never built ROM's before
sm t-800 / sm t-805
Would this rom be feasible only for the t-800 model or also for the t-805 (lte) model?
Best regards
Omg
Just curious, dirty flashed cm-11-20141030-v2L-chagallwifi.zip about half an hour ago over the same download yesterday, but youtube still has problems, should i have done a clean install?
Multi-User Name/Picture Not Showing Up
First of all, thank you very much. This ROM is great. Second, I added a second user and they set up their account, but "new user" still appears on the lock screen and in the notification shade (not their name/picture). This is really minor, but I was just curious if anyone else has experienced this.
I downloaded cm-11-20141102-UNOFFICIAL-chagallwifi.zip a couple of hours ago (before it was deleted / re-uploaded I think) and flashed it on a SM-T800. Most of the functions seem to be working fine: WiFi, Google Play Store, YouTube, Video with VLC (avi, mpg, flv)... Also, when I turn off the tablet and connect the charger, it does NOT go in recovery mode (as reported in #110 and later fixed).
I am still catching up on the thread as I just got my tablet so I might have missed some stuff, but I was under the impression that issues with Camera2 where fixed in the latest build by nvertigo67. However, when I start the camera (v2.0.002), it displays a black screen with only the icons on the right and crashes a couple of seconds later (logcat attached to this post in case it helps).
Thanks for the hard work.
PS: Not that it really matters, but the file cm-11-20141102-UNOFFICIAL-chagallwifi.zip.md5sum linked in the original post contains the correct checksum but an osolete filename (and with the absolute path on Barracuda77777's computer I guess).
Camera is working fine here (2.4.023)
Display
All is looking good except the display seems to be overly saturated and too yellow. It looks like stock Samsung did with the "Movie" mode enabled. Is there somewhere to set the display to what I think Samsung called "Basic"? To me that is what produced natural looking color.
Nearly everything is great here as well, but I noticed a couple video issues today.
1) Video doesn't show up from other participants in a google hangout (just their picture)
2) Dish Anywhere app is just a black screen after logging in
Netflix, HBO Go, Slingplayer, WatchESPN, and YouTube all work great.
Has anyone else run into these issues? Thanks!
Hi i'm a french Guy so excuse me for mistakes.
You've done a great great work.
I use this rom since the beginning and it was wonderful.
I had two questions. First is it possible two had the capacitive mod of screen like on tw. On tw we could choose between classic screen or cinema or super amoled i think ?
My second question is about the battery. Do you think you can improve it, mine is less longer than the stock version, on a 48 hours day i will make a screenshot to show you my battery consumption.
I've also remark that i can't install ebay app, there was a 24 error... i've try to erase play store data but nothing to do same error.....
Thanks for your help.
nvertigo67 said:
New Build up. See posting #5.
Happy flashing
Click to expand...
Click to collapse
Installed cm-11-20141104-UNOFFICIAL-nvertigo-chagallwifi (md5: d12610c3...) on my SM-T800 over Barracuda's 20141102 build. No issue to report.
I tested Camera2 and it worked with both cameras, several resolutions, effects (color, scene) and modes (picture, panorama, movie).
Great job.
Originally Posted by Robin M
Bluetooth Won't Turn On
After a complete wipe and flashing this ROM (Nov 4 version), I cannot get Bluetooth to turn on. When I move the slider from OFF to ON, screen says "Turning Bluetooth On...." but it times out after about 8-10 seconds and never works. Wiping Cache and dalvik-cache made no difference. Bluetooth worked yesterday on stock Samsung ROM.
Everything else seems to be working fine. Haven't seen anyone report a BT issue. Has anyone experienced this, or does someone have a suggestion as to what I can try to get BT working?
Click to expand...
Click to collapse
Hi Robin M I had the same issue with BT. You just have to re-flash the kernel chagall-Ingo-v2.zip (see post #2) and then clear cache and dalvik. It worked for me on a sm-t805. Hope it will help.
CM to 805
I have the impression the main reason you are not building CM for the galaxy tab 805 is because you don't have one.
I got one, but I need it for professional reasons in weekdays GMT +1 18:00-21:00.
Also, I don't feel confident to start developing for a tablet I need for professional reasons. maybe for you people it's less of a problem
but I loved CM on my galaxy phone (GT-I9000), so I'd like to help you for the T805.
During other moments, eventually, I could give you SSH access to it (it has a 3G data connection, and as long as you don't start downloading p0rn with it, It's fine to me).
it has been rooted, and has busybox installed, so I'd have to install an SSH server and create a tunnel so you can connect.
Would this give you the necessary information you need to port your T800 CM mod to the T805?
Love the ROM and there's a saturation fix out there...
Love the ROM, but the screen is massively oversaturated by default (reds, in particular, literally hurt my eyes). Luckily, there's an apk out there that fixes this - I use "movie mode" which is the only mode that keeps my retinas attached See:
http://forum.xda-developers.com/showthread.php?t=2675721
It works on my Tab S 10.5", although it's confusingly labelled as "Advanced Settings" *under* Settings -> Display -> Advanced Settings. It would be great if something like this could be added to a future build (and the default set to movie mode - the only mode not requiring sunglasses ).
Hey guys,
First of all let me thank you for taking the time to read my question. I tried to prevent this post but as I really don`t like bricking my unit I felt like I had to confirm my suspicions, couldn`t confirm this myself as the search button has not been proven to be my friend
I have a GS (Hot Audio) unit 800 * 480 RK3066 running on a rooted Android 4.4.2 at the moment and wanted to upgrade this to 4.4.4 however since my last visit to this wonderful forum a lot a changed and given me a case of information overload. Therefor I have the following questions.
- It is not mandatory to include the MCU.img in the update package
- Otherwise I can take one of these: http://forum.xda-developers.com/showthread.php?t=3246370 (Top 4)
- I can use any update.img as long as the resolution and chip number is correct. In other words there is no need anymore to look at the model KLD/GS/KGL (This one for example: http://huifei.fs-fileserver.de/content/firmware/KK 4.4.4 Dual core Coudu Rooted /KLD/800x480/)
If you would be able to relieve me of these doubts I would be very grateful.
Thank you all again :good:
No one will shoot you. Ignore the grumps.
You are correct on all three points as long as you are sure of your head unit's make/details which sounds like you are. I know you used it for an example but in your third point you linked to Coudu's ROMs which are way outdated, stick to Malaysk's as they are superb.
Just be aware that there might be some settings (thinking of the configurable sleep timer delay) in newer ROMs that require an updated MCU so something like that won't work if your MCU is too old. But I don't know how applicable this is to you as I don't know what MCU revision you have for your GS. You can always update your MCU at a later time by itself if need be, no biggie.
Well a small update I just finished the install and to be honest I wished I would have done it much, much earlier Malasyk has done some incredible work
Thx again for your help again :good:
Anyone looking to improve the audio quality of their MTCD/E head unit has 5 options, each in their own thread scattered across 3 of the 4 MTCD forums, so I thought I d open one overarching thread for discussing and comparing all 5 options.
These mods apply to R3188/PX3 and RK3368/PX5 units, they should also work on Sofia units as well, but I dont recall reading that anyone has tried, theyll likely work on the new RK3369/Px6 hexacore units too, but again AFIAK no one has one yet.
1) The easiest and simplest way to improve sound quality is to flash one of @cs-x(RU)'s modified sound patched MCUs which give improved overall sound quality, just find one that matches you manufacturer and flash it, job done. No root required. Gives a small but useful improvement in sound quality. Thread here :
https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
2) @Wadzio has cleverly managed to implement @7floor's hardware mod (see below) in software, all thats needed is to flash one of his MCUs and install a few apps. Root is only required if you want to replace the original amp app with @Wadzio's - the original can be left installed for non root users. It doesnt work on all units yet as it requires the MCU to be modified quite heavily and @Wadzio cant spend all his time modded MCUs ! (he has released a guide on how to do it, though). It can be buggy on some units. Increases sound quality and enables much more control and more settings. Thread is here :
https://forum.xda-developers.com/an...elopment/mod-bd375xx-sound-processor-t3834657
3) @7floor's sound mod - on units without a factory fitted upgraded DSP (ie most currently), the audio chip is controlled by the MCU, @7floor's mod involves disconnecting the MCU from the audio chip and connecting the audio chip directly to the SoM so Android control it, some basic soldering skills are required. Units must be rooted, installing an app is also required. It works on Lollipop and MM units but its not currently working on Oreo units as the system cannot find a small file, however I its a minor bug that I think could be fixed easily. The mod was originally developed for the related MTCB/C units which is why the original thread is in the MTCB forum. Increases sound quality and enables much more control and more settings. Threads here :
https://forum.xda-developers.com/an.../mtc-sound-controlling-bd37xxx-sound-t3234660
https://forum.xda-developers.com/an...re-development/7floor-sound-mod-mtcd-t3624035
4) @cs-x(RU) has managed to retro fit an upgraded DSP to the same spec as the new units with factory fitted upgraded DSPs and it uses existing apps which the unit will automatically use if it detects that a DSP is fitted to the motherboard, so units dont have to be rooted. This mod wont be for everybody as it involves buying a DSP board and a lot of soldering. Increases sound quality the most. Thread here :
https://forum.xda-developers.com/an...nt/mod-simpledsp-installation-mtcd-e-t3823075
5) Buy a new unit with the upgraded DSP fitted at the factory. Thread here :
https://forum.xda-developers.com/an...eneral/dsp-units-androidautoshop-com-t3803557
this thread is incredibly helpful! Thank you!
sev said:
this thread is incredibly helpful! Thank you!
Click to expand...
Click to collapse
No probs, thats the idea.
Agreed - great idea. As a new MTCE Android head-unit owner, my head was spinning trying to figure all of this out. Unfortunately for me, this thread was a little late, but I'm sure it will be very helpful to other new users in the near future. Thank you for putting this together.
Should Viper4Android be added to your list (I'm acutally going to go that route myself instead of any of the other options - at least for now)?
Great thread @typos1, we'll done. Re. Wadzio #2 - root is not required if not replacing the stock apk.
I.E. there are two options
1. root - replacing the built in eq app or
2. Non-root - installing a second eq app.
jtrosky said:
Agreed - great idea. As a new MTCE Android head-unit owner, my head was spinning trying to figure all of this out. Unfortunately for me, this thread was a little late, but I'm sure it will be very helpful to other new users in the near future. Thank you for putting this together.
Should Viper4Android be added to your list (I'm acutally going to go that route myself instead of any of the other options - at least for now)?
Click to expand...
Click to collapse
Thanks. I havent included Viper4android, Dolbyatmos (not sure anyones tried that on a headunit actually) or any other equaliser app cos the thread was meant to be about MTCD/E specific improvements.
marchnz said:
Great thread @typos1, we'll done. Re. Wadzio #2 - root is not required if not replacing the stock apk.
I.E. there are two options
1. root - replacing the built in eq app or
2. Non-root - installing a second eq app.
Click to expand...
Click to collapse
Ta.
I never considered keeping the original amp app as an option TBH, but it means non root users can benefit from the mod, I ll edit it.
typos1 said:
Thanks. I havent included Viper4android, Dolbyatmos (not sure anyones tried that on a headunit actually) or any other equaliser app cos the thread was meant to be about MTCD/E specific improvements.
Click to expand...
Click to collapse
Ah - that makes sense. Otherwise, you'd have a gizillion different "equalizer"-type apps to include. Although, I truly think that Viper4Android is in a league of it's own and far more than a typical equalizer. I consider is a "software-based DSP", not just an equalizer - but like you said, it's not MTCD/E-specific, so I understand why it's not included.
But thanks again for putting this together - this will be a huge help for new MTCD/E owners!
I'm curious what others think of the different sound improvements. What is their favorite and why? And how do people feel about the software mods compared to Viper4Android?
I was really disappointed to find that these units didn't have a "real" 9-band EQ. At the very east, you'd think that it would be implemented via software if it can't be done via hardware. Is there any reason why it can't be done via software by the manufacturer (instead of needing to root and use Viper4Andorid in order to get a real EQ)? To me, Bass, Mid and Treble just isn't enough.
typos1 said:
Anyone looking to improve the audio quality of their MTCD/E head unit has 5 options, each in their own thread scattered across 3 of the 4 MTCD forums, so I thought I d open one overarching thread for discussing and comparing all 5 options.
These mods apply to R3188/PX3 and RK3368/PX5 units, they should also work on Sofia units as well, but I dont recall reading that anyone has tried, theyll likely work on the new RK3369/Px6 hexacore units too, but again AFIAK no one has one yet.
1) The easiest and simplest way to improve sound quality is to flash one of @cs-x(RU)'s modified sound patched MCUs which give improved overall sound quality, just find one that matches you manufacturer and flash it, job done. No root required. Gives a small but useful improvement in sound quality. Thread here :
https://forum.xda-developers.com/an...ent/mod-cs-x-mod-mtcd-e-mcu-firmware-t3816042
2) @Wadzio has cleverly managed to implement @7floor's hardware mod (see below) in software, all thats needed is to flash one of his MCUs and install a few apps. Root is only required if you want to replace the original amp app with @Wadzio's - the original can be left installed for non root users. It doesnt work on all units yet as it requires the MCU to be modified quite heavily and @Wadzio cant spend all his time modded MCUs ! (he has released a guide on how to do it, though). It can be buggy on some units. Increases sound quality and enables much more control and more settings. Thread is here :
https://forum.xda-developers.com/an...elopment/mod-bd375xx-sound-processor-t3834657
3) @7floor's sound mod - on units without a factory fitted upgraded DSP (ie most currently), the audio chip is controlled by the MCU, @7floor's mod involves disconnecting the MCU from the audio chip and connecting the audio chip directly to the SoM so Android control it, some basic soldering skills are required. Units must be rooted, installing an app is also required. It works on Lollipop and MM units but its not currently working on Oreo units as the system cannot find a small file, however I its a minor bug that I think could be fixed easily. The mod was originally developed for the related MTCB/C units which is why the original thread is in the MTCB forum. Increases sound quality and enables much more control and more settings. Threads here :
https://forum.xda-developers.com/an.../mtc-sound-controlling-bd37xxx-sound-t3234660
https://forum.xda-developers.com/an...re-development/7floor-sound-mod-mtcd-t3624035
4) @cs-x(RU) has managed to retro fit an upgraded DSP to the same spec as the new units with factory fitted upgraded DSPs and it uses existing apps which the unit will automatically use if it detects that a DSP is fitted to the motherboard, so units dont have to be rooted. This mod wont be for everybody as it involves buying a DSP board and a lot of soldering. Increases sound quality the most. Thread here :
https://forum.xda-developers.com/an...nt/mod-simpledsp-installation-mtcd-e-t3823075
5) Buy a new unit with the upgraded DSP fitted at the factory. Thread here :
https://forum.xda-developers.com/an...eneral/dsp-units-androidautoshop-com-t3803557
Click to expand...
Click to collapse
What a nice post!
Saw this video today, which led me to your post here, and I wonder if the speaker distance/delay setting works accordingly? Not expecting Pioneer-quality time alignment affect here, but a little bit of such an ability would be a big win.
jtrosky said:
Ah - that makes sense. Otherwise, you'd have a gizillion different "equalizer"-type apps to include. Although, I truly think that Viper4Android is in a league of it's own and far more than a typical equalizer. I consider is a "software-based DSP", not just an equalizer - but like you said, it's not MTCD/E-specific, so I understand why it's not included.
But thanks again for putting this together - this will be a huge help for new MTCD/E owners!
I'm curious what others think of the different sound improvements. What is their favorite and why? And how do people feel about the software mods compared to Viper4Android?
I was really disappointed to find that these units didn't have a "real" 9-band EQ. At the very east, you'd think that it would be implemented via software if it can't be done via hardware. Is there any reason why it can't be done via software by the manufacturer (instead of needing to root and use Viper4Andorid in order to get a real EQ)? To me, Bass, Mid and Treble just isn't enough.
Click to expand...
Click to collapse
The standard DSP has a 3 band equaliser and the related MTCB/C originally had this, but at some point it was changed to the fake 9 band set up (which some how takes average values for each band to make the extar 6 bands), @7floor's and @Wadzio's mods revert to the true 3 band equaliser, so one of these 2 mods is what you need to do to get a real eq.
I stopped using viper as soon as I did 7floor's mod, as I thought it was unnecessary after that, not keen on layers and layers of sound enhancements personally.
Xcaptain said:
What a nice post!
Saw this video today, which led me to your post here, and I wonder if the speaker distance/delay setting works accordingly? Not expecting Pioneer-quality time alignment affect here, but a little bit of such an ability would be a big win.
Click to expand...
Click to collapse
Thanks. Theres nothing to suggest that the delay settings dont work.
typos1 said:
The standard DSP has a 3 band equaliser and the related MTCB/C originally had this, but at some point it was changed to the fake 9 band set up (which some how takes average values for each band to make the extar 6 bands), @7floor's and @Wadzio's mods revert to the true 3 band equaliser, so one of these 2 mods is what you need to do to get a real eq.
I stopped using viper as soon as I did 7floor's mod, as I thought it was unnecessary after that, not keen on layers and layers of sound enhancements personally.
Click to expand...
Click to collapse
When I say that I want a "real" EQ, what I mean is that I want something with more than 3 bands. To me, 3 bands just isn't enough. That's why I'm interested in Viper4Android - becuase it will give me more than 3 bands and still be a "system wide" EQ. I really don't care if it's a hardware or software-based EQ - as long as it works and has more than 3 bands. I'm thinking that an octa-core unit with 4GB of RAM should be able to handle software-based EQ without issues - at least for what I'm planning to use it for... Not to mention all of the other cool stuff that only Viper4Android offers - such as the irs files. I've always been a fan of BBE and they even have irs files for BBE...
I was really disappointed to learn that the stock EQ was "fake" and was really only a 3-band EQ as a 5-band+ EQ was one of my "pre-requisites" when buying a head-unit. I'm hoping that Viper4Android will give me the extra tuning capability that I'm looking for though - becuase I REALLY like the flexibility of these Android head-units (used to WinCE head-units without any flexibility!).
Although, I haven't actually tested the unit "in car" yet, so maybe I'll be happy with the stock "fake" EQ. After all, I have an amp that has DSP built-in (auto-tuning DSP though - I can't customize it after it sets it up, which is why I still need the head-unit EQ to make small adjustments).
Great thread idea, something like this was definitely needed, and this is fairly comprehensive. I'll just put in that I have done the hardware DSP mod (Option #4 on this list) with great success. It has dramatically increased the audio quality of my unit, which was extremely poor before (Bad hiss and processing 'noise' from both RCA and speaker level outputs, which became basically unusable if you plug in anything to the USB ports).
I will note that this option is not necessarily compatible with all PX5 SOM's - I had to swap mine out in order to have the additional 4 pins required on the SOM.
jtrosky said:
When I say that I want a "real" EQ, what I mean is that I want something with more than 3 bands. To me, 3 bands just isn't enough. That's why I'm interested in Viper4Android - becuase it will give me more than 3 bands and still be a "system wide" EQ. I really don't care if it's a hardware or software-based EQ - as long as it works and has more than 3 bands. I'm thinking that an octa-core unit with 4GB of RAM should be able to handle software-based EQ without issues - at least for what I'm planning to use it for... Not to mention all of the other cool stuff that only Viper4Android offers - such as the irs files. I've always been a fan of BBE and they even have irs files for BBE...
I was really disappointed to learn that the stock EQ was "fake" and was really only a 3-band EQ as a 5-band+ EQ was one of my "pre-requisites" when buying a head-unit. I'm hoping that Viper4Android will give me the extra tuning capability that I'm looking for though - becuase I REALLY like the flexibility of these Android head-units (used to WinCE head-units without any flexibility!).
Although, I haven't actually tested the unit "in car" yet, so maybe I'll be happy with the stock "fake" EQ. After all, I have an amp that has DSP built-in (auto-tuning DSP though - I can't customize it after it sets it up, which is why I still need the head-unit EQ to make small adjustments).
Click to expand...
Click to collapse
Lol, youre the opposite of me - the only time I use the equaliser is for music older than the 1990s when I use the Rock setting, other than that I listen to it flat.
It sounds to me like you should do @Wadzio's mod, then install viper, at least @Wadzio's mod will give you the correct 3 band equaliser and not the fake 9 band one.
kaise123 said:
Great thread idea, something like this was definitely needed, and this is fairly comprehensive. I'll just put in that I have done the hardware DSP mod (Option #4 on this list) with great success. It has dramatically increased the audio quality of my unit, which was extremely poor before (Bad hiss and processing 'noise' from both RCA and speaker level outputs, which became basically unusable if you plug in anything to the USB ports).
I will note that this option is not necessarily compatible with all PX5 SOM's - I had to swap mine out in order to have the additional 4 pins required on the SOM.
Click to expand...
Click to collapse
Thanks.
Interesting what you say about the SoM differences, do you have any pics ?
typos1 said:
Lol, youre the opposite of me - the only time I use the equaliser is for music older than the 1990s when I use the Rock setting, other than that I listen to it flat.
It sounds to me like you should do @Wadzio's mod, then install viper, at least @Wadzio's mod will give you the correct 3 band equaliser and not the fake 9 band one.
Click to expand...
Click to collapse
Maybe we're not that differernt.... It's just that I'm old, so that vast majority of music that I listen to is older than the 1990s.
I just like having complete control and be able to adjust different frequencies as needed.
I would probably try @Wadzio's mod, but I have two problems:
1. I still don't have an original version of my MCU (MTCE_WWW_V2.85d_1)
2. I don't see a MTCE_WWW version of @Wadzio's mod... Some have said WWW = KLD, but without a backup of my original, not going to risk it.
I did find a MTCE_WWW version of @cs-x's mod (looks similar to @Wadzio's, but lacking loud adjustment) - but again, without having a backup of my original MCU, I'm hesitant to try it.... I did eventually convince Eonon to give me a copy of the stock ROM zip (update.zip) for my unit, but still trying to get the original MCU files...
It's killing me, but I'm being patient as I want to make sure I have a way to get back to where I started, just in case.
jtrosky said:
Maybe we're not that differernt.... It's just that I'm old, so that vast majority of music that I listen to is older than the 1990s.
I just like having complete control and be able to adjust different frequencies as needed.
I would probably try @Wadzio's mod, but I have two problems:
1. I still don't have an original version of my MCU (MTCE_WWW_V2.85d_1)
2. I don't see a MTCE_WWW version of @Wadzio's mod... Some have said WWW = KLD, but without a backup of my original, not going to risk it.
I did find a MTCE_WWW version of @cs-x's mod (looks similar to @Wadzio's, but lacking loud adjustment) - but again, without having a backup of my original MCU, I'm hesitant to try it.... I did eventually convince Eonon to give me a copy of the stock ROM zip (update.zip) for my unit, but still trying to get the original MCU files...
It's killing me, but I'm being patient as I want to make sure I have a way to get back to where I started, just in case.
Click to expand...
Click to collapse
WWW is deffo KLD and you dont have to have a back up - there are numerous WWW and KLD MCUs spread over various threads.
If youre waiting for a specific WWW 2.85 then this is also unnecessary - new MCU versions are released all the time , so your v2.85 is already out of date anyway.
In factory settings use the "Export" function, it will save your MCU settings.
typos1 said:
WWW is deffo KLD and you dont have to have a back up - there are numerous WWW and KLD MCUs spread over various threads.
If youre waiting for a specific WWW 2.85 then this is also unnecessary - new MCU versions are released all the time , so your v2.85 is already out of date anyway.
In factory settings use the "Export" function, it will save your MCU settings.
Click to expand...
Click to collapse
I'm don't really need the exact MCU, but I would at least like a WWW MCU that is equal to or greater than what I have now before I start messing with it - and so far, I haven't found one. I remember reading somewhere that the KLD MCU is ever so slightly different than the WWW MCU (I think the KLD powers off the unit with a press of the volume knob where WWW requires a press-and-hold). That may sound minimal, but I really don't want my unit shutting down if I bump the volume knob by accident - so even that little difference is enough to make me avoid the KLD MCU if I can - at least until I have a WWW version to fall back on if needed.
This is not really the right place, but if anyone reading this happens to have a stock WWW MCU file for 2.85d_1 or greater, please share. I'm assuming it's out there because I've seen a sound-modfied version of it. I just don't want to get stuck in a situation where I can't get back to where I started - epecially if I'm going to mess around trying to use KLD versions instead of WWW versions. I learned long ago to always make sure you can get back to where you started before you start "playing". I'll post a request in one of the MCU threads to see if I can find a recent WWW version, just in case I can't get it from Eonon.
jtrosky said:
I'm don't really need the exact MCU, but I would at least like a WWW MCU that is equal to or greater than what I have now before I start messing with it - and so far, I haven't found one. I remember reading somewhere that the KLD MCU is ever so slightly different than the WWW MCU (I think the KLD powers off the unit with a press of the volume knob where WWW requires a press-and-hold). That may sound minimal, but I really don't want my unit shutting down if I bump the volume knob by accident - so even that little difference is enough to make me avoid the KLD MCU if I can - at least until I have a WWW version to fall back on if needed.
This is not really the right place, but if anyone reading this happens to have a stock WWW MCU file for 2.85d_1 or greater, please share. I'm assuming it's out there because I've seen a sound-modfied version of it. I just don't want to get stuck in a situation where I can't get back to where I started - epecially if I'm going to mess around trying to use KLD versions instead of WWW versions. I learned long ago to always make sure you can get back to where you started before you start "playing". I'll post a request in one of the MCU threads to see if I can find a recent WWW version, just in case I can't get it from Eonon.
Click to expand...
Click to collapse
Seriously, youre being way, way too over cautious. That WWW is KLD is well known and you can remap the buttons in factory settings.
If you search the MCU threads you ll find a copy of a WWW MCU, but a I said, its not needed.
typos1 said:
Seriously, youre being way, way too over cautious. That WWW is KLD is well known and you can remap the buttons in factory settings.
If you search the MCU threads you ll find a copy of a WWW MCU, but a I said, its not needed.
Click to expand...
Click to collapse
I've read that being that my unit requires a CANBUS module, that key re-mapping cannot be done. Not sure if that is only for steering-wheel controls or if that also includes the physical buttons on the faceplate (I honestly didn't even realize the faceplate buttons could be remapped at all). I've very new to these radios, so yes, I am being overly cautious. In the end, if I experiment and end up with something that doesn't work right or just doesn't work like it "used to", then I'm SOL - at least until I have a copy of the current MCU, which I know at least works 100%. Believe me, I've searched and searched and searched and so far, I cannot find an MTCE_WWW_2.85d_1 or higher MCU file. I found one post that had a link to it (2.85), but the link was dead.
I'll see what Eonon comes back with tomorrow, but yes, due to previous experiences with stuff like this, I'm being very cautious - especially since my knowledge level is still low at this point. Rather be safe than sorry - especially since I'm still within my return window and am not even 100% sure that I'm keeping the unit. I must say, the CANBUS warning-chime and turn-signal sounds that I finally heard in-car yesterday were absolutely horrible - like I couldn't believe how bad.
But I do appreciate all of the input - it's all part of the learning process. I'm still reading and searching through the thousands and thousads of posts related to these radios - but it takes time... Threads like this are a huge help though!
jtrosky said:
I've read that being that my unit requires a CANBUS module, that key re-mapping cannot be done. Not sure if that is only for steering-wheel controls or if that also includes the physical buttons on the faceplate (I honestly didn't even realize the faceplate buttons could be remapped at all). I've very new to these radios, so yes, I am being overly cautious. In the end, if I experiment and end up with something that doesn't work right or just doesn't work like it "used to", then I'm SOL - at least until I have a copy of the current MCU, which I know at least works 100%. Believe me, I've searched and searched and searched and so far, I cannot find an MTCE_WWW_2.85d_1 or higher MCU file. I found one post that had a link to it (2.85), but the link was dead.
I'll see what Eonon comes back with tomorrow, but yes, due to previous experiences with stuff like this, I'm being very cautious - especially since my knowledge level is still low at this point. Rather be safe than sorry - especially since I'm still within my return window and am not even 100% sure that I'm keeping the unit. I must say, the CANBUS warning-chime and turn-signal sounds that I finally heard in-car yesterday were absolutely horrible - like I couldn't believe how bad.
But I do appreciate all of the input - it's all part of the learning process. I'm still reading and searching through the thousands and thousads of posts related to these radios - but it takes time... Threads like this are a huge help though!
Click to expand...
Click to collapse
AFAIK its only SWC, but there is a way to remap SWC anyway, so even if it applies to panel buttons it can be overcome.
You are deffo not SOL if something goes wrong, cos there are copies of WWW MCU in other threads, any WWW MCU will work "100%" and you can also use KLD MCUs. As I keep saying. Plus theres a wealth of info and help from us on here, so SOL you deffo arent.
Try remapping the panel buttons now - go into factory settings (password 126 or m123456), go to the tab for remapping and see.
Eonon ? Lol, they know F all about the units that they resell, good luck with that !
Cant see what the turn signal sounds have to do with your unit.
typos1 said:
AFAIK its only SWC, but there is a way to remap SWC anyway, so even if it applies to panel buttons it can be overcome.
You are deffo not SOL if something goes wrong, cos there are copies of WWW MCU in other threads, any WWW MCU will work "100%" and you can also use KLD MCUs. As I keep saying. Plus theres a wealth of info and help from us on here, so SOL you deffo arent.
Try remapping the panel buttons now - go into factory settings (password 126 or m123456), go to the tab for remapping and see.
Eonon ? Lol, they know F all about the units that they resell, good luck with that !
Cant see what the turn signal sounds have to do with your unit.
Click to expand...
Click to collapse
The turn signal and warning chime sounds in my car are generated from the head-unit. With the stock radio, the CANBUS interface in internal and those sounds come out of the cars speakers (and sound very good). But with these MTCE head-units, they give you an exteral CANBUS module, which allows the steering-wheels keys to work (and from what I've read can't be changed on these GM-specific units?) and they also actually generate the turn-signal and warning-chime sounds, which they play through a little "stick on" speaker (instead of through the car speakers). However, the sounds that the CANBUS module generates are absolutely horrible (it's almost laughable how bad they are) - and I've read that it's not the external speaker that is the problem - it's the CANBUS module itself that is generating the horrible sounds - so there is no way to fix it that I'm aware of - unless I can get a different, higher-quality CANBUS module that works with these units.
For what it's worth, I have a GM-specific unit (the Eonon model # is GA9180A if you wanted to actually see it and what it comes with). Like I said, I've also read on these forums that the steering-wheel keys are preset and cannot be changed - unless there is some hack to do it (the normal method to map the steering wheel keys apparently doesn't work on these units). But again, I'm still crawling and searching through all of these threads, so I'm just going by what I've read - not from actual experience. Maybe I missed it, but I've yet to find a stock WWW MCU file the same or newer than mine (2.85). The problem with going with an older version is that you know that there were isuses that were fixed, so it seems silly to go backwards (or risk having to go backwards). This may seem silly to you, but to me, being that I'm still a "noob" with these radios, I just don't feel comfortable moving ahead with major "mods" until I know I can get back to where I started. Besides, I still have plenty to read and learn and don't even have the unit installed in-car yet (still testing "on the bench" other than a quick in-car test yersterday), so I'm not in a huge hurry.
jtrosky said:
The turn signal and warning chime sounds in my car are generated from the head-unit. With the stock radio, the CANBUS interface in internal and those sounds come out of the cars speakers (and sound very good). But with these MTCE head-units, they give you an exteral CANBUS module, which allows the steering-wheels keys to work (and from what I've read can't be changed on these GM-specific units?) and they also actually generate the turn-signal and warning-chime sounds, which they play through a little "stick on" speaker (instead of through the car speakers). However, the sounds that the CANBUS module generates are absolutely horrible (it's almost laughable how bad they are) - and I've read that it's not the external speaker that is the problem - it's the CANBUS module itself that is generating the horrible sounds - so there is no way to fix it that I'm aware of - unless I can get a different, higher-quality CANBUS module that works with these units.
Click to expand...
Click to collapse
Right, a friend of mine recently installed a unit in his (GM) Opel Astra, it came with a speaker and we wondered what it was, although he hasnt said that any sounds are different after installing it. In factory settings you can see a list of CAN Bus box manufacturers, one from another manufacturer may sound different. Any OEM MTCD/E or indeed any retro fit head unit will come with a CAN Bus box because modern cars use CAN Bus. Few have the external speaker thing though as usually the car generates the noise. As I keep saying the SWC CAN BE CHANGED !!
jtrosky said:
For what it's worth, I have a GM-specific unit (the Eonon model # is GA9180A if you wanted to actually see it and what it comes with). Like I said, I've also read on these forums that the steering-wheel keys are preset and cannot be changed - unless there is some hack to do it (the normal method to map the steering wheel keys apparently doesn't work on these units). But again, I'm still crawling and searching through all of these threads, so I'm just going by what I've read - not from actual experience. Maybe I missed it, but I've yet to find a stock WWW MCU file the same or newer than mine (2.85). The problem with going with an older version is that you know that there were isuses that were fixed, so it seems silly to go backwards (or risk having to go backwards). This may seem silly to you, but to me, being that I'm still a "noob" with these radios, I just don't feel comfortable moving ahead with major "mods" until I know I can get back to where I started. Besides, I still have plenty to read and learn and don't even have the unit installed in-car yet (still testing "on the bench" other than a quick in-car test yersterday), so I'm not in a huge hurry.
Click to expand...
Click to collapse
You dont have an Eonon unit, there are no Eonon units, Eonon are a seller not a manufacturer, they buy from the manufacturer and sell as their own, "GA9180A" is a number made up by Eonon. Your unit is a Klyde unit, its made by Shenzhen Klyde, as we ve discussed WWW MCUs are the same as Klyde (KLD) MCUs. For the 4th time - the SWC CAN BE CHANGED !! I ve also told you how to remap the panel buttons, so can try it and then use a KLD MCU, but you dont seem to have tried it. I know youre a noob, I have 5 years experience with these units and I ve given you my advice, its up to you whether you take it.