yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] Magamo:
This appears to be an upstream UI glitch. The processor respects the settings you choose, even after you exit the ui and go back in (and see that the ui has reset to 1134) I'd file a bug with CM about it.
[Samsung Galaxy S Relay 4G] :
This is not an upstream CM glitch. In kernel mpdecision works by directly altering the kernel frequencies. 1134 is the touch boost floor frequency. The performance settings will read this value and incorrectly report it as the minimum. Which it is. At the moment.
[Samsung Galaxy S Relay 4G] Magamo:
Thanks for the clarification, Nard. I was merely watching my numbers while in the interactive governor, and definitely seeing it dip below 1134 when I wasn't touching the screen.

After discussing this with the other devs, this is mpdecision and touchboost. Our CPU settings are getting automatically changed in response to system activity. Your cpufreq settings will not be respected. This is part of how battery usage is optimized. Performance will be available when the system is in use, and the CPU will be throttled back quickly when it is not.
[Samsung Galaxy S Relay 4G] dillalade:
Thanks for the details, very helpful.

Am I right in thinking setting Governor type is respected?
[Samsung Galaxy S Relay 4G] burritoboy9984:
Running the latest with the gapps from the op, and I'm not getting as good of battery life as I was with the latest stock rom. Anyone have suggestions? Or having the same issue? I can't make it through a full day right now, and I don't use my phone that much either.

Thanks in advance!

-Erik
[Samsung Galaxy S Relay 4G] dillalade:
Try the latest gapps from CM's site http://wiki.cyanogenmod.org/w/Google_Apps

I'm verrrrry pleasantly surprised how well this ROM is on battery. Specifically when the phone is idle/asleep.

It is literally dropping ~1% per hour during sleep.

Currently at 15hour uptime with 46% remaining:

1.5hour of call usage

1.5hour of screentime

~1.5hour Bluetooth connected in car

Looks freakin' fantastic to me.

I did try this rom flashed on top of some previous cm11 setup I had, and was then receiving considerably poor battery performance and a Very hot device.

But upon a full wipe install, I can't really complain at all about battery performance & the device is as cold as ice too :D

:thumbup:

*********************************

If there is 1 gripe I have noticed with the recent CM11 builds, is that SOMETIMES when sliding the keyboard out - the phone/screen freezes and is deemed unresponsive, hence forced to long press power (to power down.)

[Keyboard nor front facing navigation touch keys are unresponsive, as is power button to sleep action. The screen dims down which is the only response I receive from the device.]

This just happened to me now on this Hypnotoad release.

Anyone else experienced this, is it known?

*********************************
[Samsung Galaxy S Relay 4G] :
I am on the nightly from the 27th of last month and had 3-4 instances of lockscreen, homescreen freezes. Ussually if I slide the keyboard in and out while hitting the power button to put it to sleep.

EDIT: I updated to the newest release given by OP, I will report back on findings if I still encounter freezing problem with keyboard and sleep button.
[Samsung Galaxy S Relay 4G] Magamo:
These are known issues that effect both releases of HypnoToad and CM. It's a long standing issue that we've been working to fix for some time now. It has to do with (I believe) bugs in one of the graphics drivers. My usual work around is to unlock my phone before sliding out the keyboard. A little behavioural modification goes a long way with this one.
[Samsung Galaxy S Relay 4G] :
S

Alright, I had a suspicion it was probably similar to what you described. While I am on it, I want to say thank you to the Apex team for an awesome release, I thought my phone was fast, now it is super charged with speed. I think it was a great decision to mod CM and tailor it to this device. For what is considered an old phone now this device is awesome.

I guess here is as good place anywhere, does the team accept donations, I dont got a lot but every bit helps PM details if a team member sees this. Also it was mentioned above me, but the gapps download in OP is outdated, I have tested CM latest upload and everything works well.
[Samsung Galaxy S Relay 4G] Magamo:
After running some further tests of the latest gapps, I'm certifying it and tossing it in the OP.

