Hi guys,
There is a lot of discussion at XDA about the Sleep of Death (SOD) where some devices do not wake up from suspend mode. I still did not figure out exactly which is the cause for this "disease" and I am sure there are plenty of members trying to understand this anoying issue.
I have read lots of complaints with cooked Roms but I also read a few posts from guys with stock roms with the same issue.
There are some opinions that using MTTY or Task 29 will solve SOD but unfortunatly there are still some members not so lucky and still have SOD.
Personally I dont have SOD in my device but there are some members using my cooked Rom and others that have experienced several times the Sleep of Death.
So, share your experience here, what do you think about SOD? what is causing this? How to solve this?
. Is it Windows Mobile leaked releases not dumped properly?
. Is it a Manila issue?
. Is it caused by 3rd party apps or Mods?
. Is it caused by several cooked Roms flashed on top of each other?
. Is it caused by damaged SDCards?
. Is it radio Version?
. Operator network?
. Or like someone said in my thread:
"SOD: Septo-optic dysplasia (SOD) is a rare disorder characterized by abnormal development of the optic disk, pituitary deficiencies, and often agenesis (absence) of the septum pellucidum (the part of the brain that separates the anterior horns or the lateral ventricles of the brain)."
What do you think?
dotcompt said:
Hi guys,
There is a lot of discussion at XDA about the Sleep of Death (SOD) where some devices do not wake up from suspend mode. I still did not figure out exactly which is the cause for this "disease" and I am sure there are plenty of members trying to understand this anoying issue.
I have read lots of complaints with cooked Roms but I also read a few posts from guys with stock roms with the same issue.
There are some opinions that using MTTY or Task 29 will solve SOD but unfortunatly there are still some members not so lucky and still have SOD.
Personally I dont have SOD in my device but there are some members using my cooked Rom and others that have experienced several times the Sleep of Death.
So, share your experience here, what do you think about SOD? what is causing this? How to solve this?
. Is it Windows Mobile leaked releases not dumped properly?
. Is it a Manila issue?
. Is it caused by 3rd party apps or Mods?
. Is it caused by several cooked Roms flashed on top of each other?
. Is it caused by damaged SDCards?
. Or like someone said in my thread:
"SOD: Septo-optic dysplasia (SOD) is a rare disorder characterized by abnormal development of the optic disk, pituitary deficiencies, and often agenesis (absence) of the septum pellucidum (the part of the brain that separates the anterior horns or the lateral ventricles of the brain)."
What do you think?
Click to expand...
Click to collapse
I have ORD for what is worth ....
In all seriousness, we have had that happening in a few roms in the Blue Angel and truth be told, it goes away and comes back (which points me in the direction that it is not hardware). In our case, the most common occurrence of this was when Wifi is on and the device goes to sleep, the BA starts behaving in a weird fashion. It might wake up with lots of stability issues (and sometimes will not wake up at all). It could be that there is some sort of conflict with the radio, but that is just a theory...
I don't think it has anything to do with Manila, I didn't have it in my custom ROM's but still had SOD.
Seems completly random. I can go for days without having it.
Indeed I also don't think it has anything todo with Manila.
I've had it once using 21893 build long time ago, but untill today I didn't face it anymore.
Also no reports by my beta team or in rom thread.
Currently we are trying:
* 23554
* 25012
* 21898
Oemdrivers are Leo 1.72/2.10 base.
Radio's I use are Leo 2.09.51.03_2 and the radio from Leo T-Mob 2.10 to enable 576mb ram on Leo.
It must be build related, maybe build/radio combination no idea actualy.
rgb-rgb said:
I don't think it has anything to do with Manila, I didn't have it in my custom ROM's but still had SOD.
Seems completly random. I can go for days without having it.
Click to expand...
Click to collapse
its the way the files are dumped, if you use properly dumped flash.dio or .nb you wont have the problem...at least i dont. i learned my lesson the hard way with 23008, i think it was the first build that did that and i had all kinds of people with SOD. from then on i always dump the files myself or get them from Da_G and all is well
twopumpchump said:
its the way the files are dumped, if you use properly dumped flash.dio or .nb you wont have the problem...at least i dont. i learned my lesson the hard way with 23008, i think it was the first build that did that and i had all kinds of people with SOD. from then on i always dump the files myself or get them from Da_G and all is well
Click to expand...
Click to collapse
Unfortunately, I have had the SOD from both Da_G's files and the Flash.dio posted on HTCpedia. I dumped the flash.dio with xidump_v1.0_beta but maybe there is a newer version or something else that I should be using?
rgb-rgb said:
Unfortunately, I have had the SOD from both Da_G's files and the Flash.dio posted on HTCpedia. I dumped the flash.dio with xidump_v1.0_beta but maybe there is a newer version or something else that I should be using?
Click to expand...
Click to collapse
what build are you using? maybe its one i have here i will zip it and upload for you to try.
twopumpchump said:
what build are you using? Maybe its one i have here i will zip it and upload for you to try.
Click to expand...
Click to collapse
23554 wvga
give this a try, never know it may work i released a rom on saturday and havent had any SOD reports or had it myself. i already replaced gwes.exe with one from 23551, so just use the files as they are everything should work...let me know how it turns out.
23554 WVGA 0409
twopumpchump said:
give this a try, never know it may work i released a rom on saturday and havent had any SOD reports or had it myself. i already replaced gwes.exe with one from 23551, so just use the files as they are everything should work...let me know how it turns out.
23554 WVGA 0409
Click to expand...
Click to collapse
Thank you, I will give it a try tomorrow afternoon.
Interesting, using Beyond Compare the only real difference I see is in the S000 file of the Shell32.exe module. See screenshot. Capture1 is from your files and capture2 is from my files. Just 2 small difference, but I don't know why.
Other thing I notice it the MSXIPKernelLTK. Do you use that? I have never used it as I thought it was something that was to do with ROM image update that was never implemented. Does it go in the same directory as MSXIPKernel does in the ROM folder for EVK?
ROM
.....Shared
...........MSXIPKernel
...........MSXIPKernelLTK
rgb-rgb said:
Interesting, using Beyond Compare the only real difference I see is in the S000 file of the Shell32.exe module. See screenshot. Capture1 is from your files and capture2 is from my files. Just 2 small difference, but I don't know why.
Other thing I notice it the MSXIPKernelLTK. Do you use that? I have never used it as I thought it was something that was to do with ROM image update that was never implemented. Does it go in the same directory as MSXIPKernel does in the ROM folder for EVK?
ROM
.....Shared
...........MSXIPKernel
...........MSXIPKernelLTK
Click to expand...
Click to collapse
Is one version time-bomb patched and the other isn't? s000 in shell32.exe is what get's patched for time-bomb.
mwalt2 said:
Is one version time-bomb patched and the other isn't? s000 in shell32.exe is what get's patched for time-bomb.
Click to expand...
Click to collapse
I thought about that last night and figured that's what it was.
twopumpchump said:
its the way the files are dumped, if you use properly dumped flash.dio or .nb you wont have the problem...at least i dont. i learned my lesson the hard way with 23008, i think it was the first build that did that and i had all kinds of people with SOD. from then on i always dump the files myself or get them from Da_G and all is well
Click to expand...
Click to collapse
For the most part, from what ive found. your spot on. When the files are dumped improperly the modules are all at the same address in the text files. If dumped from the dio they are not. Im not really sure why this matters as I was always under the impression that EVK compensated for that and relocated everything to where it needed to be. I do know that every rom Ive had SOD on showed the modules all at the same address.
Wow cool find, so actualy there's a huge memory hog on one of the slots causing out of memory issues isn't?
aruppenthal said:
For the most part, from what ive found. your spot on. When the files are dumped improperly the modules are all at the same address in the text files. If dumped from the dio they are not. Im not really sure why this matters as I was always under the impression that EVK compensated for that and relocated everything to where it needed to be. I do know that every rom Ive had SOD on showed the modules all at the same address.
Click to expand...
Click to collapse
aruppenthal said:
For the most part, from what ive found. your spot on. When the files are dumped improperly the modules are all at the same address in the text files. If dumped from the dio they are not. Im not really sure why this matters as I was always under the impression that EVK compensated for that and relocated everything to where it needed to be. I do know that every rom Ive had SOD on showed the modules all at the same address.
Click to expand...
Click to collapse
I am using the EVK in order to cook my ROMs and i have a some cooks with SOD problem.
You mention that the " SOD on showed the modules all at the same address" where this file is stored when cook the ROM in order to check it before flash it?
Something interesting on this topic from my ROM thread. It looks as though users of my ROM are getting the SOD when the are traveling. I have not gotten this as of yet, but I dont really venture too far from home. But several users have stated that they never got the SOD until they drove ~45mins from home.
If the culprit module does have something to do with location, I wonder what it could be. Google Location service does not have any modules in the package. Manila has several. I also set the clock off of the cell tower. No clue where to start on this one... just wondering if any other chefs have seen something similar.
eras2r said:
Something interesting on this topic from my ROM thread. It looks as though users of my ROM are getting the SOD when the are traveling. I have not gotten this as of yet, but I dont really venture too far from home. But several users have stated that they never got the SOD until they drove ~45mins from home.
If the culprit module does have something to do with location, I wonder what it could be. Google Location service does not have any modules in the package. Manila has several. I also set the clock off of the cell tower. No clue where to start on this one... just wondering if any other chefs have seen something similar.
Click to expand...
Click to collapse
I havent seen that one and I commute between Reading and London every day
there are 2 kinds of SOD people are having:
the first is SYS SOD. this is related to build and/or source. the device completely fails to wake up after sleep (screen remains off)
the second is SOD due to manila 2.5 on some devices. the device does wake up, but the screen remains blank and the backlight is turned on. see this thread for more details about this, inc. a solution
personally, regarding SYS SOD, i have been having it very often on some builds like 21897, even when dumping from dio. BUT i have been using 21898 (from rollup) for several weeks now and never had SOD. i think this is related to the build not just the module addresses.
I get SOD on com2 builds when SRS WOW is cooked in.
Related
Touch-IT Black Leo HD2 - v4.0
I am removing my roms due to conflicts with certain members at xda, this looks like it cant be solved in normal ways. And because I do not want anymore of the bickering and fighting, I am pulling my work from XDA and all support is moved to you know where. I cant even mention that name anymore here.
Sorry to see this happen here, where I have learned so much, and met so many wonderful ppl. I can only quote my own sig:
"Don’t argue with Idiots.. They will bring you down to their level and beat you with experience"
Here is your DL link
--------
I recommend using the 2.08 radio with this rom (not included)
How to flash a custom rom using HSPL
Go to this thread
I take no responsebility for any errors you do with this procedure, its on your own risk
flash flash flash....damn i'm an addict lol..i'm downloadin it now
KUDOS!
Hello, really thanx for this great job, going to flash immediately and than will see
downloading... thx!
Thanks itje. I was itching for a NEW ROM, and you delivered with the 6.5.X build, which I love due to the Threaded emails.
Downloading now and will report soon.
ceers.
flashing now
*Edit*
ooh yeah, i can touch it now!..lol
this rom seems reall fast!, not sure its too stable cuz i just got 2 lockups with the screen not respondin and the hw keys workin. but appart from that, everything else seems to be workin fine thus far thanks!
and btw, the core player isnt workin, so i'll just install the one i hav
manila froze when i was browsing thru the weather animations
20/16 shortcuts
can i use some 20 or 16 shortcuts cab on this rom without problems ????
-Build 23518
hi itje,i installed it and it doesent say the build you said mate [Build 23518]it says 5.2.23515(23515.5.5.0)
Lizzo said:
flashing now
*Edit*
ooh yeah, i can touch it now!..lol
this rom seems reall fast!, not sure its too stable cuz i just got 2 lockups with the screen not respondin and the hw keys workin. but appart from that, everything else seems to be workin fine thus far thanks!
and btw, the core player isnt workin, so i'll just install the one i hav
manila froze when i was browsing thru the weather animations
Click to expand...
Click to collapse
The Core Player is working fine for me.
ops, coreplayer should not be in there, gotta recook and up again. (coreplayer needs edit in settings to work though, set video output to GDI)
Use radio 2.06 with this rom, that will give best results
I have used this rom heavily past few days, and had no lockups whatsoever.
The build is released with ce os 5.2.23515 (build 23518.5.5.0) check this in settings/system/About I know that in (manila)settings/about phone/software info, it say 23515. This is just the way this build was leaked out, and it really dont matter. The OS is 23518 as I said
thanks mate
Lizzo said:
flashing now
*Edit*
ooh yeah, i can touch it now!..lol
this rom seems reall fast!, not sure its too stable cuz i just got 2 lockups with the screen not respondin and the hw keys workin. but appart from that, everything else seems to be workin fine thus far thanks!
and btw, the core player isnt workin, so i'll just install the one i hav
manila froze when i was browsing thru the weather animations
Click to expand...
Click to collapse
try a hard reset if freezing continues. Did you flash the 2.06 radio rom?
see my answer abouve this one for the coreplayer. (this I should have noticed, its not supposed to be in the rom, due to license)
itje said:
ops, coreplayer should not be in there, gotta recook and up again. (coreplayer needs edit in settings to work though, set video output to GDI)
Use radio 2.06 with this rom, that will give best results
I have used this rom heavily past few days, and had no lockups whatsoever.
The build is released with ce os 5.2.23515 (build 23518.5.5.0) check this in settings/system/About I know that in (manila)settings/about phone/software info, it say 23515. This is just the way this build was leaked out, and it really dont matter. The OS is 23518 as I said
Click to expand...
Click to collapse
i'll change to that radio and let u kno
Great release itje.
The ROM feels smooth and stable. But not as fast, I'm talking specific to scrolling in cntacts, etc.
The only small consmetic issue I see is, While in lock screen, The Time that shows up... The digits for the seconds are cut off on the top. Really strange though....
This is a keeper for me until something better comes up
VizagDude said:
Great release itje.
The ROM feels smooth and stable. But not as fast, I'm talking specific to scrolling in cntacts, etc.
The only small consmetic issue I see is, While in lock screen, The Time that shows up... The digits for the seconds are cut off on the top. Really strange though....
This is a keeper for me until something better comes up
Click to expand...
Click to collapse
Hm, weird, scrolling in contacts is very fast for me.
in lockscreen I have no issues, (besides that calendar icons that shows up in theese builds) here is mine right now:
I should have specified. I use a cab where the Silde to lock comes to the bottom of the screen and the Time goes on top of the screen.
Below is the screen shot, Look at the #2, you would notice better. Again, probably to do with the CAB, but I did not see this in anyother ROM.
Please dont get me wrong... not a big deal at all...
VizagDude said:
I should have specified. I use a cab where the Silde to lock comes to the bottom of the screen and the Time goes on top of the screen.
Below is the screen shot, Look at the #2, you would notice better. Again, probably to do with the CAB, but I did not see this in anyother ROM.
Please dont get me wrong... not a big deal at all...
Click to expand...
Click to collapse
ah, ok ..please dont report bugs if mods are installed..as in thsi cause. If you do, please always write what mods is used, cause its timeconsuming to look for bugs reported in my rom that comes from mods.
Besides that, what builds have you used it on before? have you tested the mod on 23518 before? or on roms based on 2.02 leo rom?
I am trying to download but the link seems to be broken!
Warning; scrolling is very glitchy and jerky. It may address other problems, but for me it was not even close to being worthwhile. I had the original stock rom reasonably stable and smooth and this is like an amateurish cooked rom. I haven't strayed from stock for reasons of it being so new, and this update is really surprisingly rough. Good luck.
Caveate Update!
note; I went from original stock ROM to this new one, and did hard reset after setup of first flash, in other words, this was totally stock, so can't imagine need for task 29. Other than terribly annoying jerkiness, rom has crashed only once since new rom.
note 2; got new phone May 18: Identical issues, but is definitely more stable.
works great for me
may you doing something wrong
How long did you give the rom to settle? Six hours, 12 hours, 48 hours...15minutes?
See blow....sorry
davewaave said:
Warning; scrolling is very glitchy and jerky.
Click to expand...
Click to collapse
This is exactly what i felt with my phone after flashing new ROM. So, right away i flashd back my old one.
I gave rom about 2 hours before deciding that it was problematic. Now a day later it is the same. So, if it is being suggested that the rom needs to "settle in" I have given it that chance and it has not changed. Also, I do not see how a rom needs to soak in, beyond the initial setup and things settling down from the install.
I would flash back but I am waiting for replacement, the middle battery pin is bent and loose, so I've not loaded hspl or done any cooked roms. And they are all out of stock locally.
I noticed that the rom does run ****ty, im sure that its the video drivers that need to be changed. the .10 stock version did not jerking issues. this one has both jerk and typing lag. ran it for 2 days now, there is no settling in on roms.
davewaave said:
I gave rom about 2 hours before deciding that it was problematic. Now a day later it is the same. So, if it is being suggested that the rom needs to "settle in" I have given it that chance and it has not changed. Also, I do not see how a rom needs to soak in, beyond the initial setup and things settling down from the install.
I would flash back but I am waiting for replacement, the middle battery pin is bent and loose, so I've not loaded hspl or done any cooked roms. And they are all out of stock locally.
Click to expand...
Click to collapse
The new rom is awesome. what are you talking about.. maybe you updated the 2.10 and thought it was the new 2.13 lol
New rom runs like ****. How can I revert back to 2.10? Can't take the touch screen sensitivity issue!
Downloaded it direct off tmo, that"s why I quoted full name of file to eliminate any confusion. And, I don't even have any other rom. Would be great if that was problem.
It seemed to speed up today when I removed the sd card but haven't had time to test it. Either way, this rom is mucked up.
steady6 said:
The new rom is awesome. what are you talking about.. maybe you updated the 2.10 and thought it was the new 2.13 lol
Click to expand...
Click to collapse
FYI...
Something I worked on this weekend. Some test registry tweaks that really helped the sensitivity issues:
http://forum.xda-developers.com/showthread.php?p=6505849#post6505849
Post there to let me know what your experience is.
The new ROM is running great for me so far though I had very few issues with the old ROM. Swype's hold for secondary and many texting issues being fixed are the large improvements for me. Sensitivity was my only issue with this ROM though there are registry solutions for that.
After installing a ROM I do a hard reset as prescribed by most tutorials out there. Have the people having issues skipped this step? I guess I have have never NOT done it to see if it really makes a difference. It only adds a minute to the process.
I do some registry edits by default after installing, mostly pertaining to memory allocation. I also install chainfire's video driver patch pretty much right away. This could be helping me as well.
Link to memory tweaks. I do the edits from "suitable for all ROMs" down to "added 11/2/10".
Thanks, I'll give the reg tweaks a shot.
so the new update isnt worth getting?
I'm on the elegancia rom with 2.13 base, wm 6.5.5 version. it's been running nicely
more smooth than kumar's 1.3 rom, which I upgraded from. No issues with glitchy scrolling here. icons on this rom are not for me though. might try official tmo 2.13 some day.
It works really well for me so far. I've had it 4 days.
New, Replacement phone; same
Finally got my phone replaced today. It has the new rom installed already, and it acts exactly like the old one. Really notice the scrolling problem in file manager and settings tab scrolling. Only thing different about this phone is that the reset button under battery cover is yellow, whereas old one was red. Whatever. I will live with the problems until ironed out I suppose.
I don't know what you all are doing, but my HD2 now is much faster than it was using the 2.10 ROM. Using the post below, alleviated the sensitivity issue and downloading memory registry tweak makes everything silky smooth.
zim2323 said:
FYI...
Something I worked on this weekend. Some test registry tweaks that really helped the sensitivity issues:
http://forum.xda-developers.com/showthread.php?p=6505849#post6505849
Post there to let me know what your experience is.
Click to expand...
Click to collapse
The memory tweaks can be found here
http://forum.xda-developers.com/showthread.php?t=629388
Bottom of the first post there is a cab to download: HD2MemTweaks.cab
jas0nw0ng said:
I don't know what you all are doing, but my HD2
The memory tweaks can be found here
http://forum.xda-developers.com/showthread.php?t=629388
Bottom of the first post there is a cab to download: HD2MemTweaks.cab
Click to expand...
Click to collapse
Of note is that above cab file mentioned is listed as not suitable for the US HD2. Couple lines above the cab files.....
"Remember, the MemTweaks CAB is only suitable for 576mb rom users"
Just apply the tweaks manually.
Hello
This is regarding the Rhodium bug once updating the OEM drivers to the latest 2.10 build that many chefs have been getting. I'm not sure if this has any negative side effects (I haven't come across any as of yet).
All you have to do is use rilphone.dll from the 2.7 build (I haven't tried the one from the 2.8 build yet but I might soon). Lemme know if it works.
Happy cooking! (^^,)
This is not a downloadable fix but rather information for chefs.
Yep.. I asked the guys in my thread to use an older rilphone.dll because I was sure that's the problem... but nobody was brave enough to try it. They kept swapping radios for some reason.. LOL Thanks for the tip, I'll just use the older rilphone.dll. That new ATT rom is effing whack!!
NRGZ28 said:
Yep.. I asked the guys in my thread to use an older rilphone.dll because I was sure that's the problem... but nobody was brave enough to try it. They kept swapping radios for some reason.. LOL Thanks for the tip, I'll just use the older rilphone.dll. That new ATT rom is effing whack!!
Click to expand...
Click to collapse
Haha, should've known you knew about it Lol, yeah it is.. I'm getting random manila stutters and flickers now and then, that's pretty crappy though. Is that only me?
NRGZ28 said:
Yep.. I asked the guys in my thread to use an older rilphone.dll because I was sure that's the problem... but nobody was brave enough to try it. They kept swapping radios for some reason.. LOL Thanks for the tip, I'll just use the older rilphone.dll. That new ATT rom is effing whack!!
Click to expand...
Click to collapse
Lol.. I was game - just didn't know where to find the old RIL.
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=7437776&postcount=24652
Couldn't find it in the Radio thread. So where do you go to get this stuff? Thanks a bunch for the link. Will try it right away..
Don't try the cab it seems like it doesn't work for some strange reason.
seeM_ZA said:
Don't try the cab it seems like it doesn't work for some strange reason.
Click to expand...
Click to collapse
too late.. My Radio is hosed for now. Doing another reset - sometimes, replacing ROM components take a couple of resets (new location?)..
Edit: Resets didn't work. Can you link the actual rilphone.dll here?
motoq9h said:
too late.. My Radio is hosed for now. Doing another reset - sometimes, replacing ROM components take a couple of resets (new location?)..
Click to expand...
Click to collapse
Lol you know more about it than me then (^^,). It works perfectly when cooked in though, my bad
seeM_ZA said:
Lol you know more about it than me then (^^,). It works perfectly when cooked in though, my bad
Click to expand...
Click to collapse
Yup.. looks like it is searching for the rilphone.dll in the ROM. copying it over replaced the location. So it is hosed - no phone for me..
Cooking it in is the only way, looks like - Need NRGZ28's help for that.. Unfortunately, my cooking skills don't pass much muster.. lol
Edit: So is there a way to point to the new rilphone.dll location via the registry? Going to be tricky though : ROM vs overwrite location
Edit2: There, that wasn't too bad. Uninstalled the cab and reset - back to using the cooked in rilphone.dll & back to working phone (with 2 bars, ofcourse!) I have the "good" rilphone.dll though. Saved it off before uninstalling the cab - anyone wants it?
Did you try putting phone in airplane mode before installing cab? May'be That could have made a difference!!
momulah said:
Did you try putting phone in airplane mode before installing cab? May'be That could have made a difference!!
Click to expand...
Click to collapse
Lol.. I'm not hopeful - overwriting a ROM file moves the file system entry (to flash?) and invalidates the ROM file (the Cooks/Chef's will know more). The phone code appears to be hard coded to look only at the ROM file - so no deal it appears..
motoq9h said:
Yup.. looks like it is searching for the rilphone.dll in the ROM. copying it over replaced the location. So it is hosed - no phone for me..
Cooking it in is the only way, looks like - Need NRGZ28's help for that.. Unfortunately, my cooking skills don't pass much muster.. lol
Edit: So is there a way to point to the new rilphone.dll location via the registry? Going to be tricky though : ROM vs overwrite location
Edit2: There, that wasn't too bad. Uninstalled the cab and reset - back to using the cooked in rilphone.dll & back to working phone (with 2 bars, ofcourse!) I have the "good" rilphone.dll though. Saved it off before uninstalling the cab - anyone wants it?
Click to expand...
Click to collapse
Well the 'old-fashioned' way was to copy the new rilphone.dll as rilphone2.dll and then edit the relevant registry key to point to it.
Unfortunately, multiple people have tried to do so in the past (check the early Rhodium radio thread posts) and apparently it's something to do with RILPHONE being a module on Rhodium and Topaz devices that makes any method other than cooking it in, fail.
monomer888 said:
Well the 'old-fashioned' way was to copy the new rilphone.dll as rilphone2.dll and then edit the relevant registry key to point to it.
Unfortunately, multiple people have tried to do so in the past (check the early Rhdodium radio thread posts) and apparently it's something to do with RILPHONE being a module on Rhodium and Topaz devices that makes any method other than cooking it in, fail.
Click to expand...
Click to collapse
Thanks.. Yup. Was searching through the Registry a little while ago - no mention of the rilphone.dll
motoq9h said:
Thanks.. Yup. Was searching through the Registry a little while ago - no mention of the rilphone.dll
Click to expand...
Click to collapse
Just for reference, this is the key:
HKLM\Drivers\BuiltIn\RIL
"Dll" = rilphone.dll
I spent the best part of the evening trying to get it to work, but point it to any other rilphone.dll and I would get no signal at all. Resetting the key back to what it was restored it. Hope that helps.
NRGZ28 said:
That new ATT rom is effing whack!!
Click to expand...
Click to collapse
Thats why a heck of a lot of us are here (at XDA) in the first place.
wait, i'm confused. how do we replace the new rilphone.dll with the good/old one? does anyone actually have it/has anyone gotten it to work?
Da_G explains it pretty nicely in this post: http://forum.xda-developers.com/showpost.php?p=3354857.
Without the nk.exe patch, when you replace rilphone.dll, the system checks it against it's internal certificate store, finds that it's not signed with a trusted certificate, and refuses to load it. This is why replacing rilphone.dll on unpatched ROM's results in no radio function.
Click to expand...
Click to collapse
seeM_ZA said:
Da_G explains it pretty nicely in this post: http://forum.xda-developers.com/showpost.php?p=3354857.
Click to expand...
Click to collapse
Aye, if I was reading it correctly, there was an alternate way using DriverWiz to cab up the dll which has worked on older devices, even when the nk.exe wasn't patched, e.g. here: http://forum.xda-developers.com/showthread.php?p=3486508#post3486508
Unfortunately, At0mAng tried to use this method at one stage but it didn't work on his Rhodium. http://forum.xda-developers.com/showpost.php?p=4642101&postcount=215
It would be great if we could get this to work!
seeM_ZA said:
Haha, should've known you knew about it Lol, yeah it is.. I'm getting random manila stutters and flickers now and then, that's pretty crappy though. Is that only me?
Click to expand...
Click to collapse
I am getting this now and then ... try scrolling stuff on manila or weather and taskbar will flicker or blink ... i hate it ....were you able to fix this ? rilphone for which older TM base ?
'▼' said:
I am getting this now and then ... try scrolling stuff on manila or weather and taskbar will flicker or blink ... i hate it ....were you able to fix this ? rilphone for which older TM base ?
Click to expand...
Click to collapse
Nah wasn't able to fix that.. I'm using rilphone from 2.07 Rhodium ROM, that fixes the 2 bar bug.
What is exactly what you call the '2 bar bug'?
Hey guys, this post is just my way in saying thanks for all the help all of you guys have given me and for making it possible to have android on my HD2
Basically I have been doing some testing and have come up with a combination of things you can do to give yourself a fully working android build Ofcorse some of the information I had to test with was provided by other members but this combination I think is flawless, well at least it is for me ^^.
To begin you’re going to want to get the right WM rom for your android, and after testing I found the best one to be
forum.xda-developers.com/showthread.php?t=734238
I have not had any problems with it. Just flash it to your device and let’s go from there.
Next your going to want to do something allot of members do not think of doing, and that is formatting the SD card PROPERLY, as this eliminates allot of problems for various reasons. The correct way to do this is, boot yourself into Linux, Ubuntu is the easiest in my eyes, and you can get it on a live CD or USB so it’s easy to get into, just boot into Ubuntu plug in your SDcard and its better if you can insert it via an SDcard slot in an adapter. Then format it as FAT not FAT32, I wont explain why this is better, but it will. Check this out if you really want to know why you need to do it ^^ but you don’t really need to know
forum.xda-developers.com/showthread.php?t=750780
Next thing is your android build. Now there are ALOT of builds that work well but there is only one that I believe can give you a real working android experience, and the next part of this guide is based on this build so I suggest you use it .
forum.xda-developers.com/showthread.php?t=740963
Ok, so you have got your build on your card you have booted into it and it’s ready to go, right? Not yet. One of the most annoying things that occur in android under the HD2 is the random freezing and this is how I removed this pesky little annoyance.
1. Unlock your screen and hit the settings key (windows key)
2. Hit settings
3. Hit Cyanogenmod Settings
4. Hit User Interface
5. Scroll down to Accelerometer rotation
6. Make sure ONLY 90 degrees is ticked!
7. Done
Now that setting is how I have managed to eliminate the problem, but don’t worry if you still have this issue, just go back into the Cyanogenmod settings and turn off 90 degrees and then under display turn off Auto-rotate screen, this should eliminate the problems but then your screen wont rotate automatically so its swings and roundabouts really ^^
Top Tips!
DONT use live wallpapers, they WILL kill your battery and drastically decrease the performance of your HD2!
Turn off the GPS as it is on by Default, it drains battery ALOT and isn't necessary most of the time ^^
Get the XDA app because its mega? And you suck if you don’t!
Calibrate the Gsensor, it will reduce the screen freezes (that’s if you even have them, witch you shouldn’t after this guide: P)
Finally, always remember that you should turn off your phone to charge it OR have it booted into WinMo, allot of reasons why you should do this but again just do it
Hope this helped someone somewhere Its my first real post that gave something back to the community and I AM a noob hehe, so any addition to this guide is welcome ^^ Again thanks allot all you guys at XDA that made this possible and I will keep this updated as necessary
Thanks allot. Dane.
xpstyle36 said:
1. Unlock your screen and hit the settings key (windows key)
2. Hit settings
3. Hit Cyanogenmod Settings
4. Hit User Interface
5. Scroll down to Accelerometer rotation
6. Make sure ONLY 90 degrees is ticked!
7. Done
Now that setting is how I have managed to eliminate the problem, but don’t worry if you still have this issue, just go back into the Cyanogenmod settings and turn off 90 degrees and then under display turn off Auto-rotate screen, this should eliminate the problems but then your screen wont rotate automatically so its swings and roundabouts really ^^
[...]
Calibrate the Gsensor, it will reduce the screen freezes (that’s if you even have them, witch you shouldn’t after this guide: P)
Click to expand...
Click to collapse
If this works, I'll be eternally grateful.
shadiku said:
If this works, I'll be eternally grateful.
Click to expand...
Click to collapse
I hope it works for you but remember if you didn't follow all the other steps I cant guarantee and fix and even if it doesn't work, you can disable all screen rotation as I mentioned and this SHOULD fix your problem ^^ I really do hope it works for ya.
Dane.
Forgot to discuss about RADIOS and HARDSPL.
Common man.
FriedSushi87 said:
Forgot to discuss about RADIOS and HARDSPL.
Common man.
Click to expand...
Click to collapse
Well if your looking at this guide, you probably already have HardSPL :l and even if you didn't when you take a look at the ROM pages it explains it there, so I don't think its very productive or helpful to post random crap like that :l And as for the radio, i tested several radios and it didn't make any difference TO ME but if you really want to know the radio i am running its, 2.12.50. Happy now ?
Dane.
xpstyle36 said:
Well if your looking at this guide, you probably already have HardSPL :l and even if you didn't when you take a look at the ROM pages it explains it there, so I don't think its very productive or helpful to post random crap like that :l And as for the radio, i tested several radios and it didn't make any difference TO ME but if you really want to know the radio i am running its, 2.12.50. Happy now ?
Dane.
Click to expand...
Click to collapse
I think it's incredibly important to post that here.
Imagine someone sees an HD2 with android or hears about it from a friend, does a quick google search and finds this thread.
They come in here looking for a quick fix for android....
They could end up bricking their device or something....
FriedSushi87 said:
I think it's incredibly important to post that here.
Imagine someone sees an HD2 with android or hears about it from a friend, does a quick google search and finds this thread.
They come in here looking for a quick fix for android....
They could end up bricking their device or something....
Click to expand...
Click to collapse
/sigh, what are you trying to do here ? cause problems.if you had never even heard about android on HD2 you take one look at the writing in this post and think WHAT, it says things like Flash it to your device and lets go. you wouldnt know how to flash or even what it meant, so you couldn't even brick your device as you would not know how :l Please stop filling up this thread that i made to HELP people not argue with some guy who keeps coming up with random crap that is not going to happen, and i am not being unreasonable by saying that and i am sure many other members will agree im not in the wrong.
Dane.
Unfortunately still having the screen freezes, even after toying with CyanogenMod settings.
Back to the waiting game then.
shadiku said:
Unfortunately still having the screen freezes, even after toying with CyanogenMod settings.
Back to the waiting game then.
Click to expand...
Click to collapse
Did you turn off all the screen rotation under cm settings and normal settings and did you calibrate the Gsensor these things can also resolve the problem, you can also disable the Gsensor in WinMO and this will cure your problem but thats not reccomended ^^ Give those suggestions a try, again hope it works for you.
Dane.
Are we allowed to start a poll asking people which mainstream rom they're using just so we know what is the most common and popular rom is,? Or is it a taboo?
xpstyle36 said:
Did you turn off all the screen rotation under cm settings and normal settings and did you calibrate the Gsensor these things can also resolve the problem, you can also disable the Gsensor in WinMO and this will cure your problem but thats not reccomended ^^ Give those suggestions a try, again hope it works for you.
Dane.
Click to expand...
Click to collapse
I turned all the screen rotation off. Since I'm using ChuckyDroidROM, the gsensor calibration is removed.
In android, it worked for a while but tilting it continually in Gallery3D caused a freeze.
I wish I could disable the theming on shubCRAFT, it's the only thing that puts me off using it.
I think that if you look at this thread you will see
xpstyle36 said:
Next your going to want to do something allot of members do not think of doing, and that is formatting the SD card PROPERLY, as this eliminates allot of problems for various reasons. The correct way to do this is, boot yourself into Linux, Ubuntu is the easiest in my eyes, and you can get it on a live CD or USB so it’s easy to get into, just boot into Ubuntu plug in your SDcard and its better if you can insert it via an SDcard slot in an adapter. Then format it as FAT not FAT32, I wont explain why this is better, but it will. Check this out if you really want to know why you need to do it ^^ but you don’t really need to know
Click to expand...
Click to collapse
that this method is a lot of trouble for no additional benefit over a simple format using WinMo in the phone. If you would "explain why" it would be interesting because no one else can. A full WinMo format, not quick, overwrites the complete data space on an SD card with new redundant data. It also only reserves and writes one FAT where Windows on the PC reserves and writes two. You can't get something from nothing and WinMo non-quick format leaves nothing in the data space. (And yes I do understand full mil spec data destruction and redundent and random erase so everything is destroyed.)
http://forum.xda-developers.com/showthread.php?t=760996&page=5
johnboatcat said:
that this method is a lot of trouble for no additional benefit over a simple format using WinMo in the phone. If you would "explain why" it would be interesting because no one else can. A full WinMo format, not quick, overwrites the complete data space on an SD card with new redundant data. It also only reserves and writes one FAT where Windows on the PC reserves and writes two. You can't get something from nothing and WinMo non-quick format leaves nothing in the data space. (And yes I do understand full mil spec data destruction and redundent and random erase so everything is destroyed.)
http://forum.xda-developers.com/showthread.php?t=760996&page=5
Click to expand...
Click to collapse
Well i may be wrong but as far as i was aware, when you put a linux android build on your SDcard it creates a partition or something like that on the card, (i will look it up and get back to you) and windows cannot see it, wheras linux can see it and therefore it can wipe it, and these left over bits that windows cant see dont always get on when you get a new build Thanks for pointing it out though, just wanna help as many as possible ^^
Thanks
Dane.
shadiku said:
I turned all the screen rotation off. Since I'm using ChuckyDroidROM, the gsensor calibration is removed.
In android, it worked for a while but tilting it continually in Gallery3D caused a freeze.
I wish I could disable the theming on shubCRAFT, it's the only thing that puts me off using it.
Click to expand...
Click to collapse
To be honest i think that if you got yourself a Shubcraft build and then followed the guide then you would end up with a pretty stable build, with no freezing, but if you dont like the theme, then i guess that there is nothing i can do, but hope that a sense version of it is relesed so that you can get yourself a nice stable build ;D
Thanks again.
Dane.
shubcraft themes and "stock"
If you dont like the shubcraft theme you can use this ..
http://forum.xda-developers.com/showthread.php?t=760641
there is even a shub version 1.4c with "stock" Froyo theme here
http://forum.xda-developers.com/showthread.php?t=760641&page=3
thanks to all dev's & builders
ugghuggh said:
If you dont like the shubcraft theme you can use this ..
http://forum.xda-developers.com/showthread.php?t=760641
there is even a shub version 1.4c with "stock" Froyo theme here
http://forum.xda-developers.com/showthread.php?t=760641&page=3
thanks to all dev's & builders
Click to expand...
Click to collapse
Ah ! Thanks alot ^^ Hey ! now you can download that one, follow the instructions and hopefully get a working build D:
Thanks again
Dane.
FriedSushi87 said:
Forgot to discuss about RADIOS and HARDSPL.
Common man.
Click to expand...
Click to collapse
FriedSushi87 said:
I think it's incredibly important to post that here.
Imagine someone sees an HD2 with android or hears about it from a friend, does a quick google search and finds this thread.
They come in here looking for a quick fix for android....
They could end up bricking their device or something....
Click to expand...
Click to collapse
@friedsushi definitely agree with you it isn't clarified correctly about different radios affecting the android or that hspl is necessary for it to work. I am constantly getting people pming me to ask for a walkthrough, which on most occasions I have been able to get this working even though my wordage is more simplified in layman's terms-his looks like its been copy/pasted from all over these pages which in effect isn't a bad thing but to call it a guide and not including vital information is a bit haphazard IMO.
& to the op I am not flaming you but there are already guides out there & don't particularly need another unfinished version to add to the numerous threads which have only just been cleaned up by the mods, plus with only 11 posts 8 of which are on here I honestly don't see much experience to be able to give people guides
11calcal said:
@friedsushi definitely agree with you it isn't clarified correctly about different radios affecting the android or that hspl is necessary for it to work. I am constantly getting people pming me to ask for a walkthrough, which on most occasions I have been able to get this working even though my wordage is more simplified in layman's terms-his looks like its been copy/pasted from all over these pages which in effect isn't a bad thing but to call it a guide and not including vital information is a bit haphazard IMO.
& to the op I am not flaming you but there are already guides out there & don't particularly need another unfinished version to add to the numerous threads which have only just been cleaned up by the mods.
Click to expand...
Click to collapse
I dont get it ? not one word of this was copied and pasted from someone else, and this is just the process i went through to get it to work perfectly, i didnt include the parts about the HardSPL and the radio because, i tryed a few different radios and it made no difference to me AND you wouldn't be able to flash or follow these instructions if you didnt know what hard SPL was. Again i am not flaming but i was just providing a set of instructions that i did, to get it working. So its not a unfinished guide, just because it didnt include some realy basic information. Sorry if i did not make this 100% noob friendly, was just trying to get a few more phones running stable ^^
Dane.
No one discussed any where about the below scenarios.
If booting to android, Phone reboots.
If already in booted and trying to make a call or check email again booted.Always getting booten in android randomly after trying various builds.
Anyone has answer for thatt?
Thanks
Before people tell me to search the forums, that's what I've been doing for the longest time, trying every ROM on the Vogue forum. And before you tell me to try Android, I've done that too, and while I like it, I prefer Windows Mobile on this particular phone at the moment, but may put Android on it again sometime in the future.
The closest that I've found is NagROM V0.19 Touch, which is just a touch too basic. I'm looking for something like that, but with M2D and M2D Customiser, the HTC Cabs and Ringtones, the EZInput keyboard like in NFSFan's ROM, and Office 2007 or 2010. While I like the ROMs that come with other programs cooked in, such as Total Commander and PHM Registry Edit, I prefer the ROM coming without them so that when I go to install an updated version, I don't run into a problem. Too many times I've had problems installing a newer version of a program when it comes up telling me it has to uninstall the previous version, but can't, sometimes leaving me with just the old version, or both versions.
And before anyone says to cook my own, I've looked into guides, tried cooking my own, and the past few times I've tried, it wouldn't even boot up for the first time after flashing. I've tried numerous kitchens, some of which are supposed to be basic ones, perfect for beginners, but end up with one of a few problems: Not compatible with 64-bit windows, virus scanner blocks a crucial part, not meant for the Vogue, etc.
Basically what I'm asking is: Are there any basic ROMs with nothing more than M2D (and HTC cabs and Ringtones, and M2DC), EZInput, and Office Mobile 2007/2010 cooked in, or can someone HELP me with trying to cook my own (so that I can have it preconfigured for Verizon, MMS working and GPS set up)?
Hey, Ill cook you up a rom with the things you want. Should be done here in a little while!
Hey - that's a dev for you, man. Ask and ye shall receive!
I'd encourage you to hit barogi's donate link if he's got one.
Sent from my Full Android on Vogue using XDA App
mrkite38 said:
Hey - that's a dev for you, man. Ask and ye shall receive!
I'd encourage you to hit barogi's donate link if he's got one.
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Love to provide for the community! Im actually uploading the rom right now... As for donations, i dont have a link seeing how i am only 17 years old.
Anyways thanks for the kind words.
Here you go http://www.4shared.com/file/K700wk8F/23138_light_rom_upload.html
Build 23138 (Wm 6.5.3)
Code:
Includes:
M2d
M2dc
Office 2010
Ringtones
Htc apps
Ezinput
Other necessary stuff... such as Bluetooth..
Enjoy!
Barogi44 said:
Love to provide for the community! Im actually uploading the rom right now... As for donations, i dont have a link seeing how i am only 17 years old.
Anyways thanks for the kind words.
Click to expand...
Click to collapse
17??! That explains the free time! keep up the good work!
Sent from my Full Android on Vogue using XDA App
mrkite38 said:
17??! That explains the free time! keep up the good work!
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Yep 17
Thanks!!
Haha, wow. I never expected someone to actually make it fer me! I'll have to try it out tomorrow as it's late now. Also, what kitchen do you use, Barogi? I still do plan on learning. (I'm a mix of hands on learning and being shown/flat out told what to do for the first time or three lol). Also, I assume it is set up as a Generic ROM (without the provisioning cab, MMS cab and settingsh, and Registry settings for GPS)? Also, as time goes more things come to mind to be cooked in (hence wanting to learn how to cook a ROM personally, and slowly becoming less basic ) lol. Still, thanks, majorly. I'll let you know how it works out when I try it tomorrow =3
Oh, and what version of EZInput is cooked in? I know I said "like the one in NFSFan's ROM," but that's only because I was unsure of the version (which I know now is 1.5.)
Toddle said:
Haha, wow. I never expected someone to actually make it fer me! I'll have to try it out tomorrow as it's late now. Also, what kitchen do you use, Barogi? I still do plan on learning. (I'm a mix of hands on learning and being shown/flat out told what to do for the first time or three lol). Also, I assume it is set up as a Generic ROM (without the provisioning cab, MMS cab and settingsh, and Registry settings for GPS)? Also, as time goes more things come to mind to be cooked in (hence wanting to learn how to cook a ROM personally, and slowly becoming less basic ) lol. Still, thanks, majorly. I'll let you know how it works out when I try it tomorrow =3
Oh, and what version of EZInput is cooked in? I know I said "like the one in NFSFan's ROM," but that's only because I was unsure of the version (which I know now is 1.5.)
Click to expand...
Click to collapse
I use ppckitchen.org Buildos 2.0.0 And yes it is generic meaning you will need a carrier cab, Once you do install your carrier cab everything should work such as mms and gps. As for Ezinput i actually use a newer version than Nfsfans its (pcarvalho_ezInput_2.1_QVGA). If you want some help with cooking your own rom, just install ppckitchen buildos 2.0.0 since thats the only one ive ever used and know how to use and then send me a message on whatever you need some help with! Also if you want something changed in the rom i have already made for you before you get a chance to build your own, just let me know and ill do it.
EDIT: Had posted the wrong link to ppckitchen its supposed to be ppckitchen.org not .com
Hope you like it.
Barogi44 said:
I use ppckitchen.org Buildos 2.0.0 And yes it is generic meaning you will need a carrier cab, Once you do install your carrier cab everything should work such as mms and gps. As for Ezinput i actually use a newer version than Nfsfans its (pcarvalho_ezInput_2.1_QVGA). If you want some help with cooking your own rom, just install ppckitchen buildos 2.0.0 since thats the only one ive ever used and know how to use and then send me a message on whatever you need some help with! Also if you want something changed in the rom i have already made for you before you get a chance to build your own, just let me know and ill do it.
EDIT: Had posted the wrong link to ppckitchen its supposed to be ppckitchen.org not .com
Hope you like it.
Click to expand...
Click to collapse
PPCKitchen BuildOS 2.0.0 is what I was using as well. I've used enough generic ROMs to know how to get it all working, so that's simple to do. Was just curious about that. I've gotten one ROM working through there, but somehow ended up with the Windows Mobile 6.1 splash screen (even though I changed it lol.) I'll try out your ROM, and I"ll keep playing with BuildOS. Hopefully I can get the file size down, and figure out how to cook in my own things, not just what's listed on the build menu lol. I'm kind of a hands on learner, kind of need to be shown multiple times, so playing around with it (though will take MUCH longer) SHOULD help me figure it out, but I'll keep in mind to PM you if I have any questions.
Toddle said:
PPCKitchen BuildOS 2.0.0 is what I was using as well. I've used enough generic ROMs to know how to get it all working, so that's simple to do. Was just curious about that. I've gotten one ROM working through there, but somehow ended up with the Windows Mobile 6.1 splash screen (even though I changed it lol.) I'll try out your ROM, and I"ll keep playing with BuildOS. Hopefully I can get the file size down, and figure out how to cook in my own things, not just what's listed on the build menu lol. I'm kind of a hands on learner, kind of need to be shown multiple times, so playing around with it (though will take MUCH longer) SHOULD help me figure it out, but I'll keep in mind to PM you if I have any questions.
Click to expand...
Click to collapse
Ok great!
Alright, I'm trying out the ROM, and so far it looks great. Just one slight thing... I see you put in PHM RegEdit (an add on program I said I prefer installing myself so that when I go to update it I don't run into problems lol) Other than that, so far it looks perfect. Now if I could figure out how to cook a ROM where it isn't bigger than the stock, with just a few add in things as I think of them that I use regularly (and cook it as a Verizon specific ROM) then yay. Time to start playing with BuildOS while setting up my phone again lol
Toddle said:
Alright, I'm trying out the ROM, and so far it looks great. Just one slight thing... I see you put in PHM RegEdit (an add on program I said I prefer installing myself so that when I go to update it I don't run into problems lol) Other than that, so far it looks perfect. Now if I could figure out how to cook a ROM where it isn't bigger than the stock, with just a few add in things as I think of them that I use regularly (and cook it as a Verizon specific ROM) then yay. Time to start playing with BuildOS while setting up my phone again lol
Click to expand...
Click to collapse
Ahh sorry about that Its just one of those programs that i figured you might want but perhaps had forgotten to ask for
Also i realized that after i had uploaded the rom that i forgot to add the reg edit to fix the 2016 date error on sms messages... Not sure if that affects you on Verizon, because i do not get it on Bell.
If you want... I can give you a list of the necessary things you should put in your own roms to make it function to its fullest.. like all the necessary bluetooth items and such?
Barogi44 said:
Ahh sorry about that Its just one of those programs that i figured you might want but perhaps had forgotten to ask for
Also i realized that after i had uploaded the rom that i forgot to add the reg edit to fix the 2016 date error on sms messages... Not sure if that affects you on Verizon, because i do not get it on Bell.
If you want... I can give you a list of the necessary things you should put in your own roms to make it function to its fullest.. like all the necessary bluetooth items and such?
Click to expand...
Click to collapse
It's alright, I think PHM is one of the ones that can be updated even if it's cooked in without any problems. And yes, the 2016 problem will affect me on Verizon. I had it happen to me on NagROM before, but already had the fix downloaded (someone made it into a cab) so I installed it to be on the safe side. As for the list of things to make it function to the fullest, please do. And if there is another way to contact you other than on here, can you tell me in PM? I'd like to contact you off of here for help with cooking a ROM. I've tried again, and it wouldn't even finish building this time. Out of about 8 times of cooking a ROM, it succeeded only once, but I forgot to compress it (this was before you made this ROM for me).
Also, slight problem, and quick question.
The problem is on M2D. The music tab. It says that it can't play the audio file and opens Windows Media Player. I haven't found anything on this yet and had it happen to me on a few ROMs. If it can't be fixed, that's fine, i can just take off the music tab (because I don't always slide along the bottom, I'll use the D-pad at times, and if other people play with my phone)
The question... Where can I find the default background for M2D? I changed the background using M2DC so it'll be on all the tabs, but you can't see the white text, so I wanna change it back until I find a different background.
Toddle said:
It's alright, I think PHM is one of the ones that can be updated even if it's cooked in without any problems. And yes, the 2016 problem will affect me on Verizon. I had it happen to me on NagROM before, but already had the fix downloaded (someone made it into a cab) so I installed it to be on the safe side. As for the list of things to make it function to the fullest, please do. And if there is another way to contact you other than on here, can you tell me in PM? I'd like to contact you off of here for help with cooking a ROM. I've tried again, and it wouldn't even finish building this time. Out of about 8 times of cooking a ROM, it succeeded only once, but I forgot to compress it (this was before you made this ROM for me).
Also, slight problem, and quick question.
The problem is on M2D. The music tab. It says that it can't play the audio file and opens Windows Media Player. I haven't found anything on this yet and had it happen to me on a few ROMs. If it can't be fixed, that's fine, i can just take off the music tab (because I don't always slide along the bottom, I'll use the D-pad at times, and if other people play with my phone)
The question... Where can I find the default background for M2D? I changed the background using M2DC so it'll be on all the tabs, but you can't see the white text, so I wanna change it back until I find a different background.
Click to expand...
Click to collapse
Ill send you a pm with my cell number. Also I have always gotten that message when trying to use music tab. I dont think a fix has ever been mentioned... I know that it usually defaults to using audio manager and not the windows media player, perhaps that could be the problem?
The background... I think that you have to back up the default in M2DC before changing it in order to get it back, so that you can reload it. Just so you know, I don't use Manila at all on my phone, so im not quite sure how to fix many things on it. And remember that most issues are do to the fact that Manila is not made for our phones and has been ported over. But I will try my best to help you out.
Barogi44 said:
Ill send you a pm with my cell number. Also I have always gotten that message when trying to use music tab. I dont think a fix has ever been mentioned... I know that it usually defaults to using audio manager and not the windows media player, perhaps that could be the problem?
The background... I think that you have to back up the default in M2DC before changing it in order to get it back, so that you can reload it. Just so you know, I don't use Manila at all on my phone, so im not quite sure how to fix many things on it. And remember that most issues are do to the fact that Manila is not made for our phones and has been ported over. But I will try my best to help you out.
Click to expand...
Click to collapse
I've had the music tab working before. I think NFSFan's ROM. And I'll just find a different background. I'll send you a text tomorrow before my class.
Toddle said:
I've had the music tab working before. I think NFSFan's ROM. And I'll just find a different background. I'll send you a text tomorrow before my class.
Click to expand...
Click to collapse
Yeah NFSFAN always cooked Audiomanager into his roms... you could put it in your own as well and it probably would stop the error.
Barogi44 said:
Here you go http://www.4shared.com/file/K700wk8F/23138_light_rom_upload.html
Build 23138 (Wm 6.5.3)
Code:
Includes:
M2d
M2dc
Office 2010
Ringtones
Htc apps
Ezinput
Other necessary stuff... such as Bluetooth..
Enjoy!
Click to expand...
Click to collapse
Barogi...can I hit you up for a more basic one that that? I need the lighted WM ROM there is. I basically need Windows Mobile 6.5.3 and that's it...no extras.
If you could make one that has everything removed except Windows (even ezinput, office, ringtones, htc apps, etc...then I would be very appreciate
Of course if you have a kitchen link I can do it myself - thanks !!
Thread moved to General.
any screen shots avail?