yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] deckoff:
This time I copy/pasted most of the list, and added the last two. The lag issue was already there. But, to be honest, I hate it! Anyway, I would try to help everyone the way I can, and hope to receive the help needed, which, I assume is fair enough.

By the way, have you ever had a little stone in your shoe - well, that is the feeling with the wake up lag, soon you will be selling your life just to get rid of it :)
[HD2 Android NAND Development] karendar:
Oh, I see you run WinMo according to your signature... I missed that.

I know getting NAND up and running is an issue for some people, but when it does run, it RUNS! haha. I personally bought this phone with the sole purpose of running Android on it, and I'm so happy I did. WinMo is more tried and tested I will agree though... So I understand your desire for stability. Maybe when they release WinMo SD card support, you can run Android as main and WinMo as backup? ;)

I currently run HyperDroid as my main OS though, if you ever want to mess around with it, it's a good main OS until CM is completely tested (I backup/restore between the two to see if I can produce any issues)

In the meantime, I just want to urge anyone who has time to pitch in to get this build as rock solid as possible!
[HD2 Android NAND Development] dddnnnggg:
- all types of WPA2 connectivity, i think is a big issue
[HD2 Android NAND Development] deckoff:
Of course, it is, added
[HD2 Android NAND Development] :
Such as? I have read a lot of this forum. I thought nightlies meant they are built automatically? Instead of being condescending try being helpful which is what I thought these forums were about.
[HD2 Android NAND Development] brainmaster:
About wake-up lag - have you tried "Widget Locker" app? I don't have any since I use this app. When phone is off and I push any button, it wakes up instantly.

About 4-th post on the front page - you could really PM the Mods if that is O.K. with Charnsingh.

Partially right - the CM7 part is built automatically, but the HD2 drivers and kernel related stuff is where we can help our Dev with logs and testing.
[HD2 Android NAND Development] fhasovic:
What means "built from the ground up"? There is android source, and it is modified to support HD2... I have built it from source last night...
[HD2 Android NAND Development] Elmo108:
im with deckoff. when im waking up the phone i always need several swipes till it recognizes it. :)

edit:

@fhasovic: i guess many drivers and stuff are ported over from other devices which run android natively
[HD2 Android NAND Development] kampf:
I'm going to look at an HD2 tonight with a bad digitizer, which HTC has already confirmed they'll replace.

This is solidly the NAND ROM I want on this device. Having always had "Google Experience" phones, G1s and a Nexus One, and having experience with CM builds on the G1 and Viewsonic G-Tab, the nearer to AOSP the better for me. Non-Sense :)
[HD2 Android NAND Development] ookba:
So lets say I'm running MDJ's last CM7 release or any CM7 NAND ROM for that matter. Can I download apply the latest nightly update on top of it using CW AD Recovery? Or...? I have a full backup so I'm not worried just curious.
[HD2 Android NAND Development] brainmaster:
You have to do the full wipe / factory reset.
[HD2 Android NAND Development] fhasovic:
So, same as CM7 for HD2 ;-)
[HD2 Android NAND Development] drewestate:
Out of curiosity, what type of wpa2 network are people having problems with? I'm guessing enterprise as I'm able to connect to my own wpa2 personal setup just fine...
[HD2 Android NAND Development] t0ny0:
Hey guys,

I had a LOT of fun with my HD2 and this build, and would like to thank charn and everyone else helping around, but I just sold it and got the G2.

Just wanted to say bye and thank you very very much!
[HD2 Android NAND Development] poopymt3g:
Traitor! jk have fun with your g2
[HD2 Android NAND Development] mattfmartin:
Has anybody tried changing the market to a themed one. Everytime I try it just stays green. I even deleted the marketupdater.apk.... Any ideas?
[HD2 Android NAND Development] kampf:
At least he still has his G Tablet!
[HD2 Android NAND Development] pongster:
Really? Let me clarify this, based on my limited understanding of Android at the moment. The userspace and kernel are actually different parts of the entire Android ROM. As i understand it,The kernel we currently use for all hd2s is based on the evo kernel. The userspace, or what you see and know as Android, is all built from the same source aosp and cm7 are made from. So the rom I compile is really built from the ground up.

The proprietary drivers for the hd2 are probably from HTC. When you say working the kernel from the ground up, that's in the kernelspace. Making it use aosp drivers as charan has done for wifi.

