yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] agentfazexx:
I don't get anything that specific, just apps disappearing of of "My Apps" list. Reflashing new versions of this ROM makes them come back, and they slowly disappear again.

Side note, can I take a "snapshot" of the apps I have installed so when I task 29, Google restores everything, not what I downloaded a month ago?
[HD2 Android NAND Development] justeam:
Not true. Check if you have a 1A output on your AC adapter otherwise you will have a high consumption of battery from the screen being turned on.
[HD2 Android NAND Development] agentfazexx:
If it's not true, why did I lose 5% of my batter while driving to work, with the phone plugged into the charger, listening to Pandora?
[HD2 Android NAND Development] justeam:
Let me guess... because you have less than 1A on your car charger's output? ;)
[HD2 Android NAND Development] Denkov:
Charging works fine!
[HD2 Android NAND Development] ph03n!x:
USB charging, and most car chargers are rated 500mA. The stock AC charger is rated 1A (1000mA). However *not charging* in USB or Car with some kind of an activity (Screen on/ playing music/ anything at all) seems weird. I suggest you install CurrentWidget, have it in your home screen and check the current it displays while charging through USB/ Car. It usually shows about 250~300mA for me (as against 750~850mA in AC charging), and still charges the phone if I do not load it much.
[HD2 Android NAND Development] pathologo:
Market is still v3.0.27 ...
[HD2 Android NAND Development] zagzag99:
With 3.6.1 the mic level fix is not working well.

I have a very high background noise.

I can't seem to have /proc/mic_level to manipulate values in.
[HD2 Android NAND Development] Unconn:
Try App Monster. You can take copies of all the user APKs you have installed.

You were using more energy than you were getting.

Car chargers are almost always 500ma or less. That is USB level. Sometimes the USB sign will even come up on the phone. Wall chargers are normally between 800-1000ma.
[HD2 Android NAND Development] Denkov:
No problem with YouTube here! I just uninstalled it and then installed from the Market again - works like a charm!

Everything is done thru WiFi.

Another application for testing?
[HD2 Android NAND Development] agentfazexx:
Thanks. I'm talking about the auto-restore from Google. I get all kinds of apps restoring that I installed/uninstalled a while ago, and tons of apps that don't restore at all, it's like Google has an old image or something.
[HD2 Android NAND Development] agentfazexx:
No it's not, it's 3.1.3. Just checked on my phone.
[HD2 Android NAND Development] gokkko:
Mic level

Same problem here.
[HD2 Android NAND Development] ccristal:
3.6.1 MAGLDR doesn't boot up for me. It gets stuck at the Android logo and never gets to the boot animation. I have also tried cleaning cache and Dalvik cache, same result. Any idea?

ccristal
[HD2 Android NAND Development] agentfazexx:
As with any issue like this, task 29 and start over.
[HD2 Android NAND Development] Unconn:
I hear this a lot and have never had to task 29 my phone. I think it is just an easy-out as the user will have to re-install everything and if they get it right this time it will work. There is probably another problem (user data, kernel, wrong ROM cLK/MAGLDR, bad blocks...).

When you get a flat tire do you just buy a new car?
[HD2 Android NAND Development] agentfazexx:
Well, not like there's a safe mode to boot into in Android like there is in Windows. What should he do?
[HD2 Android NAND Development] tmihai20:
The checksums for the new zips are not like the ones in the OP. Mine are (I have used 4 mirrors out of the 5 available):

a22258bf186ad5e15ea7321813adbf16 TyphooN_CM7_v3.6.1-cLK.zip

ab48877232fbd91723723059e017d5d2 TyphooN_CM7_v3.6.1-MAGLDR.zip
[HD2 Android NAND Development] pathologo:
Yea, my phone is also charging fine via USB when the screen is off.....

No, the market is really v3.0.27 - at least for the cLK ROM.

I just downloaded the new ROM (cLK) from the mirrors 1, 2, 3, 4 and the Vending.apk is the very same file as in the former ROM versions - byte compared.

Also the application manager is showing "version 3.0.27" for Market..
[HD2 Android NAND Development] agentfazexx:
Oh, can't speak for cLK. I'm using magldr, and I have 3.1.3.

You can download it yourself here... http://www.androidguys.com/2011/08/23/android-market-313-adds-pin-security-google-1/
[HD2 Android NAND Development] tyween:
/proc/mic_level is included. Just verified. What partition size are you on?

I also think you guys are right. I am on cLK and see 3.0.27 for market. Will address this in the next version.
[HD2 Android NAND Development] tmotard:
Perhaps the partition size ???
[HD2 Android NAND Development] ccristal:
Yeah, that's the way... :rolleyes:

