yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] dietzr:
data recovery from nandroid

hi,

is it possible to get my data and data/media back from a nandroid backup that was done prior to changing to f2fs,using a custom restore. If yes, should I backup to external sdcard?

eg

1 Nandroid on current filesystem eg

2 install new philz recovery

3 install kernel

4 recover data from Nandroid

thx
[Galaxy S III Android Development] trein91:
Chroma saturation settings and temperature control among settings don't stick after a reboot.
[Galaxy S III Android Development] xmendp:
To arter97

can you do the patch for our SHV-E210 deviced to flash 4.4 kitkat port room similer I9300 ? thank you
[Galaxy S III Android Development] rascal0pl:
Hi [MENTION=4898097]arter97[/MENTION], found a bug in recovery. Backup is not working properly, my phone restarted 2 times (while backup has been in progress) and hangs 3 times. I flashed devil recovery again and now backup is working.
[Galaxy S III Android Development] mrjoy:
Can we get UV settings in atweaks app. Because there is setting available & can you guide me how much cpu core i should lock in atweak app (max & min)?
[Galaxy S III Android Development] iceman0826:
question regarding converting to f2fs

from the procedures that you've provided, i noticed that the partition /system that contains the rom is the only partition not converted to f2fs.

so does that mean we can't get the full benefits of f2fs if the system partition was on ext4?

and this is my first time using philz recovery and im having a hard time locating my external sd card from the menus, or does philz doesn't support flashing zip from external sd card?

before i tried converting to f2fs and flashed only your kernel, i must say your kernel is solid! :D so does the a-tweaks, coz i miss my calibrated screen and color from mDNIe. :good:
[Galaxy S III Android Development] arter97:
Thanks. Will try myself later..
[Galaxy S III Android Development] arter97:
I don't know, but it may work, but no garentees.

If it works, you should backup to external sd
[Galaxy S III Android Development] arter97:
Even after a minute?
[Galaxy S III Android Development] arter97:
I don't have e210s at the moment.
[Galaxy S III Android Development] arter97:
Please post the recovery log.
[Galaxy S III Android Development] arter97:
Please read the OP. You'll never see UV in my kernel.

Locking CPU cores is not recommended.
[Galaxy S III Android Development] arter97:
Using f2fs on /system will break almost 99% of the ROM compatibility.

Users will have a BIG trouble while installing a new ROM.

Since most data are being read and written on /data, using f2fs on /system will not be noticiably faster anyways, which has determined me to stick with ext4 on /system.

And can you post the recovery log about the external sd?

You should find it under /sdcard.
[Galaxy S III Android Development] iceman0826:
oh my gas,. i've formatted the /system partition :( (hope it doesn't convert to f2fs) :crying:

right now i'm using your kernel and philz recovery that you've provided + temasek v90 and so far i'm not experiencing weird issues being reported here and on temasek thread :D

just a silly question how do i know if i'm running on f2fs ? coz i had doubts whether i've done the procedures properly hehe :good:

will try to post a recovery log about the external sd in the recovery, though i think it's alright with me using the internal sd card :D
[Galaxy S III Android Development] arter97:
Formatting /system on my recovery will still leave you on ext4.

Install terminal app, type "mount" and seek for f2fs :)
[Galaxy S III Android Development] trein91:
Yeah
[Galaxy S III Android Development] mrjoy:
Bcoz after flashing your kernel the device gets hang, even tried to change other governors but still performs very slow with wired animations, It is giving that issue with most kernel so on default kernel when i had lock the cpu core max to 4 & min to 2 the it performs fast. So i'm confused why the device gets hang after boot.

---------- Post added at 02:41 PM ---------- Previous post was at 02:24 PM ----------

Sir i checked again & noticed that while connecting charger the device performs very smoothly & fast but after charger disconnected the device gets back to wired performance along with wired laggy animations & glitches. Please tell if we can stay on these settings those are used while charging. :)
[Galaxy S III Android Development] Darkened_Sky:
it's because it uses powerboost (see misc tab in atweaks), which locks the cpu frequency to 1400mhz (default) and sets the performance governor while charging. if you really want this also while not charging then you can also lock the min cpu freqeuency in the CPU tab to 1400mhz and set the performance governor. but believe me your battery will drain faster then you can plug it in to recharge it :laugh:

