yashsingh1/xdaforums huggingface dataset:
[HTC One A9] Silver.Shadow:
Owned the decide for almost a month now, haven't faced a lag anywhere in the UI even once. Coming from a E8 which was similar to M8, and never lagged too. Happy with the A9! :)
[HTC One A9] rlvl:
No lag noticed here... and it wasn't laggy when it on the October update either.
[HTC One A9] btort1:
Not even while using goole maps? Even reviewers from android authority or youtube mention the lag SOMETIMES. It's not much but I still notice it
[HTC One A9] techlogik:
Yes, it's laggy at times. The processor is kind of mid-level at best. Might be great for battery life, but compared to the M9, it is a dog and slow IMO. The benchmark numbers prove that. Not so sure about long term use of this thing. Its performance is the weak spot of it.
[HTC One A9] btort1:
I agree, I bought a m8 the other week and wanted to try it out and I believe it's much smoother and faster than this phone. Such a shame
[Verizon Samsung Galaxy Note5] liquidraven:
Anyone here rocking a mophie/zero lemon battery case? Persuade me in buying one please.
[Verizon Samsung Galaxy Note5] JasonJoel:
Yuck. Makes the phone too big.
[Verizon Samsung Galaxy Note5] GuestK00143:
I never used one but read good reviews about them. I would say go for it if you really need the extra juice. I personally don't need it, I get four days between charges so it's not a issue here. I'm not a gamer so mine lasts for me.
[Verizon Samsung Galaxy Note5] animal7296:
How in the world are you and others getting such amazing battery life. I'm happy when I don't have to charge it at least once day. Mind sharing your settings and secrets?

---------- Post added at 10:30 PM ---------- Previous post was at 10:28 PM ----------

Sounds like you've already talked yourself into it so my thoughts are this, go find one in a store and try it out and see if you like the way it feels to you. If you like it buy one.
[Verizon Samsung Galaxy Note5] GuestK00143:
It's more to do with my usage of the phone or lack of. I don't play games, watch movies or play music with my phone. I have other devices that do a much better job for those. My radios are off until I need them and I use greenify paid version. Attached is my block list from package disabler pro.

View attachment 3610527
[Verizon Samsung Galaxy Note5] gerbetta33:
I got my zero lemon case for free by messaging the marketing team on xda and reviewing their unit. It's okay, seems like in regular use it only gets about a 60% increase in battery.
[Verizon Samsung Galaxy Note5] liquidraven:
Thanks for the info, have you tried any others by chance?
[Galaxy Tab S2 Q&A, Help & Troubleshooting] jever55:
Hey, so i tried rooting my galaxy tab s2 810(first time doing this stuff), i tried flashing a custom kernel, and then used an autoroot. it didn't seem like it was working, and now im afraid that i have gotten myself in more trouble that i thought was possible.. when i try to boot my device it stays on the boot screen saying either '' Kernel is not seandroid enforcing'' or ''recovery is not seandroid enforcing''. i cannot enter the recovery menu by pressing Power+home+vol up.

however i can enter the download section...

i have tried a bunc of different fixes, and i dont know if all i did was make my problem worse... i could really use some help.
[Nexus 7 (2013) Q&A] vorach:
Hello i have some issue with my headphones Bluetooth on nexus 7 2013 with the Last marshmallow update.

First the volume can't be defin with the tablette button only with the headphones button (with lollipop the same headphones the tab button work). Any solution for reactivate this ?

Second when i disconnect the headphones the only way to have sound in speaker is a hard reboot

Three i don't know if it is the same problem but the wifi is very instable like bootloop connexion or inpossibility to be connected.

For information i have a lot of android Device like lg g3 lollipop galaxy note Edge lollipop etc...

And all bug is only with my 2 nexus 7 2013 tablette with marshmallow. (stock and clean install)

The same headphones work correctly in my G3 for exemple.

Please if somebody know how to solve this thank's
[T-Mobile Samsung Galaxy S6] androidddaaron:
Here's 3 nice s6 Themed keyboards that work for 920t s6 flash in recovery and profit.

Note* if you want the stock keyboard back that's up to you to have the stock s6 keyboard zip or apk on hand ..

or restore a Nandroid backup.

It's available on Google and xda just search.

I take no credit in the Mod only just the find for it working 100% on the g920t.

