PSP's/PS Vita's ARK-4 updater and XMB often don't detect new ARK-4 versions

[Dragartosaziados]

PSP/Vita Model

PSP-3000 (Slim & Bright), PCH-2000 (Vita Slim), VTE-1000 (Vita TV)

ARK Version

4.20.69 Rev 4

Homebrew/GAME (if applicable)

No response

Plugins ( if applicable )

No response

Steps to reproduce

PSP's/PS Vita's ARK-4 updater and the XMB often still don't detect a new ARK-4 version or install the same version even when a new version is out. When that happens, I have to manually update it.

USB Charge

Disabled

Overclock

Disabled

Power Save

Disabled

Balanced Energy Mode

Disabled

Autoboot Launcher

Off

Disable PSP Go Pause

Off

Unlock Extra Memory

Disabled

Memory Stick Speedup

Disabled

Inferno Cache

Off

Skip Sony Logos

Off

Hide PIC0 and PIC1

Off

Hide MAC Address

Off

Hide DLC

Off

Turn off LEDs

Disabled

Verification of form.

• I agree that I properly filled out the items listed above.

[JoseAaronLopezGarcia]

That's because we have to manually update the server. Should be fixed now.

[Dragartosaziados]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

[krazynez]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

[Dragartosaziados]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

[krazynez]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

Well its best to leave that disabled anyway.

[Dragartosaziados]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

Well its best to leave that disabled anyway.

