yashsingh1/xdaforums huggingface dataset:
[Non-Touchscreen Windows Mobile Other] benjaminries:
Okay so I'm kind of off-track. it is not the Neo home XML file that references the registry at all. It just contains:

<plugin clsid="{E9267CAB-02EE-4f37-8216-6BF6A8FF5A71}" name="T-Mobile Homescreen" height="266">
</plugin>

Following HKEY_CLASSES_ROOT\CLSID\{E9267CAB-02EE-4f37-8216-6BF6A8FF5A71} we find a default string value of CMHome and a subkey InprocServer32 with a default string value of cmhome.dll

So as I feared, that cmhome.dll likely has hard-coded references to the CHome keys. Either we go with the exe file/reg swapping app you described, or we hack cmhome.dll to reference new "NHome" keys. Which is waaaaaaaay out of my league. Question: does the new 6.1 ROM contain \Windows\cmhome.dll files for the slide interface?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I just realized how stupid I am, really stupid considering I built the test rom, but the new homescreen doesn't reference CHome at all. It uses another package called BronzeNonEA. If I just add in the the images and dlls for the Neo interface and put the tmobile CHome package back in, We should be able to use both, no switching exe required!
[Non-Touchscreen Windows Mobile Other] brandun_6:
So I'm kind of a newb at ROM cooking and most stuff but I've been following this thread since the beginning. I really want 6.1 on my Shadow. So I was wondering:

1. If by doing any of this I can brick my phone?

2. I can go back to the original T-Mobile ROM?

3. Will calling and texting fully work with no problems?

4. What do I have to do to my phone before I try to use this ROM?

Sorry if I'm being a bother.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
brandun_6

The rom cannot brick your phone. But there is always the risk that something may go wrong, so I can't assure you that 100%. You can always go back to the tmobile rom since I haven't done anything at all to the bootloader. Calling works, I haven't tried texting, but if it does, threaded sms should work. Before using the rom, use the SSPL to temporarily CID-Unlock your phone.

If you are unsure about flashing this rom image, don't. Once all the kinks are worked out, we will post a final version.
[Non-Touchscreen Windows Mobile Other] kron2:
working good so far. I have the original rom 1.11.531.5 you posted in a privies post I assume if I redo the sspl I can install it back don't knock your self you are doing a great job I am surprised we have a rom this quick .how long till this up date with the images and dlls for the Neo interface and to put the tmobile CHome package back in.
[Non-Touchscreen Windows Mobile Other] brandun_6:
Thanks ND4SPD, I'm pretty confident about this now, been readin' up:)

And wonderful job! Thanks for putting all this work into this. One question - What's the SSPL?

Sorry
[Non-Touchscreen Windows Mobile Other] benjaminries:
That would be awesome, except some Google searches of mine have turned up a few WM 6.1 registry customization threads that suggest HKLM\Software\CHome keys are used by the new 6.1 Slide interface. You can confirm that your current WM 6.1 ROM contains no such registry key?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I remember going into the bronze folders and seeing all the dlls that managed the CHome. What I'm hoping is that if this isn't true, the new today screen only refernces parts that T-Mo didn't change(there was a CHome before t-mobile edited it)

I can't confirm it, but I can test it. ;)
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
First off great job on the rom ;), a couple bugs i found. TExt messaging works, and calling works perfectlly nice job :).

Bugs:

Going into PIE, will mess up the text messaging(the keyboard layout changes the 0-9 keys wont type in letters only numbers).

ActiveSync won't work, tried getting into settings->connections to fix it but still doesn't work.
[Non-Touchscreen Windows Mobile Other] freyes01:
Some people already ported Neo to other devices. We could add that to this Rom

Check: http://xdaforums.com/showthread.php?t=370765

changing topics....do you know if WiFi works?

BTW. I'll work on the theme as soon as I have the Rom installed.
[Non-Touchscreen Windows Mobile Other] BZ19:
:(

"Run the SDA Application Unlock.exe, it will greet you with "SDA successfully unlocked"."

This is the first step to take in order CID-Unlock my phone. After i downloaded the SSPL.zip and extracted files to my shadow, i couldnt find this "SDA Application Unlock.exe." Can someone point me in the right direction so that i could get wm 6.1 tested on my shadow.

Thanks in advance.:)
[Non-Touchscreen Windows Mobile Other] brandun_6:
For the CID Unlock the instructions say "5, Now run the RUU updater and flash the USBL.nbh" What does this mean and what do I have to do? I'm doing it now with the command prompt open on my desktop and my Shadow has the black dimmed screen.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
@brandun_6, Run the RUU that you downloaded from the SSPL post by jockyw2001. It will patch the bootloader.