Remember to hit thanks :beer:

#1 Black and green

http://download1130.mediafire.com/orwksnlzjk6g/a7xb0db42hfb0b0/Samsung_Keyboard_V4-WickedGreen.zip

#2 Black and red

http://download2160.mediafire.com/iqlulfju7k9g/hbg7aejb73wtyrc/Samsung_Keyboard_V4-AllBlack-Red.zip

#3 Black and blue

http://download1014.mediafire.com/xbtzbc800qcg/9q6ad7xwqxx8vee/Samsung_Keyboard_V4-AllBlack-Blue.zip
[T-Mobile Samsung Galaxy S6] bx10r:
flashed all 3 and only green worked the other 2 were black and white or close to white...thanks for sharing
[T-Mobile Samsung Galaxy S6] trungctu:
Pls show me how to enable special characters on Samsung keyboard...

Mine..
[Samsung Galaxy S (4G Model)] xc-racer99:
Source, Downloads, Misc Notes

Main Source

http://github.com/omnirom

Device Specific Source Code

http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-6.0-t959v branch)

http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-6.0 branch). The patches folder holds all the necessary patches along with a script to apply the patches.

http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-6.0 branch)

http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-6.0 branch)

Downloads!

All builds are found at https://drive.google.com/folderview?id=0B7vXjzo0Hj-iOGJ4dmdCd09OZmM&usp=sharing. As well, recent builds are mirrored on https://files.fernandob.com/#xc-racer99/Omni6.0

Gapps

Gapps cause the first boot to be very, very laggy. Things do improve after that. The best way to get through the Setup Wizard (IMO) is to skip everything possible (ie connecting to Wifi, settings up a Google Account, etc) and then reboot. You can manually add a Google Account later in Settings. While any (small) Marshmallow gapps should work, I have had success with OpenGapps pico package from www.opengapps.org (untested on recent builds).

SuperSu

SuperSu can be found at http://xdaforums.com/apps/supersu. If on May 2016+ builds, systemless 2.71 works (other systemless versions may work, untested). If you're on an older build, you need to either force system mode (create a file in /system or /data called .supersu with the contents "SYSTEMLESS=false") or use an older version (ie version 2.52 or earlier). August 2016 build updates the systemless to 2.76.
[Samsung Galaxy S (4G Model)] mataflakitas:
Woooow thanks
[Samsung Galaxy S (4G Model)] DickyG:
As you suggested, Gapps caused lots of problems...made the ROM very slow and laggy, lots of FC's, lots of random reboots, etc. I re-flashed without Gapps. Was able to restore apps with TB and root with SuperSu. The basics...calling, browsing, messaging, camera...are working fine. Haven't taken it for a ride yet, but GPS test picked up 5 satellites and I haven't even taken it outside yet. If I desperately need another app, I guess I can find the .apk somewhere. Since I did a TWRP backup, maybe next week I'll try the pico gapps again and see what happens. At any rate, wonderful work.
[Samsung Galaxy S (4G Model)] DickyG:
Update: Took it out for a spin this afternoon....GPS works fine.
[Samsung Galaxy S (4G Model)] robonxt:
Been running the 1/7 for a few days. loving it so far
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Alright, I've uploaded a new build

Changelog for 2016-01-23

Updated Omni Source code

Fixed Google Play (and other apps) download error (I think...)

New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one

Freed a bit more RAM

Improved zRAM performance by using LZ4 instead of LZO

I've also uploaded a T959P build as I had a request for one. Let me know if you guys find any more bugs.
[Samsung Galaxy S (4G Model)] DickyG:
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it

will run smoothly....good job.
[Samsung Galaxy S (4G Model)] xc-racer99:
Sounds good. Do note that when/if you flash gapps, you will need to do a complete data wipe first, otherwise you will get force-closes like crazy.

I've always just reflashed SuperSU manually and never relied on the script to restore it so I can't help you there.
[Samsung Galaxy S (4G Model)] SuccubusInc:
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.

Any way to fix this?

Thanks in advance.
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.

Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
[Samsung Galaxy S (4G Model)] SuccubusInc:
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.

I'll be back by 5:00pm PST. I have school to take care of.

UPDATE:

Tried again after a full wipe [not a restore to stock] and got this:

