yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] xclub_101:
And the 4.2.x stuff gets more pressing ...

New UFME3 4.2.2 Samsung ROM leaked:

http://xdaforums.com/showthread.php?t=1835931

I would expect that one to NOT work with this kernel (or any other custom kernel), so now I suppose the problem starts to be Samsung publishing the sources for the new kernel ... :rolleyes:
[Galaxy S III Original Android Development] STAticKY:
No need to spam this across every kernel thread...
[Galaxy S III Original Android Development] amviewer:
AndreiLux,

I think I have found the lines of code in the kernel source which is responsible for setting the output via hdmi.

\drivers\media\video\samsung\tvout\hw_if\hw_if.h

At line 864

enum s5p_hdmi_v_mode {

v640x480p_60Hz,

v720x480p_60Hz,

v1280x720p_60Hz,

v1920x1080i_60Hz,

v720x480i_60Hz,

v720x240p_60Hz,

v2880x480i_60Hz,

v2880x240p_60Hz,

v1440x480p_60Hz,

v1920x1080p_60Hz,

v720x576p_50Hz,

v1280x720p_50Hz,

v1920x1080i_50Hz,

v720x576i_50Hz,

v720x288p_50Hz,

v2880x576i_50Hz,

v2880x288p_50Hz,

v1440x576p_50Hz,

v1920x1080p_50Hz,

v1920x1080p_24Hz,

v1920x1080p_25Hz,

v1920x1080p_30Hz,

v2880x480p_60Hz,

v2880x576p_50Hz,

v1920x1080i_50Hz_1250,

v1920x1080i_100Hz,

v1280x720p_100Hz,

v720x576p_100Hz,

v720x576i_100Hz,

v1920x1080i_120Hz,

v1280x720p_120Hz,

v720x480p_120Hz,

v720x480i_120Hz,

v720x576p_200Hz,

v720x576i_200Hz,

v720x480p_240Hz,

v720x480i_240Hz,

v720x480p_59Hz,

v1280x720p_59Hz,

v1920x1080i_59Hz,

v1920x1080p_59Hz,

#ifdef CONFIG_HDMI_14A_3D

v1280x720p_60Hz_SBS_HALF,

v1280x720p_59Hz_SBS_HALF,

v1280x720p_50Hz_TB,

v1920x1080p_24Hz_TB,

v1920x1080p_23Hz_TB,

#endif

What if all the resolutions were removed from the "enum s5p_hdmi_v_mode" and only keep v1280x720p_60Hz,

Would we be able to only get 720p@60hz output ?

Not sure what the 3D is doing in there...does the SGS3 support 3D output via HDMI :cool:
[Galaxy S III Original Android Development] STAticKY:
[MENTION=4167023]AndreiLux[/MENTION]: Could you implement a tunable accessible via stweaks that forced the kernel to handshake at a desired resolution/refresh rate. A drop down list of all of them and select the desired one. Also with a enable/disable forced handshake switch to toggle forced mode on/off above it?? Possible?
[Galaxy S III Original Android Development] amviewer:
That would be even better :good: but not sure if that is possible.

I'm looking through the code but I can't seem to find where it does the EDID handshake because that is where the problem starts.

I did find something on for a Sony were there is a workaround going into the service menu and force it from there but losses that setting after a reboot.

Unfortunately the SGS3 doesn't have something like that in the service menu.
[Galaxy S III Original Android Development] ranwej:
Hi, this is a great kernel. Do you plan to add option to completly disable android logger? Thanks
[Galaxy S III Original Android Development] habylab:
Hi, you could use pimp my ROM for this!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] jwchips:
Giving this another gentle bump as its now buried under 12 pages and I'm not convinced Andrei has even seen it. Flame me if you will but I am of the opinion that this is relative to the development of the kernel (moreso than "my colors are washed"/"hows battery/gaming" etc) and what I'd really like to know is if the current implementation of the SDS fix is based on v1 (albeit Andrei's own version) is it possible (and intended to) update to the v2 fix (or Andreis own version) which is supposedly more efficient and reduces freezing?

Original discussion from 12 pages ago can be found here and there's a lot of mixed messages from users about the SDS fix. Seems no-one but Andrei really knows whats what on this issue!
[Galaxy S III Original Android Development] andip71:
Just to kick quickly in here... I did some test today in the afternoon with some code changes to the stock sammy kernel code, forcing it to select various different output modes.

When I pushed the tv out to use 1280p_60Hz, I got no picture at all anymore. Guess the MHL adaptor cannot handle it even.

When I pushed it to 720p_60Hz, I got a picture but it was not correct anymore (shifted, cropped etc).

I tried many other possible settings like 1280i_60 and so on... but in short - I never managed to end up in a usable output for some reason.

Just wanted to share this quickly, seems it is not a piece of cake to achieve this, if possible at all.

Andi
[Galaxy S III Original Android Development] amviewer:
Did the tv also say it was getting an input of 720p when you changed it?

I'll have a look at the sgs2 source as I had normal performance on that before I started using the sgs3.

-EDIT-

Just checked it on the sgs2 and has the same behavior now since it updated to jellybean so might have to look at the ICS source
[Galaxy S III Original Android Development] andip71:
Yes, the TV was always exactly showing the correct resolution and frequency, just the picture was not usable anymore.

Ok, so back to topic, which is Perseus thread. Just wanted to throw that in as I investigated a bit this afternoon.

Andi
[Galaxy S III Original Android Development] nfsmw_gr:
Thanks for the testing, i really hope you or Andreilux can make it work.

I've stopped using my hdmi from day two because the image is way too choppy. :(
[Galaxy S III Original Android Development] AndreiLux:
I looked into the HDMI thing a few months back but forgot about it. I know about those entries. It's not only about changing a configuration, the image you get via MHL is actually video stream passing through the generic scaler and some other IP blocks. I'll check it out some other time but it's not a current priority, thanks for the reminder.
[Galaxy S III Original Android Development] jwchips:
Sorry to be pushy but would you care to comment on my SDS query? My device will randomly lock up for 5-20minutes on your kernel (will not happen on Adams kernel) and as far as I can tell the SDS implementation is the culprit...
[Galaxy S III Original Android Development] habylab:
Pretty sure this is the 1st fix. It's a fix, just slower.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] jwchips:
Thanks, I suspected as much, this backs up my theory that the SDS fix is causing the freezing. My question has now become can we expect an update to the new implementation or is andreis version incompatible?
[Galaxy S III Original Android Development] MuertoKo:
Switch off zRAM if you hadn't already, that mostly fixes the freezing. I have no freezing related to any SDS fix or whatever, Andrei answered many times about this same topic actually...
[Galaxy S III Original Android Development] jwchips:
Zram was disabled and if I understand correctly Zram freezes should only last around 1 minute, not the 5-20minute freezes I was seeing. Would you care to provide a link where Andrei talks about the technical implementation with regards to the new (update 8 sources) SDS fix? The changelog makes no mention of updating the fix.

This is not a general 'is this kernel safe' question, I'm interested in the technical implementation which from what I can gather is based on old sources and therefore is prone to freezing when a bad block is encountered.
[Galaxy S III Original Android Development] MuertoKo:
http://xdaforums.com/showpost.php?p=38759650&postcount=4545 <--- He uses something else, meaning he doesn't need to implement that as he went other way round afaik.

http://xdaforums.com/showpost.php?p=38800027&postcount=4565 <-- about update 8 itself.

Sure there are more but I'm at work so can't really dig deeper, and you shouldn't really have 20m freezing AT ALL, never had that even with zRAM, max. was 5 minutes for me... must be something else screwing your device maybe? No idea what though, sorry
[Galaxy S III Original Android Development] jwchips:
Hey, thanks for the reply and the link. While I'm aware Andrei uses a custom fix I'm still convinced it's prone to freezing when a bad block is encountered, but it would appear that his implementation means the new fix is incompatible, which is a great shame.

I'm also sure it's perseus causing my freezing as I've now switched to Adams kernel (the only one I could find that explicitly uses the new fix) and the issue has completely disappeared, I've been using it for weeks and not had a single freeze. Everything else remains the same.

It looks like I'll have to abandon using this kernel as the freezing is a dealbreaker for me, which is upsetting as I enjoy its feature set.

Thanks for the help everyone!
[Galaxy S III Original Android Development] MuertoKo:
Did you manage to check if zRAM is properly disabled? Some times Stweaks missbehaves causing settings to not stick. You can easily check zRAM by typing "free" on terminal. Try this, reboot, try again to re-check just in case... Otherwise is quite weird, as you are the only one reporting it :S Have you cleared init.d folder as well between flashing one kernel or another?
[Galaxy S III Original Android Development] jwchips:
I'll flash back to perseus and try your suggestions, it will probably be a week before I respond so I can test properly. As for me being the only one, maybe it's down to my device having an insane chip with a higher than average number of affected blocks? I've no way to prove this of course..

Back on perseus and it seems to have remembered my settings as the screen master sequence was on and Zram off (free in terminal shows 0 for swap).as for init.d I don't use this, I also don't seem to have the folder. It should be in /system/etc yes?
[Galaxy S III Original Android Development] MuertoKo:
Yep should be there, if there's no folder there's no script, it isn't always there unless ROM or previous kernel created it.

You can also try to pull some logs during the freezing if it keeps happening, but no idea what of the logs could be useful here anyway!

Good luck testing!
[Galaxy S III Original Android Development] TotallydubbedHD:
haha I didn't read:

DOESN'T WORK ON SAMSUNG JELLYBEAN 4.2.1 ROMS.

Oh well...re-flashing rom now.
[Galaxy S III Original Android Development] andreasy:
Freezing is also my only issue although I disabled zram. I didn't know there is a fix though. I tried stock kernel but battery life couldn't be compared so I came back very soon before testing for freezing.
[Galaxy S III Original Android Development] jwchips:
When you say freezing do you mean for long amounts of time (over 5min) which can occur at any point? I've had freezes while screen off and while actively scrolling a Web page. While frozen nothing will respond but if I call myself from a different device the caller hears a ring tone (ie the ring ring in their earpiece) but my frozen device does not ring or register a missed call. I just want to ensure we both have the same problem.

That said, I've had no freezing today! Still need to run the dummy file generator and stress test but usually would have frozen by now. Not sure what's changed. As for logs, logcat/kmesg/both?
[Galaxy S III Original Android Development] andreasy:
Something like that, mostly noticed on web browsing, sometimes during phone call my phone rang but I couldn't unlock or see who's calling me, but my freezing last a few minutes but not as long as 20 that you report. I usually long press power button to reboot after a few minutes
[Galaxy S III Original Android Development] benschhold:
Can someone give some undervolt/ABB tips?

I have an asv4 chip

My values:
[Galaxy S III Original Android Development] SuperAce609:
We have the same chip. Follow the guide here: http://xdaforums.com/showthread.php?t=1997838

-100mV for me. Don't really feel like going any lower. You can try it though.
[Galaxy S III Original Android Development] txpxsx:
i'm using this kernel with UltimaROM, thanks. But how come I don't have the folder data/.perseus on my root? do i have to create it?

thanks once again

EDIT: Found it! It was hidden :D
[Galaxy S III Original Android Development] STAticKY:
Indeed it is. Any folder beginning with a period "." Is a hidden folder

TP.
[Galaxy S III Original Android Development] Valtrex11:
Can I use this kernel with stock rom? Yes? No?

Thanks
[Galaxy S III Original Android Development] sherlock5545:
If you mean Samsung based ROMs, then yes. If you mean AOSP ROMs, then no.

Sent from I9300 - UltimaROM
[Galaxy S III Original Android Development] Valtrex11:
Yeah Im using samsung stock rom 4.1.2 with stock kernel
[Galaxy S III Original Android Development] sherlock5545:
Then yes, this kernel is intended for Samsung ROMs.

Sent from I9300 - UltimaROM
[Galaxy S III Original Android Development] bxlogic:
[MENTION=4167023]AndreiLux[/MENTION] dood most of roms are upgrading to 4.2.2 i love this kernel of yours i think it's good idea to make 4.2.2 release :D
[Galaxy S III Original Android Development] donteo:
There is no source from samsung so impossible to release a 4.2.2 kernel ..
[Galaxy S III Original Android Development] Steve_max:
Sure, just point to Samsung's 4.2.2.kernel sources and I'm sure Andrei will be happy to rebase on that.

PS: If you're actually searching for them, stop. They won't release the sources before they release the kernel, and leaks aren't releases. No 4.2.2 sources (and therefore no custom kernels, and no Perseus) before an official 4.2.2 release.
[Galaxy S III Original Android Development] SuperAce609:
Lol damn. Nice chain reaction. But I thought CM10 and AOSP kernels were TW compatible? Or are they based off Sammy's kernel too.
[Galaxy S III Original Android Development] sherlock5545:
AOSP kernels aren't compatible.

Sent from I9300 - UltimaROM
[Galaxy S III Original Android Development] Steve_max:
No, they're not based on Samsung's sources. Nor are they TW compatible.
[Galaxy S III Original Android Development] SuperAce609:
Oh okay. I asked since I've seen some kernels that work on AOSP and TW at the same time so I was wondering.
[Galaxy S III Original Android Development] Steve_max:
That requires a lot of load-time tests to work. This is why most CM kernels run only on CM, and most TW kernels run only on TW. But still, a "mixed" CM10.1+TW4.1.2 kernel won't boot a 4.2.2 TW ROM.
[Galaxy S III Original Android Development] Valtrex11:
Inside the compressed file there is a boot.img file, I just flash the compressed ,tar via ODIN? Or im missing something?
[Galaxy S III Original Android Development] SuperAce609:
I see. Thanks. I'd hit the thank button but I'm limited to 8 xD
[Galaxy S III Original Android Development] thechaoz:
Anyone have version 35 or where I can find it? Ty
[Galaxy S III Original Android Development] ahac85:
Here you go mate

http://db.tt/yB7dBEsn

Sent from my GT-I9300
[Galaxy S III Original Android Development] TonyTrollsten:
After some $!#t I said about zzmove that turns to be stupid I would like to see it in the kernel

Maybe a request?:D
[Galaxy S III Original Android Development] Valtrex11:
Please help me to install this kernel im using stock rom/kernel/recovery 4.1.2.....

I just flash it normally with ODIN? Or I need another step?:crying:
[Galaxy S III Original Android Development] thechaoz:
Ok so I don't mess this up will it work with i605? Verizon

Jelly beans 13 with Perseus kernel banging note 2 i-605
[Galaxy S III Original Android Development] sherlock5545:
Andrei said he wouldn't implement it as you can easily achieve similar performance by tweaking the kernel using STweaks.

Sent from I9300 - UltimaROM
[Galaxy S III Original Android Development] pistoke:
//edit: Sorry I read wrong. You have to root your phone and install custom recovery before you can flash a kernel. //

No, boot into recovery, wipe cache and dalvik, flash kernel.

Please search for a better guide and study a little. If you do something wrong, you may brick your phone or at least after a bad flash, you really have to study to make your phone work again. No one else than you are responsible, if you brick your phone.
[Galaxy S III Original Android Development] MuertoKo:
Nope

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] Erahgon:
Huh? If you use Odin on a PC, custom recoveries are not a requirement in order to flash anything.

