yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace II Android Development] ace2nutzer:
This is normal.. and according to the ramdisk inits .... May be other Gov. can work etc...

interactive should work fine.

Combining Kernels with all possible Roms may not work 100% .. there are not warranty for that.. 100% ok is only when u using a kernel for what is builded (for the base) to the proper ROM.

For me: after an reboot all CPU Settings are ok. (with my CM11 version + my kernel)
[Galaxy Ace II Android Development] ChronoMonochrome:
Afaik only with AMOLED it'll save power. We have LCD display, not AMOLED...
[Galaxy Ace II Android Development] ace2nutzer:
Yes i know that bro :) But it works anyway.. try it ! ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
I already use dark-colored themes(just hate white kitkat themes in some apps, especially if it doesn't have dark theme choice :D) :cool:
[Galaxy Ace II Android Development] ace2nutzer:
Yes same here :cool: I really like the dark theme from the Stock FileManager :o

Bro one user report me reboot.. in last KMSG i faced many errors like:

[ 7557.320251] prcmu qos: update cpufreq frequency limIts failed

I believe the arm_khz_requirements sucks :D

And i can see very often the Min freq was changed between 200 < --- > 400 Mhz..

But now the new min is 400Mhz .. i deleted all freq. < 400Mhz :D

I'l commit now abb-charger fix.. that fix slow charging when changer control is not enabled.. also wrong current limitation on USB.

Just check in some minutes on my Git ;)
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, I got same errors from prcmu-qos code when tried to use it. But as far as I remember it never cause reboots.

courageous decision xD
[Galaxy Ace II Android Development] hafizulpijul12:
Freeze

Revert back to 2.4.2 from 2.7.2 after having a lot of freeze today. The only solution for freeze is reboot the phone. However, I installed 2.7.2 yesterday. Sorry for my bad English
[Galaxy Ace II Android Development] ChronoMonochrome:
Please post your avs data:

cat /sys/kernel/liveopp/prcmu_avs

It would be better if everyone who has reboots/freezes on latest 2.7.2 build, post it here. ATM I have only one report with attached avs data.
[Galaxy Ace II Android Development] tofueatsbread:
i always use dark-colored with red/white :// :highfive:
[Galaxy Ace II Android Development] hafizulpijul12:
Right now i'm on 2.4.2 kernel. I can't find "prcmu_avs" file in liveopp folder
[Galaxy Ace II Android Development] ace2nutzer:
cat /debug/prcmu/avs
[Galaxy Ace II Android Development] biggstreet:
Hello chrono

thank you for your great work

i tested universel kernel 2.6.1 since a week in my device running on stock 4.1.2 and i had reboot experiance from the time to other and battery drain is verry heavy

but this night i wake up in the morning and i found my phone in code pin screen and battery drain is verry heavy from 100 to 21 (Interactive 100-1200)
[Galaxy Ace II Android Development] BastiZ:
Maybe u have some broken mp3s and "Media" running in a loop.

Copy all your musik to your computer an make a check with this programm mp3-checker
[Galaxy Ace II Android Development] biggstreet:
I tested my MP3 files and I found this result

can you explain to me what it means
[Galaxy Ace II Android Development] BastiZ:
Damn. Sorry. Wrong programm.

Download Mp3 Checker from my cloudspace.

Take a scan and delete or convert all "Bad Mp3" files

Dont forget to delete the files on your phone as well ;)
[Galaxy Ace II Android Development] shaqman89:
Looks like some files are compressed badly.

But, how is this an issue related to reboots?
[Galaxy Ace II Android Development] BastiZ:
Before 4.4x i had problems with that.

And because he is on 4.1.2 it does not hurt to test.
[Galaxy Ace II Android Development] fluffi444:
R2.7.2 / condiap

I had one freeze today in the morning (was on Tapatalk :)) - No reboot - Just screen freeze and no button (screen/hardware) was accepted anymore... stayed for several minutes in this state... then I did a hot-reboot by long pressing powerbutton.

Here is my prcmu_avs