I rather think your performance problems are somewhere else. If you really alredy tried everything else then sometimes it helps to reflash a stock rom with odin and then reflash the custom roms/kernel etc.
[Galaxy S III Android Development] rick0025:
mate..does this step clear/format all inside the internal sd?

does this wipe all pic,sounds,and video?

thanks
[Galaxy S III Android Development] rick0025:
gee thanks..great kernel :D
[Galaxy S III Android Development] trein91:
Yes to your question on whether it doesn't stick after reboot even after waiting a minute. Chroma saturation weight doesn't save on reboot. Even if I try to paste the settings from other kernels. Ie cs_weight=32
[Galaxy S III Android Development] mrjoy:
Ok thanx. But in some apps extsdcard does not dected....
[Galaxy S III Android Development] ikons:
I'm trying many cm and aosp based roms with system formated as f2fs and had never a problem with this roms (on devil kernel). So it's not true that f2fs on system partition breaks compatibility. The only problem is that the install scripts on most roms formats system back to ex4 (but it doesn't takes long to backup system, reformat system to f2fs and restore system with devil recovery).

So it would be great if your recovery will also handel system with f2fs formated, because devil recovery is not compatible to the dual boot feature.

Anyway, great work and wonderful kernel ☺!

Gesendet von meinem GT-I9300 mit Tapatalk
[Galaxy S III Android Development] Darkened_Sky:
I can confirm this:

if pictures are taken by camera and are directly saved to external sd card, they are completely greyed out. And downloads which are directly saved to external sdcard always fail. rom toolbox pro cannot backup apps and their data anymore to external sd.

reading from external sd card works, but writing to it seems broken.

btw. it is exfat formatted. willl try it with fat32

edit: ok fat 32 does not work as well
[Galaxy S III Android Development] Zero_One:
Well,there are normal. For deleted it you need to Format:

Cache

Data

Data/Media

then Full Wipe and Reinstall your ROM

But remember that you will pass to F2FS after it,so keep in mind this :good:
[Galaxy S III Android Development] Mostafa Wael:
i am seeing a poor graphics performance with all the governors and also i am facing some graphical issues.

can anybody confirm??
[Galaxy S III Android Development] mrjoy:
I'm already reported... same issue here
[Galaxy S III Android Development] DualJoe:
Can that kernel phone home crash logger be disabled?

Why is there no uV table tweak? I don't find anything in OP about that.
[Galaxy S III Android Development] Darkened_Sky:
do you mean with crash logger the logcat? then here an extract from the feature list:

and for uv: it has been discussed here several times and it is also mentioned in the faq, but here a detailed explanation:

http://xdaforums.com/showpost.php?p=52624726&postcount=39
[Galaxy S III Android Development] habylab:
Hi, I don't think so. Nothing personal is shared, just technical info to help the developer!
[Galaxy S III Android Development] dietzr:
Looks like it worked quite well using nandroid from ext sd:D
[Galaxy S III Android Development] Roymik:
Is there any alternative download link to your kernel? It's necessary to download the MEGA cloud app?
[Galaxy S III Android Development] lmulli:
You should be able to get around this be selecting the "request desktop site" option within your browser settings (available in both chrome and aosp browsers). That mega is a pain!
[Galaxy S III Android Development] bajica:
Mega is the best, just get the app, I use it all the time and more websites like androidpolice provide links so just import to my account and on phone download :)
[Galaxy S III Android Development] DualJoe:
[MENTION=4898097]arter97[/MENTION]:

You can't make sure it doesn't contain any personal data. Please remove that.

Undervolting:

Even AndreiLux wasn't sure about usefulness of ABB but it doesn't replace undervolting at all. Please grant users the respect to decide themselves about using uV table. Your kernel is highly experimental anyway..
[Galaxy S III Android Development] arter97:
Server is down for maintenance.
[Galaxy S III Android Development] arter97:
When? (eg. apps, benchmark)
[Galaxy S III Android Development] arter97:
Log: No, automatic kernel panic log dumper cannot be disabled. Again, no personal data are included within the sent log. You want to disable it anyways?

UV:

OP:

"No voltage, GPU clock controls?

No. I personally don't like exposing voltage and GPU clock controls to users. I have no plans of adding these controls to my kernels."
[Galaxy S III Android Development] arter97:
Well I'm sure.

Go take a look at /res/dumper.sh yourself.

What I meant by "ABB control by AndreiLux is enough" is the fact that AndreiLux has re-written the ABB driver.