I have re-installed 3.6.0 and it runs just fine.
[HD2 Android NAND Development] tyween:
Ah.. I remember what happened. I put the MD5SUM in the OP.. then had to repackage the files due to forgetting the correct kernel zImage. Updating OP with proper MD5SUM. Thank you for bringing this to my attention.
[HD2 Android NAND Development] ccristal:
Thank you, tmotard, but I have not changed partition sizes for a long time. It's set to 150/5.

I don't think it needs to be modified for 3.6.1, does it?
[HD2 Android NAND Development] gokkko:
partition size is 160/5
[HD2 Android NAND Development] tyween:
Is tytung's kernel r12b1 installed? Check in the about phone menu please.
[HD2 Android NAND Development] matthew9mm:
Check out the "Brightness Level " widget from curvefish. It works great for me.
[HD2 Android NAND Development] Puppetmaster_sr:
My market shows 3.1.3 (on clk..downloaded from third mirror)
[HD2 Android NAND Development] tmihai20:
I installed MAGLDR version from mirror 4, I also have Market 3.0.27 (this is the version I see in Applications). The kernel is Tytung r12b1. 150 MB for system should be enough (well have only 137 MB occupied).
[HD2 Android NAND Development] tmotard:
148 MB occupied with jw kernel here...
[HD2 Android NAND Development] tyween:
I will investigate the Market version issue on next release, for now if you do not have v3.1.3 you can update manually through the links that have been supplied in previous posts. I am a little baffled at why everyone would not have /proc/mic_level. The proper levels should be set by tytung's init.d script as well.
[HD2 Android NAND Development] zagzag99:
@Tyween, I take it back, it was a problem with the package, I downloaded from another mirror and it works fine.

Could be that the mirrors didn't sync on time when you repacked the rom with the correct zImage

Many thanks.
[HD2 Android NAND Development] rabosa616:
I installed MAGLDR version from mirror 1, I also have Market 3.0.27
[HD2 Android NAND Development] rigosj:
I get an error: signature verification failed. Installation aborted. What now!
[HD2 Android NAND Development] agentfazexx:
Try another mirror. The file sounds corrupt.
[HD2 Android NAND Development] Tak3r07:
Same here. This is CLK mirror 4.
[HD2 Android NAND Development] L_o_k_i:
No problem for me here! I'm on MAGLDR:

HANDSET (0): 200

SPKR_PHONE (1): 600

HEADSET (2): -1

TTY_HEADSET (3): -1

BT_SCO (4): -1
[HD2 Android NAND Development] SlyRder83:
so the partition size is 160/5 now? Its 150/5 in the OP
[HD2 Android NAND Development] clyder:
copy the 10miclevel file to folder where adb.exe is and type:

adb push 10mic_level /system/etc/init.d

adb chmod 750 /system/etc/init.d/10miclevel (not sure if this is needed)

BTW, I modified the file in root explorer without problems.
[HD2 Android NAND Development] windroidHD:
your car battery is on it's way out?. car chargers from my experience can always give out 1A, they even heat up the damn device.
[HD2 Android NAND Development] agentfazexx:
Second time I heard that today...the other time was when I was talking to somebody about these sensor issues my car keeps having...
[HD2 Android NAND Development] mknewman:
I tried that widget, it does work and allowed me to lower the levels to virtually nothing, but had a huge impact on battery usage for the negative. Once I had it installed I could almost watch my battery level drop. 10% per hour or more. I took it out and stopped having problems. I may play with it again though.

My reason for posting this is nochellis's fix and this are only band-aids, there should be a fix to the lights file that doesn't break notifications to fix screen brightness, and not have to run an external program to get it to work. I'm not asking so much, heck, if I knew C well enough I'd help but I'm not a coder. I just wanted to make sure this didn't get forgotten.

Thanks,

Marc
[HD2 Android NAND Development] 10507:
It could also be the car's alternator. Its not giving any charge to your car's battery. You should go to AUTOZONE, or any auto part shop and have your car diagnose.
[HD2 Android NAND Development] agentfazexx:
Maybe, but the phone charges with the screen off...same with the laptop. Maybe it's my phone... If it were the battery or alternator, the car would be slower to start, which it isn't.
[HD2 Android NAND Development] tmihai20:
I just spoke with my girlfriend on the phone and she said she could barely hear me. I changed the values on the init.d script to 0 400 and 1 800 instead of 0 200 and 1 600. I hope the other people will be able to hear me better.
[HD2 Android NAND Development] tyween:
Let me know your results. I have not played with the values, just used what came stock with tytung's beta kernel.
[HD2 Android NAND Development] jolas:
Changed first line from 200 to 400, but the other party can't hear me well...
[HD2 Android NAND Development] mrbr0wn:
Insane battery draining for me,and also graphic lags in the launcher

