yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] fanbogo:
hey mate, i cracked my screen 1 month ago, i paid for new about 150 pound. volume button, home and back(very bright light, i must turn it off) and also silver parts from top and bottom they dont fit perfect also i have something like hair under screen.

my suggestion is send it to htc, dont try with other companies... and sorry for you i know this feeling ;/
[One (M7) Q&A, Help & Troubleshooting] Heisenberg420:
Not the answer I was looking for but good to know.

I'm wondering if I can sell it. Like I said it's barely noticeable and I can't even feel it, I'm using swype input in tapatalk right now. It could of been A LOT worse. Curious if I could get maybe 200 out of it.
[One (M7) Q&A, Help & Troubleshooting] alray:
I'm almost sure you could get around 200 on ebay. Just try to sell it with a reserve price of 200 and see what happen.
[T-Mobile Samsung Galaxy S 4] nopotential:
I have PayPal for which I will use to donate an amount to the person(s) who can help me.

I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker

Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"

I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.

Here are my current specs:

Model

SGH-M919

Android Version

4.3

Baseband

M919UVUEMK2

Kernel Version

3.4.0-g4fe9989-dirtyjovy23@jovy #1

Build Number

JSS15J.M919UVUEMK2

SELinux status

Permissive

Secure boot status

Type: Samsung
[T-Mobile Samsung Galaxy S 4] brian117:
The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.

Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.

No donations are needed for these kinds of things.
[T-Mobile Samsung Galaxy S 4] nopotential:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1

The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?

Is TWRP 2.5.0.2 better?

Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?
[T-Mobile Samsung Galaxy S 4] brian117:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.

I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.

If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.

Download the file and flash MODEM.bin via Odin under the phone slot.

Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
[T-Mobile Samsung Galaxy S 4] nopotential:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
[T-Mobile Samsung Galaxy S 4] brian117:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:

1. Open Odin v3.07.

2. UNcheck the boxes that say auto reboot and f. reset time.

3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.

4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.

5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.

6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.

7. Click start and let Odin flash the ROM.

8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.

9. Reboot back into Download Mode and then flash the CF-Autoroot found here.

10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
[T-Mobile Samsung Galaxy S 4] nopotential:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
[T-Mobile Samsung Galaxy S 4] brian117:
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal. :)
[T-Mobile Samsung Galaxy S 4] nopotential:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
[T-Mobile Samsung Galaxy S 4] nopotential:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
[T-Mobile Samsung Galaxy S 4] brian117:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.

If you continue to have WiFi problems, flash this via recovery.
[T-Mobile Samsung Galaxy S 4] nopotential:
It looks like everything is looking good by following your list. Thank you.
[T-Mobile Samsung Galaxy S 4] brian117:
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.
[T-Mobile Samsung Galaxy S 4] nopotential:
-Deleted-
[Galaxy S 5 Q&A, Help & Troubleshooting] cherrytontonne:
My only previous experience with Titanium was with the HTC One and Nexus 5 (2013), it always opened up superfast and backed up, restored, and froze/uninstalled apps with a problem...but for some reason with my S5 I can only restore data (not apks and data) and I also cannot freeze any apps...I'm trying to go through and get rid of some of this Samsung bloatware but it just isn't working.

Is this a titanium issue or maybe something with Knox? Disabling Knox using the terminal emulator method also isn't working, just says "aborted"

:confused::confused:
[Galaxy S 5 Q&A, Help & Troubleshooting] cherrytontonne:
This was caused by switching to ART. As soon as I switched back to Dalvik (because my banking app isn't compatible with ART) the problems with Titanium disappeared.
[Galaxy S 5 Q&A, Help & Troubleshooting] gidgiddonihah:
I too am having this problem - I don't want to switch back to Dalvik but I think the greater performance increase will be from removing (AKA freezing - I don't like removing system apps from anything other than a Nexus device) apps over ART. Too bad. I am not sure what causes this as Titanium backup was updated for ART and I ran it flawlessly on my Nexus 5 on ART.

It just finished freezing an app after switching back - guess there is some weird ART bug introduced by Samsung. Odd and this makes me not look forward to the headache that will come of the Android L update.

Sorry for bumping an old thread but I thought I would weigh in. :)
[General Marketing & SEO] femimobile:
Hi all,

Kindly help review my app and I will do the same for you.

####################

Short-term Memory Test

####################

This app offers a good brain exercise for everyone. It is the best memory testing game for: kids, adults, boys, girls, men, women, even seniors (grandmas and grandpas). No age restriction at all.