Which includes thresholds and should adjust voltages in a different ways that the stock does.

If you really want UV, give me scientific showcase that UV actually makes a huge difference.

I still think it's a placebo.
[Galaxy S III Android Development] Olioaglio:
extsdcard problems

I'm on temasek v90 (also tried kernel with v80 before). /data and /cache is f2fs (was already since i used devil/AGNi kernel before.)

I can also confirm that there seems a serious problem with the new sdcard drivers on extsdcard (mine formatted to fat32)

I could not take a photo from camera to extsd, neither Titanium Backup could write to external sd (stated failed to backup).

But for me the worst problem is, that FolderMount won't work anymore. It mounts the clone folders as 0 byte files into sdcard0.

If you start FolderMount it states that it cannot write to externalsd and asks for attempt to correct this. If you agree it does some operation and restart phone. After next bootup writing to externalsd from other apps like Titanium etc. works again, but FolderMount comes up with another message that system/lib/sdcard is corrupt and asks to replace this file and backup orignal file. If you agree it does another weird operation and actually replaces the file as stated. It prompts for reboot. If you do so phone restarts again, and after reboot no new error message appear when you start FolderMount. Unfortunately it though does not work, but still creates only 0 byte dummy files in internal sdcard when activating mount points. Is this a bug or known issue or I'm the only one?

Btw, regardless of settings I tried in atweaks I noticed significant benachmark score drops in both Quadrant (6200->4300) and Antutu (20500->15300). Weird, as I thought the kernel improves most of the terms of speed with newer/improved drivers.

[MENTION=4898097]arter97[/MENTION], could you comment? Thx.

Cheers, Olioaglio
[Galaxy S III Android Development] DualJoe:
- Read up about Steve Kondik removing opt-out of sending statistics in CM and notice the ****storm/arguments.

- CPU dies/chips from center of the wafer are used as low power/mobile versions just because they consume less power/need less voltage.

Just Google it ..
[Galaxy S III Android Development] Mostafa Wael:
Benchmarks: example when i test with antutu and when it comes to the Graphics test i notice that the 2nd 2D graphics test "the one that had a fire ball" lags alot and that the 3D graphics test reaches a lower max fps than other kernels test "Mind that i was testing using the 160/266/350/440/533 steps which are the stock steps"

I know that benchmark scores are crap so i tested with real life use and i noticed that sometimes graphical glitches appear though for a fraction of a second... "which is supposed to be fixed"

However i am not a gamer and your kernel provides a more speedy and snappy experience excluding the graphical issues.

And multitasking is the same as other kernels if not better.

Please correct me if i misunderstood anything and sorry for late reply...

Thank you.

EDIT: do you recommend converting to f2fs now? Thank you!

---------- Post added at 11:01 PM ---------- Previous post was at 10:58 PM ----------

And please set the touchboost frequency to 600 MHz or 700 MHz

I think that will help much the battery life

Thank you for your awesome work.
[Galaxy S III Android Development] arter97:
I'll take a look at the external sd. Changing the mount options should fix it.

I've seen users reporting higher scores with benchmarks, which kernel did you used before?
[Galaxy S III Android Development] arter97:
Dude, I designed the whole "automatic kernel panic log dumper" in my kernel.

I know which exact data being included within the log.

CM stats did not included the kernel log.

Seriously, don't ask me to Google it, go checkout yourself what exactly a kernel log is.
[Galaxy S III Android Development] arter97:
Umm, graphics performance issue.. That's new to me.

I have no idea where to fix, but still, I'll keep it notice :(

f2fs: If you're comfortable using my kernel as a daily driver, yes.
[Galaxy S III Android Development] AndreiLux:
Please don't misrepresent my work to do something which it doesn't. ABB is not a replacement for UV.

I've already stomped on various occasions this UV nonsense.
[Galaxy S III Android Development] dietzr:
.. just want to confirm that I also experience problem with Titanium Pro backing up to ext sd card (ex32), with a message of not enough space, which is incorrect. However doing a straight copy of a pic from int sd to ext sd works with no problem.

[MENTION=4898097]arter97[/MENTION] Thanks for looking into it.:good:
[Galaxy S III Android Development] iceman0826:
just a question, i noticed in battery info that "cell standby was on 32% -- time on was 3h 2mins." on idle, not using phone, screen-off, and my battery drain was around 1% per hour.

