yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] coleburns:
whohoo. Happy you listened. It will definitely make life easier for people like myself who just want to know what works and can choose to experiment when they have the time knowing there a milestone to go back to.

Keep up the good work buddy
[Samsung Galaxy Nexus] slayp00n:
The quote function messed up from the xda app...

Someone said 1.7-1.8ghz would 'pop' the phone.

The stock freq for these chips is 1.5 they are underclocked because of PCB issues with the frequency generator locking properly. The chip itself has no problem at 1.5 so overclocking technically starts from that point forward
[Samsung Galaxy Nexus] zenzip:
sorry guys but with this kernel I can't get good batterylife, switched to imoseyon, trinity, and now franco...I've bought also app on market, can suggest me kind of governor (now use interactive), min-max frequencies (now use 350-1000), UV setting and other tips to obtain good battery life?

I ask almost 22h of battery life with mid-intense utilization.

Thanks a lot!
[Samsung Galaxy Nexus] Gahh Its Lee:
You'll never get that battery life using the phone a lot. The best you'll get on this phone is MAYBE 4 hours of screen on time. I speak of screen on because that's the easiest way to describe battery life since idle lasts forever. Interactive gov uses a lot more battery I use 700-1200 on demand and I'm doing pretty decent with battery life.
[Samsung Galaxy Nexus] maisi:
Does anyone know if franco has compiled this Kernel with the Smartreflex technology enabled or not ?
[Samsung Galaxy Nexus] zenzip:
I know that can't get super baterylife using my GN a lot...but now the best that I can take is 2h of screen on...I ask more :D

thanks for suggestions now I try ondemand with 350-1000 and I should get more battery life than 700-1200 ...

You don't use UV setting?

Thanks
[Samsung Galaxy Nexus] Gahh Its Lee:
I don't UV because the largest savings you'd actually see is 2% change so to me its not worth it. With on demand you'll get better life. Also remember wifi will save the most battery. And 3g uses less power than 4g
[Samsung Galaxy Nexus] zenzip:
at home, office, and university I'm always in WiFi, then 3G...never 2g....4G here don't exist :D
[Samsung Galaxy Nexus] Gahh Its Lee:
Hmm you should be getting more than two hours then. How's your service there? Do you get a good signal? Once he brings back francoturtle gov that helps battery ALOT
[Samsung Galaxy Nexus] zenzip:
I also have hotplug mode active... :o... You say that the only way is to wait for francoturtle governor ?
[Samsung Galaxy Nexus] bendirkss:
I'm running 350-1000 and dropped each on by 100. Its working perfect so far
[Samsung Galaxy Nexus] Gahh Its Lee:
Not the only way it just helps
[Samsung Galaxy Nexus] CaspaTheGhost:
Screen does look good mate! My setup is mostly blacks so I find it hard to test and compare the settings...

I've been having similar issues with GPS whilst using MCR and Franco's kernel, but haven't had the time to investigate further. Was fine when I was on Apex, but I think I'm gonna give AOKP a try this weekend so will see how it fairs.
[Samsung Galaxy Nexus] minipaolo:
I have seen it is almost the same if you use 350-1000 or 700-1200. You spend most of the time in deep sleep anyway.

I had amazing results with francoturtle and really hope to have it back soon! :-)

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
My local branch has smartreflex 1.5 enabled. Me and imoseyon exchanged some emails and with SR 1.5 disabled we could get to 1.68ghz but the device gets too hot and unstable. With it enabled we couldnt pass 1.5ghz BUT the device gets much more stable and doesnt throttle anymore so easily.
[Samsung Galaxy Nexus] StuMcBill:
Franco,

Still getting SoD on 18.2 with Hotplug disabled, what is the best thing for us to do to help, what logs would you need?

Stewart

Edit

Just got one now, my battery is currently out, do you need me to send anything on reboot?
[Samsung Galaxy Nexus] StuMcBill:
I rebooted my phone, and my battery has went from 60% to 16%!!

See the very end of the graph in this screenshot.
[Samsung Galaxy Nexus] IINexusII:
if you leave it for awhile you will see it crawl back up slowly
[Samsung Galaxy Nexus] Schiehallion:
Never had a sod. Not yet anyway. Hot plug and aokp(s) + always updating to newest kernel version .
[Samsung Galaxy Nexus] EsPeHil:
Those of you getting SoD.