The kernel from tytung, which I use on my roms, is technically built from the ground up as well. He's incorporating some aosp drivers to enable stuff life wpasupplicant working correctly as charan has done.

Sent from my HD2 powered by HyperDroidGBX
[HD2 Android NAND Development] charnsingh_online:
Ok guys I have done a lot of research and working in the last few days and what i have accomplished that needs to be tested -

1. GPS libs compiled from source - bye bye kanged libs :D

2. Find the Bluetooth Code Fixed - cya bluetooth drain bug :)

What am i trying to finish

1. incorporate 720p stuff - Future proof plan and a lot of more fixed that it will bring to build killing most of the proprietary libs

2. Incorporate msm flashlight so it will use a generic driver now so the torch fully works across all phones

3. Make everything in the kernel AOSP so there are minimal bugs in rom

Also to make clear about the Open Source, this rom vs other roms etc

This Rom has been compiled keeping specifically HD2 in mind and has a lot of hd2 related stuff in it that u cant find in any other rom. And Kernel and AOSP are related. They are not independent of each other. U can just boot any rom on any phone with the kernel for that phone and the ROM like we can never get SGS and AOSP love each other. They are related through the frameworks. Adding 720p support in kernel doesnt mean it would do that, we need to edit frameworks too, we need to add and edit libraries too. If u see about other roms, kernels are compiled from source, but the rom isnt. When the rom is compiled from source, the devs have to unpack the rom add all the HD2 related stuff in the rom and then repack it. With the vendor i made its compiles an AOSP rom without unpacking, repacking stuff straight from the oven with all the dressings included. About HD2 kernel devs (the original ones) - They have done a pretty awesome job but i would have more appreciated if they would have used AOSP kernel rather than HTC kernel as base it would have eliminated 99% of bugs. If anyone didnt try the RC i have uploaded its a lot lot different than the nightlies, i worked on it a lot adding more hd2 specific stuff maybe fixing banding and removed all bs from the hd2 rom like trackball ( never knew it didnt have one lol) I will be working on it more but i have only 15 days to my exams so it would be hard for me.

Also i request Tytung to work with me together so we can make hd2 kernel more on AOSP rather than htc stuff as AOSP IS COMPATIBLE with both sense and non sense roms
[HD2 Android NAND Development] xfichtenelchx:
problem

Hi guys,

flashed Nightlies with cwm. Everything fine. Then I flashed Gapps with cwm for having market. Now when I start my phone, it says "Welcome to HD2. Touch Android to start". I touched it approx. 264 times but nothing at all happens.

Any clue ?
[HD2 Android NAND Development] mattfmartin:
Reflash again without gapps to make sure your touch screen didn't die.
[HD2 Android NAND Development] xfichtenelchx:
I did reflash, but this screen reoccurs. Touchscreen is fine, can enter PIN, change language etc

Luckily got cwm backup from CM7... try to reflash, but without gapps...but how do i get market (and google account synch?)

thanks

EDIT:

waaaiiiit...that was confused. Touchscreen is working fine. Restored to CM7. Gonna reflash Nightlies. But how do I get Market and Google Sync (contacts and calendar?)
[HD2 Android NAND Development] sonick_d:
can someone help me on how to install a2sd?
[HD2 Android NAND Development] pathologo:
Do you actually mean "WidgetLocker Lockscreen"?

Also, could you elaborate a bit? What did you experience before and what are you experiencing after installing this app?
[HD2 Android NAND Development] dddnnnggg:
I can not even see the EAP, which worked just fine with winmo 10 minutes ago.
[HD2 Android NAND Development] brainmaster:
There is DarkTremors A2SD and you could try this one - since its easier to install.

Yes I mean "WidgetLocker Lockscreen". I don't have any lags, but can't also tell anything about experience before because I use that app on Android from the start.
[HD2 Android NAND Development] kundanjuit:
This app doesnt help in reducing the wake up lag for those having this problem.
[HD2 Android NAND Development] trilu:
great news! can't wait to test something :-)
[HD2 Android NAND Development] MontAlbert:
not sure if its just me but i applied the RC1 with the kernel fix for CPU governor and i no longer have usb mounting- anyone else had this?

***edit*** think it might just be my pc :D
[HD2 Android NAND Development] dusko_m:
@charnsingh_online

