yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Ambious:
Not true, 2.2 worked fine, and also I'm currently using Linux Kernel 2.6.35 beta 1e and it works fine, glitches and banding and everything gone.
[HD2 Android NAND Development] KrewsialNL:
nevermind, that question should not be here :)
[HD2 Android NAND Development] OCedHrt:
It may be better than I start a thread for this question I have, but I'm going to try here first since this is the kernel I'm currently using.

How is the battery % calculated? I know this has been answerd in some form or other on the forums, but the typical answer is something like Android calculates this based on a variety of factors from battery stats.

Now, I'm asking this because I was at 79% battery and then rebooted to 98%
[HD2 Android NAND Development] ricky886:
but v2.2 is working on Runny rom;)

so why?!
[HD2 Android NAND Development] KrewsialNL:
For me it doesn't. I put the initrd from Runny into the custom folder, copied everything to the SDcard.

It says it's installed succesfully, but it doesn't boot.

Should I do a clean install for that ROM?
[HD2 Android NAND Development] gpietron:
I am on clk Typhoon 3.6.6.

Today wanted to try DORIMANX 2wcr Kernel (incl. his initrd) so installed from zip (no other preparations!) - after initial 3 bootloops it booted and all seemed fine, incl. reboots. However, after shutdown, permanent bootloops.

Tried to clear cache, Dalvik cache an fix permissions -> no longer bootloops but stuck on second splashscreen (one after DORIMANX logo).

Restored 3.6.6, after some time cleared cache, Dalvik cache, re-installed from zip, fixed permissions -> the same, stuck on second splashscreen.

Will wait for next versions.
[HD2 Android NAND Development] gerardroid:
well those are the big questions:why and how...i always had boot problems and enlarging the cache seems to do the trick for me thats why dm also made a recovery with a 10mcache in it...after/before flashing something i hear/read different things:clear cache? and dalvik? run fix per or all?hard reset?clear data?etc etc why? dont know ,but for some it works for some it doesnt.....i just flashed dm s new rom incl new kernel and all the extra s and its flying..i have no probs..why is it not working for you?

long story short;its all about testing and trying,if i wanted to know why and how, i would probably make my own rom and kernel and still ask why and how and still have a headache:):)

greets gerard
[HD2 Android NAND Development] tinuz97:
Lol,i can call people,they cannot call me....they just get instant voicemail.

Is this me,or maybey a vodafone problem? (NL) or this new build?
[HD2 Android NAND Development] gerardroid:
i had this also with the previous rom...solved the problem(for me)by switching the simcard to a other phone made a call...switched it back to my hd2 and it worked again...:)
[HD2 Android NAND Development] opravar:
Hi DM,

Great job, now on 2.3 VPN works perfekt.
[HD2 Android NAND Development] FileFixer:
VPN work same on previous CM roms with patch. Dorimanx kernel implemented this patch into kernel installer. Same thing, different way.
[HD2 Android NAND Development] jabaneco:
Thanks for the hard work. I try many roms and kernels and i have to say that this is the best kernel for me. I have a MIUIROM with this kernel oc at 1,5 ghz and is perfect.
[HD2 Android NAND Development] themadproducer:
I can't answer your first question, but about the jump from 79 to 98%...I have seen that happen to me in both directions. For me, it was a combination of needing to recalibrate the battery and more so because I was switching back and forth between batteries of different capacities. Either way, in my experience, the full battery would get utilized regardless of the values shown. Another scenario is being down to 15% or so, and staying there for a long long time. This relates to the same thing as above. (if you want to easily calibrate your battery, go to the market and try Battery Calibration...by Marosige)
[HD2 Android NAND Development] joescian:
Dori

a small donation for your next Kernel 2.4 :)

Confirmation number: 4RX63778881759238.
[HD2 Android NAND Development] ricky886:
i am using 91 assistant

flash the kernel then mount boot\ and use it to put the initrd in the boot:D
[HD2 Android NAND Development] Cunione:
Still no idea for the -59mA battery drain ??? :-/

Because "I tried so hard, and got so far, in the end", I did'nt find my proooooblem. :(