Are you using Power Saver features? (ie in AOKP)

How about Sync? Is it on or off?

I don't use power saver and I have sync always on. Hotplug is enabled.

Still no SoD's.
[Samsung Galaxy Nexus] darrendm:
Not for me

http://img.tapatalk.com/5eaa59c8-7b81-c7ef.jpg
[Samsung Galaxy Nexus] EsPeHil:
Screen time 2h 55min.:D
[Samsung Galaxy Nexus] Elganja:
just made the same change... thanks
[Samsung Galaxy Nexus] Laynee1:
Where do you change that ?! In which app ? Thanks in advance
[Samsung Galaxy Nexus] Handymeister:
Hi all,

I still have Sleep-of-death with 18.2 with and without using the hotplug option!

Has anyone an idea for me?

Handymeister
[Samsung Galaxy Nexus] Elganja:
in Franco's app
[Samsung Galaxy Nexus] sluflyer06:
I've never had SOD issues with my phone until 18.1 and .2. Now if I undervolt at all it gets SOD.
[Samsung Galaxy Nexus] Handymeister:
Ok, but I have sleep of death without overclocking and without undervolting.
[Samsung Galaxy Nexus] taney:
I second that. First time I've had it ever. Build 25 AOKP with 18.2.
[Samsung Galaxy Nexus] bendirkss:
How much are you undervolting
[Samsung Galaxy Nexus] RikNik71:
I also got SoD on 18.2 (no OC, UV or anything). Flashed stock kernel back. Can´t stand SoD, it gives me the creeps since my days with O2X. Also, pulling battery when you have your phone in a Otterbox Commuter Case is a real pain in the ass.
[Samsung Galaxy Nexus] isinisterx:
Agreed, the commuter is a pain to battery pull :@
[Samsung Galaxy Nexus] THE_KINGDOM:
I just want to say my phone is extremely choppy on 18.2, never felt it like this before..
[Samsung Galaxy Nexus] detritu5:
Same here, but with hotplug enable.
[Samsung Galaxy Nexus] Bram77:
#18.2 is working very well for me. Had it on 1.65Ghz for almost a day but then I had my first spontaneous reboot ever. So I'm back at 1.5Ghz. I'm not complaining. Everything is smooth and battery life is very good.

Benchmark scores are low, but I don't care. The benchmarks are probably wrong because my phone feels faster then ever.
[Samsung Galaxy Nexus] THE_KINGDOM:
Surely the benchmark scores are somewhat accurate?
[Samsung Galaxy Nexus] loudaccord:
No log :( Had the first SOD in a long time when I just plugged in my phone to charge. All stock settings on 18.2 didn't change a thing. Had the phone plugged in for 2 hours and went to check to see if it was fully charged, had SOD, pulled battery, rebooted and was at 13% battery. Apparently wasn't charging while in that state.
[Samsung Galaxy Nexus] dmmarck:
Just had to batt pull myself. There goes any more deviation from the standard settings lol.

And yes, the Commuter is a pain. I always get caught with the micro USB flap too. A trick to getting it back on quickly is to put the power in first (so you don't end up doing crazy crap when forcing the buttons in).
[Samsung Galaxy Nexus] franciscofranco:
New build with hopefully SoDs fix will be up within one hour at most, waiting for the bloody train to arrive to take me home.
[Samsung Galaxy Nexus] dmmarck:
I said this on G+, but your recommended settings for color are an absolute Godsend. Thank you.
[Samsung Galaxy Nexus] Simer03:
i got rid of my Commuter case....and all my cases for that matter...im never using one again, this phone is too sexy! ;) Cant wait for the new build Franco, i didnt have SOD's but updates are always welcome! and i agree with the poster above me, the colors are sexy!
[Samsung Galaxy Nexus] minipaolo:
Use franco's app. You'll find it in the market
[Samsung Galaxy Nexus] nikosrs4:
I only had sod at 16.2 BUT with hotplug enabled. Since then, I disabled it and no problem for me.
[Samsung Galaxy Nexus] dmmarck:
Every time I try to lose the case I get too paranoid.
[Samsung Galaxy Nexus] franciscofranco:
Believe me or not I hit those values accidentally and boom the most accurate colors I ve seen on the GN. We gotta thank Ezekeel for porting the color multipliers code to GN.
[Samsung Galaxy Nexus] dmmarck:
Absolutely, many thanks indeed. I can believe it too. Took a good minute or two to get those values with my fat fingers lol.
[Samsung Galaxy Nexus] nikosrs4:
Are you talking about the recommended values in the app?
[Samsung Galaxy Nexus] minipaolo:
Ahah same here.

It'd be nice a set on boot option to avoid that every time :)
[Samsung Galaxy Nexus] dmmarck:
I am. The screen looks so much better. I can't wait to try out other combos too. Great stuff.

I agree! But hey, maybe we'll find other great combos when resetting it? Lord knows it takes me a while to get to those settings with the bloody slider lol
[Samsung Galaxy Nexus] minooch:
OK - While the chips where originally designed to handle 1.5, as even you've stated, issues were detected (There has been changes in the kernel that alter the way this chip works). Hence they have been binned at a lower frequency. The phone was then designed to only need to handle 1.2 - Therefore 1.2 is the stock frequency.
[Samsung Galaxy Nexus] mohitrocks:
Hey guys, I had a quick question. I already have Android Revolution HD rom installed. Do I just flash this as a separate zip? Will it erase any files? Thanks soo much! Eager to try this kernel out :)
[Samsung Galaxy Nexus] ljwnow:
I agree so let's (normal users) stop trying for the time being until someone sorts it out.
[Samsung Galaxy Nexus] mafiaboy01:
Hey guys I'm having problems with the camera on this kernel.

