yashsingh1/xdaforums huggingface dataset:
[HD2 Android NAND Development] Mappazza:
..no problems for me about network checks...all works...will report tomorrow about gps... :)
[HD2 Android NAND Development] Nixda99:
Test Kernel 5.8 Beta 1 (Time 12h)

WIFI: OK

BT: OK

GPS: OK

DATA: 1 time unable to get data (all tried:Flight mode,2G<->3G,APNReset), only reboot did it, now top

WAKEUP: OK

DEEP SLEEP: OK

STABILY: OK

DATA SPEED: very fast

CALLS: OK

SOUND: OK

EARPIECE: OK

HEADPHONES: -

Network Apps: OK

Good things: reaction times nearly a SGS2, like 5.7:D, no wakelocks so far (I know it needs time)

Bad things:0
[HD2 Android NAND Development] dorimanx:
yes, it's super advanced!

it's has deep sleep and fast start and io wait and freq drop to min and max on touch! to give best performance.
[HD2 Android NAND Development] dorimanx:
my hold on on 43! but i reduce to 998 to cool down, then back to 1.5!

insode your phone case there is a silicon pad that placed between cpu and external case, it's transfer heat, so if it's deteriorated in time, it's not do his job, and cpu overheat, and stuck...

you need new pad then...

it's hard to get to it...
[HD2 Android NAND Development] elesbb:
I agree everything is working but it does seem a little slower than 5.7 . I'm talking about both betas 5.8 b1 and 5.8b2 . But I have absolutely no problems with either and its been a full day ! Great work !
[HD2 Android NAND Development] maddoc1007:
bluetooth file transfer

Bluetooth file transfer not working with latest kernel pairs with phone Sony Ericsson arc s connects with car ok but won't transfer files dorimax high end rom swap zram kernel.5.7
[HD2 Android NAND Development] Yank555:
I agree no problems everything is working, except for the Gps wakelock maybe, which is annoying but not too problematic, cured by a reboot.

But battery drain is clearly higher, especially when compared to 3.2 !

I see it in use (SmartAssv2) as well as in standby (conservative) when connected to my car's BT handsfree, where it peaks at around 120mA and with 3.2 it was around 60-80mA, same CPU settings in both cases. Pure standby (unconnected) is fine at 4-7mA, which is the same as with 3.2.

Will put mine to sleep now, plugged to the wall charger, let's see if Gps wakelog is there in the morning (in about 8h).

JP.

PS: Still on 5.8 beta 2 on Hyperdroid CM7 5.9.0.
[HD2 Android NAND Development] elesbb:
I wonder if he didnt include the Bluetooth fix since he's trying to knock out some bugs . But i would love to get the speed back ;) But im patient :)
[HD2 Android NAND Development] SalviaLover:
Is the new kernel 5.7 worth updating on All-in-ine 3.1.2? I'm currently using it with the default 5.4 kernel and I'm not having much issues so far. Battery drain is good and all runs well. The phone does need a reboot from time to time. Sometimes GPS fails to start, but that's bearable. Is the 5.7 kernel much better and worth updating? I couldn't find a version for All in One, just Ultimate unlike 5.3 for example. Is Ultimate suited for all in one 3.1.2?
[HD2 Android NAND Development] themadproducer:
Absolutely.

5.7 aka "Ketchup Kernel"...is the new leader!!! It's labeled as Ultra.

If you want details, just read the last 2 months worth....it's been a battle and Dorimanx has won. Now we/he are just ironing out odds and ends.

---------- Post added at 04:16 PM ---------- Previous post was at 04:11 PM ----------

This morning I reviewed my Current Widget log.

On the most part, I am getting 1-4ma in standby...but usually 4ma.

BUT...lots of spikes...big ones...not steady but very periodic.

Here we go again.

So from my experience in the past...I took a shot and froze MAPS (nav etc) and did a 2hr standby test in the same spot etc., and sure enough...no big spikes, just the normal odd little ones...and standby drain was closer to 2ma on average and even 1ma more often. In standby, I have wifi/3g/bt/gps disabled as well as network location.

Using CpuSpy (killer feature better than SetCpu) it clearly shows Deep Sleep for the majority of the standby time followed by a hint of 96 and 998(my top freq).
[HD2 Android NAND Development] themadproducer:
- Try using Hyper. SmartAss2 does not yet work efficiently in idle and/or standby with 5.7 (not sure about 5.8betas) Dx is going to bring the SA2 from 3.2 to current kernel...unless he already has?)

- when I have a BT earpiece connected and paired in standby, I get super low values with no peaks. (2-4ma)

