yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] jasroop:
in total commander i cant find dalvik folder..if its their then please provide some instructions..also clear about change font command..i have to wait to finish this or just press back button and moves in total commander..
[HD2 Android NAND Development] mentalityx:
Jasroop

Me I like to explore all the files in my Commander or I use Root Explorer. Almost the same thing. Just open it up and go to data/davlik-cache like in my picture.
[HD2 Android NAND Development] sandymac:
Open Total Commander, click on File System Root folder, scroll down to sd-ext folder and open it (click). Press and hold down on dalvik-cache folder. When the popup dialog box appears, select delete. Done. ;)

As to the procedure for changing font then refer to Sneaky's post.
[HD2 Android NAND Development] jasroop:
I try sneky procedure, but phone stuck at tbd roms, then i install rom again and change fonts and just restart phone because i dont find dalvik folder, then again stuck at tbd roms, now i again install this build and will give the try by ur guidelines in morning, now its 11.30pm in india, thanks to u as well as sneky for providing guidance,,good luck tc bro
[HD2 Android NAND Development] gecata:
You cannot find differences because of "incorrect" install script in zip file with GBLeo kernel. It not work with CWM different from v.3.xx. If You just install - modules are not installed and ... You cannot find differences.
[HD2 Android NAND Development] Sneakyghost:
Hi mate,

not wanting to get cocky here but what makes you mistrust my judgment?

I have extensively tested all available governors and i also had a compare-chart available for a similar GB Sense ROM. Both my experience and that chart strongly hint towards SmartAss 2 being the ideal governor for scaling, and also - hear and wonder- for SD card access...

Believe it or not, SD-Card r/w performance changes considerably depending on the governor in use.

While Smartass 2 does not provide the perfect condition in each scenario, it has by far the best balance of it all on this ROM.

This being that you decide to use the direct Governor Setting in Deamon Control, as it is not meant to be working with a Deamon. It can be used with a Deamon but does work better on its own. It has a built-in screen-off profile that senses the screen state by itself and thus doesn't need a deamon.

---------- Post added at 10:19 PM ---------- Previous post was at 10:14 PM ----------

If this is true, i will have a laugh again tonight as all the heated discussion on that new kernel can be declared null and void. It's been pointless lol.

Go check the kernel out with a proper install. Haha. I might even come back to this Release to see all these fantastic magical improvements myself if any of you goes to try and report...

@Gecata: can you by any means provide information on how to properly install that kernel into this ROM? For some of us might want to try but don't know how (including me).

---------- Post added at 10:31 PM ---------- Previous post was at 10:19 PM ----------

Of course your ROM will be stuck at boot time and time again if you don't delete Dalvik Cache. No need to keep trying without doing so. And by the way: Sandymac is right, clearing dalvik via an Explorer is much more convenient than flashing that Zip. But if you still want the zip, i attached it for you, hoping that Carl1961 does not mind.

Notice: (to sandymac as well) sometimes making bigger system changes need immediate reboot and can't have app-launching and the like, especially when changing fonts. I frequently experience severe device hiccups when messing with RCmix3D tweaks and trying to navigate to anywhere else in the phone. So after all, in this special scenario, a flashable zip might indeed be the better way to go.

Notice to Jasroop alone: i read something about pulling out the battery. Please do yourself and your phone a favor and don't do it. Two reasons: the battery pins in the device are exceptionally volatile and break very soon when frequently pulling out the battery. The second reason would be: since there is no real power-fail handling in android's EXT4 Filesystem, it is very likely you damage/corrupt files if you shut the device down unexpectedly. The ONLY WAY to properly quit android is by using the shut-down command (which would be the red button in the APM). Even the reboot-command does not cater for the particularly fragile EXT4 system. Even with a normal reboot you can actually damage your android and make it run less and less stable the more often you do that.
[HD2 Android NAND Development] mentalityx:
Good thing I don't use CWM so that's not a problem.

Yakking about the module's not Installed............. uhhhmmm where can I find them then?? I don't see a thread for this kernel.
[HD2 Android NAND Development] gecata:
@Sneakyghost - check private

@mentalityx - check private

@All