https://itvends.com/gapps/gapps-kk-20140105-signed.zip

Some benefits aside from what others have posted... It doesn't crash all over the place using ART. Smaller download size, and properly updated for Android 4.4.2
[Samsung Galaxy S Relay 4G] dillalade:
Nice. Will remember that.

Though I do receive these freezes during wake/normal use, not specifically from device unlock/wake up per say :)
[Samsung Galaxy S Relay 4G] Magamo:
As always, logs will be key in diagnosing such things, especially since we (the developers) haven't seen these sorts of 'normal use' issues.
[Samsung Galaxy S Relay 4G] Magamo:
TeamApexQ is proud to release a new version of HypnoToad: 4.4.2_0002

https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/HypnoToad-4.4.2_0002-apexqtmo.zip

What's new:

WiFi Direct

Fading notification LED
[Samsung Galaxy S Relay 4G] HippoMan:
Changing bootanimation?

Is there a way to change the bootanimation in this HypnoToad ROM? I tried using the bootanimation switcher in "ROM Toolbox Pro" which has worked for me under other ROM's, but it didn't change anything for HypnoToad.

Any ideas?

Thank you in advance.

.​
[Samsung Galaxy S Relay 4G] Magamo:
Download the source, change the bootanimation.zip, and rebuild.
[Samsung Galaxy S Relay 4G] HippoMan:
Well, if that's the only way to change the bootanimation for this ROM, I guess I'll give it a try when I have the time.

Thank you very much.

.​
[Samsung Galaxy S Relay 4G] :
Wait? You download HYPNOTOAD ROM and ask to get rid of the toad??
[Samsung Galaxy S Relay 4G] HippoMan:
Yeah, I know it's a sacrilege ... but I've always been an iconoclast. :)

.​
[Samsung Galaxy S Relay 4G] :
Now I have a question, I just downloaded last night the previous update, and factory reset and wiped for fresh install. Do I have to wipe my cache again or is this compatible with previous data?
[Samsung Galaxy S Relay 4G] HippoMan:
Since you were running the previous version of HypnoToad, you don't need to wipe anything. I had 0001 running and upgraded to 0002 without wiping anything. It came up fine, and all it did was go through a sequence of updating the state of all the apps during the first boot-up. After that, everything ran fine.

.​
[Samsung Galaxy S Relay 4G] REV3NT3CH:
In terminal emulator run the following commands

su [enter]

mount -ro remount,rw /system [enter] (there is a space between mount and -ro as well as rw and /system)

then go to home and open your root file browser...copy and paste the bootanimation.zip of your choice to /system/media...reboot and profit...i suggest having the hypnotoad boot ani remade to actually fit the whole resolution of the phone...if you guys want ill do it as ive had alot of experience in doing so
[Samsung Galaxy S Relay 4G] HippoMan:
Have you actually tried that with this ROM? I used that method to copy a different, functioning bootanimation.zip into /system/media before I even posted my original question about changing the bootanimation, and it didn't work. In any case, that's exacty what "ROM Toolbox Pro" does when it changes the device's bootanimation.

There appears to be something about the way the bootanimation is handled in this ROM that is different from other ROMs that I have used.

.​
[Samsung Galaxy S Relay 4G] Magamo:
To put this matter to rest: Whatever ROM Toolbox is doing is wrong. You can just push a new bootanimation.zip to /system/media. I just replaced mine (and reverted, because... ALL HAIL!) with the Omni boot animation.
[Samsung Galaxy S Relay 4G] orange808:
Pushing a new boot animation works fine for me as well.

I also reverted back...