I'm running mcr, when I switch to camcorder the camera app closes.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GchildT:
I can confirm... same here...
[Samsung Galaxy Nexus] Dmw017:
Yepp.. I tried doign Clear Data, and it worked ..up until I tried switching to the front camera... then stuck on FCs again.
[Samsung Galaxy Nexus] Rey-619:
Camera is working fine on ARHD :)
[Samsung Galaxy Nexus] Dmw017:
I'm on AR HD 1.3.1 and Francos latest kernel non-OC..

I think this is just a matter of using Fix Permissions or clearing cache/dalvik ..but i seriously hope not ............seriously ..............
[Samsung Galaxy Nexus] JamieD81:
just so u know arhd 1.3.2 has been on rootzwiki for a couple days now :P

dunno why thread here hasnt been updated..
[Samsung Galaxy Nexus] gundamboy:
same here, running mcr after flashing ver 12 of the kernel the camcorder does not work D:
[Samsung Galaxy Nexus] godelsproof:
I changed 12kernel to 13test kernel camera is working well.
[Samsung Galaxy Nexus] Dmw017:
Yeah I saw it but have you read the changelog; not worth it imo lol.

thanks for the heads up though :)
[Samsung Galaxy Nexus] winwiz:
+1 camera is FCing as soon as I open it
[Samsung Galaxy Nexus] scimitar:
donation send! 7M8444797A688640X Thanks for your work!
[Samsung Galaxy Nexus] :
Wasn't sure if it was kernel issue, must not have been quiet enough to hear while I was testing other kernels. Thanks for clearing this up.

Another issue I've came by is the screen constantly spamming itself about 1/3 of the way down the screen uncontrollably. Believe this was undervolting too much, knocked everything up 25mV and seemed to sort the issue.
[Samsung Galaxy Nexus] EddyOS:
Confirmed camera issue. Stills works but switch the camcorder and it FCs

Using the non-OC kernel with no UV in use
[Samsung Galaxy Nexus] Shetlander:
Just tried the 13/12 test kernel (non oc version) and my camera and camcorder work fine. I also noticed a jump in performance with both Quadrant and smartbenc2011.

Franco

If you want me to post a dmesg could you explain where it is and if you want any other information. I am trying to give you feedback as best I can but have no experience in logs etc on the phone,

Im only trying to help you help us!
[Samsung Galaxy Nexus] EddyOS:
Where's the 13th December kernel? It's not in the OP
[Samsung Galaxy Nexus] The Gingerbread Man:
on 12.12.2011 camera force closes when selecting front facing camera, here is a log cat http://db.tt/5VpX8YGU

