yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] reaper000:
Dirty flashed onto Omni 4.4.3 without incident. Thanks devs!
[Samsung Galaxy S Relay 4G] wuziq:
not a huge deal, and this existed in 4.4.3, but if you're in the phone app and you want to see the dialer keypad, you have to press the dialer button, then go back, then press it again in order to see it.
[Samsung Galaxy S Relay 4G] Magamo:
New release available in the OP -- 4.4.4_0002

I've disabled Touchboost for this build

We've also fixed some instability relating to Superuser
[Samsung Galaxy S Relay 4G] seidler2547:
Yesh that is annoying me every day :)
[Samsung Galaxy S Relay 4G] Magamo:
On the device side, we don't touch the dialer. Please file a bug report with Omnirom about it. It's an upstream bug.
[Samsung Galaxy S Relay 4G] wuziq:
with the 0002 and 0001 builds, apollo plays music better when screen is off.. i occasionally need to turn screen on.. but a new thing i've noticed is that sometimes, when advancing to the next track, it will skip the track immediately after starting it. has anyone else noticed this?
[Samsung Galaxy S Relay 4G] Magamo:
New build posted in the OP.

Some changes:

We've begun blocking some wakelocks and alarms from google apps which have been a cause of battery drain -- This is configurable in build.prop

Touchboost returns. (If there is demand, I can create a flashable kernel without this.)

Fixes for Band selection in the 'secret menu'.
[Samsung Galaxy S Relay 4G] HippoMan:
Thank you! Which props control the blocking of these wakelocks?

.​
[Samsung Galaxy S Relay 4G] Magamo:
From the commit message for this patch:

Alarms and Wakelocks are blocked based on lists provided via system properties.

persist.toad.alarm.block

persist.toad.wakelock.block

We hardcode a default set into frameworks equivalent to setting properties as follows;

persist.toad.alarm.block=com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR,com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLLECTION_TRIGGER

persist.toad.wakelock.block=com.google.android.gms/NlpWakeLock,com.google.android.gms/NlpCollectorWakeLock,com.google.android.gms/SystemUpdateService

This list can be customized by adding lines to /system/build.prop.

The values to be added can be found via "logcat | grep ToadPiss"

The list is a comma-separated string with no spaces or other punctuation added. If you use a custom string, it must contain the default values as well as new custom values, or only the new values will be retained.
[Samsung Galaxy S Relay 4G] HippoMan:
Oh, I'm sorry for having missed that comment. Thank you.

.​
[Samsung Galaxy S Relay 4G] Bobby Tables:
I just flashed the 0003 update. So far, so good, but (and this was a problem with 0002 as well) T-Mobile Visual Voicemail still acts up. When playing a message, it will attempt to play past the end, and I hear static as it trys to play random data.

My quick camera tests have worked out OK (a snapshot and a short video).
[Samsung Galaxy S Relay 4G] falle21:
I have not working GPS and location, and google services stops, I gonna try later with other gapps, I guess its something relationed with that, everything else its working fine, thanks for your work
[Samsung Galaxy S Relay 4G] Magamo:
Try a battery pull as well as flashing the recommended gapps. I can assure you that GPS works fine in this release.
[Samsung Galaxy S Relay 4G] falle21:
Was something about one xposed module, everything works fine, except NFC that I can't turn off, always remain on no matter what I do.

The ROM works really good
[Samsung Galaxy S Relay 4G] Magamo:
I cannot replicate the error you're getting with NFC. Can you tell me anything more about that issue?
[Samsung Galaxy S Relay 4G] falle21:
Don't worry, I do a full wipe and reflash and works fine, I have a couple of xposed modules in conflict with this ROM, anyway, I flash all again without this modules and works fine, thanks anyway for your response
[Samsung Galaxy S Relay 4G] sorgo:
I've notices on 0003 build that the music players either makes audio distored (nPlayer, poweramp - I remember fixing this by setting a threshold for interactive governor, but it's already at 90) or the other players act also strange (apollo and rocketplayer) they stop the playback at the end of a track and I have to forward manually or skip one track.

Anyone has a working fix for this?

Thanks
[Samsung Galaxy S Relay 4G] falle21:
I use google play music and v4a and works fine
[Samsung Galaxy S Relay 4G] sorgo:
Thanks. I tried Google play Music, but got glitchy playback too. I'll have to try to uninstall everything that could cause this lag and test it over and over again.
[Samsung Galaxy S Relay 4G] rpimonitrbtch:
Oh, it's been since before 0002. (I believe I've been getting this since the first KitKat releases, both the Fat and Omni-toads.) And it's not just VV reading past the end of the message, it happens when I pause the message too. From what I can tell, it's anytime certain apps, including VV, ceases playing audio through the earpiece or speakerphone, it blasts static for a few seconds, then silence until I reboot. I've had a SIP client app do that to me as well (CSipSimple), but most other stuff seems to work fine.