Download files with a .tar extension and select it as the PDA file in Odin, to flash this kernel.

However, that being said, custom recoveries are recommended in general, when using custom kernels.

Sent from the present, which is now in the past.
[Galaxy S III Original Android Development] Valtrex11:
Well thank you guys, I flashed the kernel using ODIN and I had no issues so far..

You know which governor/scheduler works better for this kernel?

Thank you!
[Galaxy S III Original Android Development] andreasy:
Default
[Galaxy S III Original Android Development] Steve_max:
Deleted
[Galaxy S III Original Android Development] rlorange:
Actually that is not strictly true... Siyah kernel WILL boot the Sammy leak but it runs very slow.
[Galaxy S III Original Android Development] andreasy:
This happened a few times to me. I leave my phone on charger overnight but in the morning it's not fully charged. It's around 87-90. I usually see sdcard process consuming my cpu but this happens all the time anyway. Any ideas?
[Galaxy S III Original Android Development] bsamardzhiev:
New charger.
[Galaxy S III Original Android Development] zodiaxe66:
I have seen similar problems with other kernels to, when battery reach 100% it begins to discharge if you leave the phone plugged in. So it's not specific to this kernel. Even though I didn't encounter this with perseus,others might.
[Galaxy S III Original Android Development] bihslk:
can i use this on OMEGA V45 4.2.2?
[Galaxy S III Original Android Development] Thin_Bezel:
Nope
[Galaxy S III Original Android Development] bihslk:
any kernel that works with leak?
[Galaxy S III Original Android Development] Thin_Bezel:
Still no :) very negative today but really, there are no kernels available for the leak atm :rolleyes:
[Galaxy S III Original Android Development] bihslk:
haha ok no problem mate thanks
[Galaxy S III Original Android Development] maxxxy:
sorry but where files are created .profile?

