Hi!
First, i want to indroduce myself. Im a software developer form germany. I own an i9000 and i want to port gingerbread to it.
I dont know if some people here ware working in it, but if we dont collect our knowledge we will get to nowhere.
So i already worked on a android port to a windows device (meizu m8) so i think i have basic knowledge on how this should go.
So here are the steps i would go, and i already starting uop a bit:
1) We need to get a 2.6.34 kernel running on the device. With our ROM.
This includes: Here are proble which already compiled kernels. Who does this work with the drivers? Are there .config files from the i9000 kernel?
We should DL the nexus S kernel sources from android git (they are there) and give it a shot. Just compile and install a 2.6.34 kernel which should be configured as near as pssible to the i9000 kernel. If we get such a kernel to run with our phonr we are nearly there.
2) if we get such a kernel, we can just DL/compile gingerbread. Then we create an update.zip file from the generated img files. We would need to collect the config scripts from out froyo and put them into this rom too.
3) let it update and see. For me, this sounds not very hard. The hardest part is the driver part, but as there are people here, which supply compiled kernels, they
a) have the driver sources, if they are build in
or b) the drives are modules, and so we hopefully should be able to use them on a 2.6.34 kernel too.
So the first thing we would need:
Are there any people out there which know about compiling kernels etc, which compiled/hacked a kernel for galaxy already. If so, please post here about the details, drivers config etc.
c'mon guys, we can do this, this isnt that hard.
greets
I suggest you to come to NSdev at irc.freenode.net
Lot's of developers there ready to help you, including supercurio
http://www.emoiz.com/samsung-galaxy-s-to-get-android-2-3-gingerbread-in-february-2011
read this
Hum... i dont know if i can trust what samsung says... it took nearly the complete lifecycle of froyo until they brought it to the i9000...
If they need this long to to this small port, i think we will get it in summer, just with 3.0....
Lets see and hope, but i think its not that hard to bring gingerbread to the i9000.
See android runs on linux. you can boot a normal linux system, and then start android after this. i think if we get a 34 kernel to run (thats the ginger kernel) with our drivers, we can surly compile gingerbread and create a update.zip out of this.
The main problem here (like we had it with porting android on the m8) it the driver problem. U need the hardware drivers for anything to use it. But as we already have a 2.6.32 kernel and we could inspect it how this is compiled, and we have the nexus s sources (which is in fact nearly the same phone), and we have people here who manage to compile running kernel for the i9000 i sthink we can do this.
The main info i need is if those self compiled kernel use the drivers as modules or if they are compiled into the kernel.
To be precise: The baseband/modemdriver is the main problem as for such devices its very hard to get open source drivers. For all the other things, like bt network display and sound there are surly drivers avaliable.
Anyway, i will start and see how far we come and see who is faster if samsung brings a ginger in short time, its not that bad either, then we know how to port 3.0 when it comes
greets
dadyal said:
http://www.emoiz.com/samsung-galaxy-s-to-get-android-2-3-gingerbread-in-february-2011
read this
Click to expand...
Click to collapse
I'm sure it will be postponed till october.
Thanks for working on this, check in to the IRC and work with the others in there
Sent from my GT-I9000 using XDA App
^Karlo hope you will find a way to get gingerbread(vanillastyle) to work on the sgs.
Mach weiter so, werde diesen Thread auf jeden Fall im Auge behalten. Boah ich wünschte, ich könnte programmieren und würde mich besser auskennen mit der Materie. Dann wären wir schon mal zu zweit ^^
cheers mate
i'm really looking forward to this although i will get a new phone by march
ich freu mich echt auf das was mit dem sgs hier erreicht werden wird viele neue tolle ideen
und ein clean android ist der erste weg zu was ganz grossem
Sent from my GT-I9000 using XDA App
A Dream Team wish list
In my opinion this would be a perfect team to bring AOSP gingerbread port to sgs.
supercurio experienced in kernel coding - proven NS root, voodoo etc.
Aery aka Codeworkx experienced in all areas - proven dev works on CM6.1 port
Coolya Great experienced in all areas - proven dev works on CM6.1 port
KarloRanseier - unproven jet but qualified by the statement from the first post and with a good will.
With those guys working together a 2.3 would be ready in a week. I hope my wish list will come true for the holidays
oppssss
probably february-2012
nexus ( google ) + 1 year = sam
and ... but sales ...
I just DLed the kernel sources from the nexus s (these are the android git samsung sources) and the opensource package from samsung OS center. Now we need to compare them, to find out which parts ( machine init for s5pcX and mainly drivers) are different. thats a messy work but nohting really hard.
Then i think it should be possible to port most of the changes from galaxy kernel to nexus s kernel (i think there wont be that much changes...).
then compile one and give it a shot.
I will see what happens
will try it tomorrow and then i will show up in irc and hear what the others have to say.
KarloRanseier said:
I just DLed the kernel sources from the nexus s (these are the android git samsung sources) and the opensource package from samsung OS center. Now we need to compare them, to find out which parts ( machine init for s5pcX and mainly drivers) are different. thats a messy work but nohting really hard.
Then i think it should be possible to port most of the changes from galaxy kernel to nexus s kernel (i think there wont be that much changes...).
then compile one and give it a shot.
I will see what happens
will try it tomorrow and then i will show up in irc and hear what the others have to say.
Click to expand...
Click to collapse
'
dont need to port the kernel at all. focus on the rom instead. gingerbread will run fine on 2.6.32
and btw. sgs uses some properitery drivers wich we dont got sources for. so it cant even be ported,like onenand,rfs etc.
with out them /dev/block/stl* wont even exist..
sgs uses some properitery drivers wich we dont got sources for. so it cant even be ported,like onenand,rfs etc.
Click to expand...
Click to collapse
You are right with that...
BUT if no android phone in the world has rfs, i think that android dont need rfs. Thats just a bullshitish samsung development. So if we just use a stock android,
we would get rid of rfs and just use yffs like every android in the world does. there is no need for us tu use rfs (besides of some configs which surly can configed back to original)
And a onenand driver is nearly sure gettable in opensource as there are not soo many onenand ctrls but very much devices which use them.
But oki i then will start to get gignerbread sources and have a look at this.
PS: in m8 world, we did it like that: Created a root image which was mounted at startup to /data and stuff. This way we could hold this image on sd card. i think it should be possible to do the same with a gingerbread img to give it a short try and tinker with it
Related
hi guys
first off...sorry for posting the usual question...its been done to death
i have been out of the xda-dev site for a while and have lost track of things.
i always hoped himalaya linux would get done.... but from what i can see its still lacking the key components (eg phone support under gpe).
i am a uni student on placement at a company that actually writes mobile phone radio stacks...so i am learning embedded c and about the interesting side of the hardware/software interface.... now i want to actually do something about this lack of a fully usable phone.
my questions go as follows..
1> what is the current stage of himalaya linux ... i have a feeling the wiki's are probably out of date
2> is anyone actually still working on it
3> i know only a little about haret i get the idea it is also able to watch hardware (and isnt just a bootloader)...where can i find docs about using it to do this.
4> was jtag ever found on the himalaya
5> of the code in the tree what files are specific to the himalaya
i have much to learn on writing drivers etc for linux...and alot to learn about embedded c, reverse engineering etc....ok so i have a hell of a lot to learn....but i'm willing to try! (i also have 3 himalayas (1 has a bust screen) so plenty of tinkering can be done)
any other tidbits of information would also be appreciated
i think my basic goal would be the phone working.
after that get the other little bits and pieces
get the backpack cf working
get sdio and wireless working.
but these are the kind of goals that will take a long time so we'll see
i'd also love to work on the UI one day.. GPE and OPIE just dont toot my horn enough yet.
thanks
Tim
tim_programmer said:
1> what is the current stage of himalaya linux ... i have a feeling the wiki's are probably out of date
Click to expand...
Click to collapse
It is out of date, but some parts are in a good shape.
2> is anyone actually still working on it
Click to expand...
Click to collapse
Yes, because it has many common hardware and features with blueangel.
The kernel source is not being fixed, because it is decided to make blueangel
work first, and then reuse and adapt the cleaned code for himalaya.
3> i know only a little about haret i get the idea it is also able to watch hardware (and isnt just a bootloader)...where can i find docs about using it to do this.
Click to expand...
Click to collapse
There are no "real" docs, only the source code. Many pxa27x functions are
implemented in haret, that either work or need minor changes for pxa26x.
4> was jtag ever found on the himalaya
Click to expand...
Click to collapse
Yes, it's in wiki since 3 years or so
5> of the code in the tree what files are specific to the himalaya
Click to expand...
Click to collapse
Blueangel is the authoritative source.
i think my basic goal would be the phone working.
Click to expand...
Click to collapse
AFAIK, the phone works. But not with the latest 2.6.18-hh0 kernel.
This one has a lot of audio problems anyway, so it's not a major concern right now.
get the backpack cf working
Click to expand...
Click to collapse
It's a bit challenging. The backpack is implemented in so-called ASIC5,
and there are no docs for it.
get sdio and wireless working.
Click to expand...
Click to collapse
You mean SDIO wifi card ?
The SDIO host can be done relatively easy, but good luck with the wifi part
I know 2 of them, one with the TI acx100 (should be doable, because
there is linux acx100 driver), another needs the firmware upload in Motorola
SREC format, maybe even prism2.
And there is no free software SDIO for linux, you need to do some heavy RE.
Hello guys,
I have got Himalaya and I would like to help with implementation of some driver/software that is needed.
So I have got a few questions (some of them are similar to tim_programmer's, but I don't know if there are not outdated):
1. Where is the current branch with Himalaya specific code?
I have found:
- K2-6-12-hh2-xda0-ba0 (http://xanadux.cvs.sourceforge.net/xanadux/linux-2.6-xda/) and
- K2-6-21-hh20 (http://handhelds.org/cgi-bin/cvsweb.cgi/linux/kernel26/)
Is himalaya specific code that is in K2-6-12-hh2-xda0-ba0 already included in K2-6-21-hh20?
Or what differences are between these branches?
2. Is somewhere available (SD card/NFS) image with kernel+initrd+GPE that is already running on Himalaya?
I have found:
- http://wiki.xda-developers.com/index.php?pagename=HimalayaLinuxBooting
It boots, but freezes during boot (after some changes in initrd it was possible to connect to the MDA with SSH via USB bus)
- http://wiki.xda-developers.com/index.php?pagename=HimalayaStandaloneGPEWithoutSD
Link to GPE is dead.
- http://handhelds.org/moin/moin.cgi/Himalaya
There are screenshots of GPE so it should be working image somewhere.
3. Is it posssible to boot some BlueAngel "distribution" on Himalaya? (Possibly with a little changes?)
I have found:
- http://handhelds.org/moin/moin.cgi/BlueAngelHowtoInstallLinux
Could it be used on Himalaya?
4. What is the current state of Himalaya support in Linux? What is already done and what not (or partially)?
I have found:
- http://wiki.xda-developers.com/index.php?pagename=HimalayaToDo
But there is not mentioned of what branch state it is.
5. Is any other bootloader than HaRET with that is possible to boot to Linux directly from SD card without Windows booting?
I have found:
- bootldr (http://xanadux.cvs.sourceforge.net/xanadux/linux-2.6-xda/bootldr/)
What is it?
A lot of information about Himalaya development is outdated and I don't know where to start :-( So any help is welcome
Thanks
Drasar
drasar said:
A lot of information about Himalaya development is outdated and I don't know where to start :-( So any help is welcome
Click to expand...
Click to collapse
join #htc-linux at freenode.
Thanks for the link..just joined
btw when i start Haret on my Hima..the Thermometer goes up and the eyes go red..and then few lines comes up and thats it..i have tried every thing but cant get Linux to work
waiting for the New Linux Mobile
ather90 said:
btw when i start Haret on my Hima..the Thermometer goes up and the eyes go red..and then few lines comes up and thats it..i have tried every thing but cant get Linux to work
Click to expand...
Click to collapse
What kernel have you tried? What was the last message on display? Some old HaRET versions (e.g. 0.3.6) have a problem with big kernel and boot fails on mounting root fs. So try the newest HaRET 0.5.1 that goes fine.
Thankxxx alot..u are rite i have 0.3.6
here is what i have :
haret-0.5.1.exe
initrd-2.6.12.gz
modules-2.6.12.tgz
zImage-2.6.12
are these all latest
ather90 said:
haret-0.5.1.exe
initrd-2.6.12.gz
modules-2.6.12.tgz
zImage-2.6.12
Click to expand...
Click to collapse
For kernel 2.6.12, follow How To Compile 4 Himalaya instructions. It works, I have tried it yesterday ;-)
Thanks alot..thankfully i have Ubuntu so compling is no big
i will contact u for more assistance
http://www.enlightenment.org/p.php?p=about&l=en
After reading this i thought it is possible to bring this to our omap 850 devices so i just want see ur views
you can use e17 booting angstrom + illume thanks to wing linux project
but there aren't angstrom image ready to load you must compile...
As gp.triple pointed out, it should be possible to do. As Wing Linux uses Angstrom+Android so Angstrom+E17 shouldn't be a problem.
And pitillo on #wing-linux mentioned a couple of days ago that he was trying to build it for elf (aka Touch, another Omap850 device). If he succeded in making one, it should run as is on our devices.
Personally, I prefer having a Kernel that supports all Opal features before worrying about builds and packages. And sadely, I'm not having lots of success there
Anyway, check the link in my sig if you want to know more about Wing Linux.
MusikMonk said:
Personally, I prefer having a Kernel that supports all Opal features before worrying about builds and packages.
Click to expand...
Click to collapse
're right I also think that before we have a working kernel and then you can choose what you prefer
Linux is freedom
i tried android wing linux already , its cool thnx musik monk
I just got Zubuntu running on my universal!!! I'm so excited!!!!
It's kernel 2.6.32 with the android drivers enabled but i've only gotten zubuntu to start. None of the keys seem to work...or anything else for that matter. will do some more test and debugging.
Here's the link to the Zubuntu page
Here's a link to the rootfs
I got the kernel, default text, and haret attached below.
Congratulations!
Keep us informed if make any advance in getting it work!
awesome
Bravo very cool, good luck with solving the problems will watch this topic
Great news mate, I will test it by myself today
How can I install it?
The download link is crash don't work. Please upload again.
The link is working, I have no problems
I think. Thank you.
great!
touchscreen work?
is there any progress on this project?i think drivers from other linux kernel's could be imported.what works and what does not?
Any chance you could point me in the direction of the Git and defconfig that you used to build the 2.6.32 kernel?
keep it up !!
Any news so far??
Any news on this topic?
Making this work perfectly would be awsome, hence the large amount of RAM and CPU power!
Unfortunately im a linux user, not a developer.
I hope someone could get the touchscreen and keyboard drivers from other distro.-s, e.g Titchy linux, or Opie.
It has been already done for other HTC phones, and for Samsung Omnia, and there is a big bunch of programs already compiled for ARM versions of Ubuntu.
Getting and making the drivers work with this wont take more than days for developers, but without the suitable knowledge, it would take weeks for us to research everything about embedded linux's from zero.
I'm going to release a new 2.6.33 kernel, defconfig, and the source changes for everybody to play with later this evening (now posted below). It's faster and the power functions seem to work and you can see the touch screen enabled not functional in ubuntu tho.... .
KEYMAP
Posted corrected keymap above. All of the fn keys are as they are labeled on the universal except for & and the first and last rows of special keys.
Not kwl: Kernal Panic
how to fix? =]
Hi,
I want to know how can I make my own ROM using paul's ICS sources or build it from the CM9 sources, which software I need to use and is this tut good for beginning?
www(.)theunlockr(.)com/2010/03/26/how-to-create-your-own-custom-rom-for-android-part-1-setting-up-the-kitchen/?
PS: I also want to add the reason why I don't contact with paul is that I wanted to learn & develop it only for me & mine friends
Ofc. for X8 and on nAa kernel ;3
do you know JAVA atleast?
EDIT: wait, you want only to make the build, or to work on the rom and on the source?
EDIT2: Wrong section btw, you should asked on Q&A's
Java on basic level, I do not know any of it's APIs but I can learn them ( I don't know Android API too )
C/C++ on intermediate level
First build it from source, after successful modify source and compile ROM.
MOD: Please move to Q&A if possible, thanks.
You could read my thread (look at my signature). I wrote all the stuff you need to know of ROM-compiling. There's also a thread about kernel making.
eagleeyetom said:
You could read my thread (look at my signature). I wrote all the stuff you need to know of ROM-compiling. There's also a thread about kernel making.
Click to expand...
Click to collapse
Dzięki
Thanks at all, you got the point. I'll try to compile it using yours tut and post result here And one more thing, developing CM9 for X8 build for which phone i need to base on? And where I can get hmmm... X8 Driver sources? Adreno libs and others?
Right now we don't have sources for X8. You need to port most of libs. You could also paul-xxx's drivers from his github. Good luck If you have some questions PM me, I'll help if I'll be able to.
NeveHanter said:
And one more thing, developing CM9 for X8 build for which phone i need to base on?
Click to expand...
Click to collapse
doixanh based his GingerDX ROM - based on Gingerbread - on the Hero source tree. If I recall correctly I read somewhere that a CM9 port to the HTC Hero exists; that might be your best shot as the phone is about the same specs as the X8.
And as eagleeyetom wrote: You either use paul-xxx's drivers or you reverse engineer the Eclair drivers and write them anew from scratch (if your thought was going into the direction of the kernel) - there's no CM9 port for the X8. Your best option would be to try and find devices having a matching hardware component and porting the drivers from there - but chances are pretty slim that other phones use the same hardware SEMC stuffed into the X8.
---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------
Update: paul-xxx also maintains a GIT repo with a msm7227 kernel ...
paul-xxx / semc-kernel-msm7227-ics
EDIT: Along with some other interesting repos ...
- android_hardware_qcom_camera
- Xperia-TI-Wlan
- android_device_semc_msm7x27-common
These three at least seem to relate to the X8 "Shakira"
Thanks all for help, now I have some basic workaround with this
And one off topic question
ICS is running on 3.0.3 kernel, yes? So why we don't try to port it for X8 and using old 2.6.xx?
NeveHanter said:
And one off topic question
ICS is running on 3.0.3 kernel, yes? So why we don't try to port it for X8 and using old 2.6.xx?
Click to expand...
Click to collapse
It seems the genuine Google AOSP ICS is running Linux 3.0.8
Porting the Kernel might turn into a huge effort. The ABI of 2.6.29 and 3.0 are not really compatible, so the kernel drivers would need to be ported to the CM9 3.0.x series - in case a simple patching them into the kernel tree and trying to compile bombs out with tons of make errors.
Apart from that - the main problem with ICS on the X8 is that a whole lot of devices can't use a custom kernel as a change in the hardware (devices of 11W29 and newer) prevents boot loader unlock.
We could try to see if the CM9 kernel could be slapped into shape ... I got a Quad-Core Phenom II to tackle that task - if someone wants to help out in the research if some msm7227 / Shakira specific parts would need to be patched into the source tree because they aren't part of it.
EDIT: Even the official CM repo uses Linux 2.6.37.6 as their kernel, and the progress on the FXP Kernel seems to have come to a halt; at least I can't see any new stuff in the -shakira repos.
LG GT-540 has ICS on 2.6.35 kernel. Maybe we could try to port Arc's kernel. Maybe this one? Recommend me some C/C++ books to learn basic stuff
You want this book's in english or you prefer in our native? ;3
eagleeyetom said:
Recommend me some C/C++ books to learn basic stuff
Click to expand...
Click to collapse
This is a rather tricky question ...
If you do as I did simply Google up a C/C++ Reference/Tutorial (i.e. http://www.acm.uiuc.edu/webmonkeys/book/c_guide/ or http://www.cplusplus.com/doc/tutorial/) and get going ... you already got gedit to code up .c files, and gcc is also part of your Linux distro to try and compile your "hello_world.c" You could also Google for Online Classes (in the like of http://www2.its.strath.ac.uk/courses/c/) and pick whatever suits you.
However, if you want to read real books ... look through the offers of Addison Wesley and pick what you think is the best book for you. You could also hit up your closest public library and see what they have in store (may be cheaper than buying in case you don't have much money to spend) - or, in case you study, you may want to look into your University's library.
Of course you could also start off with the usual "C/C++ for Dummies" or "Teach yourself <whatever> in 7|14|21|30 days"
Polish would be awesome ;P
Best, simply writed polish C/C++ tutorial, one of the best www(.)warsztat(.)gd/tutorials.php?x=category&id=18
In adddition you can search for ( it's a big ebook ) Symfonia C++ Grębosza ( Symphony in C++ ), you can find it on chomikuj.pl but if U want I can upload it somewhere for you
And if you will have any problems with C/C++ you can write to my GG number 10037533 or PM me here
I do not know whether the idea meets with interest ...
I'll throw the idea but just once in the round ...
We all know that bada shall have its flaws and missing features that only by custom ROM can be upgraded ...
Here is a point to wear ...
Even the look you could make more of bada ...
This point comes into play two ...
Meanwhile, it allows the bada-modding to get ran well to certain design elements ...
All i can say *. Rbm-Files ...
Hence my idea of a completely new to tinker bada-ROM ...
Sense of it all, it should NOT be to create a second Android, but to create an entirely new concept ...
Therefore, would initially only once to clarify how the ROM should be made more technically ...
Next, you would have ran to the design ...
Here are a few people would get together, who know the one with the modding. Then people would of distress, which in terms of design e Bissel what's on the box.
This includes Flash programmers would include, for example, to craft a new lockscreen ...
I hope it will find a few people ...
Maybe we can develop something really good here ...
All i can say *. Rbm-Files ...
Click to expand...
Click to collapse
Meinst Du die aus dem RC1 ?
Ich kenne noch keine Lösung. Die Bilder auszutauschen...
Alle Versuche gingen zumindest bei mir bisher in die Hose...
Ich kann mit Ach und Krach einige Bilder ausschalten...
This includes Flash programmers would include, for example, to craft a new lockscreen ...
Click to expand...
Click to collapse
Bei Flash fangen leider wieder viele an zu weinen, wenn es um Decompile geht...
Die die Ahnung von Action Script haben, schmeissen lieber en masse Themes in den bada Markt... solange der Kopierschutz der Themes/Flash noch hält...
MfG
Taxidriver05 said:
I do not know whether the idea meets with interest ...
I'll throw the idea but just once in the round ...
We all know that bada shall have its flaws and missing features that only by custom ROM can be upgraded ...
Here is a point to wear ...
Even the look you could make more of bada ...
This point comes into play two ...
Meanwhile, it allows the bada-modding to get ran well to certain design elements ...
All i can say *. Rbm-Files ...
Hence my idea of a completely new to tinker bada-ROM ...
Sense of it all, it should NOT be to create a second Android, but to create an entirely new concept ...
Therefore, would initially only once to clarify how the ROM should be made more technically ...
Next, you would have ran to the design ...
Here are a few people would get together, who know the one with the modding. Then people would of distress, which in terms of design e Bissel what's on the box.
This includes Flash programmers would include, for example, to craft a new lockscreen ...
I hope it will find a few people ...
Maybe we can develop something really good here ...
Click to expand...
Click to collapse
I thought there's no way to edit RBM files to date? I might try my hands on something (using ho1ods source) myself, but that might take a long time.
Alright, I've taken a look at the RBM files internal structure, and it doesn't look any good :-/.
While the internal structure itself is actually pretty easy, the problem lies in the embedded images. Four(!) different compression methods are used: LZ16, LZ32, QMG16 and QMG32. No way that I can do this all on my own. I could do decode/encode for LZ16/LZ32, but QMG is used for most.
The only chance that I see right now is, IF RBM is also used for Samsungs Android FWs that we'll get support from this side.
Maybe RBM step by step..
Step 1 disable Pictures... like here:
http://forum.xda-developers.com/showpost.php?p=27932409&postcount=124
Step 2 could be replace content... or replace by other Pic from other RBM...
If I have more time... I will play again with bada SDK...
Maybe easier to try modified RBM instead RC1 flashing on device...
Best Regards
adfree said:
Maybe RBM step by step..
Step 1 disable Pictures... like here:
http://forum.xda-developers.com/showpost.php?p=27932409&postcount=124
Step 2 could be replace content... or replace by other Pic from other RBM...
If I have more time... I will play again with bada SDK...
Maybe easier to try modified RBM instead RC1 flashing on device...
Best Regards
Click to expand...
Click to collapse
I hope this will help us get a little bit further:
http://forum.xda-developers.com/showthread.php?p=30648338#post30648338
Okay...
let's pick up this thread again...
Maybe it could be pinned as sticky...
I think, we should collect all improvements of FW customizations here...
E.g. Tutorials for UI Customizing...
I think, we ned a plan...
So i think, we need an overview, what UI element can be modified in what RBM file...
Wat r the flaws in bada 2
Sent from my GT-S5670 using xda app-developers app
How about replacing QMG compressed chunks with LZ ones? Should be doable, no?