I've been meaning to post a logcat, but I'm a bad person... http://pastebin.com/uvByYz32
[Samsung Galaxy S Relay 4G] seidler2547:
Ah Google wakelocks. I've been using xposed with the unbounce module up to now which made the battery life quite usable.

Can you remind me again what touchboost is? I couldn't find a useful site to explain it...

Thanks,

Stefan
[Samsung Galaxy S Relay 4G] kiboy6:
For me too, the ONLY problem I have with this ROM is occasional audio glitches. As well as the playback stopping sometimes at the end of each track, I also experience random periods of glitchy stutter (say for 10 to 20 seconds every five minutes). Any chance of an update with audio playback issues fixed?

Thanks so much for the awesome ROM in any case :)
[Samsung Galaxy S Relay 4G] qqisa:
reboots and super hot

hi I've been using omnitoad for a while. i switched from liquid because i feel its more fluid. However I have 3 issues to report:

recently i've been experiencing random reboots. they were not very often and i didn't care for it too much. However yesterday it suddenly rebooted during a bussiness call and I couldn't explain to my accountant that I had flashed this awesome ROM which has some bugs.

Unrelated to the reebot issue, when I play games like clash of clans, the devide gets extremely hot in just a couple of minutes. When I say extremely hot I mean "worried about something melting inside" hot or "worried about device bending" hot or even worse "spontaneous combustion" hot.

Short phone calls works great. But after around 2 minutes of talking, the glide starts getting a little hot and the sound starts disstortioning and cutted. It is not an external signal problem coause other phones work normally.

Is anybody experiencing similar isuues? Do you know how can i fix em?

thankyou
[Samsung Galaxy S Relay 4G] wuziq:
i do get random reboots but they're uncommon. it has never reboot during a call for me, though.

i don't play games on the phone so i can't say much about how hot it gets during gaming. the hottest it's gotten for me is when i'm using google navigation and playing music and using bluetooth, but it's not "melting" hot.

i may have experienced the same thing you have with phone calls, where the sound becomes distorted and cuts. for me the sound cuts in and out rapidly, like a stuttering noise. it seems to be random, though, and not related to the length of the call. i've had long phone calls where it didn't happen; and i've had calls where it happens within moments of the call starting. i just remember it happened to me while talking with recruiters, which was mildly stressful, lol.

---------- Post added at 02:53 PM ---------- Previous post was at 02:49 PM ----------

the "workaround" for playback stopping at the end of a track is to simply turn the screen on. or just wait for like 1-2 minutes and eventually playback will continue.

you might notice another issue, though, where the next track begins, but is then automagically skipped.
[Samsung Galaxy S Relay 4G] Bobby Tables:
I got sick of plugging into the headphone jack on my phones when I want to use them in the car, so I got a Bluetooth hands-free kit. That's when I found that adding Bluetooth on top of the music and navigation was a bad idea. The phone heats up to the point where it not only stops charging the battery, but doesn't take power from the charger at all. I've had to go back to my stock LG F3 for in-car use.

Even without Bluetooth I've sometimes had trouble with navigation (certain versions of Google Maps seemed to be worse than the most recent ones).

(rant)I wish Google could leave well enough alone with Maps. New features may be spiffy, but how about concentrating on things like keeping memory usage down and not crashing, and not redoing the user interface every six months?(/rant)
[Samsung Galaxy S Relay 4G] yohan4ws:
[MENTION=4866875]qqisa[/MENTION] [MENTION=5432108]Bobby Tables[/MENTION]

I experienced the issues with the phone nearly overheating when OmniRom was first distributed, I experienced huge battery drain over the prior CM10 builds and experienced the overheating when playing Clash of Clans. Prior, I would be able to play clash for hours with the charger plugged in.

I also experienced the phone locking up completely to the point I couldn't answer a call when using GPS, my guess - the phone clocks itself down when it hits a certain temperature.

I ended up installing the initial build of SlimKat. Everything works fine, and when installing Xposed +greenify +media scanner optimizer I'm no longer worried about having sufficient battery. The phone still does lag and slow down some with bluetooth and GPS on in my vehicle (even without playing music) but it is at least usable. Waze doesn't seem to take as much CPU so the phone doesn't heat up so much.

