FIX for lost settings (passwords, BT pairing,etc.)?

[Stingray66]

I've installed MARY 3.7.1 and some other cabs. After a soft reset it was normal that BT pairing, passwords and the GPRS settings were gone or didn't work.

By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
I thought the solution was in MARY 3.7.1, but after uninstalling BT_DUN.cab I've found out that the settings were lost again.
The CAB is here: http://forum.xda-developers.com/attachment.php?attachmentid=39883&d=1180164571

Can someone check this with a ROM with the new XIP like MARY, PDAVIET, schaps, etc.?

[mousio]

By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
Hmm, at first glance you actually seem to be right :eek: which is good news for many among us :D

I had never installed that CAB before, and I learned to live with lost passwords etc. (never got around to trying the workaround), but that's all about to change with this easy fix
Some more tests have revealed that in my case the "first glance" must have been sheer luck :(
I mainly checked whether wifi passwords were required again, and tried uninstalling/re-installing/rebooting/resetting/... but all I can conclude is that only sometimes the settings are preserved and still most of the times the settings are lost - this regardless of the aforementioned CAB.

Well, I haven’t lost hope yet, though. Maybe someone will figure it out, but the sooner the better :)

[StefanoRuleZZ]

MANY THANKS,
It's seems works fine...

Many thanks again...

[SuperSport]

I've installed MARY 3.7.1 and some other cabs. After a soft reset it was normal that BT pairing, passwords and the GPRS settings were gone or didn't work.

By accident I tried an old CAB from mun_rus calls BT_DUN.cab, I don't install this one normally when I reflashed my device.
I thought the solution was in MARY 3.7.1, but after uninstalling BT_DUN.cab I've found out that the settings were lost again.
The CAB is here: http://forum.xda-developers.com/attachment.php?attachmentid=39883&d=1180164571

Can someone check this with a ROM with the new XIP like MARY, PDAVIET, schaps, etc.?

This would be VERY cool if it works! I hope that's all there is to it. :D

Thanks again Stingray66! PS: Do you drive a Corvette?

[Stingray66]

MANY THANKS,
It's seems works fine...

Many thanks again...

Work here again too on the ROM FInixNOver 3.1

[Stingray66]

Thanks again Stingray66! PS: Do you drive a Corvette?

I did a couple of times, but I'm not in the position right now to buy one. Priority is my wife, kids and moving to another house right now, but a Corvette from 1966 is a great car ..... beautiful!

[adewidt]

I already fixed this problem in my latest ROM (version 1.2).
I created a modified XIP and changed some buetooth drivers to verify A2DP still works.

I will create a personal ROM to verify if this solutions works too!
Would be great if this is another solution to fix the problem.

[sergitec]

Ok, I found something!
I opened the rom the ausdim WM6.1 and Mary rom 3.7 and took the files of the *. hv ausdim and copy for the 3.7 rom Mary!
The two rom´s are the same version and don't have any trouble copy, and I noticed that once the 3.7 rom Mary no longer loses the passwords or the codes of wifi!
I think the problem is in the register!

HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE

But where???

Translated by Google, sorry!

[adewidt]

Ok, I found something!
I opened the rom the ausdim WM6.1 and Mary rom 3.7 and took the files of the *. hv ausdim and copy for the 3.7 rom Mary!
The two rom´s are the same version and don't have any trouble copy, and I noticed that once the 3.7 rom Mary no longer loses the passwords or the codes of wifi!
I think the problem is in the register!

HKEY_CLASSES_ROOT
HKEY_CURRENT_USER
HKEY_LOCAL_MACHINE

But where???

Translated by Google, sorry!
The problem is in the XIP section, it is in the nk.exe (kernel).

Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.

Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.

[themaskfly]

The problem is in the XIP section, it is in the nk.exe (kernel).

Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.

Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.

well actually the old xip didnt lose the settings, yet it cause unstable de system, problem include cant find the contacts, lose response when launch the programs from SD card after wake up. I've been suffering for a long time about it which doesnt happens with the new xip and i dont know why, with the same cooking only expect the new and old xip

[adewidt]

well actually the old xip didnt lose the settings, yet it cause unstable de system, problem include cant find the contacts, lose response when launch the programs from SD card after wake up. I've been suffering for a long time about it which doesnt happens with the new xip and i dont know why, with the same cooking only expect the new and old xip
I did not experience any of the problems you describe.

[firiel]

The problem is in the XIP section, it is in the nk.exe (kernel).

Ausdim uses an older XIP version which does not lose settings.
The only problem was the broken A2DP. I managed to fix this problem and Ausdim will include my solution to fix A2DP in his ROMs.

Upcoming ROMs from me and Ausdim will no longer lose settings.
I hope other ROM-cookers decide to use the older kernel too.

So if it is the XIP that matters we cant have a fix right ? Roms using the new XIP are doomed to have crappy A2DP

[adewidt]

So if it is the XIP that matters we cant have a fix right ? Roms using the new XIP are doomed to have crappy A2DP
As I already said, I managed to fix A2DP using the old bootkernel (nk.exe part of XIP).

This works for wm6.1 and wm6.0.
There is no reason good reason to use the new kernel in stead of the old kernel.

[ausdim]

As i say 4 months before here:

http://forum.xda-developers.com/showthread.php?t=342269

the old xip section (nk.exe) is working better with trinity 400mhz.

All my rom in this 4 months is builded with old nk.exe and i tell to cookers to use them to.

I dont see any reason to use the new (dopod) nk.exe with that very iportant bug.

No problems and nothing, nk.exe is the kernel from the device no nead to update that in the future.

The only problem it was in a2dp sound but after the fix from adewidt (Thanks again) ;) the sound it is perfect!

Thank's

[Stingray66]

I already fixed this problem in my latest ROM (version 1.2).
I created a modified XIP and changed some buetooth drivers to verify A2DP still works.

I will create a personal ROM to verify if this solutions works too!
Would be great if this is another solution to fix the problem.

Well after some resets, it does loose it's settings.

@adewidt
I'll try your 1.2 too, but I think the DEVICE ID of TomTom will change again (like it did whenm we switched from WM5 (official) to WM6 (DOPOD))

[adewidt]

Well after some resets, it does loose it's settings.

@adewidt
I'll try your 1.2 too, but I think the DEVICE ID of TomTom will change again (like it did whenm we switched from WM5 (official) to WM6 (DOPOD))
Yes it change your device ID.