NexusHD2 Android Forum

Good Morning Superuser!

Many Thanks to Tytung for your great work to make our HD2 to the Best Phone EVER

I tested your since two years ( GB2.3.5) and all ROM are working perfekt !

All the best from Bavaria

Lolo78 wrote:Hi guys,

I've just Done a fresh Install on a new Sd (trenscend ultimates class 10) for Native Sd install and dowload the V2.3

I've made :
Task 29.
Install MAGLDR.
Formatted SD card with new FAT32 and EXT4 partitions using mini partition wizard (both as primary).

And ... all is working expcept Data (3G) ... Nothing to do I've tried with PPP and RMnet and it's the same.
what is the problem ?

Is it due to Magldr ?

Could someone can make a step by step install with good links for CLK instead of Magldr ?

Hi. Please look this post, you will find what you need for flashing android.
Thanks.

hd2-android-flashing-guides-sticky-topic-t6.html

Thks but i've already seen this post and all the tuto use Magldr ...

I would try without it but when searching how It's a bit confusing because :

1) Install BlackCLK v1.5.0.8 from kokotas => but link are not good : http://www.mediafire.com/?nhyausx0p5whu#tzg7whl9wwaih
2. Activate SBoot in BlackCLK v1.5.0.8 => What does it mean there is no option in clk
3.increase recovery partition recovery dans CLK ( 7 ou 8 Mo) => Why and Where
4. Pass to Recovery EXT4 ( http://goo.im/devs/Xylograph/Various/Recoveries/NAND ), flash it in recovery and reboot
5. Install Zip, choose zip ... choose SD-Ext at l'installation and PPP... flash after that flash_sboot_v2.zip
6.at reboot in clk choose boot sboot Wink

Could you claryfi that and tel me Why i dont get 3G working

@ tytung
Hi, I think the only problem I could find that was in version 2.2 is also true that sometimes displays a message that you need to restart your phone to the mobile phone network to work (data connection). Everything else in the best order, ROM works great. The user NativeSD.

I would still ask whether it pays to turn on "GPU Rendering" and "CPU Rendering" in this topic: Disable CPU Rendering Exactly such a description:

HOW TO
(thanks for the summary to thierry_hd2)

1) MAKE A NAND BACKUP OF YOUR ROM. Just in case something would go wrong

2) To disable CPU rendering the ONLY things to do are:
- with a file manager with root access go to system/lib/eg
- open the file egl.cfg. DELETE everything inside the file but keep this line: 0 1 adreno200
- rename libGLES_android.so from egl folder. Don't delete it so if there is an issue with your ROM you can revert back to this file.
- REBOOT

BTW. CYANOGENMOD 10.1 Stable Released

jerry608 wrote:The 2.3 version seems to have a problem with the keyboard light, and the issue was not found in the previous version. the keyboard light is lighted when I touch the screen each time. any helps?
Thanks！

It was fixed since v2.1.
Please check the value of /sys/class/leds/button-backlight/brightness. It should be 0.

Code: Select all

adb shell cat /sys/class/leds/button-backlight/brightness


Changelog
V2.1 (Apr. 21, 2013)

• Added the script to turn off the button backlight (Credit: zain0300)
• ......

Santiago94 wrote:@ tytung
Hi, I think the only problem I could find that was in version 2.2 is also true that sometimes displays a message that you need to restart your phone to the mobile phone network to work (data connection). Everything else in the best order, ROM works great. The user NativeSD.

I would still ask whether it pays to turn on "GPU Rendering" and "CPU Rendering" in this topic: Disable CPU Rendering Exactly such a description:

HOW TO
(thanks for the summary to thierry_hd2)

1) MAKE A NAND BACKUP OF YOUR ROM. Just in case something would go wrong

2) To disable CPU rendering the ONLY things to do are:
- with a file manager with root access go to system/lib/eg
- open the file egl.cfg. DELETE everything inside the file but keep this line: 0 1 adreno200
- rename libGLES_android.so from egl folder. Don't delete it so if there is an issue with your ROM you can revert back to this file.
- REBOOT

BTW. CYANOGENMOD 10.1 Stable Released

It seems the message is caused by your SIM card or your mobile carrier. Old SIM card?
I never get that message. I can switch between WiFi and 3G smoothly. I'm using NativeSD and MAGLDR with RMNET.

I never try to disable CPU rendering, so I cannot comment if it's useful or not.

We're lucky to have the last RC5 (built on June 23) before the stable version released on June 24.
Don't worry. There's not big source code changes on June 24.
You can edit build.prop to update 10.1.0-RC5-leo to 10.1.0-leo yourself.

marco.palumbi wrote:hi tytung,

did you read this post on xda?

http://forum.xda-developers.com/showpos ... count=1970


in the log that I posted i found suspicous the colon in font of bt-pan in this line

E/Tethering( 353): Tried to Tether an unknown iface :bt-pan, ignoring

any way to fix it?

In config.xml (source code overlay for framework-res.apk), config_tether_bluetooth_regexs is set to bnep.
I don't know where to check bt-pan so far.