Only way to get be able to open camera again is wipe data with titanium for the camera

Trying to start video recording with camera force close camera, log cat http://db.tt/vXk43iBk

Panorama and normal camera shooting modes OK and working fine and saving pictures.

All camera modes working in 11.12.2011 just tested all of them. So definatly something doesn't like camera in 12.12.2011
[Samsung Galaxy Nexus] eiabea:
it is in the first post, but no changelog till now ;-)

http://androtransfer.com/franciscofranco/Galaxy Nexus/
[Samsung Galaxy Nexus] Simer03:
I find that when I try to take care of my phones, it ends up damaging somehow, and when I don't try, everything goes smoothly....since I've taken it off, I haven't done any damage (knock on wood)

sent from my Nexus Prime
[Samsung Galaxy Nexus] dmmarck:
I hear ya. I put mine in a woman's plush sock too. Because screen protectors are the devil!

Anywho, the screen looks amazing and I can't wait for 18.3
[Samsung Galaxy Nexus] franciscofranco:
Yep, the interface still needs some polishes =)
[Samsung Galaxy Nexus] cgollner:
I wanted to say :

This version is the best I've ever used! The battery life is so amazing; So smooth...

Thank you all for giving a try to my Benchmark & Tuning app. The Galaxy Nexus with franco.kernel is the device with the most scores on my database for now. 405 scores at the moment!

Keep using it ! :D

---------- Post added at 12:49 AM ---------- Previous post was at 12:46 AM ----------

407 now :D
[Samsung Galaxy Nexus] franciscofranco:
Yes, absolutely, I alone flooded your database with scores. Since I lend you my GN, did you find any problems with it like the ones reported on this thread?
[Samsung Galaxy Nexus] cgollner:
To be honest. I din't find a single problem! Sorry about that :p
[Samsung Galaxy Nexus] franciscofranco:
Now people will believe when I say that my GN never have problems, which makes it pretty hard to fix bugs that I can't reproduce ;)
[Samsung Galaxy Nexus] franciscofranco:
Nightly #18.3 is out.
[Samsung Galaxy Nexus] dmmarck:
Just flashed along with a clean cache/dalvik wipe. Thanks!
[Samsung Galaxy Nexus] cgollner:
Do you even stop for a minute? :D
[Samsung Galaxy Nexus] franciscofranco:
Yes, when my girlfriend says I pay more attention to Android than I do to her ;)
[Samsung Galaxy Nexus] dmmarck:
That's when you give her your old one and tell her to have a blast.

Worked for mine. ;)
[Samsung Galaxy Nexus] cgollner:
Haha, wouldn't work for mine!!
[Samsung Galaxy Nexus] Vangelis13:
+ 1. Imagine a non tech-savvy girl going from a samsung 50€ flip phone to the nexus one. Oh man, the peace & quiet.. :p

Thank you F!
[Samsung Galaxy Nexus] Gahh Its Lee:
Running the new one. Its really smooth no more 1650 but that's fine.
[Samsung Galaxy Nexus] dmmarck:
Or imagine them discovering that you can do things like Sudoku or Crosswords? With their FINGERTIPS? Score!

Same here. Running default settings (700-1200) w/ HP enabled here.
[Samsung Galaxy Nexus] raniosman:
How about an Android girlfriend? :P

Thanks!

Is it recommended to wipe cache/delvic before or after kernel install?
[Samsung Galaxy Nexus] cgollner:
Or imagine them discovering that you can change screen colors with franco.Kernel update app?? Maybe adding a little pink to the screen??
[Samsung Galaxy Nexus] dmmarck:
If I wake up to a pink Nexus, I'm blaming you, Franco, and her--in that order lol.

It was bad enough when it was overly blue, but pink?! Good Lord!

I guess I can be thankful the multipliers don't set on boot . . . yet. ;)

---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------

I wipe both prior to install.
[Samsung Galaxy Nexus] Craiq:
my desktop is gone after flashing 18.3 :/

wiped cache and dalvik

using apex1.0 rom

edit: setupcpu dont run any more

will try restore and flash again
[Samsung Galaxy Nexus] dmmarck:
What? How? Try going to recovery, wiping again, flashing again. Or turn off, do a batt pull?
[Samsung Galaxy Nexus] Craiq:
restore is running ;)