I liked OmniRom and appreciated the development, but for the reasons above I was fearful of the heat destroying my phone. I tried LiquidSmooth and had issues with jitter and bad battery life as well. Only downside to SlimKat which may be a deal breaker is the Camera washes out images when set to Auto ISO. (I also prefer the earlier version of kit kat that doesnt make every message pop up in the middle of my screen... which is especially useful when I have my phone open in front of clients and my GF/Friends text me dirty friday memes).

If you want to stick w/ Omni, I say clock it down or try a diff. governer... I've been wondering if using Carbon or prior build of LiquidSmooth or even CM11 would resolve the issue with camera and with xposed modules retain battery life, but that's a conversation for a different thread.
[Samsung Galaxy S Relay 4G] qwerty3656:
DELETE
[Samsung Galaxy S Relay 4G] rpimonitrbtch:
Hoping to get some guidance on building this rom. I'm trying to build with backported Stagefright patches, but I'm pretty sure I'm doing something wrong. I init'd the omnirom sources, grabbed a local manifest from the teamapexq repo (android-4.4.xml, not sure that's the right one), removed system/extras/su/ (was conflicting with CWM SU), built and installed, but wound up without a working root. Worried there might be other bits missing too.

Should I be using the dobuild script instead? If so, what would be the proper values for the various environment variables? Particularly $GERRIT_CHANGES, $CHERRIES, $PATCHES, and $REVERTS.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] nbusin:
Hi.

I have a German MDA Pro. I would like to change the language of the OS. Where Would I be able to download a Windows Mobile 2005 English edition.

Any Help or any advice would be welcome.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] madkat:
From the FTP site: ftp://xda:xda@ftp.xda-developers.com

look in Universal, ROMs (or suchlike)

You may need to 'steal' the data from the temp folder if it runs and quits with an error, and use this executable instead.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] BBBenj:
Hello...

I'm new here so... Please don't be too rude with me if I missed something :oops:

But, when I clicked on the ftp link, I got a message telling me (sorry for the translation from french...) that I can't connect to ftp server....

And I need a french (you guessed, don't you!!) version of Win Mobile 2005...

Thanks a lot & best regards...

Benjamin
[JASJAR, XDA Exec, MDA Pro Software Upgrading] bambacik:
Are you looking for this ROM: ftp://xda:xda@ftp.xda-developers.co...Updates/UNI_QTEK_13097_186_10900_FRE_Ship.exe
[JASJAR, XDA Exec, MDA Pro Software Upgrading] BBBenj:
Hello!

Thanks a lot!

I succeeded in downloading this archive, but I get a message telling me that my device (O2 XDAII) is NOT compatible with this upgrade...

:cry: :cry: :cry:

Do you have any idea???

Thanks a lot :wink:
[JASJAR, XDA Exec, MDA Pro Software Upgrading] bambacik:
O2 XDA II? The ROM is for HTC Universal (XDA Exec) not for XDA II. Try searching in the Himalaya or Alpine forum.
[JASJAR, XDA Exec, MDA Pro Software Upgrading] BBBenj:
Hello!

Oups! I'm sorry! When I said I'm a beginner here :oops: :oops: :oops:

Anyway, thanks for your help!

Benjamin
[JASJAR, XDA Exec, MDA Pro Software Upgrading] NotBroken:
OK, need some help too

Got a My Guide 5500 XL from typhoon

specs:

400 Mhz Intel XScale PXA 255 Processor

Rom Version: V3.03.31 FRA

Version OS: PocketPC 2003

Boot Version: 040127150519

I would like to change this French version to a English one or even (if possible upgrade it to 2005)

I don't know wether the correct file is on your ftp, can't figure it out.

Can someone help me pls?
[JASJAR, XDA Exec, MDA Pro Software Upgrading] madkat:
A what from who?

In these forums, "Typhoon" refers to a model of phone made by a Taiwanese manufacturer called "HTC". If you're searching for ROM upgrades for devices made by a manufacturer called Typhoon I'm afraid you won't have any luck here.
[Galaxy S II Q&A, Help & Troubleshooting] ll_zalim_ll:
Stuck on Samsung Logo ... i have flashed with odin but same problem Help Please
[Galaxy Tab 3 7.0 Android Development] Phil3759:
Main thread + features + install instructions + dev support

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

PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM

It is a well proven recovery for many phones

It also adds a full touch interface a completely configurable GUI

Please give your feedback, what works, and any bug you could encounter

Read the features, and check if you are missing something

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut

Download links

Last version can be found here:

credits to [MENTION=3034891]gr8nole[/MENTION] and [MENTION=4021423]ketut.kumajaya[/MENTION]
[Galaxy Tab 3 7.0 Android Development] Ripshock:
Omg thank you so much and for [MENTION=3034891]gr8nole[/MENTION] and [MENTION=4021423]ketut.kumajaya[/MENTION] for helping

Sent from my SM-T210(R)ocketTab 3.1 $up€R_f@$T
[Galaxy Tab 3 7.0 Android Development] safariking:
Thank you so much phil
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Thank you very much for making this for us.

I flashed it and noticed that the external sd does not mount and we can not use it. I repacked your version with my fstab and external sd works correctly.
[Galaxy Tab 3 7.0 Android Development] Phil3759:
it seems your device tree is lacking needed vold code
[Galaxy Tab 3 7.0 Android Development] Phil3759:
I am reverting the fstab changes as a quick fix

Also, does mount usb storage work?
[Galaxy Tab 3 7.0 Android Development] gr8nole:
We have never had working usb storage in recovery on this device.

I will look into what is needed for the vold.

Thank you again.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] Phil3759:
ok