VBB_RET 0x00
VBB_MAX_OPP 0x19
VBB_100_OPP 0x19
VBB_50_OPP 0x19
VARM_MAX_OPP 0x34
VARM_100_OPP 0x27
VARM_50_OPP 0x1a
VARM_RET 0x04
VAPE_100_OPP 0x1e
VAPE_50_OPP 0x14
VMOD_100_OPP 0x1a
VMOD_50_OPP 0x1a
VSAFE 0x2a
VSAFE_RET 0x14
[Galaxy Ace II Android Development] biggstreet:
i tested All my mp3 files, i found a 3 bad files ! Thank you
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks, will compare then with some other avs'.
[Galaxy Ace II Android Development] shaqman89:
Did it solve the issue?

Just out of curiosity, would anyone explain why a broken mp3 (or any media?) could cause system reboot?
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't think it was cause of reboots. In kmsg log no kernel panic (should be NULL pointer panic if it was caused by software error).
[Galaxy Ace II Android Development] biggstreet:
[MENTION=5695278]ChronoMonochrome[/MENTION]

I installed the universal kernel & now I want back to the R1.6 release

what i have to do ?
[Galaxy Ace II Android Development] shaqman89:
You could just flash it directly. There should be no issues. I've tried to do it to go back to 2.3 and only need to adapt path difference in init.d scripts.
[Galaxy Ace II Android Development] ChronoMonochrome:
Okay, I compared some avs' today, and as it turned out most of them has too low vbbx voltages. Please do following test on 2.7.2 and report here.

for i in `seq 0 9`
do
echo vbbx=0xdb > /sys/kernel/liveopp/arm_step0$i
done

for i in `seq 10 22`
do
echo vbbx=0xdb > /sys/kernel/liveopp/arm_step$i
done
echo vbbx=0x8f > /sys/kernel/liveopp/arm_step23

I checked this log, it has 0xdb as vbbx. But it also set 0xdb [MENTION=322487]1000[/MENTION]MHz, that maybe not enough

please test following command

echo vbbx=0x8f > /sys/kernel/liveopp/arm_step23
[Galaxy Ace II Android Development] ace2nutzer:
So u Guys .. I've Shocking News for u ! :D

Right now tested my new GPU OC Algorithm and on the Ace 2 (not mine) with 0x14 for APE 50 OPP.. the GPU can run as far stable @ 770Mhz :D

Now the new max. adjustable is 800Mhz instead of 730Mhz :D

And CPU u already know, from stock Kernel 1250Mhz @ 1400Mhz :D
[Galaxy Ace II Android Development] str3tch72:
I don't have any lags and issues on 2.7.2 version. Great work bro!
[Galaxy Ace II Android Development] Devel0per95:
Stop Updates By the FTP or the site will be hacked easly -_-
[Galaxy Ace II Android Development] hafizulpijul12:
I'm using 2.4.2 kernel. My battery decreased even when charging. I adjust the charger control to higher and lower value, but still no luck.
[Galaxy Ace II Android Development] ChronoMonochrome:
Great! How did you do that?
[Galaxy Ace II Android Development] monstro78:
Thanks for your time and efforts.

I have tried several kernels. I think best kernel before 2.5 is 2.3 twrp ext4. Fast and smooth and stable at 1.2ghz.

2.4cwm have issues with oc and time... sometimes time stops and you must touch screen so alarm doesn't work. 2.3 is great and I suggest to everyone.
[Galaxy Ace II Android Development] ChronoMonochrome:
Updated to 2.7.3.

Changelog:

added governor OndemandPlus (thanks [MENTION=4615478]boype[/MENTION])

removed governors with hotplugging support

added interface to tweak PLLDDR freq on suspend:

echo on > /sys/kernel/cpufreq/pllddr_raw

To control freq are used raw PLLDDR register values:

echo suspend=0x000050158 > /sys/kernel/cpufreq/pllddr_raw # 675 MHz

echo resume=0x000050168 > /sys/kernel/cpufreq/pllddr_raw # 798 MHz

PLLDDR freq can be checked via

cat /sys/kernel/liveopp/pllddr

Settings applies after 3 sec after suspend/resume.

Too low suspend or too high resume value may cause reboot. Please note that this setting still experimental and unstable itself, so it's disabled by default.

adjusted some GPU OC defaults

fixed BT issues
[Galaxy Ace II Android Development] manthes:
I am testing new build but i don't see OndemandPlus. Does it have any changes for blackscreen?