Nobody can give me his battery.stat ?
[HD2 Android NAND Development] D3LTA:
Is it gone when you reboot?
[HD2 Android NAND Development] Cunione:
What is gone ? The battery.stat ?

No.

But I don't understand why I still have this -59mA drain...

Maybe if I use a "good" battery.stat from someone who hasn't any drain, it may be good for me... If it is possible to switch from one file to another. (i have the stock HD2 battery)
[HD2 Android NAND Development] dorimanx:
Thanks allot for your support :-)

i am almost done with 2.4

i will post it today.

good day.

Sent from my HD2
[HD2 Android NAND Development] Rick_1995:
:o WHAT

Driver is initialised with device platform data, and regulator limit is set in leo's regulator platform data, so when tps is probed, it already knows it's limit and what to supply. iirc the default voltage of that pmic is 1250mV. So during boot it is at 1250mV, (really not sure if SPL or IPL touch this) lk/magldr (probably)do nothing here, kernel boots, loads device list from board's code, probe's all the devices by supplying board's platform data to the driver's probe method. probe method initializes the device and brings it to a sane/known state.

Finding a stable cpu voltage is like opening a dark room, you don't know what you'll find inside and also it might differ from device to device so have to be really cautious.
[HD2 Android NAND Development] dorimanx:
i am i light year away from tytung :)

its a fact, kernel is merged with 2.6.35 / 2.6.39 /

3.0.31

this kernel not exist no where, there is no line for it. its special :)

Sent from my GT-I9100
[HD2 Android NAND Development] dorimanx:
yes, i will.

its still not so good, hwa driver is latest ported and working (by rick) ver .38

but still bugs in it, you will see black screens, and errors about hwa in logs.

so its best to wait, till stability is fixed by rick or securecrt, they do awesome work, they do what i cant, because lack of knowledge :(

Sent from my GT-I9100
[HD2 Android NAND Development] dorimanx:
deleted, dual post.
[HD2 Android NAND Development] linuxis:
On 7.1 I can't connect wifi. 7.0 no problems.

System Tuner (logcat)

=====================

I/12:53:02.495 TelephonyRegistry( 940)

notifyDataConnection: state=2 isDataConnectivityPossible=true reason=null interfaceName=rmnet0 networkType=8

V/12:53:01.067 WifiMonitor( 940)

Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:19:e0:a2:fd:3e]

I/12:53:01.061 wpa_supplicant( 1773)

CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:19:e0:a2:fd:3e

W/12:53:02.485 NetworkStateTracker( 940)

net.tcp.buffersize.hsdpa not found in system properties. Using defaults

D/12:53:02.255 dalvikvm( 1018)

GC_EXTERNAL_ALLOC freed 407K, 48% free 3194K/6087K, external 3065K/3096K, paused 36ms

V/12:53:01.909 WifiMonitor( 940)

Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]

V/12:53:01.902 WifiMonitor( 940)

Event [CTRL-EVENT-STATE-CHANGE id=6 state=0 BSSID=00:19:e0:a2:fd:3e]

I/12:53:01.902 wpa_supplicant( 1773)

CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00

I/12:53:01.902 wpa_supplicant( 1773)

Authentication with 00:19:e0:a2:fd:3e timed out.

W/12:52:59.842 NetworkStateTracker( 940)

net.tcp.buffersize.unknown not found in system properties. Using defaults

V/--- beginnin f /dev/log/system

V/12:52:52.252 WifiStateTracker( 940)

Changing supplicant state: SCANNING ==> ASSOCIATING

D/12:52:52.059 dalvikvm( 1098)

GC_EXPLICIT freed 359K, 52% free 2993K/6151K, external 0K/0K, paused 44ms

V/12:52:51.902 WifiMonitor( 940)

Event [Trying to associate with 00:19:e0:a2:fd:3e (SSID='Mekonijus' freq=2437 MHz)]

I/12:52:51.793 wpa_supplicant( 1773)

Trying to associate with 00:19:e0:a2:fd:3e (SSID='Mekonijus' freq=2437 MHz)

V/12:52:51.180 WifiStateTracker( 940)

Changing supplicant state: DISCONNECTED ==> SCANNING