I can not find in sdcard

thanks
[Galaxy S III Original Android Development] MuertoKo:
It's a hidden file, use root explorer to see it, it's in /data
[Galaxy S III Original Android Development] maxxxy:
I use es gestore file

I have already enabled the hidden files but do not appear
[Galaxy S III Original Android Development] MuertoKo:
Id you have Stweaks installed you'll have the folder in /data/.perseus ; are you seeing any hidden folder on your sdcard? Make sure it's working or try different file explorer!
[Galaxy S III Original Android Development] p33t-r:
Hey guys,

Any solutions to repeating reboots on Samsung boot animation? I thought I've found the culprit (sound settings - speaker equalizer) but the reboots are back again. I seriously have no idea what is causing this, but it's slowly driving me crazy. No chance to fast reboot my phone.

I am now using WanamLite 6.6, but it happened to me also on Android Revolution HD. Both with and without Jkay mod. No chance it's because of UV, because it happens on stock values as well.

Any help would be appreciated.
[Galaxy S III Original Android Development] MuertoKo:
Any log will be appreciated :)

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] MuertoKo:
God... what an activity drop on this thread since Andrei "left" (Moved priority actually), just wondering but there's nothing left to implement, no ToDo ideas pending to add except that tweak to pegasusq Andrei mentioned will be doing some day, right?