- also, consider you are using Hyperdroid rom. That may add a factor to the equation.
[HD2 Android NAND Development] Yank555:
Agreed, but I'm comparing kernels on the same ROM installation (hence same settings, apps ...) and just changing kernel between 3.2 and 5.8, so I'd say we can take the ROM out of this equation.

Clearly might be the ROM generating drain on connected BT, but may also be my ~500 contacts syncing with the handsfree, I guess a car handsfree will generate more drain (traffic) than just an earpiece considering the data it is querying from the phone ?

But I see a good 50% higher drain on 5.8 vs. 3.2 on BT connected standby. And as well kind of 50% more on use...

Should only be the governor setup, maybe also voltage setup ... ?

Not complaining, just reporting ;) I'd say we should get it stable, and we're extremely close, and these fine-tunings can be done afterwards.

But for now, even if hyper may be better, for the sake of keeping things comparable for finding the Gps wakelock, I'd rather not change anything BUT the kernel...

JP.
[HD2 Android NAND Development] ph03n!x:
Are you using the ROM's initrd.gz or the kernel's? Maybe you can try the one you are not using?
[HD2 Android NAND Development] themadproducer:
Yank...I agree on the comparison testing that you need to change as little as possible....in order to get comparative results and narrow down the issue.

BUT: if high drain is a concern, then SmartAss2 with kernel 5.7 and up... is a known prove-able issue that can't be ignored. Dx has already responded to my report of this issue and says he will be bringing the SA2 of 3.2... into 5.8 or higher in an attempt to get it back to normal. He also says that even so...HYPER is more advanced. To me, SA2 on 3.2 vs Hyper on 5.7 behave relatively the same.

Hopefully, it will be a simple migration for him and not some other contributing factor.

So you may not be able to know that it is a BT issue causing drain until your CPU governor is stable...right? :D
[HD2 Android NAND Development] elesbb:
I use sa2 with custom settings . Its been blazing fast and has stayed in the range of about 245 to 729 . I'm loving these new kernels !
[HD2 Android NAND Development] iPAQ 6515a User:
[Update]

In last 8 hours I got two hot reboots, I also noticed that phone's preferred network type is GSM only on k5.8 Beta 2 and GSM auto on k5.7. Is it me only?
[HD2 Android NAND Development] vinny13:
Got a BSOD with the latest 5.7 while it was sitting on the charger.
[HD2 Android NAND Development] themadproducer:
- approaching 48hrs uptime on 5.7 without freezes or glitches. I intend to keep testing it so that I may be 99.9% sure that it is my new stable friend! I have run quite a few games, BT commands, conversations, sms, mms, gps...pretty much every major feature...plus a few long charges and a few short ones. I haven't stopped changing and testing kernels so this is the first time in a long time 2 be running near perfect for 2 days straight at 96-998mhz Hyper.

- iPAQ...last time I had my temperature profile in setcpu active, it was set to scale down at 42degrees so I believe I can run it past 39 though I know it gets pretty hot to the touch. I don't think my CPU will run quadrant with 1612mhz or even slightly less...without freezing up. I haven't tried it with this 5.7 kernel yet but I don't plan to OC past 1400 or so anyway. But every cpu is unique and like Dx said..the thermal pad over it will deteriorate over time.
[HD2 Android NAND Development] marzinho:
Same here.

Also, i hade couple freezes while installing app via Google Play.
[HD2 Android NAND Development] Yank555:
As a rule I always use the initrd of the ROM.

For me it cannot be initrd related since I'm having the wakelock in Hyperdroid CM7 5.9.0 now with it's initrd and I had it also (reported a lot of pages back :)) at the time on NexusHD2 GB v3.2a with that initrd starting somewhen around 3.8, so I would say, it's not caused by that :(

JP.
[HD2 Android NAND Development] Yank555:
Drain is not really a concern, but drain by the wakelock sure is, because that really suck the battery empty in too little time :( I will switch to hyper now, since the wakelock started again the second I unplugged my phone a few minutes ago...

So 5.8 beta 2 didn't change that... see attached picture.

It is kernel related, since flashing 3.2 directly removes the issue. It's surely not ROM related, as I had the same issue BEFORE my switch from NexusHD2 GB v3.2a to Hyperdroid CM7. But it could obviously be related to misbehaviour between kernel and my mix of installed APPs, since the APPs are more or less the same on HD as they were on NexusHD GB...

JP.
[HD2 Android NAND Development] themadproducer:
The thing is Yank...your right in theory that the only difference for YOU is that a change in the KERNEL has created this ISSUE for you and your rom. That said, you are still running a different rom and it may be equally possible that your Kernel/rom combo will behave differently than Dx rom + Dx kernel. That's precisely why I changed from Typhoon rom to DX rom on his advice...to take one more possibilty out of the diagnostic loop! Know what I mean? If non of the the Dx rom users experience the issue, then it's less likely that Dx will want to chase the problem down.

Again, if at least ONE or for your sakes...more than one Dx rom user experiences the same issue, then that would give the attention a more serious purpose for Dx. So on that note, has anyone else on Dx rom had the same GPS wakelock as you? I will be watching for it and be sure to let you know if I experience it on my setup. Cheers.:D
[HD2 Android NAND Development] havard20009:
after 12 hrs every things are good and smooth

Kernel-Dorimanx-V5.8-BETA2

thanks bro ;)
[HD2 Android NAND Development] ej2095:
Think i am going blind