I re-uploaded to goo.im with your recovery.fstab

However, it could be a few advanced functions won't work properly as I am not sure I implemented external_sd support properly everywhere
[Galaxy Tab 3 7.0 Android Development] gr8nole:
Thank you, it seems to be working correctly now.

Does this background look correct?

View attachment 2587308

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] Phil3759:
sure no

I used a portrait background

Seems I need a landscape

You really prefer it flipped?

You'll get more menus in portrait
[Galaxy Tab 3 7.0 Android Development] gr8nole:
All of our recoveries are in landscape. I believe the 7 in version of the Tab 2 is the same way. I do believe it works best this way.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] Phil3759:
Ok, will fix background
[Galaxy Tab 3 7.0 Android Development] Phil3759:
Uploaading 6.16.2 with fixed background

Do you need an odin version? Dow you have a download or bootloader mode?
[Galaxy Tab 3 7.0 Android Development] gr8nole:
6.16.2 looks much better, thank you.

We do have download mode, so an Odin version would be great.

On a side note, the Reboot to Download option does work.

I don't know how you keep up with so many different devices, but you do a great job.

Sent from my SCH-I605
[Galaxy Tab 3 7.0 Android Development] Phil3759:
I keep up thanks to people like you, porting their devices trees ;)

:good:

I use scripts to build recoveries and repack them

Compiling, repacking and creating zip + tar files classified in upload path for one or 130 devices is just one command line,

Adding a tar release is just:

TAR_MD5_FLASH="yes"

However, it is still a huge impressive job mainly to port device trees, kernel sources, bugs...

the scripts must be maintained too, all the time

Hopefully I will soon be able to only focus on recovery sources and selected devices while devs can build full version at their will
[Galaxy Tab 3 7.0 Android Development] Phil3759:
Uploaded tar.md5

Let me know when you fix your device tree

By the way, recovery doesn't need all the modules

Also, no need to specify kernel sources and use TARGET_PREBUILT_KERNEL flag

Hope you can fix the vold soon too

Use my minivold binary to have exfat support through kernel modules if you compile it again
[Galaxy Tab 3 7.0 Android Development] gr8nole:
I have updated my device source on github to fix vold and kernel. https://github.com/gr8nole/android_device_samsung_lt02wifi

The external sd card is listed as /storage/extSdCard in the device vold.fstab, so I used that and it works. No extra.fstab needed.

I also updated the fstab to use the "by name" convention for all other mount points. The usb devices will probably never work for us because the device vold.fstab refers to mount points in "omap" directories which we do not even have.

I commented out the portions pertaining to prebuilt kernel, so it compiles (and uses) the kernel from source now.

I did compile a non-touch version this morning with these changes and everything seems to work great.

Thank you.
[Galaxy Tab 3 7.0 Android Development] Phil3759:
did you try:

extra.fstab is to add blk_device2 support, that is ability to format external storage to ext2/ext3 and to partition it

Also, it makes it possible to better get partition size for some devices
[Galaxy Tab 3 7.0 Android Development] gr8nole:
It does work with "sdcard1" as well. I chose to leave it as extSdCard because that is how it is named in our stock roms. Please use whichever works best for you.

Thanks for the info about the extra.fstab. :good:
[Galaxy Tab 3 7.0 Android Development] Phil3759:
recovery should use sdcard1 to avoid potential issues due to mal-formatted install scripts

That's the new CWM convention

I will go with sdcard1

