|Current Versions:||Preview versions | EOS4 Nightlies|
|Compatible optional kernel:||Tim_KatKernel_104_JB4.2_Lidpatch.zip Tim_KatKernel_103_adhoc_JB4.2_Lidpatch.zip|
|Questions & Support:||On xda forum|
How to install:
- Default browser can become unstable if you use flash with it, as flash is not supported anymore on recent Android versions. It should work mostly fine if you set it to load only on demand though: => Browser Settings => Advanced => Enable plugins: On demand - Autorotation is using about 1-2% cpu, if you want maximum performance disable autorotation - Bottom Navbar can interfere with some apps, if you want maximum performance disable the navbar (in EOSControlcenter) or disable both bars (long press on the power button) To switch between apps without a navbar you can hit alt+tab or ctrl+menu on the dock or you can use LMT for a navbar replacement: http://forum.xda-developers.com/showthread.php?t=1330150 - Default launcher can make the drop down notifications & QS lag more in 4.2.2 => disable the bars or use another launcher like Go Launcher EX. - Using Simulate secondary display will generate a bootloop => do not use that option. If ever you did just reflash the rom - Certain NTFS disk won't automount: might be dependant on the formatting and/or partitionning ? => workaround: try a 3rd party app to mount it: USB OTG Helper, paragon ntfs or the K.A.T app. - GPS: if it is taking a long time to get a lock or no lock, follow this: http://forum.xda-developers.com/showpost.php?p=38368206&postcount=2452 Official teameos bug report system for all devices
- Fix the bugs & improve things of course ;)
How to report issues
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.
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 either in a post in the thread on the xda forum or into the bug report system Thanks that will help to debug and save me a lot of time if I get correct reports ;)