---------------------------------

How the app works

---------------------------------

A few letters will flash on your device for 3 seconds. Your job is to write down as many letters as you can remember after they disappear. At the end, a report is generated that evaluates how good your short-term memory is at retaining information.

If you like the app, please share it.

Google play store link:

play.google.com/store/apps/details?id=com.yahoo.ahadeyemi.memory12

Thank you
[General Marketing & SEO] bertsy:
Hey nice app! Very responsive and polished, too bad I really suck at it :o . I left a review titled 'Very useful app'. If you could check mine out as well that'd be awesome. Here's the link to the free version:

play.google.com/store/apps/details?id=com.madlabgames.breakerfree

Also if you could try pressing the back button on your device at the main menu, I got some people saying that it caused it to crash but I can't seem to find the problem. Thanks!
[General Marketing & SEO] femimobile:
Thanks

Thanks for reviewing my app. I left a review for you as well.

Good luck,

Adefemi
[General Marketing & SEO] femimobile:
Thanks

Bertsy - I didn't notice any issue pressing the back button from the menu. One thing I would suggest though is to add an alert asking if the user wants to exit the game when the press the back button is pressed both from the play scene and from the menu scene.

Good luck,

Adefemi
[General Marketing & SEO] bertsy:
Thanks for the review and the suggestions, I really appreciate it!
[General Marketing & SEO] SimplePoet:
Good

Nice app, more tests will be better.

Here is my new app:

Simple Live Wallpaper

play.google.com/store/apps/details?id=com.simplepoet.simplefree

Thanks!
[General Marketing & SEO] francoiseamble:
app reviews

I have checked your app and its working perfectly.
[General Marketing & SEO] kjambrek:
i tested your app and it's great :)

please review our app iziTalk on google play ;)
[General Marketing & SEO] femimobile:
Thanks for reviewing my app. I have reviewed yours as well.

Adefemi
[General Marketing & SEO] femimobile:
Thank you very much for taking the time to test out my app.

Adefemi
[General Marketing & SEO] femimobile:
I couldn't find your app on google play. Could you post a link? Also, could you kindly post your review of my app on google play and I will do the same for you. Thanks!

Adefemi
[General Marketing & SEO] Mobijet:
Review left!

Hi! I reviewed your app minutes ago under the name: Steven Mah, title: Memorising can be fun!

Please kindly do the same for mine :)

play.google.com/store/apps/details?id=com.Mobijet.ChaseHimDown

Thank you! To both our successes!:good:
[General Marketing & SEO] femimobile:
Hi, Thanks for reviewing my app. I just reviewed yours. Good luck.

Regards,

Adefemi
[Galaxy S II General] manfromgta:
Downloaded and clean install. Went without a hitch including TB app restore. I will let it settle in and report any findings. Thanks Tyler for everything!

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] Screambloody:
Is AOKP better than CyanogenMOD at this moment? or What is your opinion?
[Galaxy S II General] titanic_fanatic:
AOKP has the same performance as my other ROMs. It just had different features, some of those are included in other ROMs too like carbon.

My favorite ROM is still carbon, I just want to provide others with a choice of what ROM to run. You can always test it out and restore a nandroid if you don't like it ;)
[Galaxy S II General] Screambloody:
Thanks,I'll test this ROM,but,is Carbon more stable than AOKP,CyanogenMOD 11 and Slimkat?
[Galaxy S II General] titanic_fanatic:
No, I just prefer the features that carbon has implemented. Some from cm, some from aokp and some from slim. For me it's the best of all 3 ;) And now I'm playing with the idea of permanently implementing Slim's recents app since I really like it.
[Galaxy S II General] iDynamics:
Been running this for a few days. Going to try ART later. Excellent job! :good:
[Galaxy S II General] iDynamics:
I got stuck at the boot animation for almost 15 minutes when I enabled ART :(. Luckily I had a backup. Oh well, rom is still fantastic.
[Galaxy S II General] titanic_fanatic:
When this happens, you can boot into recovery, then use the console I'm aroma filemanager and ruin this command:

Of course you need to mount the data partition before you open the console ;)

This will switch you back to dalvik
[Galaxy S II General] iDynamics:
Thanks.

I used this to switch back.

