yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Sleehond:
Thnx i'll try out zzmoove optimal for a while :good:
[Galaxy S III Android Development] jimsiv:
Hi Andi

Thanks for your great job....beta 4 is smoother and it gives you a very positive feeling....I think battery is like the previous version but only time will show this! Thanks again Andi

Sent from my GT-i9300
[Galaxy S III Android Development] janres155:
Andi, Is it possible to make frandom produce non-depleting entropy i.e 4096?

Janres
[Galaxy S III Android Development] gieffe22:
max performance:zzmove performance-lulzactiveq

balanced:zzmove optimal(this is my fav)

battery: zzmove battery yank(very good battery and performance similar to optimal) or pegasuq battery(bad performance,good battery)

governor:zen or row

but a very important thing is LMK (on last tab in boeffla config),set like this:42-50-58-66-92-160
[Galaxy S III Android Development] boyheadkick:
if he did, the battery would drain really fast

non depleting entropy generated by other entropy generators casue that because they are quite resource intensive
[Galaxy S III Android Development] theantilag:
I think you can try seeder for that
[Galaxy S III Android Development] MIKEMON:
But I do not know why these products?

kernel is beautifully smooth and stable

What more can you ask for?

---------- Post added at 11:10 PM ---------- Previous post was at 11:09 PM ----------

As the saying goes

The more the less
[Galaxy S III Android Development] gvmiguez:
Instaled new beta4 and my S3 is flying??, thanks Lord Boeffla
[Galaxy S III Android Development] JustArchi:
Andi, awesome update :).
[Galaxy S III Android Development] iNFRiNGE:
FUBARED!

Hello folks,

I think I fubard my S3 T-999 on Hyperdrive.

I've flashed numerous ROMs and Kernels before but I think I f'd this one up.

I flashed this kernal >boeffla-kernel-4.1.CWM and phone stayed with a black screen. :eek:

There's no led flashing or anything but it's not completely dead because when I plug it into my PC I hear the connection "Ding" and the "Double Ding" when I unplug it.

I can't get into download mode or recovery either and was thinking to charge the battery.

When charger is plugged in I get nothing as far as charge indicator.

I've pulled the battery and replaced , pulled SIM Card and replaced pulled external storage card etc.

I've searched as much as I can or searched as many terms and can't find anything.

Any help would be appreciated and thanks in advance for anyone that can help.

Just a note I have Odin and the rooted samsung rom I've used before as a last resort if I can get into download mode though.

Thanks again
[Galaxy S III Android Development] Robi959:
Man this is kernel for I9300 not for T999
[Galaxy S III Android Development] iNFRiNGE:
Errr I knew I f'd up somewhere and am kicking my self to death here.

I just connected to PC and there was NO DING! But I held the power button down and it then made the connection so it appears to be able to power on and off.

Any suggestions from anyone would be appreciated.

Thanks again
[Galaxy S III Android Development] boyheadkick:
if you can still boot to recovery, just flash a stock kernel
[Galaxy S III Android Development] iNFRiNGE:
I know I mentioned that in my first post but i can't get into download mode or recovery and was thinking the battery might need to be charged.

I have to run to work for a couple of hours and will check back as soon as I return.

Thank you everyone who can shed some hope here.
[Galaxy S III Android Development] boyheadkick:
oops, my bad :o
[Galaxy S III Android Development] iNFRiNGE:
No worries, I appreciate you even making an effort.

Thanks :good:
[Galaxy S III Android Development] iNFRiNGE:
Oh boy, nobody has a clue?

I know now it's the wrong kernel, the question is now how can I fix this mess?

Also while playing around with the phone connected to my PC I tried to "blindly" (since screen is just black) get into download mode, Windows 7 prompted that it was installing device drivers and failed afterword. I went into my device manager and the driver taht failed to install is called "QHSUSB_DLOAD". I'm going to search now but in case anyone may know about this driver I thought I should list it I imagine it's the driver to get you into"Download Mode" to connect to Odin but haven't verified that yet.

Thanks.
[Galaxy S III Android Development] boyheadkick:
maybe this can be of help?i hope it does

http://xdaforums.com/showthread.php?t=2439367
[Galaxy S III Android Development] iNFRiNGE:
Thank you I'm going to check that out now.

I found some info about "UNBRICK" and I know the driver installed failed due to not being signed. I'm rebooting my pc now to disable signature enforcement.

