Cupcake is catastrophe, claims Big in Japan dev

[abchiptop]

Scrannel, I think I know which wifi issue you're referring to, is it when wifi disconnects when the display turns off? If so, pick up keepwifi. it's free in the market, and is a "set and forget" app, you enable it once, and itll always keep your wifi connected unless you turn wifi off or leave coverage area.
as for file transfers, if youre on wifi and have your laptop handy, on air turns your device into a wireless networked drive, which is pretty handy to tell you the truth. sure, it's no device to device solution, but transferring from mac to sd card couldnt be easier, no wires needed.

id love to see obex added as a bt profile, but it's something i can wait for.

[scrannel]

Thanks abchiptop,

Have tried all the wifi fixes, and found one that works 90% of the time. I'll go back and give "keepwifi" another try in case of updates. Also, will give the on air idea a shot, thanks. However, there really is no excuse for a phone in this age, not having bluetooth data transfer ability. I was on a boat working a few days ago and got a call that my agent needed a script. Well, no wifi available. I was lucky that my son had a bunch of USB cables (ps3) on board so I could transfer the file to my phone and send it. My N80 had bluetooth, infrared and cable transfer ability. And, so far as wifi only sort of working...? Come on...

[Scythe]

Thanks abchiptop,

Have tried all the wifi fixes, and found one that works 90% of the time. I'll go back and give "keepwifi" another try in case of updates. Also, will give the on air idea a shot, thanks. However, thre really is no excuse for a phone in this age, not having bluetooth data transfer ability. I was on a boat working a few days ago and got a call that my agent needed a script. Well, no wifi available. I was lucky that my son had a bunch of USB cables (ps3) on board so I could transfer the file to my phone and send it. My N80 had bluetooth, infrared and cable transfer ability. And, so far as wifi only sort of working...? Come on...

There's a number of wifi fixes in the 1.5 release, so hopefully that takes care of them. I'm betting your wifi issue is the same as my own, and it's related to the name the device gives the router (it causes conflicts for most lower-end routers causing connections to drop by while still showing as connected, etc).

[kolbysoft]

LOL,
that was the funniest thing since I read the Google blog.

I would agree with you, if only they hadn't introduced some rather annoying bugs. There's also a difference in blogging in vague terms about changes and actually seeing the APIs. And then match those changes against the known bugs, the most annoying of which is that transparent backgrounds are no longer transparent.
My app doesn't use any hidden APIs (how would I know about them in the first place?), nor does it have view hierarchy issues, and still doesn't display properly on 1.5.
Finding what is broken and why takes more time than the few days I had so far.

Also, some of us are doing this not as a full time job and put apps in the market for free. Now the users get p*ssed off because the app doesn't work as expected.

Michael

This is plain silly. Google released an early version of the 1.5 SDK two weeks ago, so that developers would get a heads up on what to do in order to ensure compatibility, granted the final 1.5 SDK was released only a few days ago, but that did not force anyone to wait and not use the early 1.5 SDK release.

Even so, if the 1.5 update is pushed out in May, then we would have had at least 4 days with the final 1.5 SDK and an additional two weeks with the early release. So that would be rather close to the 2-3 weeks mentioned as a required time to update the apps.

Also, Google has been blogging about these changes for some time now and they have shown how to remain backwards compatible and how to deal with using new features while remaining compatible with previous versions. And if you would make a 1.5 only app, then they have shown how to mark that app as requiring 1.5, so that it can't be incorrectly installed on an older OS version.

As I understand it, based on the Google Developer blog, the only programs that will break are those that use unofficial API's and/or exploit security flaws.

There's also a change of the default button width that might affect the UI layout for some, but that's an easy fix. Also there's some changes affecting the maximum limit of nested items in the UI layout, but if you're hitting that limit, then you need to rethink your layout.

If your going to be a pioneer and develop apps for a smoking hot OS that haven't had time to settle yet, then you have to expect a bumpy ride.

[scrannel]

There's a number of wifi fixes in the 1.5 release, so hopefully that takes care of them. I'm betting your wifi issue is the same as my own, and it's related to the name the device gives the router (it causes conflicts for most lower-end routers causing connections to drop by while still showing as connected, etc).

The ONLY router it worked on, reliably, was my old, crappy -- low end -- Linksys. Everything else in my house works fine: two desk tops; PS3; iPhone; N80; HTC 710; XBOX 360; and even my Lenovo/Thinkpad which is notoriously hard to sort out. Plenty of people walk through the door with blackberrys and laptops of all sorts and have zero issues. So, hopefully, this will be corrected.

[Scythe]

The ONLY router it worked on, reliably, was my old, crappy -- low end -- Linksys. Everything else in my house works fine: two desk tops; PS3; iPhone; N80; HTC 710; XBOX 360; and even my Lenovo/Thinkpad which is notoriously hard to sort out. Plenty of people walk through the door with blackberrys and laptops of all sorts and have zero issues. So, hopefully, this will be corrected.

Yeah, I think it's because the device isn't giving an alias to the router to route with. Hopefully it'll be fixed.

[henchman]

for wifi file transfers, i find Afile much easier and better than On-Air.

I also found the new radio abysmal for wifi in the haykuron builds, which is why I went back to RC33.