Everybody Loves Hypnotoad.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
Again as what magamo stated...is what i stated....I've seen your source with omni ROM..congrats
[Samsung Galaxy S Relay 4G] Magamo:
lbcoder's been working with the Omni source for about a day and a half. We have it booting, but much is still quite broken.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
is your wifi borked? what other issues you guys having...wifi was my first issue that i later resolved on my Carbon Rom beta...my fix isnt posted on the ApexRelay github i created either...i havent committed it yet
[Samsung Galaxy S Relay 4G] Magamo:
Our WiFi in Omni is working fine. This is rapidly getting outside of the discussion for this particular thread.
[Samsung Galaxy S Relay 4G] Guiyoforward:
Hi, this looks great. So i understand this is dirty-flashable over cm10.2.x stable.

However, Do i need to flash the new gapps too?, would dirty flash of those work?

Thanks again!!
[Samsung Galaxy S Relay 4G] Magamo:
Yes. Do flash the new gapps. If you try and run with the Jelly Bean gapps, you will likely have some major problems as there are frameworks that cannot be updated via the Play Store. Once you've upgraded both packages, if any google apps force close on you, just clear data for those particular applications.

This will be the last time I answer this question on this thread -- This thread, as the title and forum section implies is for discussion of the development of this image, and not basic support. Feel free to open a thread on the Q&A forums for those questions.
[Samsung Galaxy S Relay 4G] Guiyoforward:
Understood. I contributed my 0.0000002 cents by creating the following very basic FAQ - the type of questions I kept asking...

http://xdaforums.com/showthread.php?p=50360446

I hope this is useful.

Thanks again for your continuing support to our diehard keyboard phone!
[Samsung Galaxy S Relay 4G] wuziq:
took the plunge and installed this after my phone went to **** after the 4.1.2 OTA.

i did an adb backup, formatted internal storage via windows explorer right-click format, then followed the instructions on the relay 4g CM wiki page, and things went fine. the only confusing part was that i didn't see a blue bar when installing the recovery via heimdall. in recovery i wiped everything, installed the bootloader, the radio, hypnotoad, gapps, and cmaccount. rebooted and things are looking good.

thanks for all y'all's work.

couple questions, possibly not hypnotoad-specific:

- i have google voice with notifications enabled, and i also have voice+ enabled, but i'm still getting all my google-voice-number texts through either the messaging app or hangouts (those are the only two available options in the system settings). i DO get them in google voice, but the messaging app or hangouts swallows them. am i doing something wrong, or is voice+ not doing its thang, or something else? :confused:

- when i click on the google search bar widget and type in an address (e.g., www.xda-developers.com), it does a google search of the address instead of just taking me to the address i typed. if it's possible, how do i make it so that it takes me directly to the site i typed?

- google sound search widget is supposedly installed (according to play store), but i don't see it in the widgets. am i missing something?
[Samsung Galaxy S Relay 4G] terinfire:
HOLY COW, DEVS!

I don't know WHAT you guys are doing, but this is SO much more stable than ANYTHING from the standard CM11 branch. I tried SO hard to crash it over and over and over again -- no luck. The thing is robust and has been up for over 24 hours, without having ANY kernel panics whatsoever.

So, whatever you guys are doing... you're definitely on the right track. So stable!

And as always, an enormous THANK YOU to everyone who has been contributing on building the ROM out.
[Samsung Galaxy S Relay 4G] dillalade:
FYI RE: OTG

My 32gb transcend USB stick is now accessible over OTG. Although my 128gb Kingston USB stick is not acknowledged by the device.

Hence is there a size restriction to OTG mass storage per say.

:thumbup:
[Samsung Galaxy S Relay 4G] HippoMan:
Intermittent hanging during boot.

I have recently installed the 0002 release of this ROM, and sometimes (maybe 20-30 percent of the time), the boot animation hangs during reboot. By this I mean that I get permanently stuck in the boot animation, which continues to "move". When this occurs, I have to shut down the phone and restart. Usually, this second boot attempt succeeds.

This happens with the standard toad animation that comes with the ROM, and I have not attempted to change this boot animation, at all.