Where is the zip file in the GIT so i can add this via cwr

Thank you
[HD2 Android NAND Development] Bologna:
Git display how developers work on their versions of a repository...it's code..

download your zip kernel here
[HD2 Android NAND Development] D3LTA:
Kernel-Dorimanx-V5.8-BETA2

Kernel-Dorimanx-V5.8-BETA2

All fine here no reboot etc...

Oc 245-1612 Hyper

I only have networks dropouts, resulting in connection timeouts in apps and browser stucks....

It was better in 5.7-Beta 3 but not as good as in 5.5 and before!

Network-bug???

what can i try to fix this ?
[HD2 Android NAND Development] SalviaLover:
I don't think so. I flashed the kernel 5.7 to my 3.1.2 Dorimanx ROM and now it fails to connect to the mobile operators. I tried different set ups. Cleared all cache and it still wouldn't work. It just says "No service". It does find the network, but when I tap on it it says its loading and nothing happens. I'll try older versions and get back to 5.3 eventually. I should have followed my gut instinct that said "Never change a working system."
[HD2 Android NAND Development] themadproducer:
Dude, are you kidding me? :confused::D

This whole HD2 thing is one big hack and troubleshoot experiment....not a turn key solution. You need to work it once in a while...like right now!

My 3.1.2 Dx rom was originally a Typhoon rom from last year with Tytung Kernel and a 100 versions in between and it still runs like a top...better than ever really.

Don't give up so easily! You just need to find out what went wrong.

5.7 works. It's a master piece and anyway...kernel installs are reversable.

Check your APN settings for starters and ask questions here.

People will help you. Chin up!! :D

IT'S SOLVABLE!!! ;):D

---------- Post added at 06:23 AM ---------- Previous post was at 06:13 AM ----------

PS Make sure to do a CWM full Backup before a major experiment.