Crossing fingers that there is hope.

Appreciate your help also btw.

EDIT: This SHOULD be the answer I just didn't get there yet. I'm frustrated and all and I appreciate you UTFSE for me before my head exploded. lol
[Galaxy S III Android Development] Iqbal Ansari:
Hey andi thanks for this kernel.

Just curious which rom are you using right now.
[Galaxy S III Android Development] boyheadkick:
This is actually a good situation you're in because you're learning something new...back when i was using sony i'd run into those kinds of situations all the time, but the worst i did with my phone back then was just a soft brick

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] Robi959:
Post this in section Q & A
[Galaxy S III Android Development] iNFRiNGE:
FIXED!!

Oh Man!

Thanks for the suggestion I appreciate it, I've soft bricked before and way back when I did it many times on my Captivate but this had me worried.

I was able to fix using KAsp3rds [HOWTO] that you were pointing out to me at the same time.

My first 2 attempts ended even worse with no recognition upon connecting to my PC..

This is what I did to get it to work perfectly along with any changes I made.

You definitely have to use a 16GB or 32GB SD Card for some reason. I tried an 8GB card the first time.

Copied all files from my 32GB Ext. SD Card to my PC.

Deleting everything off the card prior to writing UNBRICK image was not enough again got nothing for a response from PC.

Formatted the SD Card using Mini Partition Wizard along with this guide SD card partitioning

Then I wrote the UNBRICK image to the SD Card per KAsp3rds [HOWTO]

I then Re-Partitioned the SD Card again and copied old files back to the card installed and rebooted phone.

I must point out that I didn't even have to connect my phone to my PC as KAsp3rd mentioned the phone booted up completely to it's previous state immediately. :victory:

Thanks for all your help and I can now say that I have lived by the words of my siggy and it ain't fun and definitely was not the way to spend valentines day that's for sure. :p

Cheers :highfive:
[Galaxy S III Android Development] eRPeeX:
You can flash a stock Rom with Odin on download mode.

And after this you install custom Rom and kernel

Sent from my GT-I9300
[Galaxy S III Android Development] iNFRiNGE:
I flashed Route 66 and then Hyperdrive again and thank goodness for TiBU and googles backups it was a breeze..

I'm not f$&#in FUSSING with kernels for a while. :laugh:
[Galaxy S III Android Development] boyheadkick:
Good to know you were able to revive your device :D there's a very good lesson to be learned here, lulz :p

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] JMS74:
With the 5.2 betas my s3 keeps blocking on sleep mode and won't awake the screen or takes too long. With the 5.1 that don't happens and I can assure you that because I've tried moving back and forth between them for sometime now.

Is this a known bug? Please fix this Boeffla.

Thanks

Enviado do meu GT-I9300 através de Tapatalk
[Galaxy S III Android Development] JustArchi:
Disable zram.
[Galaxy S III Android Development] andip71:
There is nothing wroing fussing with kernels. Just take the right one, which fits your hardware :)

Then it is almost a piece of cake.

And by the way: It is really hard to hard-brick the S3. You would need to flash a completely wrong wrong which overwrites your boot loaders.

No, it is not a known bug. And out of thousand users this is (so far) the only report.

So for the time being, nothing I can fix which does not occur for others as well...

BTW on which rom base are you? You should at least go up to UGNA5 or UGNA7 based firmware.

Andi
[Galaxy S III Android Development] JMS74:
Wannan lite 7.3

Enviado do meu GT-I9300 através de Tapatalk
[Galaxy S III Android Development] you_man:
Hi Andi.

You can modify zzmoove profile battery extreme yank for only 2 cores?

Such as PegasusQ profile boeffla 2 cores.
[Galaxy S III Android Development] andip71:
Maybe [MENTION=3279788]ZaneZam[/MENTION] can give you a hint how to configure some of the Zzmoove tunables to achieve this.

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] ZaneZam:
yes my lord i can :)

so you man can do this by:

loading "yank battery extreme" and going into "tuneable mode" in config app then by setting "up_threshold_hotplug3", "up_threshold_hotplug2", "up_threshold_hotplug_freq3 and "up_threshold_hotplug_freq2" to "0" -> en voila yank battery extreme running only on two cores ;)
[Galaxy S III Android Development] MIKEMON:
I do not know what one wants and expects

But,., You must try more options in the kernel

All the best to try and choose from a menu application profile / boeffla moderate /