I have tried totally wiping and reinstalling this ROM, but the hanging within the boot animation continues to occur 20-30 percent of the time.

This hasn't happened within other ROMs, including the latest cm-11 releases, so I don't believe it has anything to do with my phone's hardware.

Given that this occurs intermittently, I'm guessing that it's the result of some kind of race condition within the startup code.

Has anyone else seen this behavior?

.​
[Samsung Galaxy S Relay 4G] Magamo:
This sounds like cache corruption. Rebooting into recovery and then back to system should fix it. If not, reboot into recovery and clear your cache. This is not an animation issue. It simply means that the boot process isn't completing.
[Samsung Galaxy S Relay 4G] HippoMan:
Thank you very much.

I cleared the cache and then started repeatedly rebooting. Unfortunately, this behavior hasn't changed. After about the 3rd or 4th reboot, I got into the same situation: stuck in the boot animation.

After this failure, I shut down and rebooted, and the device came up. I then tried periodically rebooting some more. Again, the problem recurred after a few more reboots.

I agree that this wouldn't be due to a bootanimation issue, per se. As I mentioned above, I'm guessing that it's due to some kind of race condition in the startup code.

.​
[Samsung Galaxy S Relay 4G] Magamo:
Have you tried looking at a logcat of the situation? Perhaps that would shed a lot more light on the situation. As always, we need the logs in order to fully diagnose problems.
[Samsung Galaxy S Relay 4G] HippoMan:
Thank you, but keep in mind that the logcat logs (/dev/log/main) get reset upon each boot, so the errors during the previous boot failure don't show up. Are there other log files I can look at?

.​
[Samsung Galaxy S Relay 4G] Magamo:
You can always grab a logcat while it is booting, and save that using a file redirect from adb. /proc/last_kmsg may yield something, but likely not, as this does not sound like a kernel issue. Mopre than likely though, you've ended up with a bad flash. You can try a complete format of /data, /system and /cache and reinstall the Image from scratch. No one else has reported this as an issue.
[Samsung Galaxy S Relay 4G] HippoMan:
Thank you.

OK. I'll just try reflashing again from scratch after a full reformat of /data, /system, and /cache, although I originally did that before. I'll also fool around with adb and try to get a file redirect during boot, although I first have to learn how to do that.

Anyway, given that no one else has reported this, I'll just go on the assumption that something is weird on my end, and I'll keep banging away at this.

Later on, I'll report whatever results I come up with.

Thank you again.

.​
[Samsung Galaxy S Relay 4G] dillalade:
Also have noticed something RE: Launcher.

Must be CM upstream stuff, but anyway.

On homescreen when "swiping down" specifically from 'just below' the notification bar - will bring up Launcher settings (similar to pressing Menu button on front face when on homescreen.)

Nothing drastic, I just have a nack for pointing out the less obvious.
[Samsung Galaxy S Relay 4G] HippoMan:
It turns out that my bootanimation.zip was corrupted. When I originally copied it from a working device, something must have failed. I tried with a different bootanimation.zip, and it works fine ... even when using "ROM Toolbox Pro".

I then pulled off the failing bootanimation.zip and did a sum on it and on the original version. The checksums were different, which demonstrates that the copy of the original indeed had failed, somehow.

I apologize to all of you for my error and for the bandwidth, and I thank you all for your suggestions and feedback.

Excelsior!

.​
[Samsung Galaxy S Relay 4G] scopedial:
USB Developer

All Glory to Hypnotoad!

I soft bricked my T699 after trying to install gapps. I did a production re-install and I think that I am good now.

Hypnotoad is back. I think I have more up-to-date gapps to try.

I have a question. Why can't I use adb with Hypnotoad? Where are the developer/usb settings?

Lou

---------- Post added at 01:47 PM ---------- Previous post was at 01:14 PM ----------

I just ran into this same problem. I noticed there is a fix in a later message.

I will be attempting that shortly.

All Glory To Hypnotoad.