Code: Select all

    <!-- List of regexpressions describing the interface (if any) that represent tetherable
         USB interfaces.  If the device doesn't want to support tething over USB this should
         be empty.  An example would be "usb.*" -->
    <string-array translatable="false" name="config_tether_usb_regexs">
        <item>"usb0"</item>
    </string-array>

    <!-- List of regexpressions describing the interface (if any) that represent tetherable
         Wifi interfaces.  If the device doesn't want to support tethering over Wifi this
         should be empty.  An example would be "softap.*" -->
    <string-array translatable="false" name="config_tether_wifi_regexs">
        <item>"wl0.1"</item>
    </string-array>

    <!-- List of regexpressions describing the interface (if any) that represent tetherable
         bluetooth interfaces. If the device doesn't want to support tethering over bluetooth this
         should be empty. -->
    <string-array translatable="false" name="config_tether_bluetooth_regexs">
        <item>"bnep\\d"</item>   
    </string-array>

    <!-- Array of ConnectivityManager.TYPE_xxxx values allowable for tethering -->
    <!-- Common options are [1, 4] for TYPE_WIFI and TYPE_MOBILE_DUN or
    <!== [0,1,5,7] for TYPE_MOBILE, TYPE_WIFI, TYPE_MOBILE_HIPRI and TYPE_BLUETOOTH -->
    <integer-array translatable="false" name="config_tether_upstream_types">
        <item>0</item>
        <item>1</item>
        <item>5</item>
        <item>7</item>
    </integer-array>


hi,

i was able to catch a logcat from phone not waking up from suspend it may point to something:

Code: Select all

I/dalvikvm(11343): Turning on JNI app bug workarounds for target SDK version 8...
E/Trace   (11343): error opening trace file: No such file or directory (2)
I/PowerManagerService(  360): Going to sleep by user request...
I/ActivityManager(  360): Process com.google.android.apps.uploader (pid 11281) has died.
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
D/YouTube MDX(11299): Recieved intent android.intent.action.SCREEN_OFF
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/ActivityManager(  360): Start proc com.google.android.gsf.login for service com.google.android.gsf.login/com.google.android.gsf.loginservice.GoogleLoginService: pid=11359 uid=10019 gids={50019, 3003, 1007, 1028, 1015, 1006, 2001, 3006}
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
E/Trace   (11359): error opening trace file: No such file or directory (2)
D/AK8973  (   88): Compass CLOSE
I/lights  (  360): battery_level_check: done with thread
D/AK8973  (   88): Compass Start
I/PowerManagerService(  360): Waking up from sleep...
D/PhoneUtils(  544): hangup(): no active call to hang up
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/WindowManager(  360): Lock screen displayed!
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
D/dalvikvm(  435): GC_FOR_ALLOC freed 335K, 15% free 9525K/11176K, paused 49ms, total 51ms
D/YouTube MDX(11299): Recieved intent android.intent.action.SCREEN_ON
D/PhoneUtils(  544): hangup(): no active call to hang up
I/PowerManagerService(  360): Going to sleep by user request...
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
D/YouTube MDX(11299): Recieved intent android.intent.action.SCREEN_OFF
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
D/dalvikvm(  360): GC_CONCURRENT freed 1921K, 14% free 15132K/17576K, paused 15ms+19ms, total 224ms
D/dalvikvm(  360): WAIT_FOR_CONCURRENT_GC blocked 101ms
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/Choreographer(  360): Skipped 32 frames!  The application may be doing too much work on its main thread.
D/AK8973  (   88): Compass CLOSE
D/AK8973  (   88): Compass Start
D/PhoneUtils(  544): hangup(): no active call to hang up
I/PowerManagerService(  360): Waking up from sleep...
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
I/WindowManager(  360): Lock screen displayed!
I/keystore(   87): uid: 1000 action: z -> 7 state: 1 -> 1 retry: 4
D/YouTube MDX(11299): Recieved intent android.intent.action.SCREEN_ON

it's 4 times trying to wake up the phone

have got this problem since a week once to three times a day...

never had it before going to correct some errors in sdcard and report back

and the black screen at incoming call is also still present from time to time but wasn't able to catch a logcat yet...

all the best

Hi, thanks Tytung for your hard work on this great rom
I have a small issue that is not important but annoying
when i have both softkey landscape mod and soft power button on, on land scape they overlap
the spacing between the soft buttons is large and the last button and the power button are over each other
i have 5 soft keys and the power is the most right.
thanks again.

tytung wrote:
It seems the message is caused by your SIM card or your mobile carrier. Old SIM card?
I never get that message. I can switch between WiFi and 3G smoothly. I'm using NativeSD and MAGLDR with RMNET.

I never try to disable CPU rendering, so I cannot comment if it's useful or not.

We're lucky to have the last RC5 (built on June 23) before the stable version released on June 24.
Don't worry. There's not big source code changes on June 24.
You can edit build.prop to update 10.1.0-RC5-leo to 10.1.0-leo yourself.

Hmm .. in what sense the old SIM card? . I got it maybe a year maybe less, can the SIM card, make a micro-SIM, so rather it is the new standard. I do not know what could be the problem. Thanks for the reply TSAI