yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Bas2ct:
No tilt -->NexusHD2-Gingerbread V2.6 [Android2.3.3][Kernel:tytung_r9]

Tytung, I want to thank you for your great work!!

However, I encountered the same problem I had with your last ROM (2.5).

My gyro sensor is either not recognized, or not supported.

WM works with it like a charm, Android doesn't even recognize it (or at least, I think that is it).

So I tried to find as much info as I could find, to no suffice yet. I do have the idea it is a driver issue more than anything else, but I don't have the slightest idea to fix it.

I did manage to get some info from the flash sequence, full of errors when it comes to the initialization of the drivers for the g-sensor (or at least, that's what I think it says). I'm not familiar with this kind of code. I did program a little bit in the past, but my skills are quite low and the languages I used are old (Basic, html and Step 7).

Log:

[ 2.857635] AKM8973 compass driver: init

[ 2.857757] msm_i2c msm_i2c.0: error, status c8 (1C)

[ 2.857818] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.867950] msm_i2c msm_i2c.0: error, status 43c8 (1C)

[ 2.868011] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.878051] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.878112] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.888153] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.888183] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.898223] msm_hsusb_phy_reset

[ 2.898254] msm_i2c msm_i2c.0: error, status c8 (1C)

[ 2.898345] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.908416] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.908447] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.918518] msm_i2c msm_i2c.0: error, status 43c8 (1C)

[ 2.918579] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.928619] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.928680] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.938720] msm_i2c msm_i2c.0: error, status 63c8 (1C)

[ 2.938751] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.948822] msm_i2c msm_i2c.0: error, status 83c8 (1C)

[ 2.948852] msm_i2c msm_i2c.0: Error during data xfer (-5) (1C)

[ 2.958862] AKI2C_TxData retry over 10

[ 2.958892] AKM8973 akm8973_probe: set power down mode error

[ 2.958953] akm8973: probe of 0-001c failed with error -5

After that it continues initializing other components and I couldn't find anything else what looks like the g-sensor. I've got the complete log, so if you need more info, I'll post it.

This is where I start thinking it must be a driver issue. It looks like the driver can't find the device it is looking for, but why? Is it set for the right addresses? what are the right addresses in that case?

If the addresses are fixed for every device (which seem quite logical to me), it is probably looking for another device or reaction. Since I don't know what the messages mean, I can't really figure out what the problem is.

Does you have any documentation or ideas / knowledge to share with me so I can solve this thing?

Thanks in advance!

Best regards,

Bas
[HD2 Android NAND Development] uxu:
Perfect! Works
[HD2 Android NAND Development] darkanubispr:
I already asked but no response
[HD2 Android NAND Development] darkanubispr:
I need the same but for bluetooth headsets
[HD2 Android NAND Development] 05081983:
Can anyone explain me whats the difference between CLK method and CWM method for flashing? And why are there two methods for flashing, I mean whats the advantages and disadvantages of CLK and CWM. And which one should we use, and what are the points to be considered when choosing between two.
[HD2 Android NAND Development] OCedHrt:
CLK is an alternative to MAGLDR. They both use CWM.
[HD2 Android NAND Development] hd2k10:
My camera isn't working on this build. If I try to run the default camera I get

"Cannot connect to camera."

And if I flash the MIUI camera I get the error

"The application Camera (process com.miui.camera) has stopped unexpectedly. Please try again."

I read somewhere about disabled Audible Touch Tones but that hasn't helped.
[HD2 Android NAND Development] 05081983:
Thank you, but can you please explain to me whats the difference between MAGLDR and CLk
[HD2 Android NAND Development] louie317:
With cLK = ppp data (fast but unstable), like native android boot, OTA with use of ROM Manager.

With MagLdr = RMNET data (slower but stable).
[HD2 Android NAND Development] mjordan79:
I have installed this wonderful ROM. I have partitioned my SD card with 1 primary FAT32 partition (14GB), 1 primary EXT3 partition for apps (1GB) and 1 primary Linux Swap partition (500MB) for swap. I have flashed Apps2SD+.

Where can I see if it's working correctly? I can't find any option in Android to verify the system is using that 1GB partition for apps.

Is it an automatic thing? I mean, I install an application and that application goes automatically on the SD card? I'm a little bit confused about this thing...

