yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] MrxSiN:
different things happen to me, got 2 S3 blue and red, rooted with same root method, blue good, red always hot reboot. back t stock still doesnt fix. Send to Samsung, fix. Got home, root it back, same things happen, resend to samsung, fix, got back home, root it back with new release from chainfire. Hot reboot, send to samsung, fix, got back home, sell it.

Of course i reset using TriangleAway. :D
[Galaxy S III Original Android Development] ZduneX25:
And when such things happen it's good to start reading about repartition option in odin. I have heard that it comes useful when phone acts very strange and where is no other explanation.
[Galaxy S III Original Android Development] FrancescoGato:
I couldn't install temasek's CM10.1 unofficial RC4.2 as second ROM (upgrading from RC4), tried installing from internal SD and it just got stuck after opening package, then I had to remove battery and after it rebooted normally either in first or second ROM...thanks in advance for any solution.
[Galaxy S III Original Android Development] sapabg:
Anybody managed to install PA 3.55 for a second rom? I get stuck on "Installing update..." when I choose to flash it from my External SD...Help...
[Galaxy S III Original Android Development] EP21:
Does this kernel support undervolt?
[Galaxy S III Original Android Development] peramikic:
2nd rom install stuck

I can confirm that recovery gets stuck trying to install 2nd rom with 1.4.5 kernel (full CWM zip CM10.1 RC4.1 and RC4.2)
[Galaxy S III Original Android Development] cerealguy:
Hay guys...I'm on Cm10.1...can you share your settings for this kernel, please? I'm looking for good battery /performance compromise :)

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] MrxSiN:
While u fixing 2nd rom issue, possible to update recovery to latest CWM?

u need to test it ur self, every device have different chip quality.

---------- Post added at 02:16 AM ---------- Previous post was at 02:11 AM ----------

i thinks its not. On my mind, its motherboard related. They just reprogram it back. Hot reboot still happen but not as wild as before. Lucky me the person that buy said she can live with it. :good:
[Galaxy S III Original Android Development] padlockedtight:
I was fully insured and had a replacement phone in 24 hours.

Still freaked me out at the time though! XD
[Galaxy S III Original Android Development] Kord:
Sorry Googy, but my SIII also stuck in recovery during installation of SecondROM :(
[Galaxy S III Original Android Development] sungc007:
I have the same issue...I can't install new second rom...
[Galaxy S III Original Android Development] FadeFx:
Can you guys clone first to second rom?

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] DaReDeViL:
OK guys, problem identified. Dynamic Fsync conflicts with builtin 2nd rom utils !
[Galaxy S III Original Android Development] DaReDeViL:
Version 1.4.6 ONLINE !!! ;)

[03/06] Version 1.4.6 :

- Dyn-Fsync : Disabled as it conflicts with 2nd ROM Utils

PS : is it me or is this version really smoother ??? :p
[Galaxy S III Original Android Development] hemal_4404:
This one is just awesome with butter smooth.
[Galaxy S III Original Android Development] RrOoSsSsOo:
Which governor?
[Galaxy S III Original Android Development] Kord:
m8s, there is a optimal voltage for ABB in our SIII?

I'm asking because I don't even know how to set this thing properly, or what is default value :)
[Galaxy S III Original Android Development] DaReDeViL:
According to yank555, our s3 doesn't have the necessary hardware for a full abb experience

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] Kord:
Then, why did you implemented ABB?

Even if we don't have hardware that can fully handle ABB, there is a still option to improve something - if yes, how or turn it to default values :) ?

I'm asking because I don't want battery drain, m8 :)

Thanks for respond!
[Galaxy S III Original Android Development] DaReDeViL:
Abb, to rapidly and efficiently adjust voltages, needs a special type of regulator, which we apparently do not have, according to an "anonymous" source.

Here is a document about it: http://www.ece.cmu.edu/research/publications/2010/CMU-ECE-2010-002.pdf

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] GabrielSousa:
can i install a sammy rom on 2rom (internal sd) ?
[Galaxy S III Original Android Development] Kord:
Oh, okay, I'm understand :)

So in next version ABB will be removed, due to lack in our hardware?
[Galaxy S III Original Android Development] DaReDeViL:
No. Until proven to have negative effect, it will be kept.

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] Kord:
Okay, your choice, m8 :)
[Galaxy S III Original Android Development] venomgz:
hi...

I'm installed the kernel with CWM, but the STweaks don't appeared in my app list... what I have to do?