If Sneakyghost and Mentalityx report all is ok i will ask permission from XxXPachaXxX to make his kernel public for TBD rom. If someone don't want to wait - use Mark's 0.21 structure and replace files with these from XxXPachaXxX's kernel and flash.
[HD2 Android NAND Development] alex.odell.2011:
Maybe it is loyalty but I think the ROM is smoother on Marc's kernel...
[HD2 Android NAND Development] Sneakyghost:
Sorry mate you where very quick there. I am currently running WP7 for seeing some new evolution happening there and i might want to stay with it for a little while so i will pass this one over to someone else. If this Kernel still happens to be the talk of the day in another week or so i might jump on the boat...
[HD2 Android NAND Development] mentalityx:
HEEHAW

Thanks mate checking and reading. Going to backup and flash. Thanks gecata.

Never hurts to test try something that is free Alex O.

Good ol Sneaks.

---------- Post added at 04:35 PM ---------- Previous post was at 04:05 PM ----------

Ok while Im waiting for this backup to finish, I have a question for Sandymac, Markusbrutis, or Sneaky.

Ive flashed v3.6 themed and v3.7 themed multiple times the past couple of weeks.

Well my Power Menu does not work. The menu comes up but Im not able to select any power option. This has happened in each version. Ive done proper flashing, wiping of everything and creating new SD Exts each time. Still the Power Menu never works. The only thing I can do is pull the drop down menu and go to Quick Settings and then reboot from there. I dont like to do that since that is not always good to do. I usually like to power down and then turn on the phone to get into recovery.

Is there a fix for this or some files that need to be deleted or moded??:confused:
[HD2 Android NAND Development] jasroop:
Of course your ROM will be stuck at boot time and time again if you don't delete Dalvik Cache. No need to keep trying without doing so. And by the way: Sandymac is right, clearing dalvik via an Explorer is much more convenient than flashing that Zip. But if you still want the zip, i attached it for you, hoping that Carl1961 does not mind.

Notice: (to sandymac as well) sometimes making bigger system changes need immediate reboot and can't have app-launching and the like, especially when changing fonts. I frequently experience severe device hiccups when messing with RCmix3D tweaks and trying to navigate to anywhere else in the phone. So after all, in this special scenario, a flashable zip might indeed be the better way to go.

Notice to Jasroop alone: i read something about pulling out the battery. Please do yourself and your phone a favor and don't do it. Two reasons: the battery pins in the device are exceptionally volatile and break very soon when frequently pulling out the battery. The second reason would be: since there is no real power-fail handling in android's EXT4 Filesystem, it is very likely you damage/corrupt files if you shut the device down unexpectedly. The ONLY WAY to properly quit android is by using the shut-down command (which would be the red button in the APM). Even the reboot-command does not cater for the particularly fragile EXT4 system. Even with a normal reboot you can actually damage your android and make it run less and less stable the more often you do that.[/QUOTE]

good morning mate, i try to change fonts and again stuck at tbd roms, what i have done is that, 1st i run change font command from rc

Mix settings, after i resrart phone into recovery and install dalvik wiper zip and restart phone but it not moves further tbd roms..also when i finish font change command i noticed that i have fonts in main screen only, when i click on all apps icons of apps come without fonts and after that i done procedure which i type earlier in the post..and stuck at tbd roms..
[HD2 Android NAND Development] costelasleontin:
well tried xpacha kernel and it happened that my mom got a phonecall on her phone and I got same call from same person in the same time and when I answered I just heared a buzzing noise and also the phone was slow responding while my mom could talk on her phone so I went for marcs 0.2.1 without further tests .
[HD2 Android NAND Development] jasroop:
i try this method also after running the change font command, but again stuck at tbd roms, any idea please..
[HD2 Android NAND Development] Kameirus:
maybe give this a try rom toolbox from the market it allows you to change fonts