Thanks for the replies.
[HD2 Android NAND Development] primus123:
So guys.I haven't done any of the updates. Is it worth it. I have been so busy with school and work I haven't had the time to read here. Bit.I've seen that alot of posts seem to have problems...I'm running v2.2 android 2.3.2... any suggestions..I just did a backup..also will backup restore apps?

sent from my USTMO HD2 android gingerbread
[HD2 Android NAND Development] Capt.PP:
Install Apps2SD+ after your internal storage under 30MB left. If you install it before using any of the internal storage then it will only add 195MB from SD for apps storage. In another word, Apps2SD+ only adds 195MB after using up most of your internal storage.

cLK

There are apps that consumes more power than others. But you shouldn't have over -20mA per 5 mins on standby. If you do, then you must have miss some steps during installation. Back up everything using titanium backup. Then tell me step by step in your own word of your installing process.

Use titanium backup in the market. Back up everything before updating the kernel or the whole ROM.
[HD2 Android NAND Development] czacha234:
Hiya,

To check, is it working or not, type in terminal:

su
a2sd check

And should get something like that
[HD2 Android NAND Development] svet-am:
I can second the issues with bluetooth headsets. I'm working on grabbing a logcat right now...
[HD2 Android NAND Development] svet-am:
i just did a test so I could capture a logcat and miraculously it worked this time -- go figure.

I _did_ reboot so I don't know if that had anything to do with it. I've attached the logcat anyway.

due to attachment file size limitations, I trimmed some data from the beginning of the log. looking through it I don't think any of it is relevant to this. let me know if there's data you need and I'll track it down.

as an aside, I've had this issue with multiple ROMs and all of them have the common theme of being recently update to the tytung_r9 kernel.
[HD2 Android NAND Development] mjordan79:
Thanks for the reply. It's The first time I use Android so ... which terminal?
[HD2 Android NAND Development] michie:
Battery drain

Is it normal that the battery drains alot faster than the froyo build ?

I tried to flash it 3 times but it stays the same, (Radio 2.15.50.14).

3 days on froyo regular use = max 2 days on gingerbread almost no use.

bluetooth, location,... turned off, only internet connection is always on.
[HD2 Android NAND Development] wasi1971:
I have done the update from 2.5 to 2.6 without "wipe data/factory reset" and it works very well. Until now I have found no problems. Thanks for the great job.

Questions: Tytung has released the new CWM 3.0.2.4 for the NexusHD2 yesterday. Currently I have installed the older version 3.0.0.5. Is it possible to update the CWM on the phone without loss of any data? And is it possible to integrate the "Homezone"-function (shows a little symbol in the status bar upper left, when the phone is in this zone) in the rom? Or if it's already integrated, where can this function be found and activated.

Many thanks, especially to Tytung, for the great work.
[HD2 Android NAND Development] T-Macgnolia:
Ok I noticed it is not Specified with either the MAGLDR instructions or the cLK instructions that the ROM download is not bootloader specific for MAGLDR or cLK. I also noticed that both download links say the file is the same size 82.03 MB and that both links seem to take you to the same place.

So my question is this those this mean the kernel of this ROM is compatible with cLK and MAGLDR, and it is up to the user what bootloader they want to use?

Edit: Never Mind I just seen in the change log that it does support MAGLDR and cLK awesome one download for both.

Also sense you can use cLK on the ROM does it allow charging while off?

Thanks in advance.
[HD2 Android NAND Development] eseregin:
----

Originally Posted by eseregin

There is a problem with Bluetooth headset. If you use voice dialing with Bluetooth headset, speak to people, after disconnect headset - internal speaker wont work till reboot.

Does anybody has the same problem and is there any suggestion to solve it?

Last kernel tytung_r9

-----

Yes, i have now, please could you have a look at it?

Thank you in advance! :-)
[HD2 Android NAND Development] jer0en72:
Any one else having a major battery drain after the update? I used to get a whole day of use (easy) before the update but now I can almost see it draining... First I thought it was the (so much hated, by me anyway) percentage in the battery icon but that is not the case....
[HD2 Android NAND Development] torquadon:
I do not think that camera is a build problem. On my HD2 it works just fine.
[HD2 Android NAND Development] stuntdouble:
Was it you who came from windows mobile to android? If so, you should know that the HD2 will never have as good battery life with android on it, as it did with WM. Google mentioned a long time ago that android is meant to go for a full day before needing a charge (moderate to high use).