It is like have 9 lives....actually 99999 lives.
[HD2 Android NAND Development] iPAQ 6515a User:
Try changing preferred network type to GSM auto ( use the magic code *#*#4636#*#*)
[HD2 Android NAND Development] zoUphd2:
Hello people .. I have Dorimanx 3.1.2 about 2-3 months and everything was ok .. i have install the new kernel 5.7 and i have a major problem. Last night and the night before that at around 4:30am my hd2 shutdown :( and i say major problem because at morning the programed alarm never ring so i was late to work ... i don't know why that happen it never happen 2 years now that i have the hd2 .. my battery is brilliant (hd2 battery) and it was the first time that shutdown at 50% and the second at 80% ..

I have search for same problem in here but nothing .. maybe someone can help me ???
[HD2 Android NAND Development] SalviaLover:
May I know how to change the APN settings. Sorry if this is a dumb or otherwise uneducated question.

Can't do it as I get "Mobile Network not Available" when I try to dial anything. Otherwise it is set to automatic. When I try from the settings to select my operator "M-TelBg" it says "Registering on MtelBG" and it just sits like this. It eventually gives "Unable to connect to network. Please try again later"
[HD2 Android NAND Development] fgth90:
5.8 beta 2 ULTRA

Hello,

'testing 5.8 beta 1 from yesterday and beta 2 from today.

Absolutely all is working !

Thanks again for all team efforts !

See you,

Franky
[HD2 Android NAND Development] ghenarys:
One day with 5.8 Beta 2 : Everything OK

Keep testing...
[HD2 Android NAND Development] Yank555:
I see what you mean ;)

DM stated the issue was know to him and it was due to long charging probably (a few pages back), so I suppose it is an potential issue on his ROMs as well ... it is at least in 2 different ROMs, Tytung's NexusHD2 GB v3.2a and Hyperdroid 5.9.0.

Let's see how it evolves...

JP.

PS: Tried DM ROM, but WiFi channels above 11 didn't work (his kernel, and the channels worked with the same kernel on HD, and I need them, so ...)
[HD2 Android NAND Development] SalviaLover:
Reinstalling the ROM with the original kernel did not help. It still fails to connect to my mobile operator no matter what I do. Please help. I've no idea what to do. When installing Kernel 5.7 I may have selected some of the options that have "No if you use DX ROM" I did not understand they should not be active for Dorimanx All in One roms so I selected most of them during the first install. Now whatever I do with any settings fails.
[HD2 Android NAND Development] ghenarys:
Reboot in recovery, wipe cache + wipe davlik then in advance, fix permissions and reboot

If it fail too, you have to do a wipe factory reset but you gonna loose all you personnal data on phone (not on SD)
[HD2 Android NAND Development] Hinnne:
5.8 beta 2 working really good.

but battery drain is higher.

more 50 to 60 ma peaks.

in standby 4-6 % per hour.

with k 5.5 it was1-2 % per hour in standby and less peaks.

hope battery drain can be optimized as in 5.5
[HD2 Android NAND Development] Dam4rusxp:
I get a SOD every 2-7 Hours with 5.7 and 3.1.2. I already overslept today because of this. Any possible fix?

EDIT: Is there any way to get the last logs before a SOD happened? I would be really interrested in that.
[HD2 Android NAND Development] SalviaLover:
This didn't help. Restoring a full backup from recovery didn't help either. Should I do Task 29. What method would you recommend to backup my apps and settings before wiping off the device?
[HD2 Android NAND Development] jolas:
1d and 22hrs without soft reset and everything still working great!

(I'm using hyper governor, deadline scheduler and frequency 245-1420MHz)

Sent from my HD2
[HD2 Android NAND Development] themadproducer:
Ok...you have a backup...that's good.

Since you have gone this far, try a clean install of Rom and Kernel and don't do anything but try to get a network connection.

If the clean install gets you back in shape, then you can do an ADVANCED RESTORE of your backup in CWM....restoring DATA and EXT only.

The most important part is APN. This tells your HD2 how to connect to your carrier's data signal. It's very specific and sometimes there is more than one way. Sometimes APN gets set automatically thanks to your SIM card. For me, I have 2 HD2s on 2 different carriers and they both needed manual help from me.

I can't remember the exact path to get to those settings but it's not that hard to find. My HD2 is not with me at this moment. I will write back with the location....unless someone beats me to it.

DID you try the BACKDOOR code for the DIALER that IPAQ advised??? This is a sequence of numbers that allows you to access connection details....you should be able to access them when you don't have a data connection. I will provide more details soon.

---------- Post added at 01:06 PM ---------- Previous post was at 01:02 PM ----------

Try freezing Google MAPS...just see what happens.
[HD2 Android NAND Development] SalviaLover:
Thanks for the comprehensive reply. I will try that. I'll also back up all my apps using Titanium Backup just in case and will be formatting. I tried dialing the code with the dialer, but it was already set to GSM Auto (PRL) What other settings may have to be changed there?
[HD2 Android NAND Development] kikisp:
wanted to ask about schedulers?which is the best to use?
[HD2 Android NAND Development] SalviaLover:
I'm starting to get a bit scared here. Did factory reset and re-installation. It still fails to connect to the mobile operators. Now when I click search networks I get "Error while searching for networks". Any ideas. Shall I do task29? Perhaps a radio re-install? All I did to get here was installing the new 5.7 Kernel on a Dormianx ROM with some features actiavted such as VPN fix and others. I noticed later that it was saying "No if you use DMX rom"
[HD2 Android NAND Development] corrsea:
IMO

VR

Noop

Deadline

In that order. VR may be unstable for some people but I have never had any issues. On kernels that don't support VR I use noop.

Probably best to test them yourself. An app like sd speedtest will give you a good comparison.
[HD2 Android NAND Development] ghenarys:
First try only to reinstall 2.15 radio

If you failed to connect then do a task29,, reinstall 2.15 radio, MALGDR and your rom. Make a backup in recovery if all work fine.

Wipe cache and davlik cache, install Dorimanx kernel without option except "no reboot".

Fix permissions then reboot

Hope it work
[HD2 Android NAND Development] Hinnne:
Ok perhaps that helps to lower it.

but there is a different with battery drain. on 5.5 it is less than with 5.8

so not Google maps makes this different.
[HD2 Android NAND Development] Yank555:
I've been on hyper today and I feel battery drain is better the sav2. I think 3.2 sav2 was better, but not that much better, hyper is fine in 5.8 b2, for me and my usage of the HD2 that is.

Put the baby to the nightly charge, so will see if the wakelock is back tomorrow morning...

Is there anything more I can do to help find the issue ? Any specific detail I should report ... ?

Anyway it's not that bad an issue, I can live with doing a daily powercycle to kill the GPS wakelock, everything else is working just great ! :D

JP.
[HD2 Android NAND Development] themadproducer:
Remind me of the exact steps so I can try to replicate it (once I finish my own messing about)

Please revise this list as necessary (just wrote it to get you started)

- leave gps module on right?

- place phone on charger (while awake or in standby?)

- leave charging until a) fully charged, b) 2hrs more than fully charged?

