hi! someone was able to made a gingerbread app working?
hi! someone was able to made a gingerbread app working?
there's a small bug creating androidmanifest.xml : delphi always add a "largeHead" options , but it's compatible only from api11, so you can't deploy.
solution is manually edit androidmanifest.template in project folder and remove android:largeHead from the xml.
so it compile and deploy correctly, but app doesn't start , it always have a black screen :(
there's a small bug creating androidmanifest.xml : delphi always add a "largeHead" options , but it's compatible only from api11, so you can't deploy.
solution is manually edit androidmanifest.template in project folder and remove android:largeHead from the xml.
so it compile and deploy correctly, but app doesn't start , it always have a black screen :(
Did you QC it?
ReplyDeleteLast time I tried it worked ok without the manifest change. Gingerbread emulators aren't supported, but devices should be ok.
ReplyDeleteAs I mentioned, it worked for me last time I tried. I checked again to be sure. New project build, deployed & installed on my HTC Desire running GingerBread. It ran successfully, screen displaying as expected.
ReplyDeleteI don't know what's going on with your device or that QC, but it's not a general issue with Delphi and Gingerbread.
To get an idea why the Android app crashes or fails you need to look at the logcat
You can do this most easily by running monitor.bat (from the Android SDK tools directory) and see the logs from your device in the LogCat pane.
If you have issues running monitor.bat (most likely due to a lack of appropriate PATH entries) you can try running the deprectaed ddms.bat in the same directory for the same result.
An alternative is to launch a command prompt and run:
adb -d logcat
but that really requires piping it to a text file and doing some searching therein.
adb.exe lives in the Android SDK's platform-tools directory. The -d flag forces it to look at a connected device in the case that maybe you have a device or an emulator. -e will force it to use the emulator instead. No flag means it will talk to any singular connected device.
If you find an issue specific to a device that looks like it ought to be predicted by the product, ensure you add all relevant details to your QC report, and please post the QC number.
ReplyDeleteHaving re-read the cited QC, I now see that it relates to a sample project that suffers from a change that occurred prior to RTM, and the project file wasn't correctly updated tp accommodate that change.
ReplyDeleteThis issue won't affect new projects, so don't put any credence to that issue being related to your problem.
And BTW, it's largeHeap, not largeHead.
ReplyDeleteCan You confirm me changes to do in delphi skd settings to change api target?
ReplyDeleteYou don't need to change the API target, as you're not linking against a bunch of API-dependent Java libraries. You're linking against the Delphi FMX framework, which works in GingerBread MR1, ICS MR1 and JellyBean.
ReplyDeleteAs such it makes no sense to switch API targets.
Ok, so maybe it's a device problem. Tomorrow i'll try with galaxy w :-) thanks
ReplyDeleteAs mentioned earlier, you may find out more from logcat
ReplyDeleteDiego Rigoni you can change androidmanifest.template.xml file. This file is in folder with project file. You should remove from it next line^
ReplyDeleteandroid:largeHeap="%largeHeap%"
And problem with supporting GingerBread devices will resolved for you.
He mentions that he has to do that in the original post. The subsequent issue that I think he was really asking about was the hanging on black screen.
ReplyDeleteDo you set permissions: read external storage and write external storage?
ReplyDeleteAll the projects I've created have these permissions set by default. If they are not, then maybe one or two of the templates are inconsistent.
ReplyDeleteBut that said, if the external storage permission is not set, you'd see evidence in logcat.