If you dont even get a full day out of your battery, then you either have an old/faulty battery, or its most likely something simple you are overlooking. Maybe you have set the screen brightness up high? The screen drains the most power out of anything. Mine drains about 150-220mA when on. On 2G standby with nothing else on it's 2-7mA. There are always fluctuations when a background process runs itself.

I dont know what your battery drain problem may be, it's up to you to keep monitoring your device daily, which it sounds like you are doing, and fixing it yourself. Constantly posting that you cant fix your battery drain isn't going to help you. If you have the 'battery monitor widget' app free from the market, it lets you see the battery drain history.

Good luck.
[HD2 Android NAND Development] kackburt:
I never used tytungs froyo package, but a maximum of 2 days is normal in gingerbread, at least for me it is... 3G drains a lot actually, airplane mode gives me power for a week though (:
[HD2 Android NAND Development] uxu:
No.

Just backup the hole ROM with CWM. After updating CWM restore the ROM with CWM. That worked for me and it's done in a few minutes :)
[HD2 Android NAND Development] eseregin:
Cannot agree with it, cause as i found, with the same load new enough versions of Android consume LESS power when last ROMs on WinMo 6.5 (Duttys ROM).

So under load imho Android has better battery life.
[HD2 Android NAND Development] cdrov:
Yes i came from WM but i had more than 2 days stand by, while now i don't even have one. The problem is that i am measuring consumption from the instalation yesterday. At first there were cases where the mobile was ok but after a few calls, open and close my location, AGPS data now i think it has stuck on high drain. I attach the battery log

Regards
[HD2 Android NAND Development] stuntdouble:
Yup but duttys rom was never very good for battery consumption. I was basing what I said off stock wm 6.5.3 with stock radio.

All I've noticed odd with your log is your battery seems to get very hot. But maybe you live in a hot country or something idk.
[HD2 Android NAND Development] cdrov:
I live in Greece. At this time it has 20oC. Despite that do you think that the rest of the log is normal? it seems that the consumption is around 200mA (i have it in front of me). What applications could do that?
[HD2 Android NAND Development] pradeep.indalkar:
good, but I love stock romes
[HD2 Android NAND Development] stuntdouble:
The screen being on. Rest of log looks normal for a device stabilising itself after an initial install. It should settle after a day or two of installing all apps.
[HD2 Android NAND Development] arned:
This is related to the wizzard. I had the same problem. If you have the setup wizzard (google account etc.) in background, home and caller button won't work. Close wizzard and it works again :)

Thanks for release
[HD2 Android NAND Development] michie:
I noticed that screen consumption varies from time to time with brightness on locked level. (varies from 35% to even 75%).

And mobile stand-by uses more battery than the froyo build.

Anyway, im happy with android on my HD2 so i'll just have to get used to recharging every 1-2days :)
[HD2 Android NAND Development] chimpsinties:
Was working fine on 2.5 so just downloaded 2.6 and tried to flash it over the top. Now the phone gets to HTC screen and hangs.

I tried wipe to factory reset and wipe cache, then reflash 2.6 but still the same :confused:

Any ideas/suggestions?

Edit:

Looks like it's a problem with my backup. When I try and restore it says "Checking MD5 sums"... MD5 sums mismatch.

Damn! I'm going to have to go to a previous backup from 20+ days ago :eek:

I wonder why the backup didn't work all of a sudden. I've never had a problem with backup/restore before.
[HD2 Android NAND Development] mikegee:
Excellent rom so far! Only minor bug identified is that when language is set to English (UK) the Turn On - Turn Off USB mass storage buttons appear to be the same! In English (US) this issue doesnt exist. Pongsters GBX had the same issue a couple of versions ago and he fixed it later.

Thank you tytung :)
[HD2 Android NAND Development] svet-am:
in terms of the Bluetooth headset issue, it's not a simple matter of working or not working because it is partially working. here's how the failure happens for me.:

1) enable bluetooth on the HD2 -- this goes okay

2) pair the bluetooth headset with the HD2 -- this goes okay

3) press the talk button the HD2 to activate Android voice commands -- this goes okay

4) Android interprets my command and launches the dialer -- this goes okay

5) dialer calls intended recipient -- the dialer either FCs or the device locks up (requiring power cycle)