Sent from my HTC HD2
[HD2 Android NAND Development] dmunseyautotech:
wifi signal

I'm getting a really week wifi signal since upgrade to 3.6.1. were before it was excellent now it's poor.
[HD2 Android NAND Development] gokkko:
I think 150 is fine, I use 160 because I sometimes switch to MIUI rom.
[HD2 Android NAND Development] tyween:
It looks like we may have to switch back to tytung r11 kernel until the "Mic Fix" is tweaked, or find better levels to use.
[HD2 Android NAND Development] gokkko:
Yes, it is, I checked.
[HD2 Android NAND Development] jolas:
Changed back to 200 and tested again with same.

Something really strange I noticed in both cases (first line 0 to 200 or 0 to 400), is that when phone convertation started was very clear for both parts (I think was better with the value of 200).

But when I changed the 'In Call' volume (in both cases), then imediately the other party lost my voice almost complete with the value of 400, and in the case of 200 my voice was very very weak :confused:
[HD2 Android NAND Development] tyween:
Please post any "Mic Fix" related information in this thread: http://xdaforums.com/showthread.php?t=1162224

I think it would greatly help those who are working on this issue.
[HD2 Android NAND Development] clyder:
I dont have any issues with r12b kernel. Mic fix works for me. I only had to change levels to 350/600. Default value of 200 is way to low for me. 400 is much louder but for my taste maybe a bit too loud and litlle distorted. 350 works nice for me.

I already posted this to mic fix thread, just wanted to share my experience here as well.
[HD2 Android NAND Development] Denkov:
Same here with 400/700! Works perfect!
[HD2 Android NAND Development] TheInVisibleGoD:
In case someone is interested in Tablet Tweaks + cLK tether fix for Nightly 181...

http://xdaforums.com/showpost.php?p=17124060&postcount=232
[HD2 Android NAND Development] Unconn:
I prefer troubleshooting and learning. Sometimes the first step is trying to reverse the last step that caused the problem.

Don't get me wrong, Task 29 might fix it, but he also may take the same steps end end up where he is now.

More troubleshooting: If it is the image before MAGLDR, then the bootloader is probably corrupted. If it is the image after (but before moving image) then it could be the kernel, corrupt boot.img, bad info userdata...
[HD2 Android NAND Development] lihkin:
after looking at 3.6.1 review i clean installed 3.6.0 and I wish to know is there any problem with the wifi for version 3.6.0 as it is very slow when wifi is left on it own to download something?
[HD2 Android NAND Development] eseregin:
The same, no problems
[HD2 Android NAND Development] eseregin:
800 too high level, will be some echo and noise probably...

Thought let us know the result :-)

600 imho big enoutgh.
[HD2 Android NAND Development] tyween:
Maybe 400/700 default will make it's way into the next version. I have not had the time to test any values myself as I am at work. But 350 also seems promising ;) Thanks everyone for the testing thus far.
[HD2 Android NAND Development] lihkin:
Hello any1 out there who is facing WIFI problem with 3.6.0 plz help
[HD2 Android NAND Development] Magic2010:
I'm having problems with the 3.6.1 version, the connection drops all the time.

And people don't hear me talking when they call....
[HD2 Android NAND Development] Tiger22:
Thankyou...it works GREAT :)

Tiger22
[HD2 Android NAND Development] tmihai20:
I have tested with 500/600 and it looks ok. I have also modified the init.d script to have 600/600 values.
[HD2 Android NAND Development] Zythyr:
I am using v3.6.0. Since yesterday, my phone automatically turns on the speaker everytime I make a phone call. Why i this happening? How do i fix it?
[HD2 Android NAND Development] themadproducer:
A few days ago, I was plugged into my car charger and navigating and it was not charging. Never had that happen before. I get 800ma charge rate normally. (minus what I am drawing) I think it was just a one time glitch since the next time I tried it it worked fine.
[HD2 Android NAND Development] tyween:
This could be a case of the car charger not being plugged in firmly.
[HD2 Android NAND Development] pringaguardias:
Micro volume problem

I upgraded to 3.6.1. I don´t know if anyone has had this problem. The microphone volume is very low. Forgive me if this problem has been discussed already, but I have difficulties with language. thanks:confused:
[HD2 Android NAND Development] louj:
Microphone volume dropped down

