i am having trouble finding a thread on how to root and rom flash the "infotmic sawee10" if someone could help me out with a link or smething it would be much appreciated!!!!
gearhead3585 said:
i am having trouble finding a thread on how to root and rom flash the "infotmic sawee10" if someone could help me out with a link or smething it would be much appreciated!!!!
Click to expand...
Click to collapse
flytouch 2 or 3? w/ android 2.2 right?
Solidus_n313 said:
flytouch 2 or 3? w/ android 2.2 right?
Click to expand...
Click to collapse
shizznit! its for a friend.... its on 2.2 i kno that....
what other specs are needed?
she said its an "infotmic sawee10"..... from websurfing i found out its a clone of flytouch but that about it..... ppl @slatedroid are no help, all they do is delete my post...
i dont own one personally, but ive used a friends once or twice, and he asked me the same thing its relly difficult to pinpoint the model, but these are usually the differneces:
1. what color is the power light / Charge
2. does it vibrate on start up
3. any model info
4. WMT version, Can be found in setting about(if its a WonderMedia Technologies)
5. Download and use Android system info look at the memory (There are some vendors that fake the mem.)
6. look at the build.prop for any vendor info
EDIT** these instructions should help you root:
http://thebelv.altervista.org/Flytouch3/rooting/rooting_flytouch3.html
cool brah! thnx! ill get the spec asap! really appreciate the help!! ppl @ slatedroid were making me RAGE!! lolz
also, do you know the specs for screen resolution (1024x600 or 1024x576) and charger (9v or 5v)?
ok regardless of HW info, im 99% certain you have a KIRF, so your options are limited (read* non-existant ) for ROMS...
root wont be a problem, there are several methods. but the big issue is flashing roms over USB+mem stick(only gaurenteed method) has been known to cause more bricks than quality results with the SAWEE10/MERCURY...
i recommend ROOT + Titanium Backup (clear bloat) + System Panel/task killer (eliminate unnecessary processes) + New Launcher (your choice [or hers, whichever], its ALWAYS user preference ;P) to optimize the tablet.
ill PM you a bunch of links to help with these efforts and shed some light on this mess of a shadow tablet
Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.
IAmTheOneTheyCallNeo said:
Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.
Click to expand...
Click to collapse
wow, i miss people like you here on XDA
Solidus_n313 said:
wow, i miss people like you here on XDA
Click to expand...
Click to collapse
Thanks Yeah this place has become a demanding :handouts now: type of place lately with people who will chastise you should you accidentally ask a question that was previously answered in some hidden grave deep within the thread lol. However there are still a lot of good people here. I support the Droid Incredible on xda along with all my mods and tweaks that are across platform, and then my tablet on slatedroid. I don't know what was happening to this new user's posts but it really set him off. I'm glad you were able to provide him some info. If you feel like exploring a new community bent on being "chastise free", look up AndroidPassions.com. ****Mods and Admins my post is in no way intended to pull members away from this site but rather offer another avenue for additional support of their device: ) ****
Sent from my ADR6300 using Tapatalk
hahaha nice cover
ive been with xda for a LONG time, and delt with A LOT of trolls and useless blockheads who would rather you fix the problem than learn to fix it themselves with the help of others, hence the current state of XDA...people with more money than brains who think they deserve your hands on help becuase they figured out how to register to the forum
so i dont think ill ever actually leave permanantly, but ill say this, this isnt my first account :/
IAmTheOneTheyCallNeo said:
Hey Gearhead I don't know what was happening with your post on my thread at SlateDroid. My last post to you however asked for specs on your tablet to make certain the firmware I have available in my roms section would work for her tablet. As Solidus mentioned, you really do run the risk of bricking because of the type of tablet you have. However, if you still intend to take the risk and flash, the usb flashing method is preferred over the IUW burning method as IUW is virtually almost irreversible unless you truly know what you're doing. On post 2 of my slate thread I go into great detail on root and bloat removal for improving your current system's performance. All the info you need is provided there in addition to what Solidus may have already provided to you. I know you have a bad taste in your mouth for that community now because you thought someone was deleting your post. However, I came up with that thread because I too could not find any info on my shadow of a tablet. If you look all over the internet you practically can't find device specific info for it.
Whether it's here on XDA, androidpassions, or SlateDroid, feel free to pm me and I will help you with what I can. Don't forget though that the people on that thread including myself have her tablet so all the problems she will face ahead will most likely been faced and overcome by them.
Thanks for providing a link to this XDA thread. Doing so may have further allowed me to assist you since you may not return to Slate.
Click to expand...
Click to collapse
thanks neo!!! idk what happened over there... all i kno is that my post werent showing.... n i was getting heated.lol.
ill be keeping THIS thread up-to-date with all steps n issues if any!! appreciate the help!
Solidus_n313 said:
i dont own one personally, but ive used a friends once or twice, and he asked me the same thing its relly difficult to pinpoint the model, but these are usually the differneces:
1. what color is the power light / Charge
2. does it vibrate on start up
3. any model info
4. WMT version, Can be found in setting about(if its a WonderMedia Technologies)
5. Download and use Android system info look at the memory (There are some vendors that fake the mem.)
6. look at the build.prop for any vendor info
EDIT** these instructions should help you root:
http://thebelv.altervista.org/Flytouch3/rooting/rooting_flytouch3.html
Click to expand...
Click to collapse
look at build.prop for vendor? where do i find this? about tablet?
spec info:
infotmic sawee10
power / charge light - red
vibrates on start-up - yes
loading screen number - 0.6.1.2(672)
settings->about device:
model number- sawee10
android version - 2.2 v2.1:#3925
baseband version - unknown
kernel version - 2.6.32.9 [email protected] #82
build number - frf858
got the link to "rooting flytouch3" thanks!!
android system info installed from market.
let me kno what else is needed!! thanks!
gearhead3585 said:
spec info:
infotmic sawee10
power / charge light - red
vibrates on start-up - yes
loading screen number - 0.6.1.2(672)
settings->about device:
model number- sawee10
android version - 2.2 v2.1:#3925
baseband version - unknown
kernel version - 2.6.32.9 [email protected] #82
build number - frf858
got the link to "rooting flytouch3" thanks!!
android system info installed from market.
let me kno what else is needed!! thanks!
Click to expand...
Click to collapse
Yours vibtates? Hrrmmmmm.... that's interesting.. Hey my rooting method on slate is probably the simplest. I also included z4root as a direct download. Should be in post #2. Rooting with z4method can't screw it up
Sent from my ADR6300 using Tapatalk
Ok sounds great! And what about the rom flash to 2.3?? That's all good too then also??
Sent from my HTC Glacier using XDA App
gearhead3585 said:
Ok sounds great! And what about the rom flash to 2.3?? That's all good too then also??
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
It's not a real 2.3.. it's a 2.2 mutant lol it lies. I discourage your flashing of the roms mainly because yours came sawee and not tab10. Although the rom most likely will work, you run the risk or losing wifi.. even mine having been tab 10 even providing the correct drivers/firmware was unable to get the internal wifi functional again. So I purchased a $13 nano USB dongle and it works fantastic. Should you decide to take the risk, I would try the official ibex build on my page or the sawee build.
Sent from my ADR6300 using Tapatalk
ok cool. ill just do a theme upgrade with adw or something then, really appreciate the help guyz!!
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.
Hi ! im looking forward to change my rom and i wanted to know if specificly the xt2051-1 had one (cuz thats the one i have) i cant find any anywhere for it and i dont want to go for another versions rom cause i dont want my phone to f up i got my phone rooted and installed twrp on it ,my manager is magisk i am confortable with command lines even tho im learning + is there any programs i should use on my pc in case my phone decides to fudge?
thanks for the help
thanks for helping newbies like me
Considering you just got yours,we can assume that it has the new touch screen,so afaik the only rom that will work with touch is this one
https://build.lolinet.com/file/lineage/ginna/lineage-18.1-20210612-HOMEMADE-ginna.zip
This is electimons modded here on xda,and as far as i know nobody else has updated for the new touchscreen
timjames474 said:
This is electimons modded here on xda,and as far as i know nobody else has updated for the new touchscreen
Click to expand...
Click to collapse
A dev uploaded an unofficial 17.1 to AFH(1) w/ the new display driver a couple weeks back. It works great, except no audio besides during phone calls or when using headphones(or BT?, IDK).
I recently stumbled upon AlaskaLinuxUsers tutorial+videos(2) on how to setup & compile custom ROMs. Am in the process of setting up an Ubuntu workstation with 4th gen i5, 8GB DDR3, 2TB SSD & slow internet. It will take some time, apparently. My goal is to get this 17.1 working w/ new display &/or the working 18.1 w/ new display sans gapps. IDK if I will achieve a bootable ROM, but it looks like it's my only path, as outside of Electimon(3), not a lot of development is going on w/ Ginna anymore. Will post progress/results, if any is gained.
1
lineage-17.1-20210608-UNOFFICIAL-ginna.zip | ROM by elisam98 for Moto e 2020
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
2
[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]
Hey everyone! There is also a telegram channel where you can drop in for some help: https://t.me/joinchat/HR_8JgyDBdw_DvmndPl0kg I really hope that you have enjoyed the series, and that it was helpful to you in your Android career! Praise...
forum.xda-developers.com
3
Nothing but respect & gratitude for E's work. Am a long-time fan. However, his build contains Gapps & I don't want them.
Understandable if you get one going let me know because I'm currently on stock due to camera issues and I would love a ROM sans g apps especially if you would put sig spoof in for micro g
Just before i do something i just want to know if AOSP has a rom for that phone already cause its my fav rom of all time but if i have to port it myself is there any guidelines i could find on how to port/create custom roms ?
Imaunicorn666 said:
Just before i do something i just want to know if AOSP has a rom for that phone already cause its my fav rom of all time but if i have to port it myself is there any guidelines i could find on how to port/create custom roms ?
Click to expand...
Click to collapse
Two posts before yours, link #2.
I have been delayed... unidentified bug bite put me out of service for a bit. Wild f'n ride. Got Ubu w/s setup, will start provisioning/downloading tonight.
After ~14 hours downloading(multiple nights @ < 1MB/s... aggregating > 50 GB) on my wireless plan, I am yet to achieve a 100% sync of the LOS repo. After hitting the MU Throttle Threshold on last month's plan, I must concede defeat at this point as I cannot afford to jeopardize my only home inet option available for another 30 days(extreme rural living, no landlines or line-of-sight options). Sigh.
my schedule is full of other things but i will take a look at the links posted and attempt to to builds as it. LOS sans GAPPS sounds like a dream. currently I use 18.1 modded and manually degoogle it. its not so fun everytime i reset :/
Any update on a XT2051-1 with the new screen and no GAPPs
roycrt said:
Any update on a XT2051-1 with the new screen and no GAPPs
Click to expand...
Click to collapse
FWIW, I should have an internet connection capable of down/uploading in the next 2 weeks, at which time I will begin failing to compile until I succeed. Hopefully, on all points.
It seems like rolling the old 17.1 w/ the new display driver would be pretty straightforward, but a lot of ignorance is wrapped in that statement.
googleverifysux said:
FWIW, I should have an internet connection capable of down/uploading in the next 2 weeks, at which time I will begin failing to compile until I succeed. Hopefully, on all points.
It seems like rolling the old 17.1 w/ the new display driver would be pretty straightforward, but a lot of ignorance is wrapped in that statement.
Click to expand...
Click to collapse
Thank You googleverifysux! Just got the phone and would really like to degoogle it, then not worry for awhile