I/12:52:51.180 wpa_supplicant( 1773)

CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00

V/12:52:51.095 WifiMonitor( 940)

Event [CTRL-EVENT-STATE-CHANGE id=5 state=0 BSSID=00:00:00:00:00:00]

I/12:52:51.092 wpa_supplicant( 1773)

CTRL-EVENT-STATE-CHANGE id=5 state=0 BSSID=00:00:00:00:00:00

V/12:52:51.092 WifiStateTracker( 940)

Changing supplicant state: FOUR_WAY_HANDSHAKE ==> DISCONNECTED

I/12:52:51.085 wpa_supplicant( 1773)

CTRL-EVENT-STATE-CHANGE id=5 state=0 BSSID=00:00:00:00:00:00

V/12:52:51.082 WifiMonitor( 940)

Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]

I/12:52:51.079 wpa_supplicant( 1773)

CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys

V/12:52:50.072 WifiStateTracker( 940)

Changing supplicant state: FOUR_WAY_HANDSHAKE ==> FOUR_WAY_HANDSHAKE

I/12:52:50.069 wpa_supplicant( 1773)

CTRL-EVENT-STATE-CHANGE id=5 state=5 BSSID=00:00:00:00:00:00

V/12:52:49.062 WifiMonitor( 940)

Event [CTRL-EVENT-STATE-CHANGE id=5 state=5 BSSID=00:00:00:00:00:00]

W/12:52:48.465 process_monitor_widget( 1846)

Log retriever started, filtering on null
[HD2 Android NAND Development] dorimanx:
i see that it's trying to connect to your router, and fail...

so with 7.0 it's connect right away?

i will check the wifi driver, didnt touched thou..
[HD2 Android NAND Development] dorimanx:
:p well that what i understood from one of your post, that you told us the bad news :)

you found that it's stuck on min of 1000mv and we cant really go under it,

i know that cpu boots with 1250 :) it's set in kernel config...

post was about min voltage that we can go...

so as you found, it's stuck on 1000 any way..

correct me if i am wrong :)
[HD2 Android NAND Development] madsponge26:
No problems for me 7.1.. running smooth no DC and whatsoever.. battery drain? I'll check later.. miuiv14+7.1
[HD2 Android NAND Development] elesbb:
Well fake or not it sure as hell helped me :)

When i would read my ebooks, i had my 96Mhz frequency set to 800 mV and i had a drain of 96mA now on the kernels that i cant change i am up to like 120+mA drain at the same frequency. So it definately did do something.

Yes i agree. It took me quite some trial and error to figure out the ideal minimums for each frequency(ended up leaving the higher clock speeds alone) i would love to get this back in newer kernels ;)
[HD2 Android NAND Development] hartleyshc:
The blocks aren't very big. I just bumped my system up to 200mb to cover my one bad block. Just make sure you're a few mb over what is required. If 165mb go to 170. The blocks are only a few KB in size iirc. So two bad blocks isn't that big of a deal.
[HD2 Android NAND Development] dorimanx:
i will set the lowest allowed range to 800.

if it's helped you, then why not, it's will kill(hang) 80% of phones if they try to reduce to 800... :)

including my phone, you are lucky i guess..
[HD2 Android NAND Development] elesbb:
This got me thinkin, if the min and max voltages that i set in the init.d script, were truly fake, why then does it freeze at times when setting them too low? If it was stuck at 1000 then it technically should never freeze as its not going below 1000. But however it does freeze cause the voltage is set too low. I personally believe that they are not fake and they do actually do a lot. Just as Rick said before, it is a difficult task to figure out what voltages work best for your device.

---------- Post added at 02:03 PM ---------- Previous post was at 02:00 PM ----------

THANK YOU! :)

I guess i am lucky ;) cause 800 works and puts drain to 96mA so that makes me happy ;) Thanks so much Dorimanx for adding it back. If you dont believe me that i can attain 800 i'll post screenshots. Plus you are right though, if i set a higher clocked frequency to 800 it will freeze.
[HD2 Android NAND Development] Rick_1995:
static struct regulator_init_data tps65023_data[5] =
{
{
.constraints =
{
.name = "dcdc1", /* VREG_MSMC2_1V29 */
[B] [SIZE="4"] .min_uV = 1000000,[/SIZE]
[SIZE="4"].max_uV = 1300000,[/SIZE][/B]
.valid_ops_mask = REGULATOR_CHANGE_VOLTAGE,
},
}
......
}