It still looses cpu frequency settings
[Galaxy Ace II Android Development] fluffi444:
Is it correct that for pllddr we use echo 0x00050168 in /sys/kernel/liveopp/pllddr

and for suspent we use echo 0x000050168?

EDIT

looks like ther is no difference actually... But 0x000 seams to be "more" correct...

BUT: For me it does not work propperly. Phone freezed with some corrution of grafix after wake up via button and Phone does reboot. Had only a very few times that it works after screen off. Mostly it does not...

Tried 798 and 975 on DDR for resume freq.
[Galaxy Ace II Android Development] XIAOSpider:
I want the higher Clock over than 1250MHZ with the voltage control Can you Update this in next version？
[Galaxy Ace II Android Development] ChronoMonochrome:
Really no difference... you can type even 0x50168 or 50168.

For me it freezes only in few times. But surely it should be reworked, probably PLLDDR can't be changed when it switching between DDR25 and DDR100(or DDR50).

Sorry, for me it make no sense, since even 1250 MHz work unstable on most codinas.

You can set higher clocks via existing arm_step:

echo pll=0x501a4 > /sys/kernel/liveopp/arm_step28 #1260 MHz

echo pll=0x501a8 > /sys/kernel/liveopp/arm_step28 #1290 MHz
[Galaxy Ace II Android Development] nikolas1274:
[MENTION=235339]chrono[/MENTION]

I have install F2FS universal kernel, I can not boot to system from recovery, it always go to recovery, any suggestion?

Thanks
[Galaxy Ace II Android Development] ChronoMonochrome:
Install recovery for 2.7.x.
[Galaxy Ace II Android Development] nikolas1274:
I found twrp and cwm for R2.7, is that OK
[Galaxy Ace II Android Development] str3tch72:
For me booting working. I'm on 2.7.3 version. Ondemandplus is really great governor. System is smooth and super fast with it. Keep working bro.
[Galaxy Ace II Android Development] manthes:
Any explanation why i don't see ondemandplus governor?
[Galaxy Ace II Android Development] str3tch72:
Go to /system/lib/modules, look at ondemandplus, and paste it in autoload folder.
[Galaxy Ace II Android Development] joop1ter:
How can i choose to install it in CWM only ? Coz i am trying to restore and it shows nothing
[Galaxy Ace II Android Development] str3tch72:
I have one issue: sometimes governor set automatic to "performance". How to fix it?
[Galaxy Ace II Android Development] manthes:
I had this problem with cm 10.1 but not with cm 11.

It seems that blackscreen has been gone.
[Galaxy Ace II Android Development] str3tch72:
I see its only when I reboot my device. Latest R2.7.3 kernel + ace2nutzer CM11.
[Galaxy Ace II Android Development] monstro78:
Last kernel is great.

Fast smooth and great battery life.

Thank you
[Galaxy Ace II Android Development] ChronoMonochrome:
Do you mean, it changes to Performance at boot? If so it's ok. Since I reduced boot freq [MENTION=667179]800[/MENTION] MHz, it's only better to change governor to performance at boot to reduce its time(as I said anyway system wants to use max freq until it completely loaded).
[Galaxy Ace II Android Development] Asus-Tek:
Hi if you want to install universal kernel i must:

1. go to recovery and flash make-ramdisk-partition.zip

2. flash bootscripts

3. install krnel

That's all? I have a GT-I8160 kernel ext4.
[Galaxy Ace II Android Development] ChronoMonochrome:
You forgot to mention to install recovery.

Install it after bootscripts(or kernel).
[Galaxy Ace II Android Development] Asus-Tek:
I have a CWM now.
[Galaxy Ace II Android Development] ChronoMonochrome:
If you install it first time, you need to install bootscripts + recovery.

Otherwise it's unnecessary to flash make_ramdisk_partition and all the rest zips.
[Galaxy Ace II Android Development] Asus-Tek:
Okey i go to recovery flash make-ramdisk-partition.zip flash recovery (CWM) flash bootscripts flash kernel and reboot its OK?
[Galaxy Ace II Android Development] fluffi444:
See first post...

Installation process:

1) flash make-ramdisk-partition.zip. this procedure need to do only once. i.e. if you don't plan to flash stock, then this archive will be no longer needed