This sequence of events _only_ happens with a bluetooth headset connected. I can make regular calls all day long with no problems.
[HD2 Android NAND Development] eseregin:
Might be you tell us what you used those times?

For example if you were watching movie and had 200 mA - it is great result, is not it? 8-)

If you were using Wifi and surfing inet - very good as well, cause 5-6 hours of such kinds of activities on our device - not bad at all i think
[HD2 Android NAND Development] tytung:
Do you mean this log is recorded under the situation of everything working?

I think I need a log including your BT headset happened the sound error?

Besides, it's better to explain your log shortly.

For example:

line xxx, time, message, [your explanation]

line 879, 04-13 21:32:44.525 I/power (97): *** set_screen_state 0 [screen off]

Or at least what you're doing step by step when you have this log.

Thanks.
[HD2 Android NAND Development] tytung:
You can use adb tool to type the commands.

If your PC is Windows, please download cLK_1.4_CWM_Recovery_v3.0.2.4.zip to get android-sdk-windows-lite folder.

Click Start, point to Programs, point to Accessories, and then click Command Prompt.

At the command prompt, type the following line, and then press ENTER to enter the Android terminal:

cd D:\android-sdk-windows-lite
adb shell

Then type a2sd check.
[HD2 Android NAND Development] tytung:
Backup your ROM from CWM 3.0.0.5.

Install CWM 3.0.2.4.

Restore your backup ROM from CWM 3.0.2.4.

Then you won't lose any data.

AOSP doesn't support "Homezone"-function, and I don't know what it is.
[HD2 Android NAND Development] tytung:
Yes, cLK and MAGLDR use the same ROM, but they have different boot partition format.

MAGLDR uses YAFFS boot format while cLK uses RAW boot format.

The ROM includes the data of YAFFS boot format by default.

So you need to additionally flash cLK_ppp_tytung_r9_update.zip (RAW boot format and some ppp stuff) when your bootloader is cLK.

Only cLK supports offmode charging.
[HD2 Android NAND Development] tytung:
Does your used ROM include iamgpc's robot voice fix?

That file libaudio.so not only fixes robot voice but also fixes some sound problems.

I'm wondering if this issue is related to ROM or kernel.

Did you ever use my v2.6 ROM, including libaudio.so fix, and have the same issue?
[HD2 Android NAND Development] tytung:
You can search "MD5 sums mismatch" in CWM thread.

I ever saw the similar issue and someone gave the solution in CWM thread.
[HD2 Android NAND Development] tytung:
Well, that means the source code of AOSP used by Nexus One and Nexus S is wrong.

I think the official Nexus One and Nexus S ROM will have the same problem.
[HD2 Android NAND Development] chimpsinties:
Thanks for the hint tytung, you're the best (did you receive my donation the other week by the way?)

I didn't lose too much going back to my previous backup. Just a couple of apps I had to reinstall and a few texts missing.

Could it be something to do with the change to CWM 3.0.2.4 because I took the opportunity to install that while I had the phone blank.

Also, after upgrading to 2.6 and restoring my previous backup from 20+ days ago I looked at settings and it said v2.2 and oldcam r6. :eek: I then ran the 2.6 zip again from CWM and it now says 2.6 in the settings. Does running a restore write over anything important from the update?
[HD2 Android NAND Development] wasi1971:
Thank you for the information, how I need to do the CWM-update without loosing data.

"Homezone" is used by my provider - Vodafone calls it "Zuhause", O2 calls it "Homezone" here in Germany. This function let the provider know when I'm at home. Therein I have an additional call number, under which I am available. I think it uses the gsm-cells in the radius of 2 kilometers around my home. From this zone I can make calls cheaper. I've seen this in some other android roms. There will be displayed a symbol in the upper left corner, that shows the state. If it's displayed, you are staying in the zone - if not, you aren't therein. The Vodafone WM 6.5 stock rom HD2 has this function also integrated - it displays in the upper right corner "Zuhause". Do you know what I mean?
[HD2 Android NAND Development] primus123:
Camera not working..says cannot connect to camera...

What to do?

sent from my USTMO HD2 android gingerbread
[HD2 Android NAND Development] TommyRose:
Hi from 2.6, thanks for great work

one question.. is possible to set the phone button to open the dialer instead of contacts? not with button savior..
[HD2 Android NAND Development] chimpsinties:
How about DialerOne? http://www.xda-developers.com/android/dialer-one-t9-dialer-for-android/
[HD2 Android NAND Development] primus123:
Not working on mine either.any suggestions