There's no question of fake or not, if you don't believe any of us, download the source code of any kernel, go to arch/arm/mach-msm and open the file board-htcleo.c then search for tps65023_data and look at it yourself :)

Linux's regulator driver checks if the requested vdd level is above or below these constraint values, so can't go below 1V and above 1.3V

Additionally you can trace the code from acpu-scorpion.c for changing vdd to the point where linux checks the device constraints and alters the value of requested vdd.
[HD2 Android NAND Development] dorimanx:
so what if i set the min_uV to 950000 and max_uV to 1350000

so we can get reduced voltage and boosted for overclock!

then maybe 1.6 or higher speeds can be stable!?

What do you think?

EDIT!

HOLD ON!!! what the HELL! :)

this is my arch/arm/mach-msm/board-htcleo.h

/* Voltage driver */
#define HTCLEO_TPS65023_MIN_UV_MV (CONFIG_MIN_CPU_VOLTAGE)
#define HTCLEO_TPS65023_MAX_UV_MV (CONFIG_MAX_CPU_VOLTAGE)

i set the CONFIG_MIN_CPU_VOLTAGE to 800 and CONFIG_MAX_CPU_VOLTAGE to 1350

this is my board-htcleo.c

static struct regulator_consumer_supply tps65023_dcdc1_supplies[] =
{
{
.supply = "acpu_vcore",
},
};

static struct regulator_init_data tps65023_data[5] =
{
{
.constraints =
{
.name = "dcdc1", /* VREG_MSMC2_1V29 */
.min_uV = HTCLEO_TPS65023_MIN_UV_MV * 1000,
.max_uV = HTCLEO_TPS65023_MAX_UV_MV * 1000,
.valid_ops_mask = REGULATOR_CHANGE_VOLTAGE,
},
.consumer_supplies = tps65023_dcdc1_supplies,
.num_consumer_supplies = ARRAY_SIZE(tps65023_dcdc1_supplies),
},
/* dummy values for unused regulators to not crash driver: */
{
.constraints = {
.name = "dcdc2", /* VREG_MSMC1_1V26 */
.min_uV = 1260000,
.max_uV = 1260000,
},
},
{
.constraints = {
.name = "dcdc3", /* unused */
.min_uV = 800000,
.max_uV = 3300000,
},
},
{
.constraints = {
.name = "ldo1", /* unused */
.min_uV = 1000000,
.max_uV = 3150000,
},
},
{
.constraints = {
.name = "ldo2", /* V_USBPHY_3V3 */
.min_uV = 3300000,
.max_uV = 3300000,
},
},
};

as i say... light years from original code :)

Kernel 7.1A uploaded with min 800mv and max 1350 :)
[HD2 Android NAND Development] elesbb:
Well im sure dorimanx already changed that value before compiling. im not arguing with you. Im just saying from an end user experience that my vdd_levels_havs work.

Ha i figured you already had that changed. See i knew i wasnt delusional xD i knew something was happening which allowed me to set 800mV it works perfectly for me anyhow. So please add it back and i'll be happy :)
[HD2 Android NAND Development] dorimanx:
download 7.1A and update busybox, it's now latest 1.20 :)

i forgot to change the name in aroma, it's display 1.19.4
[HD2 Android NAND Development] Rick_1995:
Hey,

I almost forgot, I wanted to ask you, How'd you generate frequency table for speeds above 998MHz or 1198MHz, Qualcomm didn't release any info about pll limits, multiplier limits, oscillator limit or internal clock logic (hardware) for rounding of clocks and keeping them in limit etc..

This could be a reason why there's not much increase in speed after 1.2 maybe the cpu just rejects that clock because it is out of phase with the pll being used ?
[HD2 Android NAND Development] Aternus:
Did you remove the coloring when compiling busybox? (to fix the ADB whitespace issues with Windows)

