yashsingh1/xdaforums huggingface dataset:
[MTCD Software Development] da_anton:
The version commited today should make that possible. Just create a folder in addons which includes the APK. Like e.g. Viper4Android.
[MTCD Software Development] solmer:
Great! I'm gonna flash it tomorrow, I'll post results asap ;)

Thanks for your work

---------- Post added at 09:34 PM ---------- Previous post was at 09:27 PM ----------

Thanks !!!!!

---------- Post added at 10:25 PM ---------- Previous post was at 09:34 PM ----------

Hi da_anton I've been testing your latest version and something doesn't works for me.....here's a copy of what I get in my terminal.....

[MENTION=1694567]rainbox[/MENTION] ~/GIT/MTCD_ROM-cooking-master $ sudo ./mod_rom.sh

creating working copy of ROM image

extracting image

mounting system.img

mounting failed! exiting...

cleaning up...

remove working files

In the other version everything was fine....I've tried to spot the problem (looking inside the scripts) but I cant' guess where is the problem.....

Any idea?

Thanks in advance.
[MTCD Software Development] da_anton:
You can go to the appropriate module

modules/backup_extract_mount.sh

And remove the log stuff at the end of the lines

>> $LOGFILE 2>&1

Mount should then throw the error right to the console. I haven't implemented the log stuff yet. Let me know the error or just do a push request ;)
[MTCD Software Development] da_anton:
Definitely true. Fuse is actually Filesystem in user space and means you can mount your Google drive or some exotic stuff by loading a module outside of the kernel for that purpose. The ROMs we currently have don't have FUSE support built into the kernel. What Malaysk actually means is a change to the partition scheme to generate one big partition while flashing everything as far as I understand it.
[MTCD Software Development] RWerksman:
That seems like a much simpler way to go about it. What exactly is the downside beyond having to wipe after flashing to ensure that the partitioning sets up correctly? (I'd imagine that could be addressed in a script)
[MTCD Software Development] m00n61:
It would be nice to also have FUSE support. To my best knowledge it's Booroondook who created the first FUSE Rom (http://4pda.ru/forum/index.php?showtopic=704299&st=0#entry43482386 ) I know he is also a member of XDA-Developers, maybe a PM here or on 4pda will raise his interest for this ROM builder?
[MTCD Software Development] da_anton:
I uploaded a new version today.

Changelog:

rooting by adding SuperSU is working now

repartitioning into one big 16GB partition is included and should work (you may call it FUSE ;) ) see screenshot, many thanks to malaysk!!!

module to remove oem apps which are installed after first boot (e.g. Acrobat Reader)

Would be great if someone could test the new functions too! :cowboy:
[MTCD Software Development] kc2koj@hotmail.com:
is it possible for you to mod a firmware update zip i have to have root for a 2gb ram intel head unit...

link to update .zip

https://drive.google.com/file/d/0Bz8umNL1qrsoTDcwX1ViMG1BbFU/view?usp=sharing

link to new update seller sent me jar file

https://drive.google.com/drive/folders/0Bz8umNL1qrsoTTVIbm0zVWk4QXM?usp=sharing

thanks in advance
[MTCD Software Development] da_anton:
Not from my side. Did you try the KingORoot app?
[MTCD Software Development] kc2koj@hotmail.com:
it was tried no success
[MTCD Software Development] kc2koj@hotmail.com:
would your tool work with the update.zip i have for intel 2gb ram head unit
[MTCD Software Development] da_anton:
I know ;) The answer is: no. The schema of the files is totally different. The update for a usual MTCD files is built on a tool called imgRePackerRK which extracts the ROMs different parts. As that tool is Rockchip-only it will definitly not work with files for your intel unit. Sorry, but as long as no one does a real deep dive into your ROMs specifics and finds a way to root it you have to life with it.
[MTCD Software Development] kc2koj@hotmail.com:
i did the research on this cpu and it was made be rockchip and intel as a joint venture

the cpu is made by rockchip

http://www.rock-chips.com/a/en/products/SOFIA_Series/2015/1125/734.html

same cpu on intel site

https://software.intel.com/en-us/bl...atom-x3-code-named-sofia-soc-processor-series

on the intel link a little ways down the page it says

The Intel® Atom™ x3-C3230RK processor, a collaboration between Intel and Rockchip*, includes a quad-core 64-bit Intel® Atom™ CPU and an integrated 3G modem. Figure 3 describes this SKU’s high level architecture.

