yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam ROM Development] nvsbv:
Help me Urgent

I flashed official HTC hermes rom 6.1, but after the first use, it suspended and then i got stuck at the start up screen and never log into window again. please help me. I am using Dopod 838 Pro
[8525, TyTN, MDA Vario II, JasJam ROM Development] FCW:
Ive not had a problem with my rom. Could it be to do with the version of hermes it is. mines herm100. I dont think its the big storage as Ive read ppl have experienced it with standard storage
[8525, TyTN, MDA Vario II, JasJam ROM Development] BCX7:
i've found it's after i recover my SMS with pim backup or a similar program. if after the hard reset i dont recover my sms, but recover everything else, it'll run or days. but if i recover them, the hermes will freeze within the same day.

i'm going back to wm6 or wm5 depending which one proves to be the most stable. i need my phone to be very stable for my job. (haha, windows mobile and stable in the same sentence). i've actually started to carry around my nokia 6230i incase my hermes stuffs up so then i can wack my sim in there.
[8525, TyTN, MDA Vario II, JasJam ROM Development] tjlabais:
as a rule, dude. you don't play with your hermes if you depend on it for something important. the wm6 dopod official is stable enough for daily use.

as for wm6.1 after recovering sms, you have to wait for sms threading to read all recovered messages before you even start using sms and messages. you will notice that after recovery, the status bar will flicker.

cheers
[8525, TyTN, MDA Vario II, JasJam ROM Development] tjlabais:
it's not the version. we checked this already.
[8525, TyTN, MDA Vario II, JasJam ROM Development] mmick:
I tried again a WM6.1 version (this time PDACorner V7 by USB update) and it still freezes (sometimes takes hours, sometimes a few minutes).

4 different WM6.1 packs and all freeze at random. I´ll try a WM6.1 more with SD energy off to see if it works and I´ll post the result.
[8525, TyTN, MDA Vario II, JasJam ROM Development] galaxys:
which other 3 roms froze on u?
[8525, TyTN, MDA Vario II, JasJam ROM Development] mmick:
Tried again with SD Management *off* and also changing the Infrared status.

It frooze!

TNT

Faria

CRC