Then, test that helps you out

zram not recommended for routine use.
[Galaxy S III Android Development] Maceee:
Hello guys. I just want to share my experience in fact I'm pretty happy with this kernel. With boeffla 5.2 beta 3 and beta 4 the best governor for me is pegasusq standard. This is the most stable and battery friendly governor. I managed to get 28 hours on battery with more than 3 hours of screen-on time without any battery saving settings, with gmail, fb sync on, automatic display brightness set to max value, web browsing, A LOT of messaging, music, mobile data, wifi etc... Thanks for this kernel! It's great! I'm not experiencing any issues, except with zzmoove governor there is some unstability. For example, sometimes when I press shut down key to lock the dislpay there is a delay and it seems like the display is dimming till it goes off instead of going off immediately. Furthermore, there are some launcher redraws and hickups. Zzmoove demands much work to do. But pegasusq is awesome.
[Galaxy S III Android Development] MIKEMON:
Yes, some documents to confirm

for me, but it is the best super zzmoove
[Galaxy S III Android Development] ZaneZam:
strange,i saw many things during development of zzmoove but NEVER such a thing. is this reproduceable?
[Galaxy S III Android Development] keneth_c:
To the dev

Your website main page does not reflect beta 4 for test version of Sammy 4.3 though the download page and change log have been updated to beta 4 :)

Main page still reads "Boeffla kernel v5.2 beta 3"... Update?!

--

---------- Post added at 12:35 AM ---------- Previous post was at 12:30 AM ----------

I have the dimming issue as well...

Noticed it just the other day. Try locking ur screen in a dark to pitch dark room. When I lock my phone... My screen us off... But i can still see the back light of my screen for a second or so.

I'm using your governor (zzmoove) though with the "battery yank" profile and I'm liking it. Pegasusq just doesn't cut it for me somehow. Not sure how other users are getting good results with Pegasusq.

--
[Galaxy S III Android Development] andip71:
Will correct the website tomorrow.

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] boyheadkick:
just trying to throw an idea around in here, but maybe early suspend has something to do with it?
[Galaxy S III Android Development] Morts:
Good job man. I like very much your kernel.

Thanks for developing it.
[Galaxy S III Android Development] nelsonw:
Just a suggestion, Andi. Keep a copy of the latest loaded & flashed kernel. Always I change the ROM need to find an old kernel and then load and flash again. Thanks.
[Galaxy S III Android Development] andip71:
This is already the case :)

Look into your boeffla-kernel-data folder, all load&flash kernels are archived there.

Good night

Andi

Sent via Tapatalk2 from my Galaxy S3 IPhone killer
[Galaxy S III Android Development] nelsonw:
Ok. I asked bc today I loaded and flash beta 4 and accidentally hit no when asked to proceed and when I Web to L&F it downloaded again. I figured that the kernel was on a temp folder. Thanks!

Never mind, found the flash tar.md5 option. Always learning. Thanks!
[Galaxy S III Android Development] ZaneZam:
you just made me going into a dark room and stepping on a cat's tail, all i was able to (re)produce was a loud scream!

damn kitties are lying around here everywhere. but no worries no one was seriously hurt! :)

would be involved then yeah, but i still can't see such a problem on my system. screen is going off here instantly as it ever does and i honestly have strong doubts that a governor has the 'power' to influence the system in such way. it's more the other way around a early suspend 'event' controls the governor ;) so that must be some other side effect. anyone else has this only on zzmoove? would be really strange, though.
[Galaxy S III Android Development] boyheadkick:
yeah, it was just a thought..btw, i don't have it either..

and you almost made me lose my coffee when i read the upper part of your reply :laugh:

-aL

Edit: [MENTION=947981]Lord Boeffla[/MENTION] andi, i have a question regarding NTFS module..i have a WD My Passport 1TB portable hard drive, and i have never tried to connect it to my phone via OTG but i wanna try now...question is, how to?do i just enable NTFS module and mount via StickMount?my concern is will my phone detect it automatically after mounting and power the hard disk by itself via OTG?and is it generally safe to do so?i'm afraid something might happen to my XHDD and corrupt my data :D
[Galaxy S III Android Development] Nic2215:
I know similar questions has been asked before but not exactly what I want to know. My question is the default charging is 1100. Me using galaxy current showing maximum 1000, average 1089. Before this it was maximum 1000,average 999. What does that mean? My maximum rate of receiving is 1000,but they are 1089 ma coming from the charger? Is that useful? I'm using stock battery and stock charger, am I getting 10%more or the same like wasting current? Because it's says maximum 1000 only. Thanks
[Galaxy S III Android Development] keneth_c:
Lol.