Is there any kernel/recovery you recommend for flashing after restoring to stock?

I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
[Samsung Galaxy S (4G Model)] xc-racer99:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.

Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
[Samsung Galaxy S (4G Model)] SuccubusInc:
I'll try out Blastoff if I can find it. But it probably failed because I did not partition my sdcard. I'll see if that helps later.

Thanks a lot.
[Samsung Galaxy S (4G Model)] SuccubusInc:
Hey, xc-racer99, after about four assorted blind attempts at installing your work, I flashed back to stock/AntonX kernel with Heimdall and full wiped, then used CWM to create a 4GB partition on my sdcard. The ROM installed through CWM, then TWRP without an error and booted up after fifteen minutes or so of OMNI animation, and is running on my SGS4G without any issues. The only noticeable lag was for the first five minutes after the initial boot. Now my device is gliding smoothly after a few tweaks in the performance settings and turning off background processes. Thank you so very much.

Next time, I'll read the entire post before blundering through the install process with the assumption that I know what I'm doing [as usual].

Sorry for the trouble, if indeed I was any.
[Samsung Galaxy S (4G Model)] uLose:
I tried Pico gapps and the store works perfectly for me now. Thanks!
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Changelog for 2016-02-04

Updated Omni source code - includes Feb security patches thanks to the Omni Team

Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things

More work on selinux - but its still in permissive mode

md5sum for the T959V - 975730824b335d9521d1201d4dac82b7

md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4

Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.

Download link is the same as it always is. Also, thanks to [MENTION=3833556]FBis251[/MENTION], we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
[Samsung Galaxy S (4G Model)] mataflakitas:
Wooow...thanks
[Samsung Galaxy S (4G Model)] DickyG:
Finally got pico gapps to run...the initial setup took quite a while but now that it's settled in, no problems. It's also interesting to note that Link2SD is running fine while it seems to be a major problem for other Lollipop & Marshmallow ROM's on other devices.
[Samsung Galaxy S (4G Model)] Ophidian_DarkCore:
Do you have enough time to do a one-off fassy build no selinux at all? My parents have me grounded from my desktop for a while. Thanks bruh

EDIT: Do you have twrp 3.0?
[Samsung Galaxy S (4G Model)] xc-racer99:
I might be able to, I haven't done a build for a first-gen Galaxy S device lately at all (need to update the builds here). It would have selinux permissive as disabled causes some issues. Probably won't get to it for a few days, I've been fairly busy working on the Moto G (2013).

Also, it would have TWRP 3.0.0, as will the next builds for Galaxy S 4G devices.
[Samsung Galaxy S (4G Model)] Ophidian_DarkCore:
Thanks for the info, looking forward to it :)
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Changelog for 02-29-2016

Updated Omni source - plenty of new features

