NexusHD2 Android Forum

hu016865 wrote:can who anybody install this rom ?

if yes .which : nana ? dataonext? natviesd ?

and info ???

I have updated my 4.3 to 4.4, with only wiping dalvic cache.
Anyway i 've always had an error message while installing tytung ROM's in Aroma installer, yet the ROM works perfectly (the error message is something "cant open yx file" blabla.
But it works perfectly!

hu016865 wrote:can who anybody install this rom ?

if yes .which : nana ? dataonext? natviesd ?

and info ???

I upgraded from V4.3. No problem. I'm using DataOnEXT.

I have the same problem.

Its 1st time when i cant install tytung rom :/
Aroma installer working good up to reboot: Welcome - i chose Language and click " > " button and... FC wizard.
No way bypass that. I try 3 times, always the same.

v 4.2 working good. The same device, sdcard, etc.

HD2 EU, DataOnExt 2GB, aMagldr, CWM. part. 300MB with 15MB cache

Tytung, thank you for this great update. Works very smooth to.

I installed the new 4.4 rom and it works perfectly. No problem so far. But, with this update i don't know how to customize the amount of possible icons on every page. In the previous rom i had 5x4 (height x width).

Can someone help me?

Thanks


Pedro

Thanks tytung!
Updated from 4.3, now with softkeys from aroma installer.
Everything works fine.

I recommend nova launcher if you want fast transitions(even trebuchet is lagging a bit), different homescreen grids , ...

have fun !

Hi guys, i update my phone with 4.4 and my device it gets warm very fast ... I didn't have this with v4.3 anyone else have this issue ? Thanks

Στάλθηκε από το NexusHD2 μου χρησιμοποιώντας Tapatalk

Refraction wrote:Here is the logcat right after lang is selected
http://pastebin.com/ssyTGpqD

Thanks.

Code: Select all

E/AndroidRuntime(  624): FATAL EXCEPTION: main
E/AndroidRuntime(  624): Process: com.google.android.setupwizard, PID: 624
E/AndroidRuntime(  624): java.lang.NoSuchMethodError: android.net.wifi.IWifiManager.setWifiEnabled
E/AndroidRuntime(  624):        at com.google.android.setupwizard.BaseActivity.tryEnablingWifi(BaseActivity.java:1533)
E/AndroidRuntime(  624):        at com.google.android.setupwizard.WifiSettingsActivity.launchWifiSettingsPanel(WifiSettingsActivity.java:103)
E/AndroidRuntime(  624):        at com.google.android.setupwizard.WifiSettingsActivity.onCreate(WifiSettingsActivity.java:68)
E/AndroidRuntime(  624):        at android.app.Activity.performCreate(Activity.java:5231)
E/AndroidRuntime(  624):        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087)
E/AndroidRuntime(  624):        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2169)
E/AndroidRuntime(  624):        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2265)
E/AndroidRuntime(  624):        at android.app.ActivityThread.access$800(ActivityThread.java:145)
E/AndroidRuntime(  624):        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1206)
E/AndroidRuntime(  624):        at android.os.Handler.dispatchMessage(Handler.java:102)
E/AndroidRuntime(  624):        at android.os.Looper.loop(Looper.java:136)
E/AndroidRuntime(  624):        at android.app.ActivityThread.main(ActivityThread.java:5116)
E/AndroidRuntime(  624):        at java.lang.reflect.Method.invokeNative(NativeMethod)
E/AndroidRuntime(  624):        at java.lang.reflect.Method.invoke(Method.java:515)
E/AndroidRuntime(  624):        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:781)
E/AndroidRuntime(  624):        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
E/AndroidRuntime(  624):        at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(  441):   Force finishing activity com.google.android.setupwizard/.WifiSettingsActivity


Setupwizard is a Google app, and the setWifiEnabled() method cannot be found according to the logcat java.lang.NoSuchMethodError: android.net.wifi.IWifiManager.setWifiEnabled.

The CM team changed setWifiEnabled() method
from boolean setWifiEnabled(boolean enable)
to boolean setWifiEnabled(String callingPackage, boolean enable).

See https://github.com/CyanogenMod/android_ ... c6#diff-11

Workaround: install v4.3, finish the setup wizard, reboot and then flash v4.4 over v4.3 (don't select factory reset).
It will be working if you want to do a fresh install.

prexda wrote:I have the same problem.

Its 1st time when i cant install tytung rom :/
Aroma installer working good up to reboot: Welcome - i chose Language and click " > " button and... FC wizard.
No way bypass that. I try 3 times, always the same.

v 4.2 working good. The same device, sdcard, etc.

HD2 EU, DataOnExt 2GB, aMagldr, CWM. part. 300MB with 15MB cache

I have the same problem, after trying two times as native sd, , I gave up and re-installed v 4.3 which works on the same device.
HTC HD2 EU

In case someone, e.g., in India, cannot download the V4.4 ROM, please try the mirror at Dev-Host (via adfly)

I have updated to NexusHD2-KitKat-CM11.0 V4.4, it's fast and smooth.

An intra-system problem, when I executed screenrecord command with format:

Code: Select all

adb shell screenrecord --size 480x800 /data/local/tmp/output.mp4

it did't work and outputted in prompt:

Code: Select all

ERROR: unable to create encoder input surface (err=-38)

Related logcat messages is:

Code: Select all

I/OMXClient(15755): Using client-side OMX mux.
I/SoftAVCEncoder(15755): Construct SoftAVCEncoder
E/SoftAVCEncoder(15755): internalSetParameter: StoreMetadataInBuffersParams.nPortIndex not zero!
E/OMXNodeInstance(15755): OMX_SetParameter() failed for StoreMetaDataInBuffers: 0x80001001
E/ACodec  (15755): [OMX.google.h264.encoder] storeMetaDataInBuffers (output) failed w/ err -2147483648
I/ACodec  (15755): setupVideoEncoder succeeded
E/OMXNodeInstance(15755): createInputSurface requires COLOR_FormatSurface (AndroidOpaque) color format
E/ACodec  (15755): [OMX.google.h264.encoder] onCreateInputSurface returning error -38
W/MediaCodec(15755): createInputSurface failed, err=-38
D/ScreenRecord(15755): failed

I'm considering that it's not issue comes from HD2 porting but from CyanogenMod side.