;)
[Samsung Galaxy S Relay 4G] Magamo:
This is actually a general Android thing. Google has obfuscated the developer options menu. To access it, repeatedly tap the build number in About Phone.
[Samsung Galaxy S Relay 4G] terinfire:
Hey, I had this EXACT problem as well.

You have a bad flash, since mine does the same thing -- even using the recommended CWM. If you keep having issues, wipe your system (via the advanced options in CWM) and then reinstall Hypnotoad. I also had some issues when my data was there... so I had to nuke my data and then do an advanced restore to bring it back later (after it boot up successfully the first time).

Totally worth the efforts, though.
[Samsung Galaxy S Relay 4G] HippoMan:
Thank you for your reply. I was caught up in other issues for the past day or so, and I forgot to post back here that yes, after a full wipe of everything and a reflash, this problem has gone away for me, just like it did for you.

What's weird in my case is that a few days earlier, I had also done another full wipe and reflash, but the problem didn't go away that time. However, now after the second wipe/reflash, I've been having no issues.

I'll just chalk this up to "randomness". :)

All's well that ends well.

Thank you again!

.​
[Samsung Galaxy S Relay 4G] dillalade:
Tried using wifi direct with my galaxy camera.

Although they both paired and connected to one another I was unable to actually send a file in either direction.

The galaxy camera when selecting 'share' (in gallery for example) would enlist an option 'wifi direct' hence allowing me to 'attempt' a send.

But the phone wouldn't have this option enlisted, hence not allowing me to 'attempt' a send to the camera.

Am I doing something wrong, or is wifi direct not entirely functional.

Thanks in advance

******

Also, wireless & networks settings > Mobile networks > Provider Settings causes a "unfortunately the process android.phone has stopped" whilst attempting to to hide my caller ID.

******
[Samsung Galaxy S Relay 4G] burritoboy9984:
Why the name change? :)
[Samsung Galaxy S Relay 4G] Magamo:
To accomodate this as another 'variant' of HypnoToad, rather than the primary release, as we now have OmniToad (based on OmniROM) as well.
[Samsung Galaxy S Relay 4G] chuckiev79:
Reserved
[Samsung Galaxy S Relay 4G] wedg11383:
Streaming issues.

I have been having persistent audio skips while using bluetooth streaming for months now. Decreasing the go hispeed load helps. Switching the governor did not help.Sometimes disabling mp-decision helps but it is always an issue. It doesn't happen if the screen is on. Only locking the CPU at a higher clock fixes it.

I captured a log this morning of when the issue it occurs. What stood out to me was :

02-28 10:12:26.488 E/ALSADevice(291): available buffers in proxy 40704 has reached high water mark 40000, throw it out

02-28 10:12:26.488 E/AudioHardwareALSA(291): readFromProxy returned an error, mostly a flush or an under run continuing

02-28 10:12:33.826 E/bt-avp (1705): opcode 0

02-28 10:12:36.829 D/ALSADevice(291): standby: handle 0xb72cbba0 h 0x0

02-28 10:12:36.999 D/alsa_ucm(291): snd_use_case_set(): uc_mgr 0xb7299fe8 identifier _verb value Inactive

02-28 10:12:36.999 D/alsa_ucm(291): Set mixer controls for HiFiPROXY Rx enable 0

02-28 10:12:36.999 D/alsa_ucm(291): Setting mixer control: AFE_PCM_RX Audio Mixer MultiMedia1, value: 0

02-28 10:12:36.999 D/alsa_ucm(291): snd_use_case_set(): uc_mgr 0xb7299fe8 identifier _disdev value Handset

02-28 10:12:36.999 D/alsa_ucm(291): disdev: device Handset not enabled, no need to disable

02-28 10:12:36.999 D/alsa_ucm(291): snd_use_case_set(): uc_mgr 0xb7299fe8 identifier _disdev value PROXY Rx

