[Eee Pad Transformer Android Development] timduru:
Additional info & links

Known Issues & Tips:

Multi-panel interface specific:

When collapsing the small panels, part of the apps will stay on top of the cornerstone interface.

=> just ignore, you can still hit the collapse/expand button in between the apps

Collapsing and expanding might not position the cornerstone "vertical bar" correctly sometime

=> just hit the collapse/expand button a couple of times and it'll reposition correctly.

Without running the multi-panel interface:

The default browser's is displaying the first page even if you choose another page

=> Start the cornerstone panels and try again.

Launcher seems to get killed everytime you hit the home button.

=> It doesn't do it if you run the panels.

Recent apps window might rotate wrongly.

Top most dialogs will get crazy and flash (dialogs asking you for default apps and so on)

=> you can still click on the choices if you're fast

=> hitting the home button or another recent app will get you out of the "loop"

=> running with the multipanel interface is not having this issue, so you can start the multipanel temporarily the time you can pick the choice in the topmost dialog.

General:

The cornerstone code might stop services randomly, this bug is there since the first release of Cornerstone unfortunately, so it might not be easy to fix.

Annoying side effects: everything that relies on a service that has been killed might not work properly (clock will not update, some of the EOSCC changes won't work, and so on...)

The original code is made for TabletUI, so it's not aware of of the statusbar on top, because of that the apps and cornerstone interface is "layered under the status bar currently.

=> For the top cornerstone panel you can still reach the top right button to choose the app running in the panel, even if you can't see the icon just click there.

Not all apps are compatible with the cornerstone code

Desktop wallpaper might not display with default laucher

=> use another launcher

EOS4 & JB Specific:

GPS

:

if it is taking a long time to get a lock or no lock, follow this:

http://xdaforums.com/showpost.php?p=38368206&postcount=2452

Google search

:

If the version you're using is crashing when you open Google Now,

go to Settings => Language & Input => Voice Search , then uncheck Hotword Detection.

Other Tips

How to report:

Things to check before reporting:

- If it's a general question or if it is not specific to this rom ask in the Q&A section

- make sure you have read all the tips and searched on the forum before reporting an issue.

- try to reproduce your issue right after flashing and before restoring anything

- wait that the cpu usage is down to close to 0% for a few seconds before proceeding with testing.

- Check that it is not already listed in the known issues.

Reports about performances issues:

Keep in mind that coming from a full wipe / factory reset, there are a few cpu and disk io tasks that are going to happen:

- Mediascanner service is going to rescan all your medias, which can take from a few minutes to a few hours or days if you have many

- Google will restore / sync things.

So make sure that it is finished and that some app is not eating the cpu or disk io before reporting.

What to send in your report::

- Make sure you describe exactly what happens before/during/after the issue.

- If you can reproduce it, write a step by step way of reproducing it.

- If your issue is a performance issue, explain in details what you define as such

(is it taking time when you click , is it that it seems to have a low fps ? ..)

Make also sure you indicate the following:

- which rom/version are you using ?

- which kernel are you using ?

- did you follow the exact procedure listed above for flashing ?

- did you restore any of your applications / settings ?

Run these commands in a terminal:

su -

busybox top -n1 > /sdcard/top

dmesg > /sdcard/dmesg

logcat -d > /sdcard/lc

include the resulting files: /sdcard/top & /sdcard/dmesg & /sdcard/lc in your post

Thanks that will help to debug and save me a lot of time if I get correct reports ;)