My bad ZZ. But I'm serious about the back light thingy. I'll need to find another phone and take a video. Till do so and send across in the evening.

Apologies once again...

--
[Galaxy S III Android Development] boyheadkick:
You know what, i just remembered now...i experienced this once too...i woke up around 2am and noticed that my screen was off but somewhat dimly lit so i unlocked it and locked it back again...it was ok after that...happened only just that once to me though...i was running one of the previous 5.1 beta version though, cant remember which one exactly...

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] Nic2215:
Guys need help here, before I realised my problem, I clean int. Folder and cache from the boeflla apps, sd maid to clean junks then I reboot and realised every reboot I will see the message Android is upgrading but without 0/100, meaning after the message pop out nothing changed and back to home screen unlike reformat u will have this 0/100
[Galaxy S III Android Development] janres155:
I think that Progress Dialog is when you clear the dalvik-cache, or maybe a modified dexopt flag in the build.prop?

Please elaborate the situation, I find it somehow confusing.

Janres
[Galaxy S III Android Development] Nic2215:
Sorry for the confusion. To make it simple, whenever I restart my phone now I get this Android is upgrading, starting apps. Very fast but the dialogue is annoying
[Galaxy S III Android Development] pistoke:
I updated to Omega v56 and to the newest beta Boeffla-Kernel about 34h ago. Only one problem. Last night one sms was missing from the default sms app. It's like I have never received it. Luckily I also use Ghostly sms app, which is meant to help if you have missing sms. This was the first time it have sms and default app don't and I started to use it last summer.

Is there any settings which I should avoid or use in the kernel to make sms work without problems?
[Galaxy S III Android Development] JustArchi:
How is that connected with the kernel?
[Galaxy S III Android Development] pistoke:
Maybe I have set my phone to go to too deep sleep and the default sms app don't wake up fast enough and it don't receive the new sms..? Ghostly is made to be fast and catch the incoming sms immediately.

I don't know the answer to your question. That's why I am asking if there are some settings which may cause problems in situations like this. I don't ask if I have the answer. ;)
[Galaxy S III Android Development] JustArchi:
Well, it depends on your settings. Basicly you can't "hurt" your rom if you didn't touch uV. At least from my own experience.
[Galaxy S III Android Development] janres155:
You get this message even though you didn't clear the dalvik-cache?

I haven't experienced this one, only when I'm clearing the dalvik-cache.

Janres
[Galaxy S III Android Development] Nic2215:
I did cleared but I'm getting this at every reboot. Hmm come to the worst will wait for next rom update
[Galaxy S III Android Development] pistoke:
I have had normal volts for a few months. I didn't have problems with uV settings, and neither haven't any advantages. So I decided not to uV my phone.

I have quite a normal settings.

Zzmoove optimal

Cpu 1500 MHz, AFTR + LPA

Many of the sound settings are turned on.

Touch wake 5

Led speed 2

Zram 1/300

Others are default.
[Galaxy S III Android Development] D00ky:
I've experienced similar behaviour before but haven't related it to governor. But I wouldn't say that this can only be seen only in the dark room as screen goes from current brightness to minimum brightness before shutting down the screen and not to some lower brightness than minimum. At least this is how this behaviour is in my case. But I will try to test this behaviour with other governors and report my observations.

Edit: In my case early suspend is set to zero so it is off. I also thought that early suspend could cause this but not in my case.
[Galaxy S III Android Development] MIKEMON:
Indeed, it is the interesting behavior

Never, I've never seen this
[Galaxy S III Android Development] viktor92:
I always have this dialog, maybe since I've rooted the phone with JB v4.1.2 !!. Changed to many version of JB 4.3, flashed lots of kernels, and the dialog is always present at each boot. I don't know why this thing appears, but despite it's annoying, I have not seen any side effect at all.
[Galaxy S III Android Development] Nic2215:
Try this install lucky patcher, then go to toolbox remove all odex file from data u are good to go:beer::thumbup:
[Galaxy S III Android Development] keneth_c:
[MENTION=3279788]ZaneZam[/MENTION]