2) flash recovery, bootscripts and kernel
[Galaxy Ace II Android Development] Asus-Tek:
I've seen it ... i need install this 4.4.x_ext4_p.cpio?
[Galaxy Ace II Android Development] lars85destroyer:
where is it ?
[Galaxy Ace II Android Development] str3tch72:
So any solution for that? Because when I tick "set on boot" with interactive or ondemandplus, it stay with performance.
[Galaxy Ace II Android Development] manthes:
If you don't mind install latest carbon. It doesn't has this problem with chrono kernel
[Galaxy Ace II Android Development] str3tch72:
I will wait for next verion. Maybe it'll be fixed.

---------- Post added at 06:52 PM ---------- Previous post was at 06:39 PM ----------

Ok, I flashed latest build with wipe dalvic/cache and working, sorry for disturbing and thanks for solutions :3
[Galaxy Ace II Android Development] BastiZ:
I use Trickster MOD to apply this after boot.
[Galaxy Ace II Android Development] ChronoMonochrome:
Updated to R2.7.4 :)

Changelog:

- new governor Dynamic (thanks [MENTION=3329816]mkaluza[/MENTION])

- new GPU scaling algorithm (thanks [MENTION=4996458]1N4148[/MENTION] ) - ondemand-like GPU governor

- LiveOPP: reworked avs-based varm recalibration algorithm (please report about its stability, if it's still unstable post /sys/kernel/liveopp/arm_summary) , disabled vbbx calibration.
[Galaxy Ace II Android Development] 1N4148:
You may have a look into my last work for LiveOPP with automatic voltage calibration https://github.com/1N4148/s3mini/commit/cda01bb032435361c0b3e5a9292d8d993a157a07

As we both have seen that we even could set Varm to 0x00 without crashing I'm not paying Varm much regard anymore, I focus more on Vbbx.
[Galaxy Ace II Android Development] ChronoMonochrome:
Thanks, will try it asap :)
[Galaxy Ace II Android Development] 1N4148:
Take care of the different Vbb logic between AB8500 & AB8505 regulator. My logic currently only works for AB8505 regulators so you have to change vbb_tweak table (first index -> step up/down, step 7 means no change, second index is the vbb index from code below). The basic idea behind my logic is to increase Vbb for oc by 100mV, but I don't know usual avs values from your platform so I cannot guess what would be right.

/* AB8500 device - Vbbp_vsel and Vbbn_sel in 100mV steps */
static const struct regulator_volt_range ab8500_vbbp_vsel[] = {
{ {0x00, 0}, {0x10, 100000}, {0x40, 400000} },
{ {0x50, 400000}, {0x10, 0}, {0x70, 400000} },
{ {0x80, -400000}, {0x10, 0}, {0xb0, -400000} },
{ {0xc0, -400000}, {0x10, 100000}, {0xf0, -100000} },
};

static const struct regulator_volt_range ab8500_vbbn_vsel[] = {
{ {0x00, 0}, {0x01, -100000}, {0x04, -400000} },
{ {0x05, -400000}, {0x01, 0}, {0x07, -400000} },
{ {0x08, 0}, {0x01, 100000}, {0x0c, 400000} },
{ {0x0d, 400000}, {0x01, 0}, {0x0f, 400000} },
};

/* AB9540/AB8505 device - Vbbp_vsel and Vbbn_sel in 50mV steps */
static const struct regulator_volt_range ab9540_ab8505_vbbp_vsel[] = {
{ {0x00, 0}, {0x10, -50000}, {0x70, -350000} },
{ {0x80, 50000}, {0x10, 50000}, {0xf0, 400000} },
};

static const struct regulator_volt_range ab9540_ab8505_vbbn_vsel[] = {
{ {0x00, 0}, {0x01, -50000}, {0x07, -350000} },
{ {0x08, 50000}, {0x01, 50000}, {0x0f, 400000} },
};
[Galaxy Ace II Android Development] Kiras_PL:
What is mali Nt wotkaround? How to use it? :)
[Galaxy Ace II Android Development] ChronoMonochrome:
Okay, it should be not easy :) But I'll try at least :)