Yes. I have the same problem. I updated from 3.6.0 to 3.6.1 and suddenly I can hear other site very well, but they can´t hear me very good or they can´t hear me at all. They can hear me only for first 1-2 seconds then the microphone volume suddenly drop down to almost 0. No any clicking or cracking sound is appearing during this volume drop down.
[HD2 Android NAND Development] pringaguardias:
Any solution?:confused:
[HD2 Android NAND Development] louj:
I tried few reboots, wiping, but nothing helped. Then I downgrade back to 3.6.0 and everything is fine again. So I assume there is some small bug causing it.
[HD2 Android NAND Development] SecrtAgentMan:
Hey guys downloaded this ROM and I noticed that the notification bar is somewhat blurry and not very sharp. Is there anyway to change it and somehow get a number value for the battery?
[HD2 Android NAND Development] agentfazexx:
Regarding the battery percentage, dizzle put out his framework a while back. Search the thread for it.

Notification bar blurry???
[HD2 Android NAND Development] SecrtAgentMan:
Yeah the black bar at the top with the battery and network icon just doesn't seem very clear to me
[HD2 Android NAND Development] agentfazexx:
Not sure I've ever heard of that issue before. Try throwing "blurry notification bar" into the search field, without quotes.

Could be your screen. Try cleaning it.
[HD2 Android NAND Development] Synizta:
hello kinda new to site was wondering if someone can post all the issues with 3.6.1 all on one post please so i can have a heads up as to what im in for. right now im on 3.5.5 cause apps dont seem to pop up on market on 3.5.6-3.6.0 for me. i havent tweaked a thing just installed apps i wanted. ty guys for your time
[HD2 Android NAND Development] timekeeper:
Same issue here with 3.6.0. I'm assuming it still exists in 3.6.1?
[HD2 Android NAND Development] agentfazexx:
Post all of the issues??? Read back from this morning to now, it's only a couple pages. Issues pop up at random so you won't get everything.
[HD2 Android NAND Development] SecrtAgentMan:
I did change the LCD Density to 200 since text/icons looked too big for me, I think that's the issue.
[HD2 Android NAND Development] agentfazexx:
Use 220, or 167.
[HD2 Android NAND Development] noellenchris:
I tried to get several DEV's to work on this issue, I've even tried to compare the two files and honestly I don't know how to combine them. If you can find a DEV to work on that file and get it fixed that would huge. I've last tried this almost a year ago. Maybe it's just too hard, but believe me, I've tried to get help and gave up. The file I provided actually came from Gauner I think from his git work summer of 2010, IamGPC I think also worked on it. LeTama worked on it and Tyween and I used it last fall to fix HD2Ones rom. And here we are almost a year later with 2 diff files still :( Anyhow, maybe the guys who helped fix the high gain mic issue in the kernel can do this.

noellenchris
[HD2 Android NAND Development] M..N:
Maybe create a thread with info like they did with the mic issue and see if devs will jump on
[HD2 Android NAND Development] memin1857:
MIC LEVEL

Using RootExplorer or similar file manager, edit the /etc/init.d/10mic_level file

and change the number 200 to 400.

Reboot and it will be OK.

The above way is to make it permanent. Actually you can set dynamically while inside a call to test the best value. Just give the below command from terminal emulator to temprorarily adjust mic level.

echo '0 400' > /proc/mic_level

BTW this is the thread for it:

http://xdaforums.com/showthread.php?t=1162224

TYWEEN, I think 400/600 levels would be better. You can do the same adjustment at init.d for your next rom version.
[HD2 Android NAND Development] Wickster:
Thank you again for this...
[HD2 Android NAND Development] MarkAtHome:
FWIW, has anyone paid attention to the status bar icons when you plug in your USB cable?

I originally dismissed it since it coincided with my use of new six foot cables (within the last week or so), but after reverting to the original cables, I noted the same thing.

When I plug the cable in to be charged (AC), the device sometimes displays the USB connection icon; unplugging the cable and reinserting it (correctly) no longer shows that icon. That icon should only be displayed when you connect to your PC (or like).
[HD2 Android NAND Development] walts:
See my post #15681. No one has confirmed it, but it looks to me like it depends on the charging voltage and/or current.

Walt
[HD2 Android NAND Development] mootmetal:
this happend to me before ...but i guess this is shown cuz ( i guess) the first charge of cuurent is below of 500 ma ( that's what the computer gives to the phone) so the reconize the cable as pluged into a computer ....well someone correct me if i'm wrong
[HD2 Android NAND Development] MarkAtHome:
Thanks, Walt, but that is not the case on my end. I plug my cable into its stock AC adapter, which plugs into an APC Smart-UPS 1500VA LCD 120V. Consistency of voltage, current, etc. is unquestioned.

This only began within the last 1-2 weeks, so all I am doing is suggesting the possibility that there might be a new, incorrect setting in the ROM.

Note that I am referring to the phone charging via AC and not via USB, although a USB cable is used (TMO HD2).
[HD2 Android NAND Development] MarkAtHome:
Hi mootmetal -- please refer to post #16944, where I addressed this. Thanks.
[HD2 Android NAND Development] themadproducer:
Same here...just as you described. But I know for a FACT that the HD2 will choose between FAST charge (800ma or so) and SLOW charge (500ma or less) depending on the pin configuration of the cable. I have written about this in a post way back in this thread. I have customized at least 4 usb cables, 3 desktop chargers, and 2 car chargers to achieve the HIGH charging rate.

I never have issues plugging into my dedicated wall charger or desktop charger but for some reason, plugging my HD2 into the car charger 50% of the times results in a USB connection icon and low charge rate...in which case I do as MarkAtHome described...unplug and replug it in. The HD2 is the one making the decision between fast and slow ma draw/charge not the dumb power supply. The HD2 needs to see pins/wires 2/3 shorted at it's input to enable fast/high charge mode. Some usb cables used to charge...don't even have these pins/wires...thus the USB Connection icon should never pop up with these cables/chargers.

(note: if you have a 500ma wall charger the HD2 will slow charge because the charger will only have 2 pwr wires and not the other 2 data wires.)

And yes I know...a usb cable that is meant for data transfer from PC to HD2 should NOT have these pins shorted else the HD2 will draw more than the PC USB port can supply...resulting in damage to one or more of the components.
[HD2 Android NAND Development] ph03n!x:
The USB cable has 4 contacts - two for current, and two for data. When it is plugged between the charger and the phone, only the wires carrying the current are "active", which would make the phone - 1. charge up, and 2. show the charging battery icon.

When plugged into the computer, all the 4 contacts are active - signalling the phone to show/ load the USB connected icon and interface, as well as show the charging battery icon.

If you see a deviation from this behavior, it means 90% of the times that the cable *might* be at fault, maybe have a loose connection, and a change in cable would tell you. The remaining 10% might be more serious - the USB port on the charger, or worse still, the phone itself...

The amount of current has no bearing with the USB icon being shown or not, I charge my phone regularly on the computer, on a charger that is rated 500mA, and my car charger (which is rated 500mA) - the only time I see the USB icon come up is when I have an USB extension cable and the connection between the phone's cable and the extension cable has come loose.
[HD2 Android NAND Development] jolas:
Using libaudio.so as suggested (from 'Mic Fix' thread's post #97), solved the problems which I had...

EDIT: REPLACED AGAIN WITH STOCK'S V.3.6.1 LIBAUDIO, BECAUSE (POST'S #97) LIBAUDIO GAVE ME PROBLEMS WITH FREEZING PHONE APPLICATION...

Sent from my HTC HD2
[HD2 Android NAND Development] PUFF1N:
O.K So I tried this build for the first time.

The most current radio and kernel is 2.6.32.15_tyung_r11-g343845b

It runs smooth and benchmarks great, batery is not too bad either.

The major issue I am having is that the WiFi connection is horrible! I need to almost be next to the router for it to work. I've tried different channels and only using "G" not "N".

My HTC Desire running Cyanogen Mod 7 stable picks up the WiFi in the next room, but the HD2 needs to be within about 2 feet for it to work.

Any ideas?
[HD2 Android NAND Development] idrozd:
A small report.

3.6.1 installed. Observed frequent power cuts as a microphone and speaker. Especially after running and working with Skype - no sound no. Rebooting helps for a while. Revert to 3.6.0.
[HD2 Android NAND Development] lslight:
+1

It's very difficult for me to find what's related to the "stock" 3.6.1 ROM and what's related to people who have "user modified" 3.6.1 ROM (ie changed lcd density, mic level mod, ...).
[HD2 Android NAND Development] eseregin:
The only thing about Stock will be a little low mic level. You will need probably increase mic gain.

Market not new 3.1.3 version, but 3.0.27 or about (downloaded from mirror 1). If you have Stock 240 density LCD you will be able to download any apps from market nevertheless. I did it myself, no probs with Stock density.

That is it. Brilliant ROM!
[HD2 Android NAND Development] PUFF1N:
I disagree.

Fresh install by the book here. Terrible WiFi reception. noted by 3 users on this build.
[HD2 Android NAND Development] edward0119:
does anyone have the same issue like me?

when i get a call,the volume is too small,my words are hard to be heard,but when i make a call,there is not such a issue

I don't know why