I guess I'm shameless... But honestly I was able to reproduce it again today.

Went to a pitch dark room (no cats, kittens, pets etc.)... Opened an Google Play (mine has the white theme). I then hit the home key... So i went back to home screen. Long pressed home key this time... And ended all apps. Immediately hit the lock button.

Screen goes off... But back light remains on for a bit. Was able to reproduce this... 1 out of every 3 times atleast.

Tried the same process with Tapatalk (dark theme) and same thing again.

I tried recording it using another phone... But back light is a lil too dark for the camera to pick it up.

Could you give that a try?

--
[Galaxy S III Android Development] ZaneZam:
see

hi keneth,

it's not that shameless at all ;) this time i went to a dark and save place (i distracted my cats with some nice goodies beforehand to be sure because last time i was near getting a heart attack *ggg*) tried your "combos" both but still wasn't able to produce such an effect. ;) hmm really don't know what's going on here on your device(s), sry. :confused:

cheers

ZZ
[Galaxy S III Android Development] keneth_c:
It's aite [MENTION=3279788]ZaneZam[/MENTION]... Thanks a mil. The backlight thingy is not so much of a worry for me...

Thanks again for the awesome governor.

--
[Galaxy S III Android Development] carbonize:
Keneth are you using touch to wake and if so how long is it set for?
[Galaxy S III Android Development] boyheadkick:
[MENTION=947981]Lord Boeffla[/MENTION] andi, i have a question regarding NTFS module..i have a WD My Passport 1TB portable hard drive, and i have never tried to connect it to my phone via OTG but i wanna try now...question is, how to?do i just enable NTFS module and mount via StickMount?my concern is will my phone detect it automatically after mounting and power the hard disk by itself via OTG?and is it generally safe to do so?i'm afraid something might happen to my XHDD and corrupt my data :confused:
[Galaxy S III Android Development] heusen:
I'm getting that message too every reboot

Ill try this hope it works thanks!
[Galaxy S III Android Development] pricey2009:
This is the init.d scripts such as zipalign that gives you this message on boot..

Try emptying the folder then it will go away.
[Galaxy S III Android Development] andip71:
Hi, well - I did that many times already, however you will only have read-only access. Just to tell you upfront.

You need to load the NTFS module + install an app like stickmount that automatically detects and mounts your drife.

Also, make sure the HD you use is having an own power supply as the S3 cannot deliver enough power for a harddrive.

As I said, it is only RO access, so it will never corrupt any data.

There is no charge current sensor in the S3, so everything these kind of apps show is... "something". Something which does not neccessarily concur to reality.

I think the best "close guess" is still the first page of Boeffla-Config as this directly hooks into the charging logic and displays what the S3 charging logic negotiated with the charger.

No, this is not normal. I also had it once, maybe a year ago. And the only way for me was to reinstall a clean rom.

Next time just try to use the "Fix permissions" point in Boeffla-Config. After a reboot your SMS app could be back (if it was result of an inproper zipalign which did not set correct permissions afterwards).

This did help for you? Really? Because if so, I will put this in my notes so I know next time I have that as well again.

Exactly. And this is why I am severely thinking of either excluding zipalign scripts from init.d execution in general, or make complete init.d execution switchable with default to Off.

Not yet clean in my mind what the better way would be...

Andi
[Galaxy S III Android Development] Nic2215:
[MENTION=220904]andi[/MENTION] yes, the luck patcher method works for me!
[Galaxy S III Android Development] JustArchi:
I've already moved everything to my own location and hooked android process, so this time Andi it's truly your decision, I don't have anything against.

Just keep in mind that you need a root call (daemonsu), if you don't have that already, as this is required in order to allow root access since Android 4.3 and many ROMs put it in init.d.
[Galaxy S III Android Development] boyheadkick:
Thanks for this..i was expecting r/w access but also half expecting the limitation...

My vote for this is for you to make it switchable on/off like in your CM kernel...

-aL [boyheadkick]

Tapatalked from my BoefflaDroid i9300
[Galaxy S III Android Development] heusen:
The lucky patcher works for me too
[Galaxy S III Android Development] Nic2215:
Glad that it works for you too:thumbup::thumbup: :)
[Galaxy S III Android Development] andip71:
Hi guys,

ok, now it is fixed. I am going on a business trip tomorrow and will not return before Monday next week.

So please accept delays in my responses and try to help yourself with help of the community.

Thanks

Andi