Markinus has already started his own development on CM kernel. Would be nice to see you two join forces on this

http://gitorious.org/linux-on-wince-htc/cm-on-wince-htc
[HD2 Android NAND Development] brainmaster:
O. K. Then Charnsingh doesn't need to fix that in his ROM because its not ROM related. I and others also don't have that issue, so how is he gonna fix something that it isn't there?

I want to say - its not nice for you guys to have that bug, but its not ROM related. Maybe its just issue with your hardware.
[HD2 Android NAND Development] pathologo:
Nope, everybody has this issue.

After pressing a hardware key to power on the screen, at least 0.7 seconds pass till you can see the screen.

You will notice that the screen is turned on *after* the keypad light.
[HD2 Android NAND Development] kundanjuit:
I dont agree....Well its a kernel issue and the kernel is the part of this ROM. So in order to make this build perfect for everyone, the screen driver for the EU HD2(Sharp LCD) needs to be solved. Charan Singh knows this and its on his todo list too.

PS: Its just not me, there are hundreds of user with this issue. And yes it is really irritating.
[HD2 Android NAND Development] pongster:
How fast should it pop up when there is no lag? .7 seconds doesn't seem like a lot... unless you lock and unlock your phone every time in the manner you describe above... (from the time you lock and then immediately unlock)
[HD2 Android NAND Development] brainmaster:
Good. Its there - 0,7 sec lag, but not 2 sec lag.

For me - its not that much annoying. But if it is for you and Charnsingh can fix it, then why not.
[HD2 Android NAND Development] pathologo:
at least 0.7 seconds...

Actually it's more like a full second, and yes, that's actually too long and afaik everybody experiences that.

The screen should be on instantly, just like the keypad light.
[HD2 Android NAND Development] kundanjuit:
The bottom line is that, something is wrong with the driver for these screens. And this lag is worse, goes from 5-7 seconds on SD builds. If this is fixed in Charan Singh's kernel, many people who prefer to exploit their HD2 to fullest using dual boot will benefit from this. Its really annoying for many people and they are eagerly waiting for the fix. Just look at the views for this issue

http://xdaforums.com/showthread.php?t=898087 . Its 30,053 as of now and this proves there are many many people eagerly waiting for a fix. Again we are talking about reaching a perfection on this build, so this counts as an issue.
[HD2 Android NAND Development] tageeboy:
I think the lag issue is not impacting the HD2 phones from the US with 1024 RAM, is this not correct?
[HD2 Android NAND Development] pongster:
If I may, views doesn't necessarily translate to proof that people are eagerly waiting for a fix. Users sometimes flock to threads just to read. I'm sure all of you who posted on the thread and have been passionately behind the "gimme a lag fix" are eager for a fix, if there even is one in the future...

You know some people may not even notice the issue because they use their device differently. (not locking and unlocking in quick succession) They only find out after trying out what is needed to reproduce the "bug".

I do hope you get a fix for it.. as it is a valid issue for you... meanwhile for some of us (the minority perhaps) we don't really mind or notice the "bug" because we probably use our HD2's differently.
[HD2 Android NAND Development] pongster:
ok, I don't lock and unlock my device that way so I don't notice it at all.
[HD2 Android NAND Development] pathologo:
I also don't really mind this bug, but it's definitely there and noticeable, and it's not only when turning the device back on immediately after turning it off, but instead it happens always, even when you keep your device off for hours.

Afaik it's kernel related and some kernel devs are trying to hunt it down for some time now.

I cannot say if this doesn't happen on US devices, but I think they should behave in the same way.
[HD2 Android NAND Development] cobhc:
Can't say I've ever experienced wake up lag at all. Unless I'm just not anal enough to notice it.
[HD2 Android NAND Development] dusko_m:
just tried my coleague's Desire and these two devices are behaving absolutly the same. There is some (like couple ms) delay in turning screen on after buttons lights up on each of them.

I can't claim that this behaviour is the same on each and every HD2 outthere, but I realy do not see that there is any issue about this
[HD2 Android NAND Development] pathologo:
That's nothing to do with anal or not.

