NexusHD2 Android Forum

1. Softeky - set to 200 - 240 is too big

2) Lockscreen problem
Not displaying weather details , No date Only time
How to correct same

good job man for this rom..
i found some problem
BBM can't login...stuck on black screen without welcome screen of BBM...

I hope next could be fixed this problem...

thanks..

PwnedHD2 wrote:
Thank you for your feedback. Am actually experiencing the same thing where switching to ART takes over 30 minutes. However as soon as the process completes mine reboots and thats when it fails to get out of the reboot loop. Think I will clean my Sd side and try again. will report back.

By the way have you noticed any performance enhancement and better battery economy with ART as suggested ? Thx

I have also switched on ART, and it seems to be working OK. The first startup after enabling ART took about 30 min. At that time the installer listed about 100 apps. Added later 20 more apps.

First startup of app sometimes slow. Maybe the "black screen" phenomenon is simply a slow start? It tolk me almost one hour to get facebook up and running. Now it works OK.

To be able to tell if the system is still running I switched on the kernel statistics (text in upper right corner of he screen). As long as this text keeps changing the system is doing something. (By the way, what do these numbers and colors medan?)

I have WM 6.5 in DRAM and use 4extrecovery. For some reason my European phone seems to tolerate a scandisc ultra 32Gb class10 UHS card.

Hi,
it seems that I was the only one with lost autofocus

Well, installing camera fv resolved the problem in all apps...

Camera Touch Focus?

No,

I can't touch to focus in a desired location, like in wm6.5, the camera focuses before shooting.

Before camera fv the autofocus wasn't working at all.

One time, and only one time, the camera app showed the touch focus but it was ineffective and disappeared the next reboot.

@olof,PwnedHD2: I second the long run. Normally the switch from dalvik to ART is fast, but after bounce Android has to compile all the packages and that indeed takes long. I believe if anything goes wrong in this process (like Android running out of RAM), it would bounce,but on next startup still detect some uncompiled apps and will continue compiling them (this time no such message like "Upgrading app 22/XXX"). It could then do so indefinitelly - always hit the point of no RAM, soft bounce and then again boot logo.I.e. bootloop. I found this out when I got the bootloop I mentioned before and connected to it via adb (simply running adb logcat > file.txt - and then looking inside that file - I saw the compilation there - something like "dex2oat ...").

If you want to make sure this is not the issue and don't feel that confident in using adb and plan to do clean install anyway, then I suggest you create your swap partition on the sdcard straight away (e.g. using GParted or partition magic or even directly in recovery - but this way you would loose everything on the sdcard) and then do the install. The instalation will autoenable swap for you if it finds swap partition on sdcard. So no need to mess around then with adb....

PoJD001 wrote:If you want to make sure this is not the issue and don't feel that confident in using adb and plan to do clean install anyway, then I suggest you create your swap partition on the sdcard straight away (e.g. using GParted or partition magic or even directly in recovery - but this way you would loose everything on the sdcard) and then do the install. The instalation will autoenable swap for you if it finds swap partition on sdcard. So no need to mess around then with adb....

I actually have a separate swap partition of 500Mb, which I created a long time ago when I was testing several roms, some of which support swap. And my install of 4.2 was a new (clean) install. But as far as I can tell swap is not active. I thought swap is not enabled by default.

Ah, right.didn't try it myself in this ROM, I thought it is enabled by default. But probably not the case as you already pointed out. In that case either some swapper app or creating the file in /system/etc/init.d directly to switch on swap on startup.

I actually did that few days back, didn't want to risk to run out of RAM again. So in case someone would find this usefull...I also found out that the swapon does not support -a switch(not sure if an issue of this ROM only). So I avoided mounting the partition via fstab and directly used the block device below.

1. Make sure you have a swap partition created on your sdcard. I also assume it is your 3rd partition there - if not, change 0p3 accordingly (to 0p2 should it be second partition, etc)
2. Make sure you have debugging options enabled in your phone
3. Connect your phone and launch command prompt
4. adb shell
5. echo "#!/system/bin/sh" >> /system/etc/init.d/05userinit
6. echo "swapon /dev/block/mmcblk0p3" >> /system/etc/init.d/05userinit
7. chmod 750 /system/etc/init.d/05userinit
8. reboot

Now you should see swap being used - again by running free command and seeing non null value in total swap available.

Hi,
another problem, importing contacts from sim hangs at 100%

There is a solution? I searched in various forums but found nothing...

Thanks