when the problems arent gone after reflash i wll try this.
[Samsung Galaxy Nexus] slayp00n:
My point is the issues are not in the CPU itself they are in the frequency generator and its ability to lock properly. The chip itself is not overclocked at 1.5ghz
[Samsung Galaxy Nexus] 15israellai:
Sorry guys, it's been a few times - my phone sleeps and couldn't wake up. It's as if it were on, with pulse notification and stuff, but doesn't respond to the buttons. Is this the SOD you're all talking about?

Blazing on my Galaxy Nexus using xda premium app
[Samsung Galaxy Nexus] GchildT:
If I select any max clock over 1500MHz phone instantly freezes then reboots. 1500 Runs fine though.

Swyped from my Galaxy Nexus
[Samsung Galaxy Nexus] t-rip:
Same issue here.
[Samsung Galaxy Nexus] dmmarck:
Franco says in the Change Log (and elsewhere) that 1.6 and 1.65 won't work for a majority (90%) of users.

I presume that's what y'all are experiencing.
[Samsung Galaxy Nexus] slayp00n:
Is there a link to download older versions? Thanks
[Samsung Galaxy Nexus] dmmarck:
Search through this thread; if there is one, it's in here somewhere.
[Samsung Galaxy Nexus] nory82688:
yeah, same thing i was thinking, id like to go back to 18.2 . ive checked the forums and i cant find it anywhere. if anyone can post it i would greatly appreciate it. thanks

nothing but constant reboots with 18.3, everything was fine with 18.2 @ 1.5 , 1.6 , and 1.65.

edit: found it
[Samsung Galaxy Nexus] GchildT:
Yeah, cause he re-enabled SmartReflex 1.5. Those higher clocks worked fine before.

Swyped from my Galaxy Nexus
[Samsung Galaxy Nexus] heo_con184:
Build #18.2

http://db.tt/bU6Bl4so
[Samsung Galaxy Nexus] franciscofranco:
Although #18.2 can give you extra OC capabilities it will be a lot less stable and probably cause some temperature risings, which we don't want.
[Samsung Galaxy Nexus] twitceh:
Liking the 18.3! Works without any issues so far.

I missed the Gazelle profiles from 18.1, so happy you brought it back. Battery life sucks during 18.2, so I'll give my feedback regarding this version soon. :)
[Samsung Galaxy Nexus] slayp00n:
Link by chance? Hard to find on a phone
[Samsung Galaxy Nexus] nory82688:
thanks bud, i did end up finding it about 30 pages back or so, but thank you for posting and trying to help me out. i hit that thanks for ya!
[Samsung Galaxy Nexus] rahan95:
Can't even boot any more since I flashed 18.3, boot loop at the ICS screen
[Samsung Galaxy Nexus] Vangelis13:
People should really bookmark http://www.world-of-nexus.com/download-section. It's T H E one stop shop for all older versions of pretty much everything for our (gsm) nexus; kernels, radios, roms, etc.
[Samsung Galaxy Nexus] dmmarck:
I've already noticed a temp difference with 18.3. Thank the Lord, 18.2--for some reason--made my phone run like a cat in heat.

---------- Post added at 10:05 PM ---------- Previous post was at 10:05 PM ----------

That's an absolute Godsend. TY!

---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------

Do a full wipe/restore, or wipe cache/dalvik and try again.
[Samsung Galaxy Nexus] Armani G:
Can't go past 1500ghz on 18.3 reboots the phone now..

On 18.2 I was able to go to 1650ghz ondemand
[Samsung Galaxy Nexus] dmmarck:
Did you read the changelog? 1.6/1.65 won't work on a majority of the devices now. It's like the first paragraph or so. Keep it at 1.5 or below for safety reasons.
[Samsung Galaxy Nexus] Vangelis13:
Ouch, everything froze at 1500 as well, had to pull battery.. Conservative, 700 min. Bummer
[Samsung Galaxy Nexus] dmmarck:
I've been fine on 1500 for about an hour or so. What settings were you running?
[Samsung Galaxy Nexus] rahan95:
Cant I just flash 18.2 with fastboot ?
[Samsung Galaxy Nexus] Vangelis13:
Hm. I edited my previous post. It was on min 700 / Conservative when it froze. Now on min 350 / Conservative it runs ok for the last few minutes..