http://xdaforums.com/showthread.php?t=2713622
[Galaxy S II General] titanic_fanatic:
I have a new build of AOKP running right now ;) Hope to post it by the end of the night!
[Galaxy S II General] iDynamics:
Will the fixoverlays script be needed for this build?
[Galaxy S II General] titanic_fanatic:
I assume so, but am not entirely sure until I test it out ;)
[Galaxy S II General] titanic_fanatic:
There was a whole bunch of build errors when I got home :( it seems that I synced between important commits that caused the build errors. It's now back to building, and the good news is that I incorporated omni performance controls into this build instead of cm's.

Also, this will be the first of the 4.4.3 builds ;)
[Galaxy S II General] iDynamics:
Looking forward to it :)
[Galaxy S II General] titanic_fanatic:
Just fyi, the build is done, but untested because sultanxda posted his fix for the graphical glitches and I've didn't all day porting over those changes to our kernel. I'm working through build errors right now, but hope to test tonight. If anyone is brave enough, your welcome to test the aokp I built, just let me know and I'll upload otherwise, I'll test it after I get this kernel tested out
[Galaxy S II General] iDynamics:
I'm down for testing.
[Galaxy S II General] titanic_fanatic:
Cheers, so I'll upload the zip right now. When it's done, I'll post the link with specific instructions on what to test and how to test it ;)

The only time it becomes really difficult to test and get useful loss if needed is when either it bootloops or android doesn't load. I'll explain how to overcome these situations when I post instructions.

Thanks for the help and support ;)
[Galaxy S II General] titanic_fanatic:
alright, it's uploaded to my Aokp folder inside another folder called test.

Flash as usual taking your necessary backups beforehand ;)

Then, first I need you to test if the overlays script is still needed. To check this, go to developer options and uncheck the disable hw overlays checkbox, then pull down the notification shade and if the background goes immediately black instead of starting to dim then it's still needed so disable it again. If that check passed, go to the Homescreen by pressing back and make sure there is no flicker and that the background never goes black. This must be the same for the Homescreen as well, the background cannot go black. If it doesn't then you can open a browser instance and browse to review.cyanogenmod.org specifically and use the input field in the top right corner, this causes the view to zoom and also the keyboard to appear. If nothing happens, click outside of the input field to hide the keyboard or press back one time to do the same and then back into the input field again to pull up the keyboard. Do that allot and if the glitching still remains, this will cause lots of glitching and a reboot.

With that all tested, make sure that the performance settings work as I ported omni's performance control from my carbon build.

Also make sure to check the version information.

Ok, pay close attention here. I know you know how to take a logcat, that's the easy part. What to do if you get a bootloop, this is the tricky part. You must watch the phone boot up the first time which usually takes 130 seconds give or take and depending on the rom. Getting a kernel log can be difficult when in a bootloop because it's cleared each time the phone boots, well that's not useful is it :( here's the trick, and why you need to watch the bootup. As soon as the phone bootloops, there will be the initial vibration that signifies the device is booting up, you need to press and hold only your volume up and volume down buttons as soon as you feel the vib until you get into cwm. If it boots past into the bootlooping android then the log is gone and you need to try the process again.

Once you get into cwm, open aroma filemanager by double tapping the empty space at the bottom of the menu. Make sure aroma options are set to mount everything and show hidden files. Now browse to /proc and scroll down to the files until you find last_kmsg and copy that file to a spot on your sdcard which you will need to access through /storage/sdcardX where X represents 0 for internal or 1 for external sdcard.

This log is what I would need to see to fix a bootloop ;) let me know if anything doesn't make sense ;)
[Galaxy S II General] manfromgta:
I will download and test today. :)

Ok. I downloaded and flashed but i can't get to developer options. I did the tapping in about phone as usual but it does not enable options.

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] Sultanxda:
Background going black when pulling down the notification bar is caused by the kernel not supporting persist.hwc.mdpcomp.enable=true
[Galaxy S II General] titanic_fanatic:
A new build is uploading right now that fixes the dev options. I don't know why aokp doesn't include this code in their repo :( download will be done in a couple of minutes.

That should all be working in this new build with the same filename. The only changes are to the settings app, so if you already have it flashed you can just pull the Settings.apk out of the new zip and replace the old one and set the permissions.

Thanks for the feedback ;)
[Galaxy S II General] titanic_fanatic:
This is while using the stock cm kernel.

With KitKat we first had the graphical glitches, then they slowly went away with each new build and then the kernel was updated to work with media-caf and that's when the graphical glitches turned into the black background when pulling down the notification shade. If hw overlays are left enabled, it causes the graphical glitches which get really bad and result in a reboot.

Is this the mdp drivers causing this?