I'm using stock rom 4.1.2 rooted.
[Galaxy S III Original Android Development] MrxSiN:
Download it from Play Store
[Galaxy S III Original Android Development] MrxSiN:
found new bug, I/O scheduler not working. It always on CFQ no matter which one u choose in Stweaks. Recheck using CPU Adjuster, Performance Settings in CM, it stated CFQ, but Deadline in Stweaks, Internal and SD Card

Somehow, Undervolt Preset -25 -50 -75 -100 doesnt work too

---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------

any plan to include BFQ scheduler?
[Galaxy S III Original Android Development] amppen:
Haha :D anonymous

Adaptive body biasing is surely lacking the adaptivity that could be attained via dedicated hardware, but that probably why the "slices" were introduced, to find a way to keep some part of the adaptivity. Gate voltage scaling is business as usual, has been for a long time, so the same basic scaling idea introduced to a different leg of a field effect transistor is not that far fetched idea at all.

Even with the lack of full adaptivity, it's still a way to bias voltages and manipulate the field effect inside our chips. It has great potential in my opinion, and the current implementation just might not be the final version of this... If devs are interested in abb, I wouldn't be surprised if we were to see some smart governor plugins or similar to better keep up with the gate voltage scaling.

In my opinion one could benefit from body biasing even with no adaptivity at all, just all body voltage slices pumped up to introduce RBB and reduce leak. There are many user experiences available for reading in the dedicated thread, and I try to continue my own experimenting with this also when I'll find the time to run some longer controlled tests.

Don't give up on this just yet ;)
[Galaxy S III Original Android Development] sasikumardr:
I saw some pages back 2 posts that says flashing this kernel using twrp causes hard brick.

Is there anyone using twrp for flashing?
[Galaxy S III Original Android Development] andrewilley:
I've had a couple of random reboots overnight the last two nights since installing 1.4.5 (BBS indicated one a few hours ago at 3am for example, and yesterday I saw one happen at 7:30am). I'll try 1.4.6 and see if that's any different.

Andre
[Galaxy S III Original Android Development] DaReDeViL:
2 more other reports about reboot and abb will hit the road...

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] qtwrk:
Don't, don't blame it on TWRP such good recovery.

May be this mate just accidentally, coincidentally, happens to have eMMC failure as SDS, I have been using TWRP ever since my time back with Nexus S.

Just tried: TWRP 2.5.0.0 + Googy 1.4.6 , I am still alive and typing reply to you.
[Galaxy S III Original Android Development] xclub_101:
Nice!

Nice! :good:

For the moment it seems to work OK - but to be honest it is hard to say if it is smoother or not than the previous one :)

I was/am now testing with lulzactiveq vs pegasusq and row vs deadline as governors / schedulers - it is kind of funny that after installing a new version I have to verify every single setting - in both ROMs :rolleyes:

---------- Post added at 09:05 AM ---------- Previous post was at 09:00 AM ----------

This is not necessarily related to ABB (I suspect more the touch-to-wake) - but over almost 8 months with my i9300 I have seen a total of 2 reboots - one was in the first month when I was doing some very heavy and exotic testing, and the second was few days ago with 1.4.5 I believe - the reboot was a few seconds after somebody called me on viber and we were like 10-15 seconds into our call talking; the other unusual thing was that after reboot the pin for my SIM was not requested (so it was a quick hot-reboot or something).

I will keep an eye on this.
[Galaxy S III Original Android Development] DaReDeViL:
The settings in stweaks get reset when the structure of the config file is altered (This time it's because of removing dyn_fsync setting ).

About sudden reboots, it can't be touch2wake since its code is soooooo simple that it can't be responsible for this BUT since I introduced ABB I must admit that I faced some reboot which I never had with the dirtiest alpha unstable test versions of googy-max kernel.

So to be clear, I need to have a stable and good performing kernel and I won't keep any cutting-edge feature if it's negative side is heavier than its positive one !!!
[Galaxy S III Original Android Development] DaReDeViL:
I/O scheduler settings in stweaks are applied after reboot
[Galaxy S III Original Android Development] MrxSiN:
1.4.4 i/o scheduler act immediately. Thank you for the info.
[Galaxy S III Original Android Development] gabebcn:
I also had some reboots. Had to restore a backup because I couldn't turn on the phone even changing kernel. Stood in a bootloop. But i guess it was a bad combination. Now everything's ok, no reboots. Adjusted abb with my uv voltages

Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] jugg1es:
I've flashed the last two versions of this with twrp and had no problems.