Why, since even though it installs the same version (and not the new one, if out), it sometimes installs the new one (when if disabled it sometimes doesn't), if out?

[krazynez]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

Well its best to leave that disabled anyway.

Why, since even though it installs the same version (and not the new one, if out), it sometimes installs the new one (when if disabled it sometimes doesn't), if out?

Only time its really required is if we update the zip and not the revision number. The PSP will check the version string and see its the same number and say there is no update. Even though techinally there is one, just we didn't do a rev push.

[Dragartosaziados]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

Well its best to leave that disabled anyway.

Why, since even though it installs the same version (and not the new one, if out), it sometimes installs the new one (when if disabled it sometimes doesn't), if out?

Only time its really required is if we update the zip and not the revision number. The PSP will check the version string and see its the same number and say there is no update. Even though techinally there is one, just we didn't do a rev push.

What do you mean by the first sentence?

[krazynez]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

Well its best to leave that disabled anyway.

Why, since even though it installs the same version (and not the new one, if out), it sometimes installs the new one (when if disabled it sometimes doesn't), if out?

Only time its really required is if we update the zip and not the revision number. The PSP will check the version string and see its the same number and say there is no update. Even though techinally there is one, just we didn't do a rev push.

What do you mean by the first sentence?

That is the zip that the server grabs to extract the update file from. But we use Sony's way to parse if there are new updates from ark-4.ddns.net i.e: http://ark-4.ddns.net/psp-updatelist.txt if the ImageVersion doesn't change (make it highter) the PSP/Vita will think its still the latest version. We have revistions in a global file that update when we update it. i.e:

ARK-4/common/include/globals.h

Lines 74 to 77 in 5dd06e6

	#define ARK_MAJOR_VERSION 4
	#define ARK_MINOR_VERSION 20
	#define ARK_MICRO_VERSION 69
	#define ARK_REVISION 4

if we do not update the revision or version number but we update the zip file (first image) then the update server will always think its still the latest version available. So having "force update" is good to have when that rarity case happens. It is usually a quick fix before it affects the masses and not worth another revision for a simple fix.

[Dragartosaziados]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

Well its best to leave that disabled anyway.

Why, since even though it installs the same version (and not the new one, if out), it sometimes installs the new one (when if disabled it sometimes doesn't), if out?

Only time its really required is if we update the zip and not the revision number. The PSP will check the version string and see its the same number and say there is no update. Even though techinally there is one, just we didn't do a rev push.

What do you mean by the first sentence?

That is the zip that the server grabs to extract the update file from. But we use Sony's way to parse if there are new updates from ark-4.ddns.net i.e: http://ark-4.ddns.net/psp-updatelist.txt if the ImageVersion doesn't change (make it highter) the PSP/Vita will think its still the latest version. We have revistions in a global file that update when we update it. i.e:

ARK-4/common/include/globals.h

Lines 74 to 77 in 5dd06e6

	#define ARK_MAJOR_VERSION 4
	#define ARK_MINOR_VERSION 20
	#define ARK_MICRO_VERSION 69
	#define ARK_REVISION 4

if we do not update the revision or version number but we update the zip file (first image) then the update server will always think its still the latest version available. So having "force update" is good to have when that rarity case happens. It is usually a quick fix before it affects the masses and not worth another revision for a simple fix.

I guess I'll disable it, then (even if sometimes it can update ARK-4 unlike if disabled).

What's the difference between Inferno Cache's "LRU" and "RR" settings?

Clicking "SELECT" does nothing for some seconds when returning to the XMB from sleep mode or Custom Launcher, when exiting a game and after restarting the PSP or VSH. The PSP's Memory Stick LED is blinking and only once it finishes I can access the VSH MENU (among other things). I was told doing a full flash install and deleting VSHMENU.PRX from ARK_01234 would fix the problem but it stayed the same. Also, if pressing "L", "R" and "SELECT" buttons to force the VSH MENU to open like I was told, it still doesn't open it until I wait some seconds.

What does encrypted and decrypted PSN content mean? Are encrypted PSP games in PKG format and decrypted PSP games in ISO and folder format (with EBOOT.PBP inside them)? In which format are PSN PSP games, PKG? How can RAP files be used (which might come with PKG PSP games) on the PSP?

What's the difference between npdrm_free and npdrm_free_mod and nploader and nploader_mod and why doesn't the Wiki mention the npdrm_free_mod plugin (and the npdrm_free and nploader plugins) if it mentions the nploader_mod one?

What's the difference between Inferno Cache's "LRU" and "RR" settings?

Clicking "SELECT" does nothing for some seconds when returning to the XMB from Sleep Mode or Custom Launcher, when exiting a game and after restarting the PSP or VSH. The PSP's Memory Stick LED is blinking and only once it finishes I can access the VSH MENU (among other things). I was told doing a full flash install and deleting VSHMENU.PRX from ARK_01234 would fix the problem but it stayed the same. Also, if pressing "L", "R" and "SELECT" buttons to force the VSH MENU to open like I was told, it still doesn't open it until I wait some seconds.

What does encrypted and decrypted PSN content mean? Are encrypted PSP games in PKG format and decrypted PSP games in ISO and folder format (with EBOOT.PBP inside them)? In which format are PSN PSP games, PKG? How can RAP files be used (which might come with PSN PKG PSP games) on the PSP?

What's the difference between npdrm_free and npdrm_free_mod and nploader and nploader_mod and why doesn't the Wiki mention the npdrm_free_mod plugin (and the npdrm_free and nploader plugins) if it mentions the nploader_mod one?

Can the "Memory Stick speedup" setting break PSP games (I'm excluding this issue, which affects PS Vita's ARK-4 and may affect all PSP games ran from it).

Also, why and how does PS Vita's standalone ARK-4 make a sound when scrolling PSP games even with sound turned off?

EDIT: If "Force Extra Memory" is set to "Always", the PSP freezes and restarts some seconds after when exiting the european Spider-Man: Web of Shadows – Amazing Allies PSP ISO on ARK-4 while using the PS button. I'll set it to "Disabled", then.

[krazynez]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

Well its best to leave that disabled anyway.

Why, since even though it installs the same version (and not the new one, if out), it sometimes installs the new one (when if disabled it sometimes doesn't), if out?

Only time its really required is if we update the zip and not the revision number. The PSP will check the version string and see its the same number and say there is no update. Even though techinally there is one, just we didn't do a rev push.

What do you mean by the first sentence?

That is the zip that the server grabs to extract the update file from. But we use Sony's way to parse if there are new updates from ark-4.ddns.net i.e: http://ark-4.ddns.net/psp-updatelist.txt if the ImageVersion doesn't change (make it highter) the PSP/Vita will think its still the latest version. We have revistions in a global file that update when we update it. i.e:

ARK-4/common/include/globals.h

Lines 74 to 77 in 5dd06e6

	#define ARK_MAJOR_VERSION 4
	#define ARK_MINOR_VERSION 20
	#define ARK_MICRO_VERSION 69
	#define ARK_REVISION 4

if we do not update the revision or version number but we update the zip file (first image) then the update server will always think its still the latest version available. So having "force update" is good to have when that rarity case happens. It is usually a quick fix before it affects the masses and not worth another revision for a simple fix.

I guess I'll disable it, then (even if sometimes it can update ARK-4 unlike if disabled).

Where is the settings.txt file located to the "Inferno Cache" setting and what's the difference between Inferno Cache's "LRU" and "RR" settings?

Can the "Memory Stick speedup" setting break PSP games (I'm excluding this issue which affects ARK-4 and may affect all PSP games run from it).

I enabled the "Scan SAVEDATA" setting and savedata still doesn't appear in ARK-4.

Also, can the "Force Extra Memory" setting break PSP games?

EDIT: I have issues with the european Spider-Man: Web of Shadows – Amazing Allies PSP ISO on PSP's ARK-4 if the "Force Extra Memory" setting is set to "Always" because the PSP freezes when exiting it using the PS button and it restarts some seconds after.

Please refrain from adding questions not related to the issue this is about, if you wish to ask general questions we have a discord server that would be best to ask there.

[Dragartosaziados]

That's because we have to manually update the server. Should be fixed now.

Does it mean it will keep happening? Also, I don't understand why it sometimes detects the new version if closing and opening the Custom Launcher/ARK-4 and/or enabling the "Force update" setting.

Well if you "Force Update" it will always think there is a new version. Yes it can happen as @JoseAaronLopezGarcia stated we have to manually update the server to do stable updates its not automated like testing is.

Even if enabling the "Force update" setting, it will still often not detect updates when they're available but there are times it detects new ones and installs them, unlike if the setting is disabled.

Well its best to leave that disabled anyway.

Why, since even though it installs the same version (and not the new one, if out), it sometimes installs the new one (when if disabled it sometimes doesn't), if out?

Only time its really required is if we update the zip and not the revision number. The PSP will check the version string and see its the same number and say there is no update. Even though techinally there is one, just we didn't do a rev push.

What do you mean by the first sentence?

That is the zip that the server grabs to extract the update file from. But we use Sony's way to parse if there are new updates from ark-4.ddns.net i.e: http://ark-4.ddns.net/psp-updatelist.txt if the ImageVersion doesn't change (make it highter) the PSP/Vita will think its still the latest version. We have revistions in a global file that update when we update it. i.e:

ARK-4/common/include/globals.h

Lines 74 to 77 in 5dd06e6

	#define ARK_MAJOR_VERSION 4
	#define ARK_MINOR_VERSION 20
	#define ARK_MICRO_VERSION 69
	#define ARK_REVISION 4

if we do not update the revision or version number but we update the zip file (first image) then the update server will always think its still the latest version available. So having "force update" is good to have when that rarity case happens. It is usually a quick fix before it affects the masses and not worth another revision for a simple fix.

I guess I'll disable it, then (even if sometimes it can update ARK-4 unlike if disabled).
Where is the settings.txt file located to the "Inferno Cache" setting and what's the difference between Inferno Cache's "LRU" and "RR" settings?
Can the "Memory Stick speedup" setting break PSP games (I'm excluding this issue which affects ARK-4 and may affect all PSP games run from it).
I enabled the "Scan SAVEDATA" setting and savedata still doesn't appear in ARK-4.
Also, can the "Force Extra Memory" setting break PSP games?
EDIT: I have issues with the european Spider-Man: Web of Shadows – Amazing Allies PSP ISO on PSP's ARK-4 if the "Force Extra Memory" setting is set to "Always" because the PSP freezes when exiting it using the PS button and it restarts some seconds after.

Please refrain from adding questions not related to the issue this is about, if you wish to ask general questions we have a discord server that would be best to ask there.

I don't have a discord account and should I create issues for the problem, then? These questions should be answered in the GitHub repo.