Low-resource spinner from LegacyXperia (means that the loading spinner isn't the only thing using the CPU)

Miscellaneous performance tweaks (see github if interested)

md5sum for T959V: a7aa8cca3259208eafba7c2cccecdbfd

md5sum for T959P: 879256c93a0e58de0fb9c9e1be91e0e9

Selinux is still in permissive, files have been uploaded to both GDrive and files.fernandob.com. I'll post the link to the fascinate build in the Fascinate 5.1 thread, I don't want to cross-populate download links.
[Samsung Galaxy S (4G Model)] robonxt:
Just installed the 2/29 version. First impression is its faster then the older 1/7 build. Bugs: when I'm charging the phone, the screen seems to go crazy when I touch it.... Not sure if its just my charger
[Samsung Galaxy S (4G Model)] xc-racer99:
That's a very odd behavior, I didn't change any of the charging code. Is this when plugged into the wall, the computer or both? Is it the stock charger?
[Samsung Galaxy S (4G Model)] robonxt:
Using a outlet
[Samsung Galaxy S (4G Model)] xc-racer99:
Not sure what's up, I can't reproduce. If you're still getting problems, please take some logs (see http://xdaforums.com/showthread.php?t=2185929)
[Samsung Galaxy S (4G Model)] robonxt:
Seems like its just mine that's acting wacky.

SuperSU is not working currently for me, any tips/fixes that I can do?
[Samsung Galaxy S (4G Model)] xc-racer99:
Which SuperSU version are you trying? If you're using one that supports "systemless" (ie 2.65 or above IIRC), then you'll need to force system mode (google how to do it). Or, download an older version (ie 2.4x).
[Samsung Galaxy S (4G Model)] robonxt:
Thanks for tip, got SuperSU working and new version of OMNI working.
[Samsung Galaxy S (4G Model)] xc-racer99:
CMA Kernel

Alright, this is a test kernel that has been in the works for a bit, a joint effort between [MENTION=6794010]Coldwindofnowhere[/MENTION], [MENTION=5916159](°_o)[/MENTION], and myself. It uses CMA for the FIMC (camera driver) and MFC (hardware video decoder). This results in a whopping 442MB of available RAM. We also pinched a bunch of commits from the OMAP AOSP project (see http://xdaforums.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574). If you want to build it yourself, use the cma-tuna branch from my github. Note that you need a full build environment set up. This is also only compatible with this ROM (but probably could be backported if someone wanted to).

Do note that are the occasional issues with a page allocation when booting up, but I haven't noticed an issue with performance. If you do have any issues (especially with Camera or video playback), please let me know and include logs. I'm using it on my daily driver so I think its fairly stable...

It uses the kernel installer that [MENTION=3770444]jeffsf[/MENTION] created for the hefe kernel, I hope he doesn't mind me using it (if he does, let me know I can do something else)
[Samsung Galaxy S (4G Model)] mataflakitas:
Wooow thanks for this support...

??
[Samsung Galaxy S (4G Model)] graycow9:
Nice work! :D I got the random FCs' as expected, and a couple reboots (once from gallery, and one random shutdown while lockscreen was shut.) No logcat though- sorry. I'm loving it already though :) veryyy different. Keep it up!

Also one small question, any way to remove the sd card notification that pops up?

EDIT: I also just realized that my data is not working. Wifi and general call/text are fine but no mobile data. Weird.
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, I don't have a data plan so I rarely test mobile data as I pay a ridiculous sum to use it... Does MMS work for you (it uses the data network)? I have no issues with data here (I just tested).

Also, the random shutdown/reboots - which kernel is this with? The CMA kernel that I recently posted or the default one?

I need to upload a new build as I've made plenty of changes to the kernel to improve performance (besides CMA, but that's not totally stable yet).

Edit: And no, I know of no way to prevent the SD card message from popping up all the time. I could disable it while building, but I'm trying to keep this as close to the official Omni source code as possible.
[Samsung Galaxy S (4G Model)] graycow9:
It was default kernel, and I actually didn't test MMS- but browser would not connect and 2g/3g would not enable.

My original steps were:

- heimdall-flash with Stock KJ6+Root

- factory wipe in cwm blue

- flash marshmallow zip

--TWRP3 recovery flash pico gapps.

--wipe dalvik/cache then reboot and wait for install. (about 4-6 min if that's normal)

But then it's pretty darn smooth! :D

So I've tried flashing a number of ways including heim-to-mtdROM-to-Marshmallow... Nothing. :eek:

I'll give it another go tomorrow. lol

That being said, I'll be saving data :) and I am glad that you are helping to make this possible :D thank you
[Samsung Galaxy S (4G Model)] graycow9:
So I have data working! It worked as soon as I flashed SuperSU :) so I guess that means no root - no data for some reason. Had a weird feeling it was gonna be this. LOL

My bad.. but while I did I guess I could mention that I noticed the AOSP keyboard's gesture type is funked and the rest has been smooth including data :) :D
[Samsung Galaxy S (4G Model)] xc-racer99:
That's very, very odd.... I have data working without SuperSU.

Oh well, whatever works :) Glad you figured it out.
[Samsung Galaxy S (4G Model)] xc-racer99:
That's because gesture typing relys on a non-open source library which isn't available by default. If you install Google Keyboard, then the library is installed and suddenly gesture typing is working in both (or you can google around for the right lib, I forget what its actually called. Something like libjniswip.so...)
[Samsung Galaxy S (4G Model)] graycow9:
I see, well then that should be easy... after I figure out flashing SuperSU now. And after about 8 hours of flashing I figured out my data needs a jostle after reboot so to speak. If I click on airplane mode then off my data kicks right in. Haha. :thumbsup:
[Samsung Galaxy S (4G Model)] MrAndroid12:
Have I done something wrong that caused this to happen? (One with no internal SD)