Just workaround of mali voltage overriding.
[Galaxy Ace II Android Development] 1N4148:
Can you provide me some collected vbb_max_opp from avs? I know there was a spreadsheet on github but I cannot find it anymore. So I can have a look which logic the defaults on AB8500 are following and maybe have a clue how to tweak it automatically.
[Galaxy Ace II Android Development] ChronoMonochrome:
sure, https://drive.google.com/file/d/0B_OwIFfWQnj_WVk3WkZXSjF2MUU/view?usp=sharing

but there are so many different vbb, so I think it's better to use +-300000 uV (0xdb) for 100-900 MHz steps and +-400000 uV(0x8f) for 1000-1200 MHz as it's already done. But I'll also try rewrite your patch for ab8500, I almost finished to write, it remains to test it :)
[Galaxy Ace II Android Development] 1N4148:
Thx. I wouldn't touch Vbb for the original steps, only for the oc steps as raising Vbb is also raising static power losses. And too much Vbb may also cause crashes on some devices as the transistors are biased to much. If have another device where default Vbb is -50mV/0mV (0x10 on AB8505). Raising above 200mV is making this device unstable. With 200mV bias it's stable [MENTION=1348102]1200[/MENTION]. So max. bias isn't the holy grail for overclocking the Novathor platform.

---------- Post added at 03:07 PM ---------- Previous post was at 02:44 PM ----------

Thx. I wouldn't touch Vbb for the original steps, only for the oc steps as raising Vbb is also raising static power losses. And too much Vbb may also cause crashes on some devices as the transistors are biased to much. If have another device where default Vbb is -50mV/0mV (0x10 on AB8505). Raising above 200mV is making this device unstable. So max. bias isn't the holy grail for overclocking the Novathor platform.

Edit: Doesn't matter which values I'm putting in into 100-1000, even with Varm=0x00 & Vbbx=0x77 (Varm=600mV, Vbbx=-350mv/-350mv) both devices running like a charm. Looks like there's a hidden link to ARM_OPPs :confused:
[Galaxy Ace II Android Development] nikolas1274:
[MENTION=235339]chrono[/MENTION]

I am using R2.7.4 for about eight hours and I have seen big improvement, no reboots, no huge or stuck, I am running 30-1200 freq, with all the latest version before that I had many many lag and black screen and the phone stuck all the time, all gone now with the last version
[Galaxy Ace II Android Development] heml0ck:
any updates for stock?
[Galaxy Ace II Android Development] fluffi444:
[MENTION=5695278]ChronoMonochrome[/MENTION] : This fix is no longer needed in R2.7.4? Am I right? Looks like that its already included in R2.7.4...
[Galaxy Ace II Android Development] ChronoMonochrome:
Yes, now it's unneeded.

Please install bootscripts for 4.1.2 as mentioned in OP and report if wifi works. It might not work, I replaced the module dhd.ko with the symlink to same file in /system.
[Galaxy Ace II Android Development] lars85destroyer:
Maybe it's just an impression, but my phone seems smoother after updating to 2.7.4 from 2.6.1
[Galaxy Ace II Android Development] ChronoMonochrome:
Might be due to tweaking some GPU defaults like up(down)threshold, that affected forcing APE100 almost all time. Good in terms of performance, but worse - in terms battery lifetime (it seems I set unbalanced values).

To restore defaults use commands:

chmod 644 /sys/kernel/mali/*
echo threshold=192 > /sys/kernel/mali/mali_boost_high
echo threshold=64 > /sys/kernel/mali/mali_boost_low
chmod 444 /sys/kernel/mali/*

By default these values are 64 and 12(or smth around that).

UPD. it might be fixed just by raising downthreshold, just set 32 or smth:

chmod 644 /sys/kernel/mali/*
echo threshold=32 > /sys/kernel/mali/mali_boost_low
chmod 444 /sys/kernel/mali/*
[Galaxy Ace II Android Development] lars85destroyer:
That's really not only an impression, phone is smoother :D I'll report about battery life tomorrow ;)
[Galaxy Ace II Android Development] manthes:
I have black screen with 2.7.4. Most of the times black screen is happening while charging and not only on latest build.
[Galaxy Ace II Android Development] nikolas1274:
Litlle offtopic,

I switch at art runtime, but i have a little lag, does art need more than 113M ZRam?

Or do i need to do something else?

I am at R2.7.4 F2FS kernel + Carbon ROM

Thanks
[Galaxy Ace II Android Development] 1N4148:
The actual "stock" algorithm in mali driver is a bit simple: If load > 75% (=192) upscale, if load < 25% (=64) downscale. This has its origin in the "stock" code, where frequency is only switched between APE100 and APE50 (half frequency) where this hysteresis is needed to prevent switching forth and back (at half frequency load is doubled). A new algorithm with tunable is in the work. If you have ideas about, let me know.
[Galaxy Ace II Android Development] ChronoMonochrome:
Yeah, I know about that. I noticed that it scales too slowly, with the new algorithm it may take few seconds, before it'll reach max freq. This might be caused by too big mali dfvs table, that I use, so I had to modify also up(down)threshold.
[Galaxy Ace II Android Development] str3tch72:
Any chance to update for 4.2?

---------- Post added at 12:41 PM ---------- Previous post was at 12:06 PM ----------

And how to OC GPU without NT-app?
[Galaxy Ace II Android Development] HCDanny24:
Thanks for OC on 4.3.1. This Kernel runs like Hell und i have no bugs! Happy
[Galaxy Ace II Android Development] xo.en:
How did you...i mean...you just flashed it and it works fine?

With last cm 10.2?

Which screen driver do you have? ws, sd?

Could you tell me what files do you have in /libs/modules after flashing this kernel?

Do you have default partition table, or you did repart of any kind?

(i have reparted machine)

Goddamn, it's freezing at bootanim and resets, weird bootloop/.
[Galaxy Ace II Android Development] HCDanny24:
Yes. I have wiped cache partition then dalvik cache then then ive flashed the Kernel and it works fine.

The kernel version before the update also [emoji6].
[Galaxy Ace II Android Development] dragos281993:
I noticed just now that my phone can't enter deep sleep mode. I'm gonna flash the build from 27/06 to see the difference. This morning I woke up and the battery had 76% and when I went to sleep had 95% so that's not good
[Galaxy Ace II Android Development] ChronoMonochrome:
I don't think it's related to kernel, because i never change deep sleep algorithm. In 90% cases it's related to some app that causes wakelocks. I think you have to install wakelock detector or any similar app to see which apps causes wakelock.
[Galaxy Ace II Android Development] dragos281993:
"Sweep2wake" is the problem. It's odd, cause this is the first time I've had this problem. I've been using this feature for a while and only recently caused me this wakelock. I think I'm gonna wipe everything again then flash all that needs to be flashed and see if problem is still there.

Just did a fresh install and the bug is still there and I haven't flashed your kernel yet, which means it's a ROM bug.
[Galaxy Ace II Android Development] HCDanny24:
On my aceII the accudrain, you write about, for me its normal when deepslepp works fine!
[Galaxy Ace II Android Development] HCDanny24:
Where can I see which screendriver i have?

These files I have in lib/modules:
[Galaxy Ace II Android Development] dragos281993:
I'm on CM11. "Sweep2Wake" turned out to be the thing that didn't let my phone enter deep sleep mode. And I also found out that it's supposed to stay that way.
[Galaxy Ace II Android Development] HCDanny24:
Yeah I know. With sweep to wake/double tap to wake, the phone cant go in deepslepp mode.
[Galaxy Ace II Android Development] ace2nutzer:
Yes, but with wakelock BLN with blink works perfectly :D (Not with all drivers..)
[Galaxy Ace II Android Development] HCDanny24:
Ok good news.
[Galaxy Ace II Android Development] dirtyl0lharry:
I cant install this kernel.

I tries a clean instal, format system/data/storage0 and SD from PC.

Then 3 wipes, install last rox cm11, its modular gapps and your ext4 kernel.

Once in cm11 setup it reboots itself, tried three times and it keeps rebooting, i dont know why this is happening.

Enviado desde mi GT-I8160
[Galaxy Ace II Android Development] j8hnb:
hi i just flashed f2fs 4.4 kernel and migrated to f2fs but on booting im unable to use keypad to type its seems to be stuck on voice and its not working :( so i disabled f2fs wiped every thing then flashed a backup i made but now after restoring backup i cant get data or wifi receptions my baseband has changed to xxxx . does anyone here know the best way to fully fix this ?

im gunna try restoring an older backup in the mean time but i dont think it will sort the problem