Thank you again

Probably because you did not use auto as mount point then
[HTC One X] knuddeknurft:
Hello Members, First of all I just want to say that I tried almost everything and searched a lot on the Xda forums!

It started whit the new Venom 4.0.7. update. Never had any problems whit the Venom OTA updates but last night when I tried to install it, the little green andriod in recovery was just laying flat on it's back whit a red (!) above it.

Tried to install it manually but the same results. Soon after that my HOX began to have trouble with booting up and now it doesn't do anything. The only thing that it does is when I hook it up on my laptop that it bleeps and says that something is conected to the laptop and later in device manager I found out it says "APX".

No back lights from the screen or soft buttons, no red or green led.. Just nothing.

Now I've tried to install new drivers and that does somthing, the laptop recognizes its a phone but that's it. (no longer "APX") It says "NVIDEA USB Boot-recovery diver for mobile devices".

No I'm stuck :P Someone with the same problem and solved it? Or has anyone an idea how to fix it?

Hope to hear something soon from u guys!
[HTC One X] Mr Hofs:
APX is a dead hox, hardware failure. A new mainboard is the solution !
[HTC One X] knuddeknurft:
Maybe it's smart to say that every time (after the new update) it became harder and harder to enter recovery mode.. black screen took longer and longer before recovery came up.
[HTC One X] knuddeknurft:
Oke.. But how? From one second into the other?
[HTC One X] Mr Hofs:
All things break sometime ! Buy a brand new car and it can be back to the garage the next day....or in 10 years.....nobody can tell
[HTC One X] knuddeknurft:
Car Therms always work :P Thanks. So there's absolutely nothing I can do for my HOX anymore? (other than sending it to HTC for a new main board)
[HTC One X] Mr Hofs:
Nah not really, and all the phones that got out of apx died in the end again. It's all temporarily.

Some got it out of apx by rebooting it like 100 times and pressing button combos....to me it's pressing luck ! And it will come back 100%

So it's safe to say it's a dead end. Sorry
[HTC One X] knuddeknurft:
Thanks for the quick and strait (no bullsh*t) answers. Back to the old but trusty Nokia 5210 :laugh:
[Omni Features Development] unh0ly1:
Currently the "Settings" button, which you can find when pressing "menu", is only able to open launcher specific settings.

I think it would be great, if we would be able to choose which settings to be opened, the system or the launcher settings.

In previous versions of android opening the system settings was default behaviour so I am wondering every time when the launcher settings come up :laugh:

What do you think?

cheers, unh0ly1
[Omni Features Development] curl66:
+1
[Omni Features Development] UtkarshGupta:
We already have this option. But your gapps must be replacing it with Google's launcher which we can't control.

You can ask in your gapps's thread how not to replace aosp launcher with Google launcher.
[Omni Features Development] unh0ly1:
Thanks for your reply. I will check this tomorrow :eek: Me and a friend (both omni users on galaxys2 intl version) had the same problem, so I was thinking this was the state of art. Tell you more tomorrow :good:
[Omni Features Development] unh0ly1:
Okay, I double checked now. When I press "Menu" > Settings, I get what you see on the image attached. This is, because its not tranalated, a part of omni, isnt it? Is there a way to restore the androod default behaviour?

Cheers, unh0ly1
[Nexus 5 Q&A, Help & Troubleshooting] lipenosis:
Hello, I created a bootanimation for my future nexus rom 5 hammer.

but malgrés all, I can not do take into account the device restarts repeatedly.

you can have a look at my bootanimation see in the desc.txt.

Thank you so much for help.

https://mega.co.nz/#!uZkTkKja!0-jy767MVZnR0E2NC0BZUQ6AZt1a0T50NVlPtFVOnwc

desc.txt

1080 289 7
p 0 0 part0

total 5 png
[Nexus 5 Q&A, Help & Troubleshooting] lipenosis:
Up

please :)
[Nexus 5 Q&A, Help & Troubleshooting] makers_mark:
Have you tried to change your frame rate to an even number like 8?

How about the vertical resolution. Have you tried changing it to 290 or 288?
[Nexus 5 Q&A, Help & Troubleshooting] lipenosis:
I served as a model for doing so,

a model that works.

I tried to change a multiple recovery values ​​but has the strength to do and undo, I'm tired and going around in circles: (

here is the model that works it

https://mega.co.nz/#!GMtn1ZQD!dBdhiToBfFWY24TSoqxQXhYuihPXqH2J8NydtvqszT0

is that a bootanimation must not have less color, it can be any restrictions?

I'm lost ....