I've been trying to build with all of your latest commits and have been unsuccessful as of yet. The complication I keep running into is my display is a mipi dsi s6e8aa0_720hd and all caf code keeps removing my display code so I keep having to reintegrate it and also the rebase for pmem optimization is killing me. I can't seem to get rid of pmem for my device. No matter what I try, when I remove those lines referring to pmem and change my kernel offset to 0x404 I get a bootloop. I'm not sure what to do about that but figure it has to be sorted out for us to move forward.
[Galaxy S II General] Sultanxda:
Yeah, the black background and other crazy glitches caused by that prop are probably being caused by the mdp drivers (at least, when I tested that mdpcomp prop on my HTC Sensation, a device with with a mipi panel, the kernel log was flooded with mdp errors). I got really sick of having to reintegrate my display drivers, so I just moved them into mach-msm: https://github.com/sultanxda/sultan...mmit/8269bc462a9f9c0027f53a31b654dbd56aac1cac

I tried changing the kernel offset of my Skyrocket's kernel to 0x48000000 and I couldn't get it to work. Even though that pmem optimization prop is enabled, you're not using pmem at all; it mostly just changes the kernel offset to 0x40400000. The Skyrocket uses an lcdc panel, not mipi dsi, so you're probably going to have to do some things different from me to get the new framebuffer drivers working (also, all of my changes to mdp4_overlay_lcdc are useless for you).
[Galaxy S II General] iDynamics:
When I tap the build number, settings force closes.
[Galaxy S II General] titanic_fanatic:
Working on this ;)
[Galaxy S II General] manfromgta:
I was able to get dev options using a playstore app called "dev options"

1. unchecked disable h/w overlays, pulled down shade and screen went black and was somewhat glitchy. On home screen it is quite glitchy as well.

2. from here I did the browser check that you indicated and was able to cause a bootloop.

3. sucessfully entered cwm on loop and copied kmsg to sd card. Following is the file...

View attachment 2789182

4. Could not check performance setting because they are not present in settings.

Cheers!!
[Galaxy S II General] jbpanache:
Just noticed..."Developer Options" also available under the "DEV Tools" app which comes pre installed...:)

BTW, thanks TF for this ROM...as always, your work towards this device is highly appreciated...
[Galaxy S II General] manfromgta:
Just wondering if the lastkmsg held anything useful for you.

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] titanic_fanatic:
It had the same error message about mapping memory :(

I'm just building with sultan's latest patch right now with a Carbon build. I'm hoping this will fix the screen glitch and that pesky error message ;)
[Galaxy S II General] titanic_fanatic:
Hey guys, I just read a post by car vs driver about his android 4.4.3 upgrade from Google is killing his battery. Is anyone on our 4.4.3 experiencing worse battery life than before?
[Galaxy S II General] manfromgta:
I have run the test release for an entire day at a time and noticed a slightly faster drain. But to be fair, I didn't use all my battery saving techniques while testing. I still wouldn't say its a drastic difference from carbon build which at this time is my daily.

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[Galaxy S II General] titanic_fanatic:
New Build is UP!

New AOKP build is now available for download. Like my other ROMs, this one includes settings for controlling the vibrator intensity in the Advanced Device Settings and added Omni Performance Control. I have also uploaded the AOKP mini GAPPS to my androidfilehost.com for easy download. It's really minimal, like only 75MB minimal and all apps only fill one screen in the app drawer. There is an AOKP full GAPS that I have not tried, but if you would like to try it, you'll find it here:

https://goo.im/devs/kxp/gapps/

If you try the Full GAPPS, please let us know if it worked without any apps Force Closing.

Now, like my other ROMs, I have forked and committed all of my special changes in order to make AOKP build for our device. This will make future builds easier to manage and will make it easier for the next dev to take over in a little over a year when I switch to a new device.

Download

Enjoy!!!
[Galaxy S II General] manfromgta:
Just some quick feedback on latest aokp build.

I did a clean install and used aokp mini gapps.

Happy to say that I've not run into any bugs after 3 days of using as a daily driver. Haven't tried ART yet as I'm unsure if its functional in this aokp build.

Well done TF!!!! Thanks once again for your continued effort!

Sent from my SGH-I757M using Xparent Cyan Tapatalk 2
[JAM, MDA Compact, S100 General] deepdark:
i have this device can i install Windows Mobile 5.0???

thx
[JAM, MDA Compact, S100 General] JaapB:
NO

There are many threads on this topic. If u used the search option first you would know the answer, which is no. You can not install mobile 5 on the magician.

Use the search option first before asking questions.