Thanks
[HD2 Android NAND Development] dorimanx:
no, i cant find the damm config for it, it's has huge configuration file, and i dont know what reflect this addon.

if any one know what i should set off in busybox config to get rid of it, please tell me..

sorry i have searched, but i have no idea!

but i have updated to 1.20 + all patches from source site :) and enabled all new addons and features!

and it's still smaller than 1.19.4 :)
[HD2 Android NAND Development] elesbb:
What do you mean by "update busybox" im not exactly sure how to do that. I thought it was just a file in the /lib directory.. sorry for my confusion xD
[HD2 Android NAND Development] dorimanx:
about overclock, it's actually 1198 = 1602 but with 1350mv

cpu cant work faster :( if i set more clock to freq cpu stall..

it's not really 1.6Mhz i have posted about it before...

no cheating, just added more scaling and added more voltage than was to 1198 by default.

and my 1198 has less clock, than in tytung kernel. (so for me 1198 is not max speed! the 1602 is.)

see the avs.c in arch/arm/mach-msm/ and acpu-scorpion.c (i think the name is slight different, i am away from my kernel server now.)
[HD2 Android NAND Development] dorimanx:
in kernel menu you have option to install new busybox :)

use it!

brain = power! :) (no disrespect!)
[HD2 Android NAND Development] Aternus:
Its here:

http://git.busybox.net/busybox/tree/coreutils/ls.c

You need to define a flag for it to compile without color support.
[HD2 Android NAND Development] elesbb:
not my brain xD i feel really stupid :D hahahahahaah
[HD2 Android NAND Development] dorimanx:
Cool, i will make it so...

but i am not connected to my server now..

it's will be fixed as soon as i can :)
[HD2 Android NAND Development] dorimanx:
:D just follow all the great devs and you will be one if you like!
[HD2 Android NAND Development] elesbb:
Will do sir! Thanks for your awesome work! Maybe one day i jump in with ya and tinker around with some kernel work myself! Id like to make a ROM some time soon.
[HD2 Android NAND Development] zyclone:
wifi

Wifi don't work for me with 7.1 & 7.1A:confused:

Thanks dori for continue your work.
[HD2 Android NAND Development] linuxis:
Yes, 7.0 6.9 connects, dalvik cleared, configured new connection. 7.1 fails, older kernels connect immediately
[HD2 Android NAND Development] maddoc1007:
partial wakelocks

with 7.1a kernel it says in better battery stats that alarm accounts for 59.9% of partial wakelocks also find that battery drains very quickly compared to 6.8 kernel would that have something to do with the partial wakelocks?
[HD2 Android NAND Development] dorimanx:
ok, i will see what i can do...

maybe i have changed some setting...

thanks for report..
[HD2 Android NAND Development] dorimanx:
well if wakelocks are present, then battery drained faster, i have ported wakelock code from 2.6.35 kernel, maybe something there should be tuned, or i can revert the changes, thanks for report.
[HD2 Android NAND Development] Hammerfest:
code tags... they make everyone happy...
[HD2 Android NAND Development] Hinnne:
Yes there is alarm manager Wakelock.so battery drain in standby is high.please look into this.

Thanks.

On my Acer a500 I have even more of this standby drain with new ics ROM.it must be something with new code which is there also used.
[HD2 Android NAND Development] Mappazza:
... :confused: ... back to senior member? What's happened Dori? :(
[HD2 Android NAND Development] Hammerfest:
srsly, wtf over.
[HD2 Android NAND Development] Aternus:
Bugs with 7.0, 7.1 and 7.1A

:

* Very high battery drain

* Slower boot time compared to 6.8, 6.9

Also some of my myMIUI ROM users reported weird activity when it comes to booting up, specifically - launcher icons locations change by themselves...
[HD2 Android NAND Development] Wojtas98:
with 6.9 my phone freezes - i can't wake phone (must remove battery)

with 7.1A battery drain is about 4-6mA, phone wakes perfect but wifi not working, pops up an error when switching.

i use American Android SD version.
[HD2 Android NAND Development] hengsheng120:
I don't think the kernel is compatible with AOSP roms. Try fikret or rafpigna.
[HD2 Android NAND Development] zyclone:
This Kernel works very well on AmeriCanAndroid SD