TNT´s ROM is the fastest but also freezes faster. I hope TNT solves the problem because I love his ROM :(
[8525, TyTN, MDA Vario II, JasJam ROM Development] cirial:
Damn, I was anxiously awaiting flashing a WM6.1 release, but all these hard reset stories have me nervous now. So no one has a successful cooked 6.1 ROM that is stable? :(
[8525, TyTN, MDA Vario II, JasJam ROM Development] mmick:
I just installed this one

">>> 30 March 2008 <<< HTC_Hermes_S64_WM_6.1_HTC_WWE Lite"

and it also crashes frequently.

I don´t know what´s going on but I think it´s something with the WM6.1 core.

Schaps WM6.0 works flawlessly
[8525, TyTN, MDA Vario II, JasJam ROM Development] IVAces:
Which version of Schaps?

I am running a WM6.1. Version 4.31. As you can read from one of my last post, It froze up on me and I lost all my contacts; same as everyone else. When it froze up on me, I had just set up a wireless VPN and an Exchange Push client email account.

It did it to me twice. Both time required a hard reset to get my contacts to show up again until I figured out to uninstall and reinstall Yahoo!go to sync my address book:It would tell me that my addresses were synced even though nothing was there.

To me it looks like two possible problems; radio and/or the contacts database.
[8525, TyTN, MDA Vario II, JasJam ROM Development] mmick:
I have changed to Shamanix Ultimate V2 (based on Schaps 4.31). It´s very fast for a WM6.0 ROM (faster than Schaps v4.31) and with great stability.

No WM6.1 ROM has given more than a few hours of stability. I flashed WM6.1 ROMs both with card and SD, both full or lite and from several makers.

Both Schaps 4.31 (slow) and Shamanix (Schaps 4.31 but fast) updated from SD card work flawlessly.
[8525, TyTN, MDA Vario II, JasJam ROM Development] dioxda2:
No Freeze for 1 week, no sleep to death, no delay power on ....... Sounds Good? ^_^

[size=+3] Faria-R32 / Dr Puttingham WM6.1 HERMES[/size]

Also, personally I had the rom tuned in Harmonized setting for Task manager (WkTask ) and Start menu (QuickMenu), both exists for best efficiency.

Asian Region added,

VBruntime hooked.... and many customization... ^_^

so far..... more than 1 week, all problems like freezed, deep-sleep, lagging... now NO MORE !!! )

(P.S. my device = Hermes 100 / Dopod 838pro)

WkTask............... QuickMenu..................Asian Region.....................VBRuntime ^_^

very smooth....... ^_^ ............... ^_^
[8525, TyTN, MDA Vario II, JasJam ROM Development] markafreeman:
I've tried 4 WM6.1 roms and not found any that have been stable enough yet (thank god for PPCPimBackup) so it's back to Shamanix Ultimate UC for me. I can cope without threaded sms for now and netfront is a much better browser than the microsoft offering anyway. I'm sure this will get sorted eventually but for now I'll stick to 6.0.
[8525, TyTN, MDA Vario II, JasJam ROM Development] tjlabais:
I'm running 9 days already without any problem. So, the solution to flash your device with a full rom official at&T latest prior to any wm6.1 solved the problem. Since you, mmick, flash using SD card, you will always get the freezing problem unless you flash your device first official rom with standard flashing. then flash 6.1 with sd.
[8525, TyTN, MDA Vario II, JasJam ROM Development] crusti:
wm6.1

ive tried most of the 6.1s, my 2 favourites and schaps and starbase64, they all look nice, but im waiting for K's 6.1, i keep going back to try his beta (best camera by far and hes gonna add slipperyducks vista theme with slithers C++ Cube :) ) , its a long way from ready, let hope he will come back to finish it off

i dont have the hard rest problems most seem to have.

My problem is the screen staying white and bluetooth, i use schaps advanced config to set the glyphs cache to 64kb, that seems to stop the white screen but the bluetooth problem is on all the 6.1s - havebt seen this issue anywhere else

all the wm6 my bluetooth gps finds instantly, but all the 6,1s get to the pairing bit and fail :(, but sometimes in s64 rom the gps reciever will try to pair with the phone and then its all fine
[8525, TyTN, MDA Vario II, JasJam ROM Development] epsilonkore:
Absolutely correct, my unit would suffer a slow down, then lock up, and upon reboot never fully boot again until a reflash. Flashing with ATT first, then flashing back to ANY of the 6.1 ROMs i have tired (Faria, Schap, Shadow) resulted in stability where it was not before with any of those. Thanks TJLABAIS!
[8525, TyTN, MDA Vario II, JasJam ROM Development] ricrellim:
I flashed to AT&T WM5 then Faria Clean 6.1 It is very fast very stable and I have never experienced a lockup in over a month.
[8525, TyTN, MDA Vario II, JasJam ROM Development] muskangul:
hi

i have insalled official rom wm5 of imate jasjam from imate

os5.1.195(build 14955.2.3.0/0

radio 1.07.03.10...

then i have installed this rom 6.1 but still same problem

after restarting rom hangs
[8525, TyTN, MDA Vario II, JasJam ROM Development] stabloid:
I am currently using CRC's ROM, and have found it to be EXTREMELY stable. I have had not one lock up, and not even worried about it hard resetting.

I went to official AT&T WM6 ROM prior to flashing, as I have with all recent ROM updates, but with Faria/Dr Puttingham 6.1, and TNT 6.1, I had a lot of problems.

Both of these ROMs have a lot of extras, where CRC's ROM is quite minimal.

CRC's ROM does run a heck of a lot slower than the others I have tried, but its stability has kept me with it as I use my device all day as a service engineer to obtain wiring diagrams/technical info when there is none present with the equipment.

It appears to me, that this could be an operating speed related issue, and that our poor little Hermes just can't run flat out with all the little extras we put on them.

Just my tupence worth... hope it helps.
[8525, TyTN, MDA Vario II, JasJam ROM Development] greatbal:
I used CRC without any problems. A lot slower than the other "fast" roms which proved to be very unstable for my device, Cingular 8525, but at least CRC's rom hasn't let me down.

Then I tried Shadow CE 2.1, and to my surprise, running it now for 3 weeks straight, no lock-ups and hard resets! It was a surprise because Shadow 2.1 TE on the other hand was giving me problems.

Shadow 2.1 CE is fast and stable for me. Could the random freezes and lock-ups is caused by any in-rom installed apps? I don't know... BUt I'm happy with Shadows's Clean Rom. It's bare, yes, but it's fast and stable! :)

Oh, BTW, I've installed tons of apps on Shadow CE already, and still no lock-ups. :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] rafalmag:
I tried CRC 12 release 10 - it froze during Tomtom 6 installation. Then I soft-reseted and it locked at second splash screen. Hard reset then. And it froze every time when i clicked "Start"...

Then I downgraded to release 9 - I am still testing it, but no problems at all !
[8525, TyTN, MDA Vario II, JasJam ROM Development] crusti:
is anyone else haveing wm6.1 bluetooth isuses,? all the new roms i've tried cant stay connected to my bluetooth gps, some times it'll pair ok, then i can set com porti but then i keep getting the message the gps wants to connect to me, over abnd over again, i dont get this on any wm6 roms

anyone have the same problem?

does anyone have any suggestions?
[8525, TyTN, MDA Vario II, JasJam ROM Development] angelica21188:
freezing

yup...had the same dealio.tried a lot of ROMs and i had this prob with the 6.1 and i freaked cuz i was like "wtf i bricked my phone!!!ahh!!!" but i just re-flashed the phone with schaps latest ROM and now it works fine.
[8525, TyTN, MDA Vario II, JasJam ROM Development] muskangul:
--------------------------------------------------------------------------------

the only rom that hasnt froze on me has been CRC's rom. All the others seem to suffer from this weird problem
[8525, TyTN, MDA Vario II, JasJam ROM Development] Phil_123:
Unfortunately my Hermes with CRC's PHKv12r10 ROM, Radio 1.54.30.10 flashed died like this too.:( And yes I flashed AT&T's offical ROM before flashing it to CRC's.

Now I'm flashing AT&T's official ROM again, then lagoskon's build 19400 ROM, then radio 1.47.30.10. Let's see what happens.
[8525, TyTN, MDA Vario II, JasJam ROM Development] FCW:
like in post 10 i think it could be to do with the radio rom compatibily
[8525, TyTN, MDA Vario II, JasJam ROM Development] vasp2005:
IMO these hrs, sods are in some link with bluetooth stack. Always got it when did something with BT. - i.e - connecting devices, installing app which tryed turning on BT byself, using bt GPS device and so on. And never got HRs with BT switched off.
[8525, TyTN, MDA Vario II, JasJam ROM Development] kivo:
I discovered the same phenomena too. No matter which Cooking ROMs are, they all have this problem - WM6.1's issue should be.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
I don't think so myself. I flashed the official Dopod ROM with 1.47 radio because that one works best here for me. Both my ROM and the PDAViet I was playing with HR'ed within hours (and I reflashed with the Dopod each time, fresh, before these 6.1 BS ROM's)

Since then I have flashed the AT&T 3.62 with the 1.54 radio and flashed both mine and the PDAViet 19400 ROM and ran with no problems. I've got three clients running our Clean ROM with the 1.47 radio from the first day we released it, no HR's or freezes. I DID flash the AT&T first, HardSPL7, flashed the 1.47 radio then the Faria Clean.... Looking back, that's one month :) ...

Just my observations... :cool:
[8525, TyTN, MDA Vario II, JasJam ROM Development] greatbal:
I used to have ramdom freezes and HR's. but when i followed Dr Puttingham's procedure in flashing WM6.1 roms (with Radio 1.47 as it works best in my region), i could flash any roms without any problems anymore. Using PDA Viet Build 19701.1.1.0 PV DVH B&C at the moment. Loving it! :)

Dr Puttingham's Procedure:

http://xdaforums.com/showpost.php?p=1990320&postcount=6

Kudos to Dr Puttingham! :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
I don't believe that this a WM6.1 issue but rather BigStorage. I had the exact same issues with WM6 BigStorage ROM's....
[8525, TyTN, MDA Vario II, JasJam ROM Development] klabton:
Problem fixed
[8525, TyTN, MDA Vario II, JasJam ROM Development] galaxys:
Doc, I agree the culprit is Big Storage & no Extended rom with WM6 or WM6.1
[8525, TyTN, MDA Vario II, JasJam ROM Development] CRCinAU:
I'm going to chip in my thoughts... I think it goes down to the windows build in use...

19199 seems stable as a rock.

19209 seems to be stable as a rock on SOME devices, glitchy as all hell on others.

Now this is the interesting part - I haven't been able to find anything in common between the devices that don't work properly with build 19209. I am thinking that it's some kind of compatibility bug. None of my ROMs are BigStorage, and all have an Extended Rom - so this rules out the issues with BS - unless maybe that's another symptom of a buggy Windows Mobile base?

I tried picking apart someones build environment for 19400 - but even with the default packages and XIP I couldn't get it to boot at all. This leads me to believe faulty package, but not 100% sure.

I haven't been able to find anything newer than 19400 anywhere, so my development has pretty much stopped at the moment.
[8525, TyTN, MDA Vario II, JasJam ROM Development] gregma:
And using that exact same procedure, and the exact same PDAViet build, and I get hard resets within a couple of hours. However, I have NEVER had a hard-reset on a Non big-storage 6.1 ROM. And although I asked once for someone with a big-storage ROM to create a non big-storage ROM to verify this, I never got any traction.

I'm convinced also that it's big-storage and 6.1.
[8525, TyTN, MDA Vario II, JasJam ROM Development] galaxys:
FYI...DVH's latest build is 19701. Also, my ref to Big Storage / no Extended rom issues is when its already on the device before flashing the next cooked rom. The new flashed rom just does not 'sit' right for some reason, and U can almost bet there will be lockups (until you flash the official to straighten things out). Keep up the good cooking and testing!
[8525, TyTN, MDA Vario II, JasJam ROM Development] CRCinAU:
Yeah - the release of 19701 I've been able to find is an already cooked ROM. I need the source of that to be able to do much with - otherwise things become very hit and miss.

Ah - I understand what you mean about the BS ROMs now, maybe it's something to do with the partitioning of the flash space?
[8525, TyTN, MDA Vario II, JasJam ROM Development] brownianmotion:
One thought on this note: I finally borrowed a Windows machine, and ran the AT&T OEM ROM update believed to repair this issue. I used USBSnoop to capture the process, so I could see if there was anything interesting going on (and possibly add that to pof's HTCflasher, so I wouldn't need a Windows box in the future)...

One thing which stood out: after issuing the 96 "wdata" commands to upload the ROM, and getting the NBHUpdateComplete response, the RUU sets the progress bar to 100%, issues a "task 28" (format NAND), then issues the "ResetDevice" command.

Looking at the HTCflasher source code, it doesn't do the "task 28". Does anyone know whether the CustomRUU's do?

If they don't, then the suggestion of bad formatting/partitioning sounds likely, and the fix could be as simple as "task 28" ...

Edit: I realise that we don't always want an RUU to issue a task 28; especially when it's being used to flash something other than an OS nbh. Still, it might be worth someone who's getting the hard resets to try it, and see... I'll keep looking through the snoop logs (all 400MB of them) to see if there's anything else which looks interesting. If anyone else wants a look at them, I'm happy to share.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Dr Puttingham:
Wow, great troubleshooting brownianmotion! This DOES sound interesting indeed...
[8525, TyTN, MDA Vario II, JasJam ROM Development] CRCinAU:
I had a quick discussion on IRC with Olipro and cmonex - it seems that the CustomRUU does not run a 'task 28'. This means in theory, it would be wise to flash a new ROM, then perform a hard reset manually.

This should have the same result as if the CustomRUU issued a 'task 28' command.

It would be interesting to see if this solves some peoples issues.
[8525, TyTN, MDA Vario II, JasJam ROM Development] r3d3:
I don't believe that this will solve the problem. The issue forces you to perform a hard reset anyway. And after performing a hard reset the problem still exists...
[8525, TyTN, MDA Vario II, JasJam ROM Development] tjlabais:
I agree. In the first part of this thread, I mentioned about using the RUU from the AT&T official to update my Hermes, but I still ended up with a freezing device. AND I also hard reset manually after flashing... :rolleyes:
[8525, TyTN, MDA Vario II, JasJam ROM Development] brownianmotion:
Exactly what I was thinking... Well, with the clarification of "hard reset manually" by issuing task 28 in mtty/minicom/cu/HTCFlasher.

I realised this, whch is why I hadn't used the term hard reset. There might be a difference between a L+R+Reset Hard Reset (which is our current temporary resolution), and a task 28 Format NAND (which

might

be a permanent resolution - no promises).

I understand that there are a few people like yourself for whom the problems have persisted, which is confusing. I've had my current ROM (post-AT&T) for about 7 hours, so I don't yet know if I'm in your camp or not...

But the majority of feedback about this method so far is positive. I don't know what the problem is, I'm working with the theory that some other people might have found a magic incantation which provides a cure for them, and I'm just trying to distill out what part of their magic incantation does the trick.

If you or anyone else finds a different magic incantation which works for you, I'll try and find what distinguishes that from what we're doing so far.
[8525, TyTN, MDA Vario II, JasJam ROM Development] gregma:
I've tried this many times. In the most recent case of the PDAViet's recent ROM which hard resets for me after a few hours, I have tried flashing an official AT&T ROM first, then PDAViet (hard reset) and I've tried flashing an official AT&T ROM then doing a "task 28" (hard reset).
[8525, TyTN, MDA Vario II, JasJam ROM Development] gregma:
I will say it again. To truly find out whether it is BigStorage or not, the easiest way would be for a ROM cooker that has a 6.1 ROM with big-storage (that people are having difficulties with), and produce an identical ROM with big-storage removed. I'd LOVE to do this myself but I just can't figure the cooking out.

Then those who are having problems (I'd be happy to volunteer to do this part) can run the big-storage, wait for the hard resets to verify it happens... Then put on the non big-storage and see if they experience any hard resets. If they don't, then we know for sure what the problem is. If they continue to see hard resets then we know for sure it's not big-storage.

I'll ask again. Will any of the fine cookers be willing to create a non big-storage version of their current big-storage ROM?
[8525, TyTN, MDA Vario II, JasJam ROM Development] brownianmotion:
Fair point. I might be barking up the wrong tree. I'm still trying to figure out what else might be different.

One other thing to keep in mind is that there are non-BigStorage ROMs which suffer from this problem... CRC's v10, for example. So BigStorage doesn't seem to be the only factor involved.

I'd love to see the differential analysis for BigStorage on vs off for some problematic Cooked ROM, though. You're right - it would shed some much-needed light on the problem.

Edit: for the record, I've _never_ used BigStorage. I've only had official OEM ROMs, and CRC's r9 and r10.1. Problems started with 10.1.
[8525, TyTN, MDA Vario II, JasJam ROM Development] gregma:
I'm currently using MRH's 6.1 ROM and so far no hard resets. Once I've run that for a day or two I'll try CRC's.
[8525, TyTN, MDA Vario II, JasJam ROM Development] its right:
just for a little help;

you have to install any 3rd party app to give you safe startup mode feature just in case, like spb pocket plus.
[8525, TyTN, MDA Vario II, JasJam ROM Development] kkp:
FARIA-R32-XDA2 ROM clears SMS(all folders) when you soft reset

Can any one help me if there is a fix, i'm using FARIA ROM which is really good, HTC animation, dragon photo.. all works fine but recently noticed that when i do the soft reset its clearing the whole msg in all folders.

Is there any solution for this.

Thanks in advance.
[Samsung Galaxy S7 Edge Questions and Answers] bomblader:
Anyone else had this experience? While I was on Nougat I was getting "tag not supported" for each classic tag I was scanning. However, after updating to Oreo it started to successfully read mifare tags.
[Samsung Galaxy S7 Edge Questions and Answers] Meemo23:
While I was on Android N I could not use my Barclays banking app. It kept saying rooted device even if I Odin flashed and went back to stock. Now on Oreo if I go back to stock I can use the Barclays app np, and if rooted with Magisk I simply tick it in Magisk hide and it works.

I think Oreo is a better base in a long time a lot of things that previously didn't work on N work on O.
[Samsung Galaxy S7 Edge Questions and Answers] jjhaohao:
Hi, are you using Snapdragon or Exynos variant? Thanks
[Samsung Galaxy S9+ Questions & Answers] rdefino:
I just received my Infinity S9 plus and I noticed there is no option in settings-device maintenance-battery-advanced settings for Fast wireless charging. Same with my wife's phone. My friend with Verizon version has it.

Any idea if they disabled this or what?

thanks
[Samsung Galaxy S9+ Questions & Answers] yuppicide:
What are you talking about? Plug in the phone to a fast charger and it fast charges. If your charger doesn't support that then it doesn't fast charge. Same thing with my old LG V20.

Mine fast charges fine, but seems slower than my LG a little bit.
[Samsung Galaxy S9+ Questions & Answers] corallus:
"I noticed there is no option in settings-device maintenance-battery-advanced settings for Fast wireless charging''

Mine doesn't show the setting either on international version.
[Samsung Galaxy S9+ Questions & Answers] Scott:
I have a Verizon phone and I have no such option. I only have an option for battery saving apps and fast cabled charging.
[Samsung Galaxy S9+ Questions & Answers] Cristi10:
It was the same for me. The option appears after you put it on a wireless charger or at least a fast charging compatible one.
[Samsung Galaxy S9+ Questions & Answers] rdefino:
Strange, my friend who has a verizon model has the setting for fast wireless charging.

wonder if they are removing it so the phones don;t over heat...maybe.
[Samsung Galaxy S9+ Questions & Answers] Cristi10:
Like i said, you need to put the phone on an wireless charger and the option appears
[Samsung Galaxy S9+ Questions & Answers] rdefino:
Odd, I tried that already and the settings still don't show. Now I'm not using a samsung fast wireless charger, but it's a fast wireless charger.

Not sure what is causing it not to show.
[Samsung Galaxy S9+ Questions & Answers] Matttrix:
My Verizon S9+ has it (maybe cause I use a wireless Samsung stand up wireless charger daily).
[Samsung Galaxy S9+ Questions & Answers] Scott:
Yeah, that makes sense if you are using a Samsung charger. I am using a standard samsung charge from the... I dont know what device days... BUt yeah, the message says something about fan noise. I do know that my charger has no fan.
[Samsung Galaxy S9+ Questions & Answers] termdj:
Go to settings/advanced features/accessories. There you will find the option for fast wireless charging. For cable fast charging, the setting is in advanced under battery. Stupid that they put it in 2 different places