@BZ19, here is a link to the SDA app unlock: http://www.gpcarreon.com/?p=151

Thanks crozzbreed for posting bugs. I'll look for some solutions. Until then, hold down the * button and it will let you choose T9/ABC mode/123 modes for the keyboard

Uploading new version to rapidshare now. Fixes: Comm Manager works, Settings work, ActiveSync works

Things to do for future test version:

Completely port XIP

Fix text messaging/PIE problem

Add Neo theme back into rom

Create BigStorage version of rom (will free up 30 MBs of space)
[Non-Touchscreen Windows Mobile Other] shadowmike:
bugs found

active sync runs and connects for 45 seconds after boot up. then disconnects and cant reconnect till reboots

can not add new gprs settings to make internetsharing work.

after entering settings menu once, cannot enter settings menu again untill reboot.

can not dissable screenlock no settings for it.

camera does not work. I plan on installing freddys shadow camera fix from the t-mobile update to see if the camera will indeed sart working again.

when booting up 6.0 windows mobile splash screen shows then 6.1 screen for 5 - 10 seconds.

can not set clock through 6.1 neo interface (GETTING STARTED)

comm manager only works after a fresh reboot after closing comm it will not open again

bluetooth is non existant. i was going to active sync using bluetooth but there are no bluetooth settings on the phone.

wifi does not work

____

after trying to app unlock and install the freddy camera.

all cabs will not installl due to no privlidges.

i am sorry if these have been adressed but just pointing out what ive noticed so far.
[Non-Touchscreen Windows Mobile Other] shadowmike:
how are you connecting to the phone if active sync isnt working ?

also how will i install this new version if i cant connect the phone to active sync
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
A couple more bugs i found:

**EDIT didn't see this was allready posted**The camera doesn't work, says its missing camera resources.

And for the internet it says your internet connection is not configured properlly.
[Non-Touchscreen Windows Mobile Other] shadowmike:
i got t-mobiles rom back on the phone just to fimiliarize my self with flashing on windowos mobile htc phones.

if this were a psp it would be a piece of cake but the psp scene definiatly is making this alot easier then most new users to this community.

all i have to say is, keep up the good work and have you gotten the new version uploaded yet ?
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
how do i reflash the phone(so i can put back on the old t-mobile rom) active sync isn't connecting to the phone, and the flash program isn't connecting to the phone.
[Non-Touchscreen Windows Mobile Other] kron2:
how do you do this"5, Now run the RUU updater and flash the USBL.nbh" and i don't see the ruu in the sspl folder post by jockw2001 :confused:
[Non-Touchscreen Windows Mobile Other] shadowmike:
kron I would advise to not do this. Wait till the next version.

also to get back to the t-mobile rom. Shut down the phone. and hold the camera button and turn on the phone. The phone should go to the 3 color screen. From there plug in your usb cable wait 10 seconds and run t-mobiles update rom and it will install the t-mobile rom. The 6.1 rom number is 1.0.0.0 so that you can still install t-mobiles rom.
[Non-Touchscreen Windows Mobile Other] benjaminries:
Yeah, I poked around that thread and a few others. Anyone who has tried to package the Neo homescreen into a CAB has always hit a dead-end; most seem to think it has something to do with \Windows\cmhome.dll having a dependency on cmhome_smartfon.dll - the later of which cannot be found in any device or ROM dump. So just copying and registering DLLs, registry keys and PNG files to other devices has not worked so far.

Though they got the Neo interface successfully cooked into a Tornado WM6 ROM, nobody provides any info on how they pulled that off exactly. Nobody has ever got Neo working on WM6.1 as far as I can tell.

I remain convinced that both our old WM6 "Neo" theme and the new WM6.1 "Slide" theme use registry keys under HKLM\Microsoft\CHome. Indeed, that's how freddy's photo dialer has been easily transposed to WM6.1 (often without giving him credit, hehe). They also both rely on the DLL \Windows\cmhome.dll - and if those files aren't the same between Shadow WM6 and generic WM6.1, we might have to say bye-bye to the Neo interface.