Is that normal?
[Galaxy S III Android Development] Olioaglio:
Thanks, m8.

Reflashing to AGNi 2.7.8 kernel with same rom and no other changes immediately returns me desired high benchmark values as before. It's on par with Devils latest available f2fs kernels.

Olioaglio
[Galaxy S III Android Development] habylab:
I think letting us choose the touchboost setting would be great!

Also, I'd very much like it if you could update Zzmoove to the 0.9alpha 2. Although it is alpha, test it yourself - so much less lag and just better!

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] DualJoe:
Dude?

It's completely irrelevant what you send, it's about sending without permission, disrespecting the users, exloiting the ip, collecting meta data. You are not the short fat guy who got North Korea at Xmas.

But that discussion is useless anyway... The kernel has too many flaws and limitations anyway. Thanks for the support though.
[Galaxy S III Android Development] Olioaglio:
My 2 cents on this: you are right. Discussion is useless. Why? because it's arter97's decision to auto send this logs in his <unofficial> beta kernel. The auto dump kernel panic log feature is not secret and documented in 1st post. On the other side it's of course your decision to stay away from his kernel if you dislike the function. No offense though!

IMO arter97 is legend in developing and his contributions are/were undoubtedly important for this community.

Cheers, Olioaglio
[Galaxy S III Android Development] dietzr:
Totally agree. It is clearly spelt out in the OP. If the kernel has too many limitations for you anyway why do you bother in the first place?:confused:
[Galaxy S III Android Development] DualJoe:
Because kanged feature list looked so brilliant in the first place. Who could know he is so fundamental about basic stuff like uV.

And by far not the only one. Most kangers are radical about 'their' work. It's their personal TukTuk, Golf GTI or whatever. I just didn't expect that on basic functionality like uV. Usually it's about much more complicated things like master sequence or something.
[Galaxy S III Android Development] habylab:
I just had a RR, hope your system picks it up and you can fix it. No UV, so no excuses.

Sent from my SlimKat Galaxy S3. Was a proud Googy Beta tester.
[Galaxy S III Android Development] arter97:
Sorry for my misunderstanding..
[Galaxy S III Android Development] arter97:
ZZmoove's beta source are not available, am I wrong?
[Galaxy S III Android Development] arter97:
I had clearly said in the OP that this kernel automatically dumps log. Saying "without permission" from whom had said "Why is there no uV table tweak? I don't find anything in

OP

about that." doesn't seems legit.

And plus, your IP gets recorded the moment when you visit iencoder.co.kr in the first place.

What am I gonna do with your IP and kernel log, sell it to China?

Most importantly, I had let the users choose whether they want to install my kernel or not. If you don't like this "too many flaws and limitations" ****, you can leave quietly.

Saying something is full of flaws, limitations in front of the face of that developer is very disgraceful.

Get your self a piece of respect before you talk about it.
[Galaxy S III Android Development] habylab:
Not publicly, but if [MENTION=3279788]ZaneZam[/MENTION] is about, I am sure he'll send you them!
[Galaxy S III Android Development] arter97:
Hmm, even though it may be better in some ways that'll benefit the users, there will be also some reasons why it's called a beta.

I'd like to carefully suggest not using beta will be better in terms of stability ;)
[Galaxy S III Android Development] trein91:
Chroma saturation weight still doesn't stick after waiting a while after reboot. Hope you can look into it. Thanks again
[Galaxy S III Android Development] arter97:
Yes, I will. It's on my radar.
[Galaxy S III Android Development] minhdale:
I like your kernel. But lmk not smart. When i play heavy game for a while it always kill my game. How can i improve ?
[Galaxy S III Android Development] arter97:
Find another way to tweak lmk.

My kernel uses stock lmk values.
[Galaxy S III Android Development] minhdale:
Edit: never mind.
[Galaxy S III Android Development] rascal0pl:
Yes it is real pain, 80% apps can't write on SD :(
[Galaxy S III Android Development] Assa551N:
If I install your kernel, the video playing goes wrong. If I want to play a video, the phone craches. Youtube too.
[Galaxy S III Android Development] nagi_007pk:
The new sdcard drivers are better at detecting mtp when dualbooting cm11. I use temasek v90 myself. The problem are not the sdcard drivers but the permissions blocked by KitKat to write on the sdcard. The 0 byte folder error also can be solved using the sdfix app from the playstore. I tried it only yesterday and the folders are mounting perfectly fine. Also titanium works like magic!
[Galaxy S III Android Development] rascal0pl:
Thanks! Apps now are working (after applying fix), but foldermount still not.
[Galaxy S III Android Development] Roymik:
So every time I flash a new version of temasek rom , the system partition is formatted back to ext4.. How can a f2fs system survive a new rom flash?

