Thx walter for ur multiboot solution.
And sry that I don't do anything for defy anymore but I can't develope for two devices. Even for one the time is very limited.
I hope u don't bother me
And since xda doesn't like xiaomi I can't post my results here
So we will never get multiboot script work with 2nd-boot rom? What a pity. But why can't you post your result
I have tried several things regarding the calibration, but haven't gotten far since I have no idea what I'm doing
In my case, I never had any WiFi problems with the old drivers, and from what I've found, others haven't had much problems either with the old drivers either, so I'm not really sure there is a point in having new drivers. Maybe WiFi direct won't work without them, I don't know. Either way, as the saying goes "if it ain't broke, don't fix it", I wouldn't expect any serious developer to live by that, since I don't; I'll flash almost any new build if I have the time, just for the sake of trying something new. :good:
The only reason I stopped using Quarx's ROMs (and basically any new CM10/10.1 ROM, since everyone bases their ROMs on Quarx's) is due to the fact that until we actually see changes being made to the WiFi, I know for a fact this problem will still be there.
And, I do consider it a bug since I can easily reproduce it, and if you do a WiFi direct peer search, the interference will stop while it's searching; but actually figuring out what's going on with that is way out of my league.
The only way to prevent this, in my case, is getting closer to the router, and I've tested/confirmed this with at least 7 different Quarx ROMs uploaded after 03/26 (including CM 10.1), "Slim-3.1.1-mb526-20130527-1138-UNOFFICIAL", and "Taki_jeden_rom_03062013".
) last night. I was dead on tired though. I for one know i have a cheap 30$ router and don't except to much from it, but it's been working for the last 2 years since i bought my Defy so it should work now. After a couple of reboots it seems to work. Will test further. I am well aware it's a real bug. It happened to me a lot on some nightlies in the past when Quarx was testing Wifi drivers.
@m11kkaa , I know it has been developed strictly for Defy, but I wonder if you could tell me which part of code provided to DefyMultiboot@Github is based on your Defy info and specs, so that I can understand where is the parts I have to change to port it to my phone.
PS: Obviously in the hypothesis you let me port it!
[B]v0.8:[/B]
- addon.d (Multiboot will be kept on ROM-Update)
- working reboot recovery inside multiboot-rom(will boot directly into the recovery for that rom)
- working reboot into bootmenu inside multiboot-rom
- security-fixes
- TLS-support
- fixed sdcard-problems for NAND-system
[B]v0.7:[/B]
- added integration in touchbootmenu. This is no compatibility-patch - since now multiboot can only be used in combination with touchbootmenu
[B]v0.6.1:[/B]
- fixed some memory-leaks in kernel-module
- fixed stupid bug which prevented creating backups on first start
[B]v0.6:[/B]
- new hook-method with kernel-side code which should be the solution to most rom-problems
- fixed a bug which prevented mounting cache-partition inside recovery
- fixed installer-bug when TouchBootmenu is used on NAND
- reboot to recovery/bootmenu does not work for now. will be fixed in future
[B]v0.5.5:[/B]
- support for Stock-roms with Greenbreadmod
- added version-file(for updater which comes soon)
[B]v0.5.4:[/B]
- fixed problem with install-script
[B]v0.5.3:[/B]
- support for TWRP recovery
- fixed problem with virtual systems with names longer than 9 chars
- don't change 2ndBoot-script for bootmenus with 2ndSystem-support
- show graphical error-message when error was detected and copy log to "/cache/multiboot/error.log"
- experimental support for booting stock-roms
[B]v0.5.2:[/B]
- more configurable(via config-file)
- fixed error-detection. On early errors you will get back to bootmenu
- fix boot-problems for some roms
[B]v0.5.1:[/B]
- fixed crash of GUI when choosing recovery
- fixed bug which prevented creating important images on first boot
- virtual systems now are using nand-backups with real data so you could install backups of virtual systems on NAND
- installer sets default bootmode to 2nd-boot
- added recovery-option for NAND
- patch background-image of virtual recovery so you see if you are flashing real or virtual system
- reboot system if you click "Go Back" in virtual recovery(until I found a solution for going back to multiboot-GUI)
[B]v0.5:[/B]
- better protection against unwanted changes on real partitions(thanks wizwin)
- fix Phone for for GB-kernel(thanks quarx)
- set props so apps can detect if phone started with multiboot or not(for future versions of multiboot-manager)
- reboot into bootmenu/recovery now works
ATTENTION: reboot into recovery will open recovery for REAL system!!!
- added GUI for choosing which (virtual) system you want to boot
[B]v0.4:[/B]
- replacing all references to real system with stub-image(will be automatically created at /sdcard/fsimage/stub.img).
Now the recovery for the virtual system should be completely abstracted and it shouldn't make any changes to the real system
- a PDS-backup will be created and injected because it's needed by android-system and above change removes the reference
[B]v0.3/v0.3.1:[/B]
- moving original system-partition to another location instead of lazy unmount so she will be accessible in 2ndBoot-system and will not be busy
- fixed recovery to improve installer-zip compatibility. MIUI works now
- internal script-changes
[B]v0.2:[/B]
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
[B]v0.1:[/B]
First release