Come to think of it though, there might be some upsides to Neo and Slide sharing the same registry keys - user customizations like order, extra CLinks and CProgs, etc. could be consistent across both themes. Time for me to stop asking these questions, though, and just fire up the WM6.1 emulator to do some comparisons.
[Non-Touchscreen Windows Mobile Other] shadowmike:
that would be great to know ben.

also any one find away to install any programs ?

edit

tried to get the images from the comm manager but couldnt find them using file explorer on the shadow.

will have to wait till we are able to explore the phone
[Non-Touchscreen Windows Mobile Other] ND4SPD:
After turning off your phone, you can enter bootloader by pressing the on/off button, back button, left and right soft key buttons and the home button for 2 secs and release on/off button while still holding other buttons until it turns on. It goes into bootloader and for some reason you don't need to SSPL.
[Non-Touchscreen Windows Mobile Other] benjaminries:
RE: cmhome.dll - I've compared them between devices, and one DLL is twice the size of the other. These are different versions of the file; one displays Neo and the other displays Slide.

I have lost much of my previous hope in seeing these two interfaces interchangeable in the same ROM.

RE: comm manager - you're probably going to need Total Commander to get at those files.
[Non-Touchscreen Windows Mobile Other] freyes01:
Try to install this: http://freddyreyes.com/forums/index.php?topic=339.0

If you don't have access to ActiveSync try to copy it to your SD card from your pc using a card reader.
[Non-Touchscreen Windows Mobile Other] freyes01:
Flashed my phone with WM6.1

This is what I found:

- Free Memory after upgrade: 81.14 MB

- Was able to install a screen capture utility and Total Comander from my memory card.

- Can't install any unsigned application: Can't install my tweaked version of CommManager

- App Unlock utility doesn't work

- Can't sync with the PC using ActiveSync

- Bluetooth/Wifi don't work (they can't be activated from the CommManager)

- Changing the Ring tone fails (give an error message).

- Was able to make and receive calls.

- I couldn't find the CHome images under \Windows directory (Only the ones related to Windows Live).

- Since CommManager doesn't work (hangs up) I couldn't configure T-Mobile GPRS setting so I wasn't able to test PIE6.1

- Camera doesn't work

- Back to T-Mobile Official WM6 Rom
[Non-Touchscreen Windows Mobile Other] maxima00se:
Great work guys, keep it up. I flashed to the rom, but there were too many bugs so I am going to flash back. I am looking forward to the next version!
[Non-Touchscreen Windows Mobile Other] maxima00se:
am I the only one that is having a hard time getting to the bootloader with this method?
[Non-Touchscreen Windows Mobile Other] Dougall:
For the people who prefer the Neo homescreen to the new one, wouldn't it be easier to extract the updated applications and put them in the shadow rom then to port it into 6.1? Just a thought.
[Non-Touchscreen Windows Mobile Other] pixelwix:
why would anyone want the neo theme anyways its just a ram hog, the new homescreen is much cleaner!!!
[Non-Touchscreen Windows Mobile Other] Dougall:
Personally, I prefer the neo theme. I like the style better. The new homescreen is much cleaner, I agree, but I think it's better suited for touchscreen devices.

I'm sure you could trim some of the fat off of the neo screen to free up some ram, and with all the themes out there it can look pretty too.
[Non-Touchscreen Windows Mobile Other] shadowmike:
I would like to have both, just to have both.

it would allow more theme customizing on my end. and end users would have 2 GUIS to choose from.

Ill admit i love the new 6.1 gui but i like some key features of neo

like a bigger picture preview and the ability to add rinkus dockstation.

however i noticed that he made a version for non shadows so hopfully he will hook us up on this 6.1 rom

also any news nd4spd ?
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
I had problems getting to the bootloader too, but I had the USB cable plugged in, make sure the USB cable is NOT plugged in, hold the camera button and turn on the phone.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Just to let you know, since my spring break ended, I won't have as much time to make new releases, or as frequent, so please bear with me.

That being said, I finished a new version yesterday which has improved, a bit:

All settings work, ringtones, sound, clock, etc.

Camera works

Forgot to put in the WiFi and bluetooth drivers, but will do so now

Got a successful connection with WMDC

I'll post soon. I'm going to port more of the XIP partition over before giving another test release. (only ported one file from the XIP partition). Another thing I will test is Neo and WM6.1 home screens in the same rom.

Just wondering, benjaminries, which chome.dll is bigger the Neo file or the wm6.1 file? Is my guess that the neo one being bigger correct? I'm on a different computer and can't check.
[Non-Touchscreen Windows Mobile Other] maxima00se:
So the wifi and bluetooth drivers are in the newest release and also, is it the same rapid share file? Also, is the internet bug fixed?

