@kireevco Should we (you) remove AppVeyor checks from Sming develop branch and add it to a PR or other branch? Currently all PRs are failing and showing up as failed in the list which may influence how quickly PRs get applied, e.g. an admin looking at a failed PR may ignore it, expecting the submitter to fix the problem. These are all failing becuase AppVeyor is not yet configured correctly.

@riban-bwI have asked @kireevco the same several times but he only pointed to the issue but did not solve.Just merged a PR from me that removes an appveyor.yml file from the repo.Probably this will solve, if not we have to search further.

@sfam : Your question is ambiguous.You want to enable OTA and only one Rom ? That combination is not possible

@hreintke I mean like the way it was before rboot... back then, OTA was simple: specify links for new firmware and update... the end user didn't have to worry about two roms, big roms, memory offsets, ram length... how can I use rboot the same way?

ok, thanks alot... I've been trying for a few days the two roms method and I think a regular 512k esp01 does not have enough space for two Sming roms... I always got invalid rom nr1 or device self reseting...

Hey, i have problem with HttpServer_ConfigNetwork example. After upload, i cant connect stable from Android smartphone to AP. Network is disappear for second and then phone connected for some seconds. From PC i dont have problem. I try with 2 phones (android 2.3 and android 5.0.1). I try other example, dont have any problem.

I found the problem... On my galaxy s 3 mini with cyanogenmod 12.1 (android 5.1.1) wi fi is very unstable. I try with Android 2.3 too. But with other phones and computers is ok... strange. Maybe bad port with wi fi drivers or something