Boh, won't flash device until 4.2.2 sources, and then hopefully not until I get Note 3 xD
[Galaxy S III Original Android Development] p33t-r:
I've followed this thread: http://xdaforums.com/showthread.php?t=1726238 and I used ADB to logcat. But I can't get anything in output file, because it says " --- Waiting for device ---- " which means logcat can't be obtained before the system actually boots. But the resets happen right after the bootanimation starts.

Any suggestions?
[Galaxy S III Original Android Development] MuertoKo:
Can you detail a little bit more, like step-by-step your issue? If it's some sort of random reboots you can pull last_kmsg after the reboot.
[Galaxy S III Original Android Development] p33t-r:
This is happening after I tweaked some settings in the kernel using Stweaks. It is not related to UV nor ABB, because it happens even on stock values.

Here's what it looks like :

1. I reboot the phone / turn it on / reboot from recovery, doesn't matter which one

2. 'Samsung Galaxy SIII GT-i9300' splash appears.

3. LED turns blue, the bootanimation starts (the original one). First there is this blue / purple ring starts moving in circle and the sound is played.

4. During that 1st part of the animation phone reboots itself, Samsung Galaxy SIII splash appears again.

5. This happens sometimes once, twice, sometimes even 10 times or none. Finally the phone boots itself normally (goes after that animation part and it is played normally).