- unplug charger before turning on HD2 or after turning on HD2

- wake lock shows immediately in the 60ma range (more or less)

---------- Post added at 04:52 PM ---------- Previous post was at 04:27 PM ----------

- GSM Auto (PRL) is what I have in backdoor phone settings.

- but my wife's phone, on a different carrier, works with the setting WCDMA only

Perhaps you can experiment with the various options there followed by a reboot each time. It can't harm. It just requires time.

Check these out first...

settings/wireless and network settings/mobile networks

- Data enabled (obvious...but some new users may miss this one)

- network preferences....this may actually be the one that changed on you since your kernel upgrade. I vaguely remember a USER mentioning that his changed after the latest kernel upgrade. Mine is set to GSM/WCDA(WCDMA preferred) How this works with the other mention Dialer back door settings...I don't know...but I bet that's where your issue is!

- Access Point Names (APNs) This is very important to have correct information here. This will control access to carrier data, sms, and MMS. Sometimes this area is littered with multiple APN's. (automatically preloaded) Recently for my carrier, I did the research and testing and found "an all in one" combination of settings that made everything work perfect. So I have only 1 single APN that does it all! If nothing else works, research your carrier's APN settings via Google.

And if it's not one of the above issues...then your carrier has coincidentally cut you off because you haven't paid your bill! ;);):D:D (kidding...but totally possible)
[HD2 Android NAND Development] arkoser:
try sim card in other phone.
[HD2 Android NAND Development] Yank555:
Hi,

First off, just checked, it's there again, it is daily reproducable :(

- GPS is activated in settings, but not active (no icon shown in notifications)

- phone is placed to the charger, but I use it sometimes in the evening without unplugging, and I leave it in standby for the night. Sometimes it is on in the morning, if I receive an SMS overnight for example.

- I leave it charging way more than 2h after fully charged, probably 6-8h easy. Yesterday I plugged it to the wall at around 22:30, I unplugged it at 7:35 this moring, and it was at ~25% when plugging it in.

- happens in both cases, when I unplug it and it is still in standby, or if it's switched on by itself

- wakelock is instantly there and I've seen 60-80mA if I remember well

As a sidenote, I have 'stay on when charging' activated in settings / apps / developpment.

JP.
[HD2 Android NAND Development] kokotas21:
Using v5.7 with v48 NDT miui. Whereas everything is working very well, and VERY fast. There seems to be a problem with battery consumption. Battery was completely drained overnight.
[HD2 Android NAND Development] dorimanx:
add the mouk locations.

may help.

Sent from my HTC HD2
[HD2 Android NAND Development] dorimanx:
some wakelock stuck, or gps or proximity

we are working on it in beta 5.8.

Sent from my HTC HD2
[HD2 Android NAND Development] themadproducer:
What does that mean Dx?
[HD2 Android NAND Development] SalviaLover:
My card got misplaced for ome reason. After testing on another phone and then back to HD2 it worked. Sorry to waste your time over this.:p
[HD2 Android NAND Development] zenida:
It means that simulate fake location not the one that you are... It's useful for developers when need to test localization system and they are indoor

HTC HD2 will live forever!
[HD2 Android NAND Development] themadproducer:
Happy you got it going. Was it your SIM card your talking about?
[HD2 Android NAND Development] hypergamer1231:
Have a strange issue here I am on 3.1.2 rom and have installed the high end user all goes fine in the 5.7 kernel install but when it comes to zram the install says ZRAM : light user no zram need? and i feel it skips the zram install any way to fix this
[HD2 Android NAND Development] Yank555:
Will check that setting, and we will know more tomorrow ;)

Pff it's time-consuming when we always have to wait 24h for the next result :D :cool:

JP.
[HD2 Android NAND Development] Hinnne:
I have one urgent question.

people say, that they can hear me very bad.

i think mic level is too low so they can only hear me only silently.

how can i raise mic level.

which settings are recommended.

please give feedback very soon.

i use 5.8 beta 2 and 3.1.2 rom.

i will go on holiday tomorrow.

thanks very much.
[HD2 Android NAND Development] elesbb:
Look in your init.d folder for the mic_level file and edit to your liking