https://play.google.com/store/apps/...DUwMSwiY29tLmpydW1teS5saWJlcnR5LnRvb2xib3giXQ..
[HD2 Android NAND Development] alex.odell.2011:
That's true man :)
[HD2 Android NAND Development] sandymac:
I have had problems with the Power Down menu when playing with system files in the past. All I can suggest is that you do another clean install. As I mentioned before on a few occasions, just boot into CWM and factory reset the phone. Don't play about any further with the sd-ext as this is wiped with the reset function. Re-install the ROM and once you have set it up but before you do anything else, check the Power Menu option and see if it works which it should on a clean install. If it does, you will then need to look at whatever else you do after this. Try installing each app individually, in case it is an app causing the problem (unlikely but worth a try) then individually set your own tweaks, checking the Power Menu after each. ;)
[HD2 Android NAND Development] Sneakyghost:
Mate, i have been helping you the past few days to an extend where i would think you must be doing something seriously wrong there. I can hardly imagine virtually everything going wrong for you for a week or longer. Beginning with your Problems regarding the download mirrors for Ansar's ROM up to now not being able to change fonts on Android for some odd reason.

I remember you saying you got a TmoUS HD2. So do you have an SD-EXT partition then? Because if not, your Dalvik will be on the NAND and the normal Dalvik deletion commands should be working OK. You wouldn't even need that zip or delete manually.

So, to conclude: we are as smart as before and know nothing. You are stuck on Boot and don't know why. Are you running CLK or MagLoader? Which Recovery do you use? Which Kernel do you use?

Maybe, if you first change your Kernel to the latest 0.2.1 from marc, clear Dalvik cache, reboot. Then change fonts, clear Dalvik Cache again, reboot...

Try that.

Or, alternatively, follow my wiping guides. Clean the whole phone out like there was no tomorrow, then rebuild everything from scratch. Maybe even go the MTTY way and delete everything with MTTY to see if it reports bad blocks, then once done so, flash the newer kernel right after flashing the ROM without letting it boot at all before, then once booted, first thing to do is try to change fonts and clear dalvik...

Just to exclude every possible other reason.

I know its a lot of work but mate, honestly, being stuck at boot happens to some people every now and again, some never resolve it but i'd think its from doing something wrong because your phone would normally boot without problems, wouldn't it?

And another thing: i really don't want to help you anymore because i am getting the feeling that communication is a little bad. we get very little information from you but a lot of "help me please" and it is very hard to figure out whats going on when there is no decent helping info. Its like you are drifting along the forums and do this, do that but never really dive into it deep. Forgive me if my impression is wrong but i'd try pretty much everything and read a lot before going to ask stuff.

Please refer to my guides to get an idea of how to clean your phone out decently and maybe a thorough wipe will already solve all your issues...

---------- Post added at 12:51 PM ---------- Previous post was at 12:49 PM ----------

There's also still that possibility of a dying End Key. Well known and discussed a lot. Could also be the culprit because to call up the APM one would need to long press the end key and if done too hard, it might disable the Digitizer temporarily. It comes back after a reboot and some more button pressing usually. The description could fit that scenario too. Just wanting to add that...
[HD2 Android NAND Development] sandymac:
Always possible, Sneaky, but he does say that he can pull up the menu but can't select any option which is really weird. :confused:
[HD2 Android NAND Development] Sneakyghost:
press end key long: APM appears, digitizer becomes unresponsive, so no option can be selected because the screen would not react to touch. Press back button in panic, everything would/might go back to normal. Why? because the back key sits next to the end key and might readjust the position of the keys...
[HD2 Android NAND Development] jasroop:
Its okey bro..u help me lot, big thanxxx for this help, u helped me from begining to end. , u never loose mind to my request, thats why i respect u lot, anyways i suceed to change fonts using room toolbox and it works great, i have t mobile, i.m using magldr, rrcovery is 5.0.2.6. Partition is 7,277,7. I have 1024mb ext partition with 256mb swap,and kernel is dansta inbuild in rom, i think its not latest marcs kernel, once again thanxx a lot for helping me, good luck for ur future brother, take care...
[HD2 Android NAND Development] Sneakyghost:
There you go. Some minor adjustments recommended here.

When using an SD-Ext on the TmoUS phone, this ROM automatically installs the EU layout. Thus, your system partition is big enough with 172 as Dan recommended but even runs well with only 149 (sandymac has it that low i think). 160 is a good choice. 277 is only needed for if you don't have an SD-Ext partition on a US phone.

