Related
ACS Presents:One Click Odexer and Restoration Toolversion 1.0 - by tanimn
*** PLEASE NANDROID BACKUP ***
DETAILS:
OneClickOdexer is an odexing and restoration tool for deodexed roms. It will determine if it has been previously run and automatically odex your rom or restore it to a deodexed state. If a critical error occurs, it will return your phone to it's previous state. Care has been taken to only odex apps that come stock with an odex file.
With one click, it odexes.
With one click, it restores.
Complete details are available in the included README.TXT, including instructions for manual operation and running from the handset instead of through adb.
By changing from a deodexed to an odexed system you are modifying the method in which your dalvik virtual machine works. PLEASE backup your phone before using! I will accept no responsibility for your failure to follow this basic safety tenet.
PROS:
Increases speed by about 15%
Reduces memory usage
More space available on /data
Reduced use of dalvik-cache
CONS:
You might need to re-add some widgets and home screen icons after applying
You will need to restore your deodexed system to make any theme swaps (But that's just one click away...)
Exclusively for Samsung Epic 4g. Tested on DK28 and DI18 roms. Contact tanimn for porting instructions.
Thanks to raiderep for the idea, Paul O'Brien for the commands, and ACS for the help and support.
Downloads: (Please report mirrors)
MultiUpload
Sweet idea!
Sent from my Nexus S with a keyboard
Nice, thanks!
Alot of work went into this and its well worth it.
Sent From Da Hood.
hi, i am rooted with cwm 3.0.0.5(ext4).... is this program not compatible with that? it is saying it did not find root.... but i am definitely rooted and running cwm 3. thx
As always amazing work. Thank you the hard work long hours and dedication to your project and getting this out to the users benefit. I know everyone will enjoy the performance boost and ease of file conversion on the fly.... look out for some more great releases from ACS!
Looks really cool. I look forward to reviewing this tool!
yogi2010 said:
hi, i am rooted with cwm 3.0.0.5(ext4).... is this program not compatible with that? it is saying it did not find root.... but i am definitely rooted and running cwm 3. thx
Click to expand...
Click to collapse
When using the one click you neef to have your screen set to always on. Adb ask for su permission. You'll get a su pop up on your phone and you have to hot allow
Sent From Da Hood.
mysteryemotionz said:
When using the one click you neef to have your screen set to always on. Adb ask for su permission. You'll get a su pop up on your phone and you have to hot allow
Sent From Da Hood.
Click to expand...
Click to collapse
thx. got it to run but the phone seems to be not rebooting.... stuck at Samsung screen, then goes off and hangs at Samsung screen, etc etc.
yogi2010 said:
thx. got it to run but the phone seems to be not rebooting.... stuck at Samsung screen, then goes off and hangs at Samsung screen, etc etc.
Click to expand...
Click to collapse
If the script gets interrupted while it is going through the framework, this can happen. THIS is why you have that nandroid backup in cwm, right...?
If the script doesn't cause the phone to reboot on it's own, rerun the script before rebooting by hand, and restore a backup if your handset has stopped responding.
tanimn said:
If the script gets interrupted while it is going through the framework, this can happen. THIS is why you have that nandroid backup in cwm, right...?
If the script doesn't cause the phone to reboot on it's own, rerun the script before rebooting by hand, and restore a backup if your handset has stopped responding.
Click to expand...
Click to collapse
yep, i have the backup. the script did finish and start the reboot itself... the reboot just keeps getting stuck at Samsung screen, then turning off, and getting stuck again and turning off. no biggie, i can always restore, just lettin ya know what happening.
What rom are you running
Sent From Da Hood.
Thanx for doing this for us. It will really come in handy for re-odexing after adding mods and/or theming to a deodexed system.
mysteryemotionz said:
What rom are you running
Sent From Da Hood.
Click to expand...
Click to collapse
been running Viper 4.0.3 ext4.
yogi2010 said:
yep, i have the backup. the script did finish and start the reboot itself... the reboot just keeps getting stuck at Samsung screen, then turning off, and getting stuck again and turning off. no biggie, i can always restore, just lettin ya know what happening.
Click to expand...
Click to collapse
Yeah, what he said...
Thanks. What rom is this happening with? I'd like to be able to reproduce it and find out what's going on...
tanimn said:
Thanks. What rom is this happening with? I'd like to be able to reproduce it and find out what's going on...
Click to expand...
Click to collapse
Look up
Sent From Da Hood.
tanimn said:
Thanks. What rom is this happening with? I'd like to be able to reproduce it and find out what's going on...
Click to expand...
Click to collapse
no prob... it's happening with Viper 4.0.3 ext4. i just odined back to stock tho, and flashed Syndicate 1.0.2, because i wanted to check that out for fun anyway, lol. the only thing is i'm having a problem with my touchscreen now.... the physical buttons work, but the touchscreen mostly doesn't work... just sometimes. touchscreen sometimes does work after a reboot, then goes out, etc/
yogi2010 said:
no prob... it's happening with Viper 4.0.3 ext4. i just odined back to stock tho, and flashed Syndicate 1.0.2, because i wanted to check that out for fun anyway, lol. the only thing is i'm having a problem with my touchscreen now.... the physical buttons work, but the touchscreen mostly doesn't work... just sometimes. touchscreen sometimes does work after a reboot, then goes out, etc/
Click to expand...
Click to collapse
Sounds like it's still settling, TBH. Could you pastebin a logcat?
tanimn said:
Sounds like it's still settling, TBH. Could you pastebin a logcat?
Click to expand...
Click to collapse
sorry, not sure what you mean by pastebin a logcat... i closed all the screens of the program by now.
btw, touchscreen working fine now .
Just installed on Nebula v1.0.6 with EXT4. Seems to be running normally, I'll play with it some more.
Hi,
I have a Wifi only Stock XOOM with 3.0.1
Whenever I power off and then power on my XOOM , after first screen unlock it shows -
The process android.process.acore has stopped unexpectedly with a Force Close button.
Any idea what this process does or why it is happening ?
Ishan
LeapSwitch|Ishan said:
Hi,
I have a Wifi only Stock XOOM with 3.0.1
Whenever I power off and then power on my XOOM , after first screen unlock it shows -
The process android.process.acore has stopped unexpectedly with a Force Close button.
Any idea what this process does or why it is happening ?
Ishan
Click to expand...
Click to collapse
Quite generic. What specific customization you have done? for example, launcher? any other apps that set to set some configurations on boot? more information may be helpful to see what may be going on..
jiwengang said:
Quite generic. What specific customization you have done? for example, launcher? any other apps that set to set some configurations on boot? more information may be helpful to see what may be going on..
Click to expand...
Click to collapse
Firstly, this should go to Q&A forum, I am sorry for posting it here.
No customization other than installing a few apps, like Engadget, Skype, Arseblog, and some games. None of them should require something while booting.
Launcher and background is same, I just got it 2 days ago.
LeapSwitch|Ishan said:
Firstly, this should go to Q&A forum, I am sorry for posting it here.
No customization other than installing a few apps, like Engadget, Skype, Arseblog, and some games. None of them should require something while booting.
Launcher and background is same, I just got it 2 days ago.
Click to expand...
Click to collapse
No no , don't take me wrong. when I said quite generic I meant please describe / include a bit more info for discussion =) that acore process is quite generic one.
Sorry that caused some misunderstanding.
Did you try to flash it back to stock (since you haven't have tons of customizations yet, but still, backup information data you may have).
If you use http://forum.xda-developers.com/showthread.php?t=1052644
to do a stock flash of boot.img system.img recovery.img userdata.img
does this problem still occur? Seems to me it is some minor system glitch. Hopefully it will go away once you flash it to stock.
jiwengang said:
No no , don't take me wrong. when I said quite generic I meant please describe / include a bit more info for discussion =) that acore process is quite generic one.
Sorry that caused some misunderstanding.
Did you try to flash it back to stock (since you haven't have tons of customizations yet, but still, backup information data you may have).
If you use http://forum.xda-developers.com/showthread.php?t=1052644
to do a stock flash of boot.img system.img recovery.img userdata.img
does this problem still occur? Seems to me it is some minor system glitch. Hopefully it will go away once you flash it to stock.
Click to expand...
Click to collapse
I guess I will wait a few days for the 3.1 update and see if it gets fixed. If not, I will try your method.
Thanks a lot,
Ishan
I am trying to install NextGen 1.5
Problem is, in main menu, whenever I go to "recovery", fone gets struck with htc logo(white background). Then I have to take out battery, re-insert, press vol down+power up .....fast boot and run "recovery.bat" from pc(while connected fone to pc). then I get back the CWM Recovery Menu.
This is occuring everytime. Please help me to fix it.
Try with some other recovery, it's not like you don't have a choice And from which main menu you're getting in to recovery?
shortyoko said:
Try with some other recovery, it's not like you don't have a choice And from which main menu you're getting in to recovery?
Click to expand...
Click to collapse
well "main menu" refers to vol down+power button, which leads to "fast boot, recovery, factory reset" options.
Also u only suggest me some better recovery plz.
http://forum.xda-developers.com/showthread.php?t=2123503
I don't know if it's better or not, I'm still with the good old yannou's recovery, staying with the principle 'if it aint broke, don't fix it'
shortyoko said:
http://forum.xda-developers.com/showthread.php?t=2123503
I don't know if it's better or not, I'm still with the good old yannou's recovery, staying with the principle 'if it aint broke, don't fix it'
Click to expand...
Click to collapse
Thanks buddy...1 more thing, I hv installed nextgen1.5 Now when i go to music player-->sound enhancer..i get a FC, can u help me wid dis ?
Plus when i try to grant SU permission to any app..it says "Sorry, test failed. This feature cannot be granted to ur fone"
Fone is perfectly rooted. Had been using it for 1 yr, n now for the frst tym put custom rom and all these issues.
That's for the dsp
.Music player force closes bcoz of DSP libraries to fix just remove the library file from /system/lib/soundfx/libcyanogen-dsp.so it will perfectly like breeze.
Click to expand...
Click to collapse
For super user, enable usb debugging option from the phone menu(at the moment I don't remember where it was in the menu)
shortyoko said:
That's for the dsp
For super user, enable usb debugging option from the phone menu(at the moment I don't remember where it was in the menu)
Click to expand...
Click to collapse
Thanks a ton ! worked like charm ! +1
If u dont mind, tell me from where did u get that solution for music player ? I was looking for that but google dint help >_<
From NExtGen thread, when firstly 1.5 was released this was kind'a annoying bug, so there was a lot of question about that, here is the specific post from where I took it > http://forum.xda-developers.com/showthread.php?p=33599083&highlight=1+5+dsp+fix#post33599083
Just a friendly advice for the next time, there is a 'search in this thread' function which is really helpful when you have an issue with, whichever rom, cos it's possible for somebody to yell at you if you asked something that has been answered several times before
shortyoko said:
From NExtGen thread, when firstly 1.5 was released this was kind'a annoying bug, so there was a lot of question about that, here is the specific post from where I took it > http://forum.xda-developers.com/showthread.php?p=33599083&highlight=1+5+dsp+fix#post33599083
Just a friendly advice for the next time, there is a 'search in this thread' function which is really helpful when you have an issue with, whichever rom, cos it's possible for somebody to yell at you if you asked something that has been answered several times before
Click to expand...
Click to collapse
will keep that in mind thought google was more accurate, but oh well !
Help?
You got your answer bro, or still need help....
Sorry i checked PM today so didn't reply...:good:
artistaditya said:
You got your answer bro, or still need help....
Sorry i checked PM today so didn't reply...:good:
Click to expand...
Click to collapse
its fine, shortyoko helped me. You may edit the thread name with [solved] tag
try another custom rom
Kinda new to this so forgive me if i miss something somewhere and if i need to give more information somewhere just let me know.
With that out of the way I'd like to start with the fact that this is my first rooted device. Currently on C-spire (cellular south) if that matters.
A few days ago before the phone was rooted or even unlocked i went to make a phone call and the screen blacked out and a few seconds later went into a reboot loop where it would get to the Motorola Logo for about 6 seconds or so then shut off and try again ad nauseam until the battery died. After letting the battery die and connecting it to the charger it continued the loop so after a quick gogle search I began fiddling with buttons and realized i could boot into fastboot and recovery modes. I decided i might as well root since it couldnt get a whole lot worse and after a quick look around the forums and a trip to motorola to unlock my phone i was able to flash TWRP recovery, after which i accidentaly wiped the os, managed to find any number of replacement roms none of which solved the boot issue. I eventually found the stock Sprint roms which allowed the phone to boot and work for the most part, but it wont send media messages and has trouble picking up 4g service. I am also forced into using the sprint updater among other things which include having sprint plastered everywhere I have tried flashing several custom roms (pacman, paranoidandroid, and cyanogen) all of which get hung up booting just like the phone did before but the sprint stock rom will reload and work just as before. I'm not sure what would be causing this or if there is a way to fix it and i apologize for the wall of text. If any more info is needed let me know and ill provide ot to the best of my knowledge. Thanks in advance :fingers-crossed:
So all ROM's fail to boot?
Are you doing a factory reset in TWRP before you boot?
Are you flashing gapps? Although that shouldn't cause the phone to fail at booting...
Correct. All roms except the stock sprint rom fail to boot.
Now that i have everything backed up on my external sd I've tried factory reset using twrp as well as wiping everything prior to flashing a ROM as well as after but
Before booting. And the many combinations thereof
And yes i am flashing gapps.
You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.
arrrghhh said:
You don't get any errors when it flashes?
Did you check the md5sums?
I flash around a lot, and just got another Q - latest ROM's are not a problem here.
Click to expand...
Click to collapse
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though
AMerexican said:
I haven't gotten any errors while flashing. Not quite sure how to check the the md5 sums though
Click to expand...
Click to collapse
Every ROM should include a md5sum with it. If you're on Windoze, use a program like WinMD5 - check the md5sum locally, and compare it to what is on the server. If they match, the download is probably good.
So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?
AMerexican said:
So after checking the pacman rom matched up (it's the most recent one I've tried), the cyanogen didnt
but i recently redownloaded it and its better now (haven't tried flashing yet), and I can't seem to find the MD5sum for
the paranoid android rom on here.
Anything else i should try?
Click to expand...
Click to collapse
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.
arrrghhh said:
The PA build I think is "blind", I don't know if anyone has tried it - additionally, the individual who built it does not own this device... So it's double blind? Haha
The CyanogenMod ROM's, however, are official and work great - many others have confirmed this.
If you had a bad download, that would explain it.
Click to expand...
Click to collapse
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
I suppose some sort of hardware issue. Like I said, I've flashed most of the newest ROM's here for the Q - all work fine. Hell, some I even ported myself...
I'm kind of at a loss. Can you get adb? Not even sure what to check for next... if you are wiping properly in recovery, that should be sufficient.
Hm, I guess that brings up a good point. Have you tried wiping system, flashing, doing a factory reset, then booting? Most, if not all of the ROM's should wipe /system before flashing... So it probably won't do anything different.
AMerexican said:
I tried flashing the good download this morning, it hung up just like the others.
I get the bootloader unlocked screen then it'll show the cyanogen logo for roughly 24 seconds the first time before hanging up,
after which it reboots to the bootloader unlocked screen, but when it gets to the cyanogen logo each time gets subsequently shorter between hangups...
Any ideas?
Click to expand...
Click to collapse
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.
kabaldan said:
After the crash during CM bootanimation, boot to recovery and
Code:
adb pull /data/dontpanic/apanic_console
apanic_console should contain the log of the kernel panic, post it here.
Click to expand...
Click to collapse
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead
arrrghhh said:
For my own personal edification, /proc/last_kmsg would work in this instance as well?
Just curious why you went for the apanic_console instead
Click to expand...
Click to collapse
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot
kabaldan said:
Yes, /proc/last_kmsg would work as well.
Though there's a scenario were it wouldn't be the same - if the user would miss the right time to hold 'volume up' (to get to the recovery after crash) and pressed "power+volume down" to force reboot and try to enter recovery again. In such case, /proc/last_kmsg would not contain the panic from previous boot, the panic would be only in /data/dontpanic/apanic_console.
/proc/last_kmsg - log from the last boot
/data/dontpanic/apanic_console - log from the last crashed boot
Click to expand...
Click to collapse
Ah, that makes sense - I was not aware of this apanic_console
Thank you!
arrrghhh said:
Ah, that makes sense - I was not aware of this apanic_console
Thank you!
Click to expand...
Click to collapse
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?
AMerexican said:
I'm getting an error from the forums saying the text is too long. any way around that? or do i need to divide into multiple posts?
Click to expand...
Click to collapse
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!
arrrghhh said:
Pastebin.com, hastebin.com, pastebin.ca, heck even put the file in .txt format and attach to this post, upload it dropbox...
Thanks!
Click to expand...
Click to collapse
Thanks wasnt sure of the forums rules as far as that was concerned
http://pastebin.com/QFq1naK0
Any ideas?
Or anything else i need to do?
My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
haimmalka said:
My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
Click to expand...
Click to collapse
did you follow all instructions for the new rom install properly? its some problem with the rom. Try a new rom and make sure you follow all the instructions properly
rollerdyke44 said:
did you follow all instructions for the new rom install properly? its some problem with the rom. Try a new rom and make sure you follow all the instructions properly
Click to expand...
Click to collapse
I do it right
wipe
Then install rom
There rom works
Some do not work to restart always get stuck
I wonder why
haimmalka said:
My device would always restart
I know my device right
No untying
I found a problem
Why is he doing restart
I am with this rom
It works fine all is not doing a restart
When I install another rom problem begins to restart stuck
Example Hammerhead v1.8 installed BlissPop
And much rom it to the same problem
Why is this happening? Really strange problem
There is a solution? Know why this happens?
Sorry for my bad English
Click to expand...
Click to collapse
If nothing else works flash a factory image ☺
sachin.parmar100 said:
If nothing else works flash a factory image
Click to expand...
Click to collapse
What you seem I do not understand?
haimmalka said:
What you seem I do not understand?
Click to expand...
Click to collapse
I meant if any other methods doesn't work then grab a factory image via Google server and flash it via fastboot
Link :
https://developers.google.com/android/nexus/images
sachin.parmar100 said:
I meant if any other methods doesn't work then grab a factory image via Google server and flash it via fastboot
Link :
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I understood but I ask why this is happening
Some of the works
And some do not work restart
I want to know what the problem is
Probably kernel issue.
Aerowinder said:
Probably kernel issue.
Click to expand...
Click to collapse
Explain what this means?
haimmalka said:
Explain what this means?
Click to expand...
Click to collapse
Google it
dicecuber said:
Google it
Click to expand...
Click to collapse
Hahaha
I looked it up on Google
I went back to the same state device always do a restart
Until it worked fine now again it came back to do it] =
I was looking google what he means I get here:
http://kernels.franco-lnx.net/Nexus5/5.0/
Then again it returned to constantly restart the device
Now there is a direction to know how it happens?
How to fix it?
I do not remember what I did that worked
Tip know at least that's how it happens:crying:
haimmalka said:
Explain what this means?
Click to expand...
Click to collapse
A kernel acts as a connection between the
hardware and the software.
so if you flash a wrong kernel, it will misbehave
sachin.parmar100 said:
A kernel acts as a connection between the
hardware and the software.
so if you flash a wrong kernel, it will misbehave
Click to expand...
Click to collapse
I think that's a problem for the solution of the fire makes it
I order the same day repair lab
Flash a factory image. If the restarts stop then you know it's a problem with the ROM/kernel. Not all phones are identical, what may work for some doesn't always work for others. Your phone simply may not like some custom kernels, simple as that. If the ones you are flashing are undervolted by default that could be the problem, as some phones respond better to undervolting than others.
_MetalHead_ said:
Flash a factory image. If the restarts stop then you know it's a problem with the ROM/kernel. Not all phones are identical, what may work for some doesn't always work for others. Your phone simply may not like some custom kernels, simple as that. If the ones you are flashing are undervolted by default that could be the problem, as some phones respond better to undervolting than others.
Click to expand...
Click to collapse
Happens all the time for my device
I also install this rom Original still to helping through Toolkit
I also put a device
Start-up Shutdown button repair
It did not help thinking maybe this is the problem
So what is the problem I can not figure] =
haimmalka said:
Happens all the time for my device
I also install this rom Original still to helping through Toolkit
I also put a device
Start-up Shutdown button repair
It did not help thinking maybe this is the problem
So what is the problem I can not figure] =
Click to expand...
Click to collapse
Don't use toolkits. Flash the system image with fastboot. If the problem is still there, it's your phone. If the problem disappears, it's the ROM/kernel. Again, use fastboot and not a toolkit.
_MetalHead_ said:
Don't use toolkits. Flash the system image with fastboot. If the problem is still there, it's your phone. If the problem disappears, it's the ROM/kernel. Again, use fastboot and not a toolkit.
Click to expand...
Click to collapse
I try many things to no avail
I put it back to the lab to solve this problem
I've had enough to deal with it without success..
I do not know if it's a software problem
Or issue with the device
I do not believe more than 5 Nexus device that happens to many people
haimmalka said:
I try many things to no avail
I put it back to the lab to solve this problem
I've had enough to deal with it without success..
I do not know if it's a software problem
Or issue with the device
I do not believe more than 5 Nexus device that happens to many people
Click to expand...
Click to collapse
But have you restored to 100% stock by flashing a factory image using fastboot?
_MetalHead_ said:
But have you restored to 100% stock by flashing a factory image using fastboot?
Click to expand...
Click to collapse
I do not understand exactly what you record
I can not understand English I use Google Translate
Thank you you try to help
You need to tell me what to do to try ..
I just try it
Guide me step by step what to do
If you ask yes I have fastboot
Files
flash-all
image-hammerhead-ktu84p
bootloader-hammerhead-hhz11k
radio-hammerhead-m8974a-2.0.50.2.22
image-hammerhead-krt16m
cache
boot
bootloader-hammerhead-HHZ11d
userdata
system
recovery
I press
flash-all
Command window opens install it
It does not help
I also make it a manual command that does not help
I try a lot of versions
This is repeated restart problem ]=