http://www.intel.com/content/dam/www/public/us/en/documents/product-briefs/atom-x3-c3000-brief.pdf

with this info do you still think it the tools wouldn't work
[MTCD Software Development] da_anton:
No
[MTCD Software Development] kc2koj@hotmail.com:
thank you for your info
[MTCD Software Development] markze:
Great work

Great work guys, I wish I had the time and skills to tackle this myself as I can see a lot of potential for my buggy head unit. For now I will wait and see what Witson come up with next.
[MTCD Software Development] leonkernan:
Is there any chance of an option to enable the developer menu in settings like Malaysk's rom?
[MTCD Software Development] da_anton:
I haven't tried yet, but does the usual method not work? http://www.greenbot.com/article/245...-options-on-your-android-phone-or-tablet.html
[MTCD Software Development] solmer:
Hi da_anton,

I've deleted the >> in the modules to avoid the previous error and now seems to work but when I try to compile the image I get the next errors:

rooting ROM ...

mkdir: cannot create directory ‘/home/israel/GIT/MTCD_ROM-cooking-master/mount_path/app/Superuser’: File exists

mkdir: cannot create directory ‘/home/israel/GIT/MTCD_ROM-cooking-master/mount_path/bin/.ext’: File exists

ln: failed to create symbolic link ‘/home/israel/GIT/MTCD_ROM-cooking-master/mount_path/bin/install-recovery.sh’: File exists

mkdir: cannot create directory ‘/home/israel/GIT/MTCD_ROM-cooking-master/mount_path/etc/init.d’: File exists

mounting oem.img

ls: cannot access *: No such file or directory

Error: Expected at least 7 tokens for --checklist, have 4.

Use --help to list options.

I've noticed that I must to create a new forlder (called mount_path) otherwise the script cannot mount the image....

Any idea?

Thanks in advance for your help and support.
[MTCD Software Development] leonkernan:
Nope, I think they removed that when they changed it into the screen with the QR code.

I just tested tapping every field there and nothing happens
[MTCD Software Development] SirOrigami:
One solution is the Developer options app
[MTCD Software Development] leonkernan:
I never thought to look for an app to open it. Thanks, i'll try that.
[MTCD Software Development] da_anton:
Looks like an inconsistent state. Try this:

- umount /home/israel/GIT/MTCD_ROM-cooking-master/mount_path/

- remove everything under MTCD_ROM-cooking-master

- repull the git repo

Please don't not cancel the process in between and finish it till the end. This is still a very early version and so far the cancel procedures haven't been tested very intense.
[MTCD Software Development] da_anton:
To integrate or not to integrate?!

I'm a little undecided. In my local branch I have some tuning integrated for the CPU interactive governor. It scales up to 1,6 Ghz more aggressively. Otherwise it mostly stays at max 1,2 Ghz. As I integrated that pretty early in the boot process it boots around 5 seconds quicker now. BUT: I'm not sure if that "overclocking" does not damage any of our headunits. What do you think? Shall I integrate that or do you think risks to high?

Here you can see the current result: https://goo.gl/photos/xvQGKhgnaDwvBv6MA
[MTCD Software Development] da_anton:
Commited a new version today. This version should fix some bugs which occurred with the memory unify mechanism (aka FUSE). Also the missing "mount_path" folder should now be present after a "git clone" run. As my time is very limited the next couple of weeks and I'm on holiday later in October/November as well this will probably be the last version till December. So don't expect many commits or posts in the near future ;) Happy building!

If anyone else wants to work on the tool I'm more than happy to add his pull requests to the repo!

Changelog:

fixed memory unify (aka FUSE)

added missing mount_path folder

included performance optimizations (I/O governor, CPU is disabled)

Added Quickboot.apk to repo

improved logging: now most stuff is written to a file namend "logfile"

disabled the download mechanism as I don't have a proper hosting solution
[MTCD Software Development] solmer:
Hi da_anton !

Sorry to bother you again :( but I want to collaborate in the project (I'm working with some scripts) and the only way is to learn how to "cook" the image first....

1.- I've umounted the mount_path, cleared all under MTCD_ROM-Cooking (I've changed the foled so now I'm working with this folder to be as closed as possible to you)

2.-I've clone again the repo using:

sudo git clone https://github.com/da-anton/MTCD_ROM-cooking

3.-I've fetch all to be sure everything is ok (That's the way I use to repull it...Is there another way to repull?)

Now when I try to cook the image I get:

mounting oem.img

ls: can't access to *: no such file or directory

I'm totally lost :crying::crying::crying:

Thanks one more time....I'm sad to say this but as Terminator says... "I'll be back" ;)
[MTCD Software Development] da_anton:
Ok, I do my very best to fix your problem. :)