I've already partitioned the SD card into 2 2GB partitions using the wizard into FAT32s and marked as primary partitions.

The phone was completely wiped prior to flashing your T959P roms, both Lollipop and Marshmallow returned with this screen during the initial boot up.

the phone was also wiped again but the problem still preexist.

Anyway of fixing it?

Thanks,
[Samsung Galaxy S (4G Model)] xc-racer99:
Wow! Another T959P owner :) Didn't think there were that many left....

Try formatting the second partition as ext4 as opposed to fat32. You can do this from TWRP (even if you're not booting to android) (reboot to recovery, Advanced, Partition SD Card, select EXT size of 2048MB, Swap size of 0MB, and make sure EXT4 is selected).

If this still doesn't work, use the oneclick that I uploaded in http://xdaforums.com/showpost.php?p=60203233&postcount=310.
[Samsung Galaxy S (4G Model)] MrAndroid12:
Finally got it running.

Should also mention to people that they must partition the SD card using TWRP or CMW recovery as it doesn't seem to like ext4s being partitioned using Minitool Partition Wizard.
[Samsung Galaxy S (4G Model)] robonxt:
Hehe same problem here after I installed the kernal without wiping.... it messed up my SD card too...

Gonna repartition my SD, how do I do that again...?
[Samsung Galaxy S (4G Model)] xc-racer99:
Odd, very odd. I don't know why installing the kernel would have caused that...

In TWRP, go to Advanced, partition SD card, select ext4 and create an sd-ext partition of the size of /data you want, and don't have a swap partition.

Also, wait until later today to reinstall as I'm currently uploading a new build (already available on https://files.fernandob.com/#xc-racer99/Omni6.0).
[Samsung Galaxy S (4G Model)] robonxt:
Ok, thanks! Trying Minitool Partition to partition the SD card, if it doesn't work I'll do it in TWRP
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Changelog for 2016-04-02

Security fixes in the kernel

Freed roughly ~4MB of RAM in kernel

Updated android drivers resulting in better multitasking

OpenDelta updating system removed as we weren't using it (it used ~3MB of RAM)

Recents menu now has less lag when opened

Selinux contexts have changed. It could likely be put to enforcing now but this would require a complete data wipe so its still permissive

Live Wallpapers removed - we're low-ram

Bootanimation now fits the screen better

PowerHAL removed - it was broken and has been for a while...

Misc other changes - if you didn't notice problems, you won't notice the solutions :)

md5sum for T959V: 247a721f4c27c5191a2a460e4c72ba3b

md5sum for T959P: d15339d8aa10f765155bdd8d1bb0c5f5

You can still use the CMA kernel that I posted earlier with this build if you want. I'm not including it by default as its not 100% stable (and likely never will be). It already has most of the kernel changes mentioned above.

Edit: The camera on the T959V is broken in this build due to me re-arranging some things. Is fixed in next build.
[Samsung Galaxy S (4G Model)] robonxt:
Should I install the kernel first then the ROM or vice-vista?
[Samsung Galaxy S (4G Model)] xc-racer99:
Whenever you install the ROM, it automatically updates the kernel as well (this is standard for all zips). So, if you want the CMA kernel (or any other kernel...), then flash it afterwards.
[Samsung Galaxy S (4G Model)] robonxt:
Oh... ok. Thanks! BTW I got the ROM running, it feels faster than before
[Samsung Galaxy S (4G Model)] rich@rd:
Hi I have a SGH-T959V and install the new version of marshmallow rise for you and this runs really well with the only drawback that the camera application does not open, when installing the rom execute it and asks a number of permits, gives a mistake and then tells you that the application is not installed and removed the link, I tested with other camera applications and also give error
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, that's odd. Perhaps I was too aggressive in trying to reduce the RAM given to the camera.

Can you try flashing the attached kernel and if you still get errors include some logs (see http://xdaforums.com/showthread.php?t=2185929 for info on how to) or at least a screenshot of the error message (push Power+Volume Up at the same time)?

Thanks.
[Samsung Galaxy S (4G Model)] rich@rd:
Install the kernel uploaded by you and the same problem remains with the camera application, try again with other applications after installing the kernel mode and reset to factory and returned to try, obtaining the same result.

I uploaded the screenshot of the error as you asked me, thank you.