NexusHD2 Android Forum

guest__1 wrote:I installed tytungs Android KitKat 4.4.4 & CM-11.0 Mod ROM for HD2 from here. Because I liked his work (NexusHD2-ICS-CM9-HWA_V3.0b) which I had installed before. I decided to reinstall a newer version because my mobiles software was crashing a lot. But after the tytungs KitKat installation the crashes didn't stop, sometimes even the booting of the phone hangs. Also I can see any form of pattern in the crashes, they just happen 1-x times a day.

I tried the suggestion in this thread to pipe the dmesg into a textfile shortly after a phone reboot. With this I couldn't find any bad blocks, but there is one error message that is comming up very often. Could that the reason for the phone crashes?

What is the size of your /system partition and how much free space do you have in /data?

Hi there,

I'm not quiet sure if I got you right NYLimited, I try to answer as good as i can. I use a Samsung 18GB SD-Card Speed 6 in my HD2 and a DataOnExt installation. My PRIMARY FAT32 Partition is 11,09GB with 64 Sectors per Cluster, it has 978,20 MB about 8% in use. My PRIMARY EXT4 Partition is 3.81GB and has 921,06MB about 23% in use. Between both Partitions I left 2MB free and unpartitioned. Checks with MiniTool Partition Wizard Free 9.0 found no bad blocks or write/read errors on both partitions.

Partitions as shown in cLK 1.5.1.1 (name/ blocks/ size in MB):

• recovery/ 40/ 5
• misc/ 8 / 1
• boot/ 40 / 5
• system/ 2600/ 325
• userdata/ 682/ 85
• cache/ 192/ 24

cLK 1.5.1.1 shows in it's main menu KERNEL @ boot [UNDEFINED], but it boots KitKat when it's note hanging up.
Is there a way to see how many space recovery and system use? I couldn't find it, sry.

I also made another dmesg.txt and found not only the "qtaguid: iface_stat: stat_update() lo not found" error. This is what I found. I'm sry I have no clue on these errors what they are.

Code: Select all

<6>[  360.101165] sharp_panel_unblank
<3>[  360.583343] msm_i2c msm_i2c.0: error, status c8 (5C)
<3>[  360.583435] msm_i2c msm_i2c.0: Error during data xfer (-5) (5C)
<3>[  360.583526] msm_i2c msm_i2c.0: error, status c8 (34)
<3>[  360.583618] msm_i2c msm_i2c.0: Error during data xfer (-5) (34)
<6>[  360.584747] [R] late_resume end

guest__1 wrote:I also made another dmesg.txt and found not only the "qtaguid: iface_stat: stat_update() lo not found" error. This is what I found. I'm sry I have no clue on these errors what they are.

Code: Select all

<6>[  360.101165] sharp_panel_unblank
<3>[  360.583343] msm_i2c msm_i2c.0: error, status c8 (5C)
<3>[  360.583435] msm_i2c msm_i2c.0: Error during data xfer (-5) (5C)
<3>[  360.583526] msm_i2c msm_i2c.0: error, status c8 (34)
<3>[  360.583618] msm_i2c msm_i2c.0: Error during data xfer (-5) (34)
<6>[  360.584747] [R] late_resume end

I am not familiar with those errors but I guess thay may be clk related errors. Since I never ran clk you'd have to find answers to that from someone else, sorry.

More importantly, looking at the same log you took the above from, does it show any "block is bad" messages? I am guessing the answer is yes...

guest__1 wrote:I'm not quiet sure if I got you right NYLimited, I try to answer as good as i can. I use a Samsung 18GB SD-Card Speed 6 in my HD2 and a DataOnExt installation. My PRIMARY FAT32 Partition is 11,09GB with 64 Sectors per Cluster, it has 978,20 MB about 8% in use. My PRIMARY EXT4 Partition is 3.81GB and has 921,06MB about 23% in use. Between both Partitions I left 2MB free and unpartitioned. Checks with MiniTool Partition Wizard Free 9.0 found no bad blocks or write/read errors on both partitions.

Partitions as shown in cLK 1.5.1.1 (name/ blocks/ size in MB):

• recovery/ 40/ 5
• misc/ 8 / 1
• boot/ 40 / 5
• system/ 2600/ 325
• userdata/ 682/ 85
• cache/ 192/ 24

1. First and most importantly, try changing the system parameter from above to read at least 400 instead of 325. That may make a very big difference especially if your device has bad blocks. Don't forget that you will also have to adjust the number of blocks specified if clk needs both numbers.
   