- What Linux do you use? Ubuntu?

- What ROM do you use as source? The latest Joying or another one?

- You work with your normal user and not "root" I guess?

- Please pull the newest version from this evening. After the script finishes there is a file called "logfile" in the root directory. Please post that one on pastebin.com and add the link here

- when the script fails please execute the following command in the root dir: "ls -R ./ > directory-listing.txt" and paste that file on pastebin.com as well
[MTCD Software Development] solmer:
Thanks in advance :)
[MTCD Software Development] SirOrigami:
If iam not misstaken you should not use his Beta ROMs because they are already modified, you should use Standard from example JY 1.90.
[MTCD Software Development] solmer:
:crying::crying::crying::crying: I can't belive it ! I think youre right :highfive: I'm gonna try right now....

Thanks !!!
[MTCD Software Development] da_anton:
Thats true :) You can fetch the latest JY ROM which I use for my ROM here: https://drive.google.com/open?id=0BzxkkrRwpR3Ea0oxTHRXb0Uwb0U

Is is only the dupdate.img file.
[MTCD Software Development] solmer:
:good::good::good: Thanks ;) I'm gonna try it now...I'll post results asap....

---------- Post added at 08:54 PM ---------- Previous post was at 08:46 PM ----------

Hi Guys !!!! Mission Accomplished :highfive::laugh::laugh::laugh:

The problem was on the ROM :silly: after downloading the latest JY (thanks da_anton and SirOrigami) I can compile it.....now it's time for work....

Thanks a lot for your tiem and support !!! Let's make a fast and stable ROM ...
[MTCD Software Development] da_anton:
Great to hear that!!! :good: Happy coding and building! Let me know if you have a pull request :D
[MTCD Software Development] solmer:
:):):) Sure ! I'll try to collaborate as much as possible :good:
[MTCD Software Development] solmer:
I've flashed today my first custom ROM and something went wrong....I got a logo-loop-reset-logo........ The problem was I changed a lot of things in mount_path folder while compiling..... Now with my second ROM everything works as it should, booting time is really short and i love it ...I'm happy :)

I've a question..... Could be possible to add apks to the OEM before compiling? I like the addons feature but having some apk in the OEM is a good idea, in case of need 'em you can install them frome the OEM.... I know that I can mount the oem.img and include my own apks inside but I'm afraid of making a bad ROM if a mess with it...

Thanks :)

---------- Post added at 04:34 PM ---------- Previous post was at 04:24 PM ----------

ooops one more thing.....I'm working on a list with the description of the apks that are safe to remove, I've noticed some that some members are afraid to cook their own ROMS due they don't know if removing an apk could be bad for the ROM. Perhaps that list could be inserted in the remove menu....
[MTCD Software Development] da_anton:
Great to hear that the tool worked for you and that the ROM feels fast! :)

The idea of adding a list of apps you can remove safely is indeed a great one! If you post the list I'll put it in the second post as I reserved it for things like that.

Regarding your idea with adding own APKs to the OEM image: I'm not sure but as far as I know OEM apps are only installed once after the first boot. Right?
[MTCD Software Development] solmer:
Hi !, thanks :)

I need to find some free time and I'll send to you a list with the description of the apks that are safe to remove. Let's make a great ROM ;)
[MTCD Software Development] Pattond:
I may be too limited in skills for this, but a couple of questions anyhow. I have about 3000 songs on my SD card, and the existing music program isn't very strong with a large library. When I use another music app, it doesn't take control of the sound (i.e. Have have to stop the radio first or both play). If I remove the stock player and replace with something (say vcl) will it act as the default. Also, can I make any app my launcher? I like DashLinQ, and own a full copy, but it's not a launcher (though it should be)
[MTCD Software Development] da_anton:
I can't tell you anything regarding your questions about setting other launchers. So far I have just used one.

I don't think you can just remove the default player and add something new. I have Spotify on my unit and I always have the problem that the radio app is playing simultaneously with Spotify. Everything seems to be pretty hard wired. There is an app here on XDA called MtcdTools developed by [MENTION=7621504]f1x[/MENTION] which is supposed to deal with that kind of problems. Unfortunately there hasn't been an update for a longer time and currently switching apps is not working reliable with that app.
[MTCD Software Development] SirOrigami:
You can replace stock Music app etc in system app folder.
[MTCD Software Development] avionaru:
I've tried the tool last night (even made screenshots and started a step-by-step guide). Although the process seems to be working without errors (both on Linux and the HU), none of my 5 variants booted. All of them got stuck at the Logo (ocassionally rebooting after 5-6 minutes).