sent from my USTMO HD2 android gingerbread
[HD2 Android NAND Development] chimpsinties:
Camera is fine on mine
[HD2 Android NAND Development] nurseav:
how to install MIUI music ?

when i install .apk the application not install (install unsuccessfull):mad:
[HD2 Android NAND Development] TommyRose:
no i don't need a different dialer.. i want the default one, but..

i would like to set the green phone button to open directly the dialer not the contatcs app

does anyone know a tweak to do it?

thks
[HD2 Android NAND Development] Savag3Vim:
Guide pls

Hi, sorry for asking but i really wanna install this rom.

I have followed the installation Guide for MAGLDR 1.13 seen on the 1st post and installed both MAGLDR 1.13 and the CWM Recovery. I however am stuck on the 3rd step. How do i flash android rom after entering AD recovery

Any help is appreciated.
[HD2 Android NAND Development] mjordan79:
Hello.

You have to copy the ROM zip file on the MicroSD as it is, unmodified.

Then you have to enter the CLW flasher (turning on the phone while pressing the power on button) and you must select the option to flash from the SD card (I don't remember the exact name of the menu but it's straightforward). Select the correct file and the flashing process will start.
[HD2 Android NAND Development] chaozh:
Thanks your good ROM!

But I always meet WIFI diconnect and reconnect issue, it continue repeat these two operation and I can not connect WIFI network. It make me very sad, Do you know why and how to fix it?

Thanks a lot!
[HD2 Android NAND Development] Savag3Vim:
Thanks man
[HD2 Android NAND Development] nbhor:
Wifi Issues

So do I. I most often visit this issue with my phone as well. Also I would like to add another issue where I am able to connect to wifi network but can't browse, while other DELL Streak user can connect and browse.

Fortunately I am able to connect to my home wifi network. But once in for all I would also like to know the solution for this issue as I can not browse at my work location.

Thanks
[HD2 Android NAND Development] tytung:
Yes, I got a donation from you on Mar. 29, 2011.

CWM 3.0.2.4 won't affect MD5.

Restoring a previous backup will mainly replace system partition and data partition and the version number is read from system partition.

Flash v2.6 ROM again will only replace system partition, so your data is retained.
[HD2 Android NAND Development] tytung:
Yes, I see.

But it's obviously a carrier related function, and won't appear in an AOSP ROM.

You need a customized ROM.
[HD2 Android NAND Development] tytung:
Do a clean install.
[HD2 Android NAND Development] tytung:
What?

When I press the phone button, the phone dialer will appear instead of the contacts.
[HD2 Android NAND Development] tytung:
What kind of WiFi network do you have? WPA2? EAP?

If you get any WiFi connection issue, it should be related to your WiFi network environment, not this ROM.
[HD2 Android NAND Development] badai:
one is getting contact, one is getting dialer, and mine will open up call log. :D
[HD2 Android NAND Development] CR5N:
Tried to PM but anyway have a coffee/beer on me to say thanks.

94D482753M2572830
[HD2 Android NAND Development] wasi1971:
Thank you, Tytung.
[HD2 Android NAND Development] nbhor:
Case where I am able to connect to wifi network but cant browse is of WEP encryption.

Case where I am trying to connect to adhoc wifi network (created using WIN7 using http://lifehacker.com/#!5369381/turn-your-windows-7-pc-into-a-wireless-hotspot) and getting stuck at Obtaining IP Address loop, also has WEP encryption. Also tried WPA2/Open here but doesn't help.

Any other suggestions?

Thanks
[HD2 Android NAND Development] milkidou:
I have a problem, many times my gallery hangs, i only have titles of the folders, but no picture and cannot go into the folders, even when i take a photo i cannot see them, many times, turn off and on th ephone and it goes well but donno why???

have you ever meet these problem???

i'm using the mar27 version.

I have to say that it's the first i'm really in love of my HD2 this is the fastest and smothest soft i've ever used, many froyos, WP7 and WM6.5 and sine I use your's i'm in love!!!! thx so much for your work !!!

julien.
[HD2 Android NAND Development] brd912:
please no one bite my head off because i dont know my way around the hd2 forum,but i used the magldr method,the process went good until i went into recovery and flashed the rom,when it restarted magldr tries booting android from nand and its stuck at go

?