Has anyone else got problems with hangout notifications not showing since flashing this kernel?

“Count your age by friends, not years. Count your life by smiles, not tears.” ― John Lennon
[Galaxy S III Original Android Development] qtwrk:
Have reboot as well, phone was in idle, and then I suddenly hear the boot sound and take it out of my pocket and see it is rebooting...
[Galaxy S III Original Android Development] DaReDeViL:
2nd report...

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] arsalanaly:
Working flawlessly on miui rom.... Waiting for battery stats
[Galaxy S III Original Android Development] GabrielSousa:
[MENTION=1897326]googy_anas[/MENTION]

do you know why i have this error trying to install 2 rom ??

I: Cant partition non-vfat: datamedia

I: Cant format unknown volume: /emmc
[Galaxy S III Original Android Development] Leicxan:
version 1.4.6 working perfect on my asv3 device

do some abb undervolt and nerver get reboot..

sorry for my english
[Galaxy S III Original Android Development] habylab:
This is awesome, I love it! Coming from CM10.1, dual booting with Stock, as I love the camera.

Quick question, it seems you're as technical as other developers, in terms of going for cutting edge rather than a simple approach, would this be correct? You seem to have done lots of commits. Which is why I love Perseus and Temasek's kernel for example!

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] arsalanaly:
Battery stats....

No uv/ov

Zzmove... Cfq
[Galaxy S III Original Android Development] peramikic:
I flash all of my S3 stuff with TWRP, including googy 1.4.6, no problems here

---------- Post added at 04:47 AM ---------- Previous post was at 04:33 AM ----------

No reboots here, 1.4.6 with default ABB(ASV3), no UV/OC, zzmoove & cfq, idle for 11 hours, with WiFi, 2.1%/h best I ever had so far.

Depending on the ABB settings, the old UV settings that were stable before might not be anymore, so that might be the cause of some reboots since ABB was introduced.

[MENTION=1897326]googy_anas[/MENTION], is there a way to turn-off ABB without removing it from code, i'm not sure how integrated into core code it is. Some chips might be more tolerant than others and the ones that aren't could just turn it off, or better yet keep it off by default and then users can enable it on their own
[Galaxy S III Original Android Development] habylab:
Getting half scores on I/o, read/write and CPU with no changes really. Odd! Can't tell though, and it is just a benchmark after all.

Sent from my forever getting older Galaxy S3 (AVS2). Long live the original Galaxy S :)
[Galaxy S III Original Android Development] GabrielSousa:
can some one help me with this ?

would love to install SECOND rom.

thanks
[Galaxy S III Original Android Development] DaReDeViL:
Which rom are you planning to install as 2nd ? Did You wipe 2nd rom first?

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] GabrielSousa:
i did wipe 3 or 4 times, i formated...

i try to install cyanogenmod or a sammy rom, same problem :(

the only thing that work is clone 1rom to 2rom

but now i want to install other rom on 2 rom and i have that error :(
[Galaxy S III Original Android Development] tracemonkey:
Title of the thread needs an update to reflect current version.
[Galaxy S III Original Android Development] FadeFx:
[MENTION=1897326]googy_anas[/MENTION], i have had the same problems back when i first flashed something to my 2nd rom, when gokhan implemented dual boot...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] ZduneX25:
Guys if you were using 1.4.5 you should reset stweaks settings, cause old data of Dyn-Fsync (that disallows to install 2nd rom) still presents on your main /data partition.
[Galaxy S III Original Android Development] GabrielSousa:
Whats the solution ?
[Galaxy S III Original Android Development] imepv7:
Ex-tweaks app ain't working no more! Even SetCPU! I flashed 1.4.6. :rolleyes:
[Galaxy S III Original Android Development] FadeFx:
Install cm as a first rom and clone it to second rom did the trick for me that time.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] invinciblecc:
Nice job mate

1) sometrllimes mic doesnt work on calls please fix this I m unable to use ur kernel for this aa I have to flash siyah repeatedlt when it happenes because a reboor doesnr solve the issue im on pac and sotmax both