Work method:

1. cloned the repository, installed dependencies, setup the APK folders and so on. No errors.

2. Used the latest official manufacturer ROM as a base.

3. started the script with sudo.

4. I have made 4 variants with various things removed, in order to experiment:

- V1: removed only parts I was familiar with/recognized from normal Android components (wallpapers, calendar etc) + FUSE + NO personal APKs + English + Date format change + NO Viper + NO Adblock + the performance/dalvik modes.

- V2: got more aggressive and additionally to V1 I removed some manufacturer APKs, based on their names (Photos, Ipod stuff, all wallpaper related stuff except for a viewer + FUSE + some personal APKs (folders with the same name as the APK and all, youtube/soundcloud/waze etc). + English + Date format change + Adblock + performance modes.

- V3: back to V1 in terms of APK removal + FUSE + personal APKs + English + Date format change + all defaults addons (viper, adblock etc) + performance mods

- V4: experimental, I removed a lot of stuff + [V3]

- V5: just loaded the ROM, did not do anything (Clicked cancel on all screens). I think the only th ing I enabled was FUSE, but can't remember for sure. Then rebuilded the ROM . Basically I tried to test just the unpack/repack of the same features, to see if issues arise from this part.

None of the versions worked, I installed each twice, factory reset in recovery 1-4 times and so on. The recovery installation process goes fine and does not throw errors. After these, I tried Malaysk 7.3 and it worked as expected.

Attached is my log and some screenshots from the process (I noticed someone asking around here).

http://i.imgur.com/GTnK2c8.png

http://i.imgur.com/ZrJNX4r.png

http://i.imgur.com/48sf53W.png

http://i.imgur.com/PeRZ5xC.png

I also checked the scripts, I understand what they do and how the process works, but I am not skilled enough to debug.

Edit: My unit is a HotAudio MTCD, latest manufacturer MCU (1.81), 10" touchscreen only. Base ROM used was the latest manufacturer one (31 Aug).
[MTCD Software Development] solmer:
Hi !, reading your post I see that you know what are you doing, everything seems to be right, you understand the scripts, the plataform (linux)....I've cooked 4 images and they didn't work for me neither......The solutions was not include any personal app (I installed them afeter booting using the regular way) and deleting & re-cloning afer new compilation...sometimes there are some files / folders that mess with the new cooking process....Thats all the help I can't give to you, I've a JY UL135 (Joying) and it's working like a charm with my latest cooked ROM....

Good Luck :)

Oooops I forgot to tell you that I think that the FUSE was the main cause of no booting in my unit.... try to avoid it and check....
[MTCD Software Development] da_anton:
Indeed a very deep inspection! :good: I have some questions:

Did you maybe also disable the boot animations in build.prop?

Did you always root the ROM?

Did you always include performance optimisations?

I also had random reboots. What I found out so far during the last couple of hours of testing is that debug.sf.nobootanimation=1 definitely breaks the unit. I'd never thought that it has such a huge effect. Not only my unit reboots but also all my buttons stopped working. Could not even turn up the volume :eek:

I then started from a plain ROM created with the tool and stepped up to a fully functional one with almost all the bells and whistles included in the different modules. So far everything seems stable on my unit. My guess is that either the updated busybox binary or SuperSU makes some trouble. As the SuperSU binary has been compiled by the app on the unit itself I tend more to busybox. Thats why I disabled the code in the repo. Would be great if someone else could also try to verify the current state.

A comment on FUSE/memory unify:

There is no complete documentation available how to integrate this functionality into a ROM. At least I could not find one. Thats why I asked malaysk for permission to copy it over from his ROM. But still there is no step-by-step guide what to do exactly. Thats why I did diff the different folders and images and tried to find the relevant parts. But there is of course a chance that I missed something and that now is the cause for some instability. I personally had no reboots which I could track down to this special feature.

A comment on releases:

I think it is a good idea to create a branch for new functions and create releases when they seem to be stable. So it would be great if everyone who

doesn't have problems

with any ROM created by the tool could just report that. :D Makes it easier
[MTCD Software Development] avionaru:
My answers below, in blue