02-28 10:12:36.999 D/alsa_ucm(291): Set mixer controls for PROXY Rx enable 0

02-28 10:12:36.999 D/AudioHardwareALSA(291): suspendPlaybackOnExtOut_l activeUsecase = 1, mRouteAudioToExtOut = 1

02-28 10:12:36.999 D/ALSADevice(291): Writing to mPfdProxy[1].fd 28

02-28 10:12:36.999 E/ALSADevice(291): Error Nothing copied from Proxy

02-28 10:12:36.999 E/AudioHardwareALSA(291): readFromProxy returned an error, mostly a flush or an under run continuing

02-28 10:12:36.999 D/AudioHardwareALSA(291): ExtOut Thread is dying

02-28 10:12:36.999 D/AudioHardwareALSA(291): ExtOut thread killed = 0

02-28 10:12:36.999 I/audio_a2dp_hw(291): suspend_audio_datapath: state 1

02-28 10:12:36.999 E/bt-btif (1705): bta_av_str_stopped:audio_open_cnt=1, p_data 5f0f6a5c

02-28 10:12:36.999 W/bt-btif (1705): bta_dm_rm_cback:1, status:6

02-28 10:12:37.009 W/bt-btif (1705): bta_dm_rm_cback:1, status:6

I wanted to figure this issue out myself but I'm not sure how to proceed. I wonder if someone here can provide insight.

I attached the full log, the issues are towards the end.

Thanks to everyone.
[Samsung Galaxy S Relay 4G] C3POID:
Is FatToad "dead" and "Omni" the new king?

Hail to the HypnoToad

SGH-T699 (Relay 4G) Talk with a little Tapa
[Samsung Galaxy S Relay 4G] orange808:
Same issue here. Flashing back to an official nightly (currently on 3/6) fixed it for me. It is important to mention that I completely removed Apollo and DSP Manager; I use PowerAmp.

From where I'm sitting, the official CM builds are king. The official builds give me the least amount of heartache. I guess it comes down to what you want. Personally, I like to have a rom that isn't drawing much discussion because there isn't a whole lot to complain about. The CM builds are so mature, they just work.
[Samsung Galaxy S Relay 4G] C3POID:
Thanks for your opinion.

SGH-T699 (Relay 4G) Talk with a little Tapa
[Samsung Galaxy S Relay 4G] Magamo:
At the present time, TeamApexQ is not planning on any further releases of FatToad. OmniToad will be our main platform going forward.
[Samsung Galaxy S Relay 4G] Magamo:
Also, to respond to this directly. This was basically the discussion thread for the official CM builds for a long time. Generally all three will benefit from the work that originates out of our development in the Omni trees.

(For those of you who did not know, the official CM builds for the apexqtmo are managed and developed by TeamApexQ as well. We usually end up backporting fixes from OmniToad to it)
[Samsung Galaxy S Relay 4G] HippoMan:
Please forgive the following questions, but I'm a late arrival to the "Toad" world, and these name changes are a bit confusing for me.

What is the difference (if any) between HypnoToad and OmniToad?

If there is a difference, where is the online "home" of OmniToad? An xda search for "OmniToad" didn't return anything.

If there is a difference, will work continue on HypnoToad? Or is OmniToad where all new development is taking place?

Thank you in advance for any clarification.

.​
[Samsung Galaxy S Relay 4G] :
New gapps: http://d-h.st/F0D
[Samsung Galaxy S Relay 4G] Magamo:
New build posted. --

... Link redacted in case of future expiry ...

It's been confirmed. Bluetooth and NFC work.
[Samsung Galaxy S Relay 4G] btack:
Gave it a go today. Looks good. Didn't have WiFi (didn't factory reset) but other than that I rocked it for an hour no other issues.
[Samsung Galaxy S Relay 4G] Magamo:
If you're feeling adventurous with a terminal window. You can just issue:

rm -rf /data/misc/wifi

and not have to do a factory reset to get Wifi.