2) whats this voodoo sound engine does it have a control app also does it have an option to increase microphone sensitovity if not can u please add this option ...or awitch to another sound engine which has this if u cant do any of this can u jist create a new kodofied version of ur kernel with boeffla the latest one please
[Galaxy S III Original Android Development] shoxyy:
Default io scheduler settings dont work on 1.4.5. Even after reboot it stays on cfq
[Galaxy S III Original Android Development] GabrielSousa:
I did that. But if I want to install the 2 ROM, gives me the same error
[Galaxy S III Original Android Development] FadeFx:
[MENTION=3666499]vladnosferatu[/MENTION] You then install the other rom to first rom, probably even with other (philz or whatever) recovery.

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] tracemonkey:
Me too. I don't know if googy made a big tweak or I just haven't noticed gradual improvements before, but running 1.4.6 the battery life is amazing.
[Galaxy S III Original Android Development] FadeFx:
For me battery life is back to normal, after some problems on recent versions

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] romskii:
So who loves this kernel? Hit thanks!

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] torrentship:
Hi,

Cloned the max repo, setup tool chain, failed to build. Seems some kconfig and makefile files are missing. Any idea why?

Always fails on trace/events/random.h. Maybe some files weren't added to the initial commit?

I'm sure you're busy but any help would be appreciated. I'd like to eventually try to sort out the voodoo stuff.

Cheers

W
[Galaxy S III Original Android Development] JB-007:
It seems 1.4.6 is slower than 1.4.4. After benchmarks results comparison with the same settings (gov & i/o sched), but in daily usage i didn't see big differences.
[Galaxy S III Original Android Development] Yank555:
Forget benchmarks, they are hardly worth the time it takes you to run them, if it feels fast, it is, you're the best benchmark ;)

JP.

Sent from my SlimBean 6 / Yank555.lu CM10.1 kernel v1.6b-beta1 (Linux 3.0.80) powered Galaxy S3 i9300
[Galaxy S III Original Android Development] djskarpia:
thanks!