Noob here :p
[Galaxy S III Android Development] bajica:
System stays ext4 all the time, only cache and media storage get to be f2fs
[Galaxy S III Android Development] Olioaglio:
No way. Rom script auto formats to ext4 before copying new data. Only way to get system back to f2fs is to do a nandroid after flashing new rom version, then go to recovery, format system back to f2fs and then choose advanced restore and only restore system partition.

Olioaglio
[Galaxy S III Android Development] Roymik:
Thanks, that's exactly what I thought to do.. But I wonder if the benefits are worth it..

Another question, how I can revert back to full ext4? Today I tried formatting system, cache and data/sdcard with latest philz recovery , but it won't let me do so... There is another way to do it?
[Galaxy S III Android Development] ZaneZam:
Normally I would definitely agree (and im known for my never ending release delays *g*) but this beta will get this stage just because 0.9 hasn't reached its final feature level yet but it's stable and was testet for some weeks without any troubles and It takes quite some time till I consider a version stable, I know that beast very well :D

So now the truth: I just wasn't able to put in enough bugs yet which means I had no time to work on it further :) but i promised to shorten the release delays in form of a beta repo with it i can release stable versions earlier.

Just for info: there will be no big changes in this beta version compared to 0.8 just a code reduction (DFS and legacy mode removed) and the performance feature auto fast scaling was tweaked, that's it. But anyway u decide at the end, you can fetch it any time from my beta repo when it's released these days ;)

Gesendet von meinem GT-N5110 mit Tapatalk
[Galaxy S III Android Development] habylab:
Thank you!
[Galaxy S III Android Development] dietzr:
yes there is: ;)

1 flash 'old' PhilZ recovery, eg 6.41.6

2 reboot to recovery

3 format data and data/media

4 wipe cache

5 reboot to recovery

then either restore a nandroid or flash rom and kernel of your liking.
[Galaxy S III Android Development] Mostafa Wael:
hey arter

did you mess up with anything in the mail drivers? or you merged them as is from the N7100 KK source ?

just trying to help!

may be we can resolve the issue of those annoying graphical glitches :D
[Galaxy S III Android Development] arter97:
Merged drivers/gpu/mali400 from N7100 KK.
[Galaxy S III Android Development] Darkened_Sky:
just tested two times with antutu where you said these graphical glitches should appear. and i wasn't able to see any glitch, in fact I've never seen that it was so smooth before :D (the fireball test) and I haven't seen any suspicious fps drops. and i couldnt detect any other glitches anywhere else.

rom is temasek rom v91.

which one are you using?
[Galaxy S III Android Development] Mostafa Wael:
ArchiPort Preview 5..

and i see them not so frequent but yeah they are still present

And i was wondering, what are the stock GPU steps used in this kernel?

are they: 160/266/350/440 ?

Or: 160/266/350/440/

533

?

what is the max fps detected in the last test? mine was 27.0

just tested now with Zzmoove -performance governor and cleared RAM memory before testing..

temeperature of the battery was 28C according to "Cool tool"

i got a total score of 21426 while with others at same conditions and same CPU governor and frequency as well as GPU frequency, which i suppose that it is the same here, gave me 22k+ "just wanted to give all details about the benchmarking tests, i personally don't look at the total score :D "

Also 3D graphics score is 4249 while other kernels gave me around 4.6k and 5.2k

I guess that all of you might be asking: why are you then sticking with that kernel?

the answer is that this kernel gives me best multitasking as well as that screen settings including the touch-wake settings so yeah it is the best for me. i am not a gamer, i just play some simple 2D games so GPU Overclocking is not necessary for me, but if we got to fix those graphical glitches that appear from time to time, that kernel will be awesome....

I also tried to turn off UKSM but no effect !

hope that helps..
[Galaxy S III Android Development] DualJoe:
Try this:

cat /sys/module/mali/parameters/step{0..4}_clk

Edit:

I'm not running that kernel so i can't tell you directly...