If YOU cannot notice it then you should be worried about your health/brain. :rolleyes:
[HD2 Android NAND Development] y3kt:
How can i install this if i dont have clockworkmod installed? Any way to do it from the system? Thanks
[HD2 Android NAND Development] MotoMudder77:
Thats not an issue, Every build on every android device I've ever had was like that. Its normal, dont count on a "fix" for that
[HD2 Android NAND Development] MotoMudder77:
If you dont have CWM installed then you obviously dont have this build installed.

But im sure that extracting the files and adb pushing them into there respected locations would work.
[HD2 Android NAND Development] wheeliemonster:
Even better! :) No offence intended...! :)
[HD2 Android NAND Development] y3kt:
I dont have that build exactly, i have mdj's one, based on the same but i am stuck with google apps, i will try pushing the files through adb, thanks
[HD2 Android NAND Development] Bib_x:
No thats not right. Some HD2 users told me, that HD2 is the only device with this behavior. All other android-devices they had before had hardware button lock - so you only can answer a call by sliding on the screen.

An extra app to lock the buttons would be great too, no need to fix this in the rom. But there isn´t any app out yet as far as i know.
[HD2 Android NAND Development] themadproducer:
I have to agree with you Bib.... It really doesn't matter if the TERM is bug, issue, non-feature etc., common sense says, you would think that the hard keys would lock during an incoming call just as they are normally locked on screen wake up. Boy if I could write code, it would be in the top 10 list of things to fix/modify.

Back in Winmo, there was the same issue but someone developed a tiny app to take care of this. I used it. It worked. With Android, I've tried all the 3rd party screen lockers incl WidgetLocker, and even wrote the developers of these lockscreen apps about this very matter. Seems only a few of us see a need to have the buttons locked in call! Slide to unlock is great...that is...unless you END the call first, by mistake, in your pocket, via END BUTTON...right?
[HD2 Android NAND Development] Bib_x:
On WinMo i used S2U2 and it worked perfect!

During call it doesn´t matter, bigger problem is while phone is ringing. I bought a leather pouch and every time i pull out the phone (in pouch) from my jeans bag, i accidently press one of the hardware buttons. Sometimes call is answerd and sometimes call is ended.

I don´t see any need of slide to answer if i could answer a call by hardware buttons too. Slide to answer was developed for exactly this problem (no more accidently answerded or rejected calls).
[HD2 Android NAND Development] totalcmdext:
If the SD card have an EXT4 partition is problem fo this build?
[HD2 Android NAND Development] charnsingh_online:
I think ill work on integrating it in CMParts

All those asking, yes the build is using RMNet because i heard Rmnet was more stable than ppp connections.

Just wanted to confirm a few stuff from the latest build

1. Are the animations working now

2. Is the green Led issue fixed, if its not, get me the logcat for when system is booted from start and also get dmesg

And feel free to report any other issue so it can be fixed, Currently i am working on overclock/undervolt kernel for HD2 also updated the KGSL(GPU) drivers to the current so ull see a boost in GPU performance, after the testing is complete ill upload the build which will be likely 12 hrs or more. Also Wats the difference between US and EU,this one was compiled taking EU in mind. If u need a different build for US, ill be happy to work on it
[HD2 Android NAND Development] Barlows:
EU has 512mb internal memory, US has 1024mb internal memory
[HD2 Android NAND Development] karendar:
1- Affirmative. Animations seem to work for me.

2- LEDs look to all be working for me, green/red/button backlight. Even the LCD backlight is more responsive than all other builds

As for the whole robot voice, I was able to reproduce it on a clean install. Wiped partitions with CWM, flashed the zip, went into phone call and dialed my number. Robot voice and FC on dialer. Now no sound on dialer. If I reboot, issue is gone for good... Just if you're bored and for reference purposes, here's the adb log:

http://pastebin.com/download.php?i=ZAUEHvFH

If you need any other testing, I'll do my best! Thanks for the build, can't wait for a complete official release of CM7!

And as someone mentionned above, yeah it's mostly NAND size that is different from EU and US HD2. The T-Mobile edition has 1024 MB of NAND space and EU has 512. I believe there's a RAM difference according to official specs list, but I believe this was rectified. Not too sure about that one.
[HD2 Android NAND Development] Astellar:
Can you check if something can be done with color banding issue? I think it is somehow related to used display driver, as any ROM that I've tried has it.
[HD2 Android NAND Development] MotoMudder77:
I had phone proccess FC on me a couple times today during a outgoing call, and again on a incoming call. After reboot it seems its fixed, came home to try and get a log of it and I cant reproduce it.