Seriously man, great work.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
No, whatever's in the other post is the original one that I posted. I'll post it very soon, hopefully.
[Non-Touchscreen Windows Mobile Other] shadowmike:
ND4SPD. Id be happy with the version you have yet to release. Even if it was the final. You have done the unthinkable along with the help of others and I greatly appreciate what you've done and the hard work you've put into this.

Ive told jockw as soon as i get money on my paypal im donating.

One question what kitchen can I use to extract the rom you give us that way I can change and add acouple apps here or and there.

and for the new release.

How is installing unsigned code and cabs working ?
[Non-Touchscreen Windows Mobile Other] ND4SPD:
As soon as we have a release that is polished and ready for everyone to use, pixelwix has graciously offered to make a kitchen out of this rom.

I haven't tried installing any cab files yet. I had gone back to the T-mo rom for the day so that I had a working phone and will report as soon as I put a newer version on.
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
Did you happen to fix the random shutdown bug? A work around I found in the old rom was playing a song over and over again and leave media player running the background, a new workaround we might be able to do is in the power management settings.

Anyone know why Active Sync wouldn't pick up the phone with the new rom?
[Non-Touchscreen Windows Mobile Other] shadowmike:
Thank you. I also switched to and from the t-mobile rom the past 10 hours testing the 6.1 out here and there.

As for the active sync im guessing there was a file missing or somthing causing it not to connect.
[Non-Touchscreen Windows Mobile Other] benjaminries:
RE: Neo vs. Slide

This has been tried without success. New WM6.1 features:

a) Slide homscreen: uses reg keys and DLLs with same names as Neo UI

b) New Mobile IE: won't port

c) New threaded SMS: won't port (new tmail.exe won't run on WM6)

It would be nice, but as I've tried to show with my preliminary investigations, this won't be a simple accomplishment. I'd rather see brilliant guys like ND4SPD focus on making a stable, fully-functional WM6.1 ROM without the Neo UI for now. Once that's done, we can try to port Neo as an add-on theme.

I'm pretty sure the Neo version of the DLL is the bigger one - over 400 kb on my device. Others have posted the new cmhome.dll from WM6.1 on xda-devs, and it is just over 200 kb.

So please, let's just leave Neo out of this for now! I like it as much as anyone, but I'd hate to see it stall the release of a clean, working WM6.1 ROM.

On a different note: can anyone report on if/how the scroll-wheel works in the new ROM? There are some mysteries that might crop up. I know that in just any app, the scroll wheel emulates up/down. In the homescreen and in xt9, the wheel emulates left/right. In Windows Media, the scroll wheel switches to the opposite of up/down, so that clockwise = up = volume up. In different UI controls (lists, pages, etc.) the wheel moves things slower or faster.
[Non-Touchscreen Windows Mobile Other] brandun_6:
I installed this last night and used today.

Major Bugs (for me)

- Turns off after 5 minutes of inactivity.

- Most settings don't work. (Can't change lock settings)

- Can't go straight to your Memory Card pic folder from the Menu in Photos.

- No internet connections.

Pros

- Calling works perfectly.

- Texting works perfectly.

- Home Screen completely functional.

- It works!

No matter the bugs it's still great to me. ND4SPD and everyone that helped, you guys are great! Thanks.

@benjaminries

The Scroll Wheel works the same as it did on 6.0 except on the homescreen it scrolls up/down. As far as I've seen. About using it in apps, I'm not sure because I wasn't able to install any.
[Non-Touchscreen Windows Mobile Other] benjaminries:
How about in Windows Media? Does clockwise turn up the volume, and clockwise turn it down?
[Non-Touchscreen Windows Mobile Other] brandun_6:
Nope in Windows Media track lists it scrolls up/down and doesn't control the volume anymore. But if you're at the Now Playing screen it does turn the volume up/down.
[Non-Touchscreen Windows Mobile Other] shadowmike:
I believe I remember the wheel controling the voluem when i tested the wmp

also benjamin. I 100% agree to leave neo out untill we get a 99% stable 6.1 rom running on the shadow then try and incorporate it.