PS: I will also try to skip any APK add, as I was advised above.
[MTCD Software Development] solmer:
Hi, today I've cooked a new ROM. I've choosed not to use "FUSE" , root the ROM, no extra APKs and removed these apps to make the ROM "slim" :) :

Removing BasicDreams

Removing Browser

Removing Calculator

Removing Calendar

Removing Exchange2

Removing Galaxy4

Removing Gmail2

Removing GoogleCalendarSyncAdapter

Removing GooglePinyinIME

Removing HoloSpiralWallpaper

Removing LiveWallpapers

Removing LiveWallpapersPicker

Removing MTCCarCD

Removing MTCCivicUSBIPOD

Removing MTCDVD4

Removing MTCIpod4

Removing MTCTV

Removing NoiseField

Removing OpenWnn

Removing PhaseBeam

Removing PrintSpooler

Removing VisualizationWallpapers

Removing OEM Adobe_Reader_PDF.apk

Removing OEM Instruction2.apk

In my unit (JY UL135 Joying) the booting time is about 15"-16", really fast !!! Need to test it for a couple of days for bugs.
[MTCD Software Development] avionaru:
I gave it a shot again, using only the first "Remove Apps" screen (I removed approx. the same stuff mentioned in the list above) and enabled the FUSE option on a manufacturer ROM as a base. It worked fine, now I have a functional ROM with a big partition and a boot time of 20 sec. I had to manually root and install my apps.

So I can say for sure that removing default ROM apps and FUSE support work fine.

I'll try and make a backup this week if I have time and try adding other options in the tool, one by one (but it will take a while). I'll hold off the documentation in GIT until we get a clear idea of what works and what not.
[MTCD Software Development] Pattond:
How is the ROM working out now that you are a couple of weeks in?
[MTCD Software Development] nexxusty:
Really curious to see if this would work on an MTCD Intel unit.
[MTCD Software Development] solmer:
Hi !, I must admit that works pretty well, no reboots, stable, fluid.... I think is the ROM that suits my needs. Give it a try

---------- Post added at 09:39 AM ---------- Previous post was at 09:34 AM ----------

My bet....don't try it with a Intel unit....may result a bricked one.....
[MTCD Software Development] doitright:
Probably would be a good idea to specifically mention that this is EXCLUSIVELY for RK3xxx **ARM** devices. The newer Intel devices have a completely different image format, so the rk image repacker will NOT work on them.

---------- Post added at 04:08 PM ---------- Previous post was at 04:05 PM ----------

This project is basically a frontend to imgrepackerrk, which can ONLY manipulate the images for the ARM rockchip update packages. From what I've seen, the intel units use a *standard* update image format, so you would use more conventional tools to manipulate those.
[MTCD Software Development] zoxenrbg:
good job thanks
[MTCD Software Development] OldRon:
Hi :)

I have an Erisin ES4028A Unit for an Seat Exeo (which is basically the old Audi A4).

So far the unit worked fine...

I updated the MCU to the version: KGL V1.87_2 --> worked fine :)

I also installed this rom and even that it is a JY rom it works fine... except for one thing: Waze keeps crashing :(

Any ideas why this is happening, or which info I should provide, so you guys can take a deeper look into this issue?

I also tried Malaysk (which runs fine, even with Waze) but I'm not a big fan of all those fancy xposed things... ;)

Thanks for some advice with my issue :)
[MTCD Software Development] gunmoule:
Same here, MTCD KD V1.82_1, I cooked my ROM based on latest JY Rom. First I removed some APKs and added some of my own (Waze, Youtube), enabled FUSE, root, build prop optimizations. Double factory reset and installed Rom => Bootloop

As suggested I just did not include any addon APKs, installed ROM and it boots fine, but I have the same issue, Waze launches and immediately crashes, or on first launch will let me choose my country as it apparently can't locate me (google maps does), it would Initialize and then download language and crash.

I guess the problem lies in the build.prop added lines but I could find anything that could be related
[MTCD Software Development] emarcin:
Perfect!
[MTCD Software Development] OldRon:
What I would like to know is, if Waze also crashes at the test-system from da_anton.

If so, it would be much easier to geht a crash-report...

If anybody could tell me where Android safes such reports, I could post them here...
[MTCD Software Development] solmer:
Hi ! I've tested the tool compiling a ROM with a different base ROM (My unit is a JY-UL135 and I've used a KL base ROM) and I can confirm that the cooked ROM doesn't works, just to clarify, I only can use JY base ROMs for my unit.