Had it happen on a different 2.3.2 build also, cant remember which one tho.
[HD2 Android NAND Development] fatrix1:
hi

can you put Sysfs interface for optional under/overvolting in the kernel?

if you can?

http://xdaforums.com/showthread.php?t=821372
[HD2 Android NAND Development] shadiku:
It's hardware, we all have it. No software can change that.
[HD2 Android NAND Development] MontAlbert:
is this the robot voice issue as well that occurs on many other roms? Still happens to me occasionally on MDJ 2.6 (my other HD2 but tbh there is not much it has that this doesnt, and considering how long this has been in development its bloody awesome)....
[HD2 Android NAND Development] themadproducer:
Friendly question...if NOTHING can be done about it, why do the SENSE builds not have this gradient banding ...in the UI. (some apps still have it) Same HARDWARE!!

Also, in those same SENSE builds, if using Launcher Pro, widgets do not have the issue either. (except while in motion during swiping)

Further more, my wife's SGS Fascinate only has banding in certain apps...but when using Launcher Pro, when swiping, the widgets show THE EXACT same banding???

I do believe something SOFTWARE or DRIVER related...could help!

Launcher Pro does not help with banding in CM7 builds even though there is a DITHERING option which probably works in CM6 builds... (not sure)...but definitely works in Sense builds.
[HD2 Android NAND Development] MotoMudder77:
No, Not a robot voice issue, I've never ran into that, Im assuming that has something to do with older radio's, which I've never ran.

IDK what caused the FC, as I was unable to reproduce and get a logcat of it.
[HD2 Android NAND Development] miharkula:
I get green LED on boot but if I plugin the phone (usb or charging) and unplug it goes away and acts normal. dmesg/logcat attached.

Main differences in US is that we have more space left over for apps. Also a minor thing is needing to update gps.conf but at the moment GPS isn't working for me with this build.
[HD2 Android NAND Development] pathologo:
I once checked this with a Samsung Galaxy S and every time I pressed the power button the screen powered on instantly.
[HD2 Android NAND Development] mattfmartin:
This is correct for me. Wakes up instantly also with the keypad lights. Its not kernel related. Absolutely no lag whatsoever. Even if I press it on off, on off, on off, still wakes up like a native device.
[HD2 Android NAND Development] deckoff:
Wakeup Lag

1. I am sorry for bringing this discussion to this thread.

2. The lag and the bug is real, it appears when screen is off while talking,too, you have to wait for a second or two for the screen to switch on.

3. It is bad software support for hardware(I believe this is due to SHARP LCD were used when HTC were not avaible)

4. I COMPLETELY agree GPS and CPU issues (and others) are to be fixed first but...

5. I would like to see that bug fixed, too. It is here, it hinders performance and annoys

Lets support each other, and support our devs.

PS. Very few TMOUS report to have the lag as well, but still they do.
[HD2 Android NAND Development] kundanjuit:
There are hundreds of threads out there, people dont flock around those quite often. I guess the subject is quite amusing maybe :P

Anyways the behaviour is consistent throughtout, its not about switching on and off, its same everytime we switch it from idle state. You might not be using much of IVRS calls, but when we do, we find our keyboard appear when the response time is gone. And this is irritating when you cant use your phone as a PHONE.
[HD2 Android NAND Development] mattfmartin:
I can see you guys point. I say we drop the subject and not hijack the thread since it has nothing to do with this build.
[HD2 Android NAND Development] dusko_m:
@everyboby affeted by lag issue

repeat your test in total darknes and see if display turn on instantly. might be that there is a delay between moment when screen turns on and moment when it reaches required brightness.
[HD2 Android NAND Development] trmacdonal:
I don't think this issue affects TMOUS users. I have tried to reproduce this bug on my 1024 HD2 and at the very most I get a .1 -.2 sec delay. Usually the screen is on before the button comes back up. This is with this build the AmeriCanDroid SD build and the CMY Stock Desire HD2 build. Do the two phones use the same memory, just different amounts? Are the screens the exact same? I know the touchscreen digitizer is different, but that may just be a connector difference. Without a Euro HD2 to compare with it would be hard to pin down the cause.