2. You may want to consider increasing the size of the recovery partition from 5 to 10. This does not matter for your current problem but it will make it easier to update your custom recovery when you are ready for it. Don't forget that you will also have to adjust the number of blocks specified if clk needs both numbers.
   
3. You are allocating 24 MB to cache but if I recall correctly Tytung's ROMs do not use that partition so you can, if you want to, reduce the size safely. Don't forget that you will also have to adjust the number of blocks specified if clk needs both numbers.

guest__1 wrote:Here is the Pastebin link. As you see there is no BAD BLOCK warning which is the same result that I got from the read/ write check I mentioned.

How old is your HD2? Most HD2s will likely have some bad blocks by now. Technically you do not have to know about the bad blocks. If you are curious you can click "show" below.

Also, which sd card do you have (brand, size, speed and age)?

guest__1 wrote:Should I resize the partitions like you answered in the thread? Are you sure with the numbers? Could you give me a recommendation for all partitiones/ blocks/ size in MB that I posted? Do I have to reinstall everything afterwards?

As noted before I have never personally worked with cLK. However, the partitioning info should be applicable all HD2 setups.

You said you were using DataOnExt installation method. Simply put, that moves your entire /data partition to the sd-card. As a result any space allocated to /data in NAND memory is unused. Because of this you can increase the /system partition to very large without worrying about your data and apps. A large /system partition gives the system a chance to skip over bad blocks without running out of crucial space.

By the way, how big is your /data partition on the sd card? I assume this is an EXT4 partition in good shape and large enough for you needs.

First, make sure you have current Nandroid backup created with a recent version of TWRP or CWM. There are versions of TWRP (but not CWM) which can also backup your data partition from the sd card.

When you repartition the device you WILL WIPE OUT EVERYTHING IN NAND MEMORY (but not the EXT4 partition on the card!). After partitioning you can either install the ROM again (not a bad idea) or restore the system partition from the backup.

Again, your data and apps residing on the EXT4 partition should not have been touched. DO NOT repartition the sd card! This would wipe your data and installed apps!

I would repartition the device as follows:

recovery/ 80/ 10
misc/ 8 / 1
boot/ 56 / 7
system/ 3200/ 400
userdata/ 176/ 22
cache/ 40/ 5



Once repartitioned, you can install the ROM again (a clean install - probably the better choice) or restore the backup of your boot and system partitions.

I don't think anything in here conflicts with cLK requirements but you could try to contact kokotas (he released black cLK for the HD2) although I am not sure often he reads here or on XDA. He certainly should be able to give you more accurate info, if that was needed.

Hi,

The security password for wifi hotspot in "settings/wireless and networks" doesn't work. When I use my HD2 as a wifi hotspot for my tablet, there is no password needed / no security.
That's a problem for me.

Thanks.

jeyjey wrote:The security password for wifi hotspot in "settings/wireless and networks" doesn't work. When I use my HD2 as a wifi hotspot for my tablet, there is no password needed / no security.

I no longer have a working HD2 so don't have an answer for you but, if you cannot get it to work you might want to try Portable WiFi Hotspot which works quite well for me.


----
You can chose to ignore reality, but you cannot ignore the consequences of ignoring reality.

NYLimited wrote:
I no longer have a working HD2 so don't have an answer for you but, if you cannot get it to work you might want to try Portable WiFi Hotspot which works quite well for me.


----
You can chose to ignore reality, but you cannot ignore the consequences of ignoring reality.

It seems that this app works more like a widget so still the same problem.
Thak you in any event for your help.

jeyjey wrote:
It seems that this app works more like a widget so still the same problem.
Thak you in any event for your help.

Not sure what you mean by working like a widget but the hotspot can be configured to work with our without a password which I thought was your issue. The password is set directly through the app and is enforced when connecting.


----
You can chose to ignore reality, but you cannot ignore the consequences of ignoring reality.

NYLimited wrote:
Not sure what you mean by working like a widget but the hotspot can be configured to work with our without a password which I thought was your issue. The password is set directly through the app and is enforced when connecting.


----
You can chose to ignore reality, but you cannot ignore the consequences of ignoring reality.

The problem is that when I set a password with WPA(2)/PSK encryption (native or with portable wifi hotspot app), my wifi hotspot (SSID) appears unsecured and I can connect any other device without any password needed.

I just saw on the first page :

Not Working:

Black screen in the panorama mode of the camera.
Wi-Fi hotspot Security. (Solution: Install WiFi Tether for Root Users 3.x and go to setting to change "Device-Profile" to "Google NexusOne" and select "Enable WiFi-Encryption" and "WiFi-driver reload".)

I will try this app with these settings.