The last good for me 6.9 build.

You right with 7.1 and. 7.1A wifi not working.

Start from scratch.

This kernel is the smoothest and fastest kernel i know.

This kernel is also the most supported one.

Cheers
[HD2 Android NAND Development] maddoc1007:
partial wakelocks

these is also wakelocks in event log services which is also high when phone is in standby....

Wakelocks

=========

AlarmManager (Android System): 2 h 17 m 25 s (8245 s) Count:266 37.4%

Event Log Service (Google Services): 1 h 3 m 58 s (3838 s) Count:13 17.4%

---------- Post added at 08:43 PM ---------- Previous post was at 08:36 PM ----------

What is code tags? i know nothing of codeing etc
[HD2 Android NAND Development] dorimanx:
thanks, i need to remove some commits that i added, something is wrong, no doubt.
[HD2 Android NAND Development] Screemi:
[/code][/code] <- remove first / and add your text between ][

like this
[HD2 Android NAND Development] kobers:
found a way to solve ?

thanks

kobers
[HD2 Android NAND Development] Nixda99:
Have no WIFI problems with 7.1, 15MBit/s Down, 0,8MBit/s Up.:D.

7.1 is top, very fast, no problems so far (runs since 2 days).

Thanks to all devs!
[HD2 Android NAND Development] maddoc1007:
more partial wakelocks

more partial wakelocks on 7.1a kernel running 3.1.6.2 rom

show keyguard (Android System): 9 m 16 s (556 s) Count:11 15.6%
[HD2 Android NAND Development] zyclone:
hello again

Latest Fikret Kernel don't work on SD rom's,

because they are based on .35.

.35 kernel won't work on SD

Latest kernel that works is .32

Alternative to Doris Kernel you can test tytung R14

Good luck
[HD2 Android NAND Development] NLsalvador:
Update:

After 2 days of using this kernel with TyphooN CyanogenMod 7.2 is must say if have the best results i ever had. Kernel is very stable and the battery drain is good. Haven't had issues so far with it. Only sometimes when i travel by train, i have a totally disconnection (no signal). But this lasts 10 secondes and then it reconnects. Is there a fix for it? I'm using Magldr.

I'm using Kernel 7.1 and i saw tha there is a 7.1A now. Is there a huge difference between it? I'm not using Set cpu or anything so if it's just about undervolting i don't think it's necessary to flash it.

Guys, does onyone has the same problem as i do? Let me explain, a few weeks ago i bought a new phone (HTC Sensation) and i wanted to sell my HTC HD2. But somethings kept me from doing it because i love flashing my HD2 so much. Therefore i decided to sell the Sensation again! I just can't live without my HD2..:( I hope that Dorimanx will be here for a long time! Because his kernel updates are great for my phone.

Greetings,

Arjan
[HD2 Android NAND Development] Spaqin:
Hey,

Any plans of adding USB Host support?
[HD2 Android NAND Development] triggaz:
Dorimanx aby chance of 7.1 HWA for experimental use with Nuke 2.3????

Wysyłane z mojego HTC HD2 za pomocą Tapatalk 2
[HD2 Android NAND Development] boss_4:
Since 6.3 will not boot / start

Hello dorimanx :)

your work are great :))

But since version 6.3 it will not boot myMiui :confused:

I have yet myMiui v14 with Dorimanx 6.0 .

But since the version 6.0 has changed a lot .

I have already run Task29 and take the partition as it says in the instruction.

SD-Card is formated :( .

I hope you can help me :(
[HD2 Android NAND Development] Aternus:
You should try installing a clean version of myMIUI without a SIM card and with a cleanly formatted SDCard (preferably a new card / one that certainly works).

Also make sure you have the right HSPL and Radio installed. For more information you can read the first post on the myMIUI thread, available by clicking my signature. :)
[HD2 Android NAND Development] jjmmll:
about wifi problem

@Dorimanx

about wifi problem,

I found that, if I activate the wifi from the program Tasker, everything works fine, however if activated from the settings page, does not detect wifi networks.

kernel 7.1

rom 3.1.6.2 + system 3.1.8