I know one or two other people having the same issue. One person reported that after applying my Stweaks profile. Someone else tried my profile and it doesn't happen to him. He says it happens to him on all default settings in Stweaks. Weird...

Here is my profile I am using now. Notice this happened on other settings as well as stock too. http://db.tt/C0uVHoKU

I am on WanamLite 6.6 right now, but this issue was also on stock XXEMC2 and Android Revolution HD 25.

My ASV is 03 of that matters.

The problem with logging is that I cannot make a logcat before the system boots. Are there any logs from system startup?
[Galaxy S III Original Android Development] The Broken:
I have exactly the same problem, but I must add that the boot animation (stock) always, if it does, hangs when the circle is being drawn on the top left. I will try to make a logcat or lastmsg for you technical people ;)

I have my asv3 chip undervolted (CPU only) by 100 mV, so the rest are at stock values.
[Galaxy S III Original Android Development] p33t-r:
Mine gets stuck when the line is at bottom-right from the SAMSUNG logo. Sometimes a bit earlier, sometimes a bit later.

I wanted to make a logcat too, but how to do this when you can't access adb before the system boots?
[Galaxy S III Original Android Development] Frag1le:
I'm also experiencing random reboots since last kernel. I'm not sure if it's the kernel though. It started with I wanted to take a picture I suddenly got presented with the boot animation and the phone did some sort of quick boot without showing me the white samsung logo and device id. Then 2nd time was when I was listening to music with my earbuds with the screen off. 3rd and 4th time also randomly during typing and playing a yt video. All on stock voltages.

I'm flashing back last 34 kernel to see if it changes anything

Sent from my GT-I9300
[Galaxy S III Original Android Development] andrewfung888:
Random reboots are usually caused by too much uv. My case is that when i reboot, sometimes it will stuck in the boot logo two or three times and then ok.

I've tried these

1. unchecked set on boot in uv ->ok

2. Uv set on boot -25 only, Abb stock ->3bootloop

3. uv-100 abb +50 ,uncheck int/mem -> ok

4. Reset to default -> ok

So i think it is not just one setting cause the problem. This happen only after abb introduced because i used to be 150uv. But still can get very good battery life.

*not a scientific test and too aggressive in uv and rbb cause more bootloops.

Omega 43.3 asv3 Perseus 36.3