The Kernel should be changed to 0.2.1 as the boot problems can stem from the older kernel. There where more people with boot problems on the previous kernel versions and there are less on the latest kernels. This is an observation i have no proof of but its my impression nonetheless.

The Recovery you use has frequently given me headaches with the boot. This can be identified as the main reason why your system might not be booting. I had been using this recovery for quite a while and it does not boot the ROM after applying changes to the system rather often. So if you wouldn't mind to use the 4EXT Recovery Dan recommended, i'd be pleased. I will attach it to this post for you since you seem not to be able to download from my MediaFire.

Finally, swap should by no means be necessary for you if you'd stick to the SD-EXT/EU layout i described above. You will have RAM plenty and need no swap enabled.

I am sorry but i cannot refrain from saying it: if you do not stick to the recommendations of the chef, which is your good right, then at least inform yourself very well, i.e read numerous posts and threads from people that have done the same alterations to gain from their experience. If you do not wish to read a lot of this, please just stick to what the chef recommends as this has been proven to work.

And yet again for all that didn't hear this before: do not ask for help for things the creator of a ROM is not responsible for. Or if you have good reason to ask a chef for things he didn't create, provide detailed information of what you have done so people can actually UNDERSTAND what was going on...

Of course, experimenting is, what brings us forward. So it's not a bad thing in itself to do, it is even good. But without any information, people assume you are working under the recommended conditions and go looking for errors there. That causes a lot of timewasting and frustration. No gain for noone there. But come here and say: hey dudes, i've been trying something new and i found this, this and that... that'd be much more valuable...

I bet if you reflash with my information from this post (provided you understand my primitive english) and you do a full wipe before with the Guides in my Sig you will not have any problems anymore. I bet you 10 bucks that i am right.
[HD2 Android NAND Development] jasroop:
okey bro, thanxx a lot for clearing stuff in such a good manner, please i request that never dont mind if i ask anything weired ..
[HD2 Android NAND Development] mentalityx:
HEEHAW

Only way to learn is trial and error.I definitely know so much more about Android now than I did 2 years ago. I did alot of tinkering and sometimes it was good and other times I broke something:eek:

Thats why reading the OPs/Chefs recommendations is very important to you and your HD2. Ask your questions but please exhaust all efforts before asking one of the radical guys on here.:D

---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------

I can see the MTTY being a little to difficult for a rook (rookie). Need to stick with the easy things first.
[HD2 Android NAND Development] Sneakyghost:
MTTY is fairly straightforward and easy if you run Windows x86 machines but it can be a pain in the backside if you have to deal with the (required) ActiveSync Drivers on Windows x64.

It is also dangerous though, as the SPL does contain commands that are capable of bricking the device. At least thats what happened to me when i was too nosy and tried them all. All commands work with the Stock SPL but not all with Cotullas HardSPL. That's also why i chose not to list them all in my docs but just those which are fairly safe.

You have to understand that MTTY is nothing more than a command interface to send mtty and at commands to Modems. It can be used to send commands to the Chip of your phone too. Those commands are programmed into the Bootloader and are HTC exclusive commands i think. Thus, you can only use these commands which the Chip knows, no other. They can be found by taking apart a stock ROM and then opening the SPL module with a hex editor. The commands are in there in plain text.

There is a thread with various other TTY interfaces that can be used to send these HTC Commands.

Once you know what you want to tell the chip, you only launch MTTY, type in the command and the SPL will execute it. Nothing more. The RUU also uses these commands to do its job. Its simple. Really.

And to get the drivers to work on x64 i have a package ready in my guide bundled with a little (hopefully understandable) instruction on how to get it done.

I swap these drivers nearly daily now as i need the standard ActiveSync drivers for some tasks too and so i can say the method i provide to exchange the drivers is definitely working.

I think the bigger problem for you is, that you cannot exchange drivers if you are limited to that library machine you where talking about.
[HD2 Android NAND Development] mentalityx:
Well then human guy you are Johnny on the spot now.:D
[HD2 Android NAND Development] r_i_x:
i think this kernel is good, wifi and data does not drop much...