Just waiting for the version nd4spd has rdy that way i can hopfully get rid of running the tmo rom and then focus on testing and changing 6.1
[Non-Touchscreen Windows Mobile Other] benjaminries:
The mystery is this: what controls the differing scroll wheel behaviour? A unique driver? A DLL? Either the applications themselves are responding differently to the wheel, or the wheel is emulating different d-pad buttons (at differing intervals) depending on the application that has focus. Solve this, and we may learn how to adjust the sensitivity of the scroll wheel generally!
[Non-Touchscreen Windows Mobile Other] shadowmike:
have any other phones with scroll wheels been hacked to slow the scroll ?

I know in some versions of HTC album when i turn the wheel clockwise it will zoom the picture in. But on the version I have now CounterClockwise zooms the picture in. Based on this, I think that It can be controlled by the focused app.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
Ok. I'll leave the Neo out until we can get wm6.1 stable and clean. I haven't got to work on it yet because of schoolwork, but I promise that I'll do some XIP porting later tonight.
[Non-Touchscreen Windows Mobile Other] shadowmike:
that will be great.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
I've just posted in the dev & hacking forum about the powering off after inactivity problem. At this point, I don't know what other XIP files are safe to port. Does anyone else know the files that aren't device specific?
[Non-Touchscreen Windows Mobile Other] benjaminries:
Maybe. If counter-clockwise zooms in, that could also just mean a lack of recognition of the scroll wheel by the particular app (or a lack of recognition of the particular app by the control wheel driver), leading to the default "up key" action. Whether it is the app or the driver, there must be some default behaviour for when the app is not specifically designed to work with a wheel. That behaviour must be controlled by the driver, not the app.

It is that default behaviour we'd likely like to mess with, if we could find it. And if special app-specific wheel behaviours were also controlled by the driver, we'd have a better shot at getting the wheel to behave correctly with the new WM6.1 homescreen.
[Non-Touchscreen Windows Mobile Other] ND4SPD:
This dll would be found in the bronze folder of the wm6.1 rom dump. Or should I just post the module on here?
[Non-Touchscreen Windows Mobile Other] shadowmike:
dont mean to pesk you nd4spd but is there anyway for us to get a copy of the rom that allows pc connection bluetooth and wifi ?

I could live with it shutting off every ten mins. As stated before let a song play in WMP with WMP vol at 0 and it will stay on.

Just wondering.
[Non-Touchscreen Windows Mobile Other] benjaminries:
Nah dude. I'm in exams this month; will check into things in the next ROM release.
[Non-Touchscreen Windows Mobile Other] crozzbreed23:
I still think if we changed some of the power mangement settings it wouldn't shut off anymore.
[Non-Touchscreen Windows Mobile Other] freyes01:
I'm been playing with MS WM6.1 emulator and one thing that I noticed is that Bluetooth/Wifi, CommManager don't work. Could this be the reason of why those features don't work in this Rom?

Maybe we should use the Motorola Q9 Rom instead.
[Non-Touchscreen Windows Mobile Other] benjaminries:
Check out the XDA-devs forum section for the HTC Vox. Cookers have a clean, stable and working WM6.1 ROM that they claim is based *entirely* on the emulator image (with respect to system files), with no WM6 files whatsoever. Maybe they can explain how that worked out, because they're definitely using a working Comm Manager.

I'm talking about their "WM6.1 1.1" rom by Dr. Martin Gonzo, here - http://xdaforums.com/showthread.php?t=384129

Aside from the keyboard, the HTC Vox is actually pretty similar to the Shadow in terms of hardware. Screw the Q9! :)
[Non-Touchscreen Windows Mobile Other] pixelwix:
it doesn't work cus its an emulator the files are there but there is no hardware to support it. i extracted the files out of the emu image and the drivers were in there.. still working on making a room too. i'm still porting the xip, once thats one ill see if its flashable
[Shield Tablet Q&A, Help & Troubleshooting] Hand76:
System/xbin or su/xbin?

On Android 6
[Samsung Galaxy S9  Guides, News, & Discussion] ChillinKalinin:
PDAnet is able to directly share internet over USB, but it seems limited in what it can do. I can hardly connect to any game servers, steam's download speeds are slow (Figured it may be some Steam port issue but I also have problems with Origin so I'm unsure), and I can't directly connect to other peoples lobbies. I'm using Ver 5.10.5 of Pdanet (and have paid version) and am wondering if anyone knows a possible solution. I tested connection with built in USB tethering and I was able to connect, but I'd rather not blow through the limit for the built in option
[Samsung Galaxy S9  Guides, News, & Discussion] van131:
I would second this. When I upgraded to the s9 plus everything got slow.... Any solutions?