[MENTION=1897326]googy_anas[/MENTION] thanks for this fantastic kernel... it is working so smooth that my s3 with cm10.1 is very very fast!!! everything is ok ... continue in this way ... and especially keep it updated as you are doing....
[Galaxy S III Original Android Development] GabrielSousa:
on 2 rom, on about the phone the kernel version is the kernel from the 1st rom, its normal ?
[Galaxy S III Original Android Development] Jimbo239:
[QUOTE=vladnosferatu; on 2 rom, on about the phone the kernel version is the kernel from the 1st rom, its normal ?

Yes it is, otherwise you would only be able to access 1st rom.
[Galaxy S III Original Android Development] zenosteam:
Already done thanked and rated

Envoyé depuis mon GT-I9300 avec Tapatalk
[Galaxy S III Original Android Development] hemal_4404:
After running stable with 24 hours I am getting bootloop with V1.4.6. I am on stock 1.4.2 Chaos latest Rom. Can any one show me that how to set ABB value with UV values?
[Galaxy S III Original Android Development] Z3US911:
I know its a stupid question but

will this work on miui v5 by muchopoli83??
[Galaxy S III Original Android Development] GabrielSousa:
anyone has a sammy rom on 2ROM, with wifi working ?
[Galaxy S III Original Android Development] hemal_4404:
Yes I am having Chaos as primary and ARHD 26 as secondary Rom.
[Galaxy S III Original Android Development] GabrielSousa:
ARHD 26 on 2rom, wifi work ?
[Galaxy S III Original Android Development] francescozanghetta:
To everyone who has reboot/bootloop problems, you should play carefully with uv/oc/abb. Often even if some vakues seem stable after some time/reboot/some charge cycle/skype/etc they can cause reboot/bootloop. So before report just check what you are doing

What I suggest from my personal experience(AVS3) is:

first of all find your stable uv/oc values without touching abb slice;

after that increase your uv of 12,5/25mV per each abb increase of 50mV. You should work step by step to find your optimum. To give an idea these are 3 different stable conditions for my 200Mhz:

gate voltage: 712,5mV >> 1 slice :950mV

gate voltage: 737,5mV >> 1 slice :1000mV

gate voltage: 775 mV >> 1 slice :1050mV

Finally reboot (1 stress condition), and full charge your phone (2 stress condition). The masters stress condition is the time but if your phone survives to the first 2 conditions you are on the right way.

Last advice: DON'T USE somebody else values/profile because every chip is different even if it belongs to the same AVS category

Have fun!
[Galaxy S III Original Android Development] GabrielSousa:
tried ARHD 26 and i have the same problem :( ( authentication fail )

i remove my wifi password on my router and i have the same problem authentication fail :(
[Galaxy S III Original Android Development] hemal_4404:
Deleted.
[Galaxy S III Original Android Development] alien_jiggy:
Amazing work
[Galaxy S III Original Android Development] hemal_4404:
Yes it works smoothly.
[Galaxy S III Original Android Development] gilbus:
I am experiencing a really weird thing sometimes, my phones becomes unusable within seconds and I have to remove the battery. The screen stays on, but I have to make remove it very quick, just waited about 30 seconds that my phone solved it itself, but I am losing a lot of battery when rebooting that way!

Anyone experiencing the same problems?

using cm 10.1 nightlies, oc up to 1600 MHz, UV - 100 mV, deadline scheduler for internal sd card ( but just changed it recently), row scheduler for ext sd
[Galaxy S III Original Android Development] amppen:
Hear, hear! That is good advice.

Just faced yet another charging death while experimenting with ABB on a different kernel. Since zzmoove came along (and I'm using it 'cause it's awesome) I've been struggling with stability issues with ABB. Before it I used lulzactiveq and was able to play more freely with ABB and UV.

I guess there's no such thing as free lunch, getting maximal savings from both ABB and governor choice at the same time. Zzmoove is a very dynamic governor with quite aggressive scaling and hotplugging, so using it is another way of getting your ABB/UV values to shore their true colour.

Now I've tweaked my values again and testing can I get my phone to charge to 100% without dying. I have to admit that I use a dirty fix sometimes for this. I set a charging profile via setcpu, so that it stays within 400Mhz-1400MHz when charging, and sets governor to SmartassV2 (no hotplugging, as it isn't a multicore aware).
[Galaxy S III Original Android Development] FadeFx:
Try disabling zram to compare if problem persists

Btw, [MENTION=1897326]googy_anas[/MENTION] zram can not be permanently disabled, it has to be done on each reboot...

_________________________

tapatalked from GalaxyS3
[Galaxy S III Original Android Development] GabrielSousa:
manage to find the problem with WIFI

/cache (the first boot of the ROM) must be created with Siyah kernel

if the first boot of the rom will be with Googy-Max the WIFI will not work :(

after the first boot we can change to Googy-Max kernel, the WIFI will still work ;)
[Galaxy S III Original Android Development] 2727alex2727:
On 1.4.6 Bluetooth doesnt turn on for me, Just flicks from on to off until I restart my phone. D;

Did wipe and reinstall but same problem
[Galaxy S III Original Android Development] arsalanaly:
No uv/ov

Zzmove... Cfq
[Galaxy S III Original Android Development] gabebcn:
Enviado desde mi GT-I9300 usando Tapatalk 2
[Galaxy S III Original Android Development] MrxSiN:
im still using 1.4.4 until 1.4.6 fix. For people who have problem in 1.4.6 try revert back to 1.4.4. Its the most stable one.
[Galaxy S III Original Android Development] andrewilley:
I'm not touching ABB or UV at all, and have used Reset Defaults in ST Tweaks after installing 1.4.6 (not set any OCs either) and I'm still getting occasional random reboots. I had another one at 4am this morning - phone had been idle and not on charge since about 11pm. Of course it might not be related to the kernel, but it's the only major change that I've made in the last few days.

It would be a shame to have to go back to 1.4.4, as 1.4.5 fixed a fair major wi-fi wakelock issue for me.

Andre
[Galaxy S III Original Android Development] hemal_4404:
+1
[Galaxy S III Original Android Development] MrxSiN:
well, let we wait for 1.4.7 :D
[Galaxy S III Original Android Development] sapabg:
I noticed somebody else had a hot phone but didn't see what solution was offered...I am running 1.5.6 with Paranoid 3.56 and noticed that Facebook Messanger wasted most of my battery and I only recieved 1 message...bummer...I am pretty concerned with the heathing tho...restart solved it but still...
[Galaxy S III Original Android Development] jugg1es:
Ive not got a hot phone, uv -100. I don't get hangout notifications though :(

"Man is like a banana: when he leaves the bunch, he gets skinned." - Proverb
[Galaxy S III Original Android Development] sapabg:
hmmm...hope it doesn't happen again but...:confused:
[Galaxy S III Original Android Development] jugg1es:
No idea:confused: except they stopped after i flashed the kernel:screwy:

"Man is like a banana: when he leaves the bunch, he gets skinned." - Proverb