Franco, what is the status of affairs with that, should we be on 350 or stick to 700 as you always advised (in order to reach sleep faster etc)? Or is it just my phone that is weird..?
[Samsung Galaxy Nexus] dmmarck:
Presumably, but I'm not fastboot expert so I'd defer to those who are. Can you get into regular ole CWM?

---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------

Could be your device. I'm on 700-1500, conservative, with hot plug enabled. So far so good. Of course, each is different and I've hardly been "power using" in the past hour or so.
[Samsung Galaxy Nexus] rahan95:
I can but with MTP I have no way to mount usb storage and copy the file. I'll adb push it if fastboot fails
[Samsung Galaxy Nexus] dmmarck:
Hmmm. And your phone won't get past the boot screen, right? You could try doing a wipe/restore, trying to get past the boot screen and going from there.
[Samsung Galaxy Nexus] yyz71:
Man 18.3 gave me problems to get past the Google logo!! And that's with auto flash.. and when it did boot up :) copied 18.2 back to my phone I'll stick with that...
[Samsung Galaxy Nexus] rahan95:
Lucky you could boot at all =)

fastboot flash worked, well so it said, but boot image is now messed up. Can't boot on anything but bootloader

And, stupid of me, I'm so used to auto flashing with Franco's app I didn't make a back up this time =(
[Samsung Galaxy Nexus] kimboinatl:
+1. 1.65 is smooth like butta on my phone. Super impressed.
[Samsung Galaxy Nexus] neverhappy:
downloaded 18.3 thru Franco app and hit the kernel auto-flash and went into boot loop for the first time since I got this phone.

pulled battery and tried to reboot. This time it got to the home screen froze and rebooted to home screen and froze and rebooted....

Puled battery went into CWM, wiped, and manually installed .zip from download folder. Yup, boot loop again.

Went back to recovery, loaded 18.2 and all was fine.

Like a fly heading into a bug zapper, I re-downloaded 18.3.zip and tried to manually install again.... boot loop. I'm back at 18.2 and all is fine again.

I think I went thru all possible bad things people sometimes report all within a 20 minute period of time tonight. lol.
[Samsung Galaxy Nexus] dmmarck:
Try not auto flashing. It seems like a lot of problems are coming from that. Download the zip do your wipes and then flash in CWM.
[Samsung Galaxy Nexus] franciscofranco:
Strange reports. None of my testers complained and I always give them boot.imgs to fastboot. Maybe you guys had 1,6ghz or 1,65ghz set on boot then flashed 18.3 and boom it freezes.
[Samsung Galaxy Nexus] neverhappy:
I tried all ways and 18.3 would not work. The second I loaded 18.2, it worked fine. Did this multiple times. Oh well, not complaining. Everything can not be perfect all the time.

I'm no expert, but I was wondering if the rom, set cpu... one of these might be trying to set 1.6Ghz when booting and that crashes it with 18.3?
[Samsung Galaxy Nexus] dmmarck:
Wow. Talk about intense. Lol
[Samsung Galaxy Nexus] neverhappy:
Wow,

So from 18.2 I set the max freq from 1.6Ghz to 1200 first and then I auto flashed 18.3 from the Franco app and all is working fine. Hmmm. Previously I was set to max 1.6GHz in 18.2 and I just went right to 18.3 auto flash with boot loops soon to follow. Now it is fine. Everyone should check that no other programs are hijacking the freq setting (including rom) before you flash 18.3.
[Samsung Galaxy Nexus] franciscofranco:
It would be much easy on my if people actually read the changelog. I specifically stated that > 1,5ghz wouldn't probably work anymore because I had to enable Smartreflex 1.5 again for stability issues. Obviously users got stuck at boot because I'm 99,9% sure those users had 1,6ghz or 1,65ghz set on boot, which would cause the bootloop. It's really really hard on me seeing that those issues are easily avoided if users actually READ the changelog and prepared their devices accordingly before updating the kernel. Now that I was going to sleep I have to rebuild the kernel without >1,5ghz frequencies support to prevent more bootloops and release it within the hour.