but it drains my battery so fast even not in use (sleep mode) :confused:
[HD2 Android NAND Development] Sneakyghost:
You are some funny guy sometimes :D
[HD2 Android NAND Development] mentalityx:
R_i_x your not using the right kernel. If you read a few more posts down from that link you will see that the kernel does not have any modules and is incomplete. I've been testing the correct kernel the past 39 hours.

---------- Post added at 06:15 AM ---------- Previous post was at 06:14 AM ----------

Sometimes brosef........... I'm hilarious all the time. ;)
[HD2 Android NAND Development] alex.odell.2011:
*Cough* http://xdaforums.com/showthread.php?t=1658936 *Cough*

Dansta, since your (quietly) brilliant? ;)
[HD2 Android NAND Development] Sneakyghost:
Pay close attention to the "not working" compartment. It is a first step into the right direction but if i where Dan, i'd still wait some time until most things are worked out and then begin to do some theming... lol... this time dan should stretch his back and relax, watch others do the work. It's been long enough that we had it the other way around...
[HD2 Android NAND Development] alex.odell.2011:
Fair enough :)
[HD2 Android NAND Development] r_i_x:
okie i'll check that out after work... or do you have the link for the correct kernel? thanks...

:D
[HD2 Android NAND Development] Kameirus:
Hello,Hello,Hello

Is there anybody in there

Just nod if you can hear me

Is there anyone at home

hehehehe
[HD2 Android NAND Development] alex.odell.2011:
Nod Nod
[HD2 Android NAND Development] Sneakyghost:
Hehe you caught me there with one of those typical language twists that mostly happen to non-native english speakers...

Of course i rather meant you being rather hilarious than funny. But well, not sure if you aren't a bit funny too... ;)
[HD2 Android NAND Development] mentalityx:
I do but it's currently being tested. Maybe after a couple more days of testing when I send up my results to the boss it will be released. Patience is a virtue.

---------- Post added at 06:55 AM ---------- Previous post was at 06:49 AM ----------

Who are you kidding mate your English is really good. For native english you speak better than alot of people in this state.
[HD2 Android NAND Development] mentalityx:
(Head nod, to head bang, pumping fist in the air space)
[HD2 Android NAND Development] bipinsen:
Is this rom officially dead? Haven't seen any activity in a long long time! :D
[HD2 Android NAND Development] OSIRIS2010:
Hello

i´m here

good old germany 4:50PM

waiting for ICS with Sense

like: http://xdaforums.com/showthread.php?t=1658936 :D
[HD2 Android NAND Development] Kameirus:
talked to dan this morning and he has been working 6, 12 hour days so he hasnt had much time for it at the moment
[HD2 Android NAND Development] SagaPer:
Not dead at all! The ROM is just working like a charm. In daily use as my business phone.

The chef Dansta had (or has) health-problems and probably needs to sort that out before continuing his excellent work.
[HD2 Android NAND Development] bipinsen:
Thanks for the update guys! Wish Dan the best. Everybody's gotta make a living. :D
[HD2 Android NAND Development] mentalityx:
This ROM is easily ahead of most of the weekly updated ROMs on this board. I like that the apps are not locked to where you can't update them on your own. You would have to wait for the developer to release updated GAPPS.

Been around the block with the HD2 and this ROM is as close to perfection as you can get. Just read what MarkusBrutis73 wrote:

Lastly this thread has the most responsive mates that are friendly, and give much help when asked. Heck I even befriended a lad on here from Facebook for the first time ever. Who would have thought lol.

---------- Post added at 09:47 AM ---------- Previous post was at 09:44 AM ----------

Dan is waiting for a good useable kernel for an ICS Sense ROM. Look at the list of things not working. Lol its not even useable at least on my terms its not.
[HD2 Android NAND Development] OSIRIS2010:
ICS with Sense 4

look at this:

Marc Kernel for ICS

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

and this:

[May 17 2012] Blackout ICS Primo v1.0 [First Sense 4.0a for HD2][WIP Preview][Tytung]

http://xdaforums.com/showthread.php?t=1658936
[HD2 Android NAND Development] mentalityx:
I saw the kernel update yesterday. I got happy because this is going to be good for Android 4.0.3 ROMs. I like to keep my ROMs based on Sense. This is nice and promising. Still has a little way to go.