yashsingh1/xdaforums huggingface dataset:
[Nexus 4 General] vickpick:
tried to switch to ART and have been stuck at bootanimation for the past 4 hours.

Even sideloaded 4.3... now stuck on 4.3 bootanimation.

No idea what to do.. maybe flash userdata as well. I really didn't wanna lose all my data :/
[Nexus 4 General] michaelpryce_:
All games like FIFA, Dots and Whale Trail perform absolutely horridly.
[Nexus 4 General] ytv:
VPN isn't working for me ;(
[Nexus 4 General] Lox_Dev:
Same issue here ...

Same issue here ...

D/Tethering( 598): sendTetherStateChangedBroadcast 0, 0, 0
D/BluetoothAdapter( 2442): 1107936488: getState() : mService = null. Returning STATE_OFF
E/NetdConnector( 598): NDC Command {64 softap fwreload wlan0 AP} took too long (890ms)
E/SoftapController( 172): Cannot update "/data/misc/wifi/hostapd.conf": Permission denied
E/WifiStateMachine( 598): Exception in softap re-start java.lang.IllegalStateException: command '67 softap set wlan0 AndroidA broadcast 6 open [scrubbed]' failed with '400 67 SoftAP command has failed'
E/NetdConnector( 598): NDC Command {65 bandwidth gettetherstats} took too long (891ms)

ls -la /data/misc/wifi/hostapd.conf
-rw-rw---- system wifi 215 2013-11-14 10:40 hostapd.conf
[Nexus 4 General] rasengan82:
All these bugs that are getting found... I'm wondering if Google will release the OTA in this condition... I hope not...Maybe Google released the factory images on purpose before the OTA??
[Nexus 4 General] oxxshadow:
I found that sometimes the notification pulldown lags sometimes even when not on the lockscreen. It occurs in stock image rom and custom roms based of 4.4.
[Nexus 4 General] oSandmaNo:
+1

It seems only some of us have this problem. There are very less reports of this!!
[Nexus 4 General] lazer155:
Has anyone noticed delayed gmail notifications on wifi?
[Nexus 4 General] 3dreamers:
I just realized that Maps is using 40% from battery and I didn't even open the app. What can it be?
[Nexus 4 General] A4ko:
Soft keys are not transparent. :confused:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] PansenJim:
First thread = noob question

Hi, what exactly does mean: "Set warranty Bit: Kernel" after root?

(Using the search function I couldn't find it)

Thanks
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] farewellartist:
reply

Same question here. It isn't a tragic issue, but still annoying on boot.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Dzovicek:
Same here

Same here, it's OK but if there's any way to get rid of this, I'd be glad :) :good:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] rolo143:
Is there any way too get rid of that annoying message? After I root, and install custom recovery it appears on every boot and even when I enter in recovery is annoying -.-
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] ladislav.heller:
Only way is to flash back stock firmware = loose root.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] unit999cn:
Baseband will loose too.-_-!
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] rolo143:
So there's no way to have custom recovery + root without having that message.. right? Or at least for now. ..
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] nickcaper:
Yea ok. But Knox wont let you flash back to stock.

I tried.

The messages are from Knox.

Its to tell Tmobile we modified the phone...

Dont you just love Samsung now?:rolleyes:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] systwk:
No one mentions which JB but if you upgrade or re-install Chainfire's Super SU, I believe current is 1.80, upon installation it will mention Knox asking annoying questions and do you wish to disable Knox. Answer OK, and it will do so upon re-establishing root. You can go into System/apps and rename, move or delete the Knox apps, I suggest 'rename' if you are new to this. (just add .bak to .apk's) Use Root Explorer or ES File Explorer as R/W root and you should be OK.

EDIT: Knox files to rename or whichever, KNOXAgent.apk KNOXStore.apk ContainerAgent.apk

ie: rename Knox...xx.apk.bak

I create a directory on the Ext SD, /App_Bak and just move what I de-bloat or don't need while testing, that way I have them if needed later.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] rolo143:
I rooted using the old method, by flashing custom recovery first, then flashing the zip file "rootkit" and then having Superuser.apk on my phone. It worked even with the latest firmware, but now I have that yellow message thing. .
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] systwk:
Which ROM do you have now? And have you gone to the Play Store and updated to the latest Super SU?

When you update SU it re installs and will, with permission disable Knox. I'm guessing you have. Try a reflash w/Odin 4.2.2 and just repeat the S4_Mini_Rootkit and update SU. Kinda' do it over...Sometimes that helps.

Sorry I'm not too clear right now, been up 25 hrs and gotta' sleep. I'm older than dirt and can't go the distance any more.

EDIT:Apologies, missed the part about you having the latest firmware. If you are on 4.3, others have had success so IDK, unless you have an earlier SU than 1.80.

My Bad...Another EDIT: Did you by chance go into system/apps and delete KNOXAgent.apk, KNOXStore.apk, ContainerAgent.apk ? Just maybe......... I gotta' sleep, bye.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] rolo143:
Lol... I don't have Knox security warnings, I deleted all Knox files. The message in yellow says "Set Warranty Bit: kernel" on Samsung boot logo, but that's it. I think is nothing to worry about, but if I can get rid of it, that would be great. It appeared after I installed TWRP Recovery. .
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] systwk:
Yeah, that's still that blasted Knox, doing it's "Set Warranty Bit: kernel", you are tripped at 0x1 with an eFuse.

I was going to play with TWRP, I think I'll retain CWN for a bit. It still might be worth a shot to go back to square one with the baseline Arco68-CWN setup with 1.8 SU and at least see if the warning goes away. Or have you already?

(I'm kind of tempted to duplicate your setup, I'm curious about this.) Can you clarify? Are you on 4.3, or did I misunderstand and you're on 4.2.2 ?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] rolo143:
I'm on 4.2.2.. I stupidly updated my phone via OTA, because I thought it would have 4.3 but surprise! I got a Knox firmware and I can't go back. And I think TWRP or CWM it doesn't matter, I think when you flash any recovery that isn't stock, the warning activates..
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] systwk:
The OTA explains your problem. 4.2.2 is fine, the below root process deals with Knox.

Re-do with the Arco68 root from square one. Stick with CWM for now, TWRP may not be fully stable with the S4 Mini at this time, CWM is. Using it removes any question.

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

(make sure to click the Arco68 thanks)
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] laurie89:
Got the same message in my galaxy 4 mini

Hi guys! First of all consider I'm a graphic designer and have no idea about rooting and getting in phones softwares hahaha, but I have so bad luck that after purchising my Samsung S4 mini (GT i9195) on a trip in France about a month ago and trying to use it here in Buenos Aires with a local SIM, I got Samsung's Region Lock message pop up. I gave it to a friend from work and not only he couldn't fix it, but also returned it to me with this tiny annoying message in the initial animation that says "Warranty bit: kernel" (really bad caption attached).

So here I am, trying to fix the region lock and also the Warranty Bit message. The most important thing is the region lock, of course, but now I think my friend rooting the phone caused this message to appear.

The thing is, can I fix both things? In order to fix the region lock I need to have the device rooted, and, in the other hand, the root left this message.

Can anyone help me? I swear I've tried to understand it on my own but there are so many thecnical vocabulary I just don't get.

Couldn't thank you enough!

Hope you are all doing great,

best

Laurie.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] fburgos:
Laurie, if you don't want to see that yellow message you have to install stock ROM with Odin, your warranty still voided.

have you tried region lock away I'm not sure if it works but it won't hurt trying.

sent from my i9192 with CM11 by sekil
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] H3nr1b0y:
set warranty bit kernel

I have galaxy s5 sm900f but i think every phone is the same text proplem . I try many difference roms and only one work without that text is alliance rom. Every others roms always come text kernel is not seandroid enforcing and set warranty bit. I dont know what is difference that rom i use philz recovery.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] rubbertoes:
Also where is the best place to get the stock ROM files so we can use Odin and load them? Thanks for all your help!
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] fburgos:
Sammobile dot com
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] hackersecrets:
just install i9192.4.4.2.StockROMLite.2.0 [/I rom] via odin and your problem is solved with root access.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] kennyk09:
CM11 M12 Gi915 set warranty bit : kernel

I also get this message during boot up now.

set warranty bit : kernel

There still is no way to fix this other than installing stock ROM?

Thanks,
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Razvan:
No it isn't any solution until now.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] daboss5:
You don't need full stock. Just the kernel. I installed alliance ROM v8 with stock kernel and it boots normally
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] ProMusic:
Hi,

Same problem here.ANybody can send me that Kernel orig.file ?... :)

Thanks
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] enkeitankado:
same problem here..

Can anyone help? thanks.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Nicofisi:
Problem...

The same here :P
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] RuffBuster:
Original kernel is "stock" kernel. You can only have the stock kernel on Samsung firmware and ROMs. If you want to get rid of that message you need to flash a stock firmware from Sam Mobile. Or extract a matching kernel from the firmware. There are guides for this all around XDA. If you want to use ROMs like CM you can't get rid of message. Personally I say just put up with it.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] pkfoneboy:
Set Warranty bit: kernal

I removed the message using kies, tool
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] piotreks4:
How?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] shadow01505:
Probably by restoring to stock firmware.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] jjitty1:
re-install SU

So you mean uninstall the SU and re-install it and then follow the directions above?
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] italyuser25:
solution?

no one wants explain truthfully and simplified if this method solves the problem of string?

I have a galaxy s 5 to which I have just rooting
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Chris4877:
"Set Warranty Bit : Kernel" is a message showing that the device has somehow been modified from factory condition. Such action usually voids the warranty. The message will appear if you have:

Installed a custom kernel.

Rooted your device.

Installed a custom ROM.

The only way to get rid of that "Set Warranty Bit : Kernel" message is to reinstall a stock ROM/kernel, and you can ONLY DO THAT BY USING KIES. If you try to do it using Odin, it will fail, and when you reboot, you'll get an error message to the effect that you have to use Kies to fix your device. Your device will not start, and you will have to pull the battery, connect the device to your computer, reinsert the battery and switch on the phone, and then start Kies, which will then go about fixing the problem.

Kies will:

Restore your phone to factory.

Replace any custom recovery with stock recovery.

Install the LATEST AVAILABLE UPDATE for your device/provider.

UNROOT YOUR DEVICE.

THE ONLY THING KIES CAN'T/WON'T DO is set the warranty bit to "0" because you need special hardware and lots of specialised skill to be able to dismantle your device and use the hardware to write to certain chips on your device's motherboard.

Hope this explanation helps.

Best regards

Chris Souter
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] AnthonyCarl:
And What if You Only Reflash the Stock Firmware or Rom ? or the Kernel Will Be The Root Affected or Removed ? :confused:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Chris4877:
The device will be unrooted by Kies, stock recovery will replace any custom recovery you may have installed, the latest available stock firmware for your device will be downloaded and installed, but the warranty bit message will remain, and your device will no longer be eligible for repairs under warranty.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] AnthonyCarl:
i just installed the twrp because cwm wont work on my sm-g900i and the seandroid Enforcing Appears is this normal ? there are two messages now the warranty and the seancdroid
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Chris4877:
I haven't seen the second message, but that could be because I'm not using a Galaxy Note 4 Mini, which is the subject of this forum.

I'm using a Galaxy Note 4, SM-N910G, (VAU), from Vodafone Australia, running stock Android v6.0.1 Marshmallow.

It's possible that your device might give different messages from mine.

SEAndroid is the version used by Samsung, and the kernel is normally set to "enforcing," which limits some things you can do as root, as far as I know, but I'm certainly not any kind of expert in this field. I've learnt about 99% of what little I do know from the xda-developers forum.

A few days ago, I installed an app from the Play Store, called "SELinux Mode Changer," which I have used successfully to disable "enforcing" mode at startup.

I have no idea whether or not this app would be compatible with your device, and there's only one way for you to find out: visit the Play Store, search for the app, and when you reach the page, it will tell you whether or not it will be suitable for you to use.

I should also warn you that it's not easy to set up, but that depends on your installed version of SuperSU by ChainFire.

I'm using SuperSU Pro, (paid app), and I had to fiddle about with it to make it work.

Also, there's a special version of SELinux Mode Changer which you have to download directly from the app developer's web page. It took me a fair amount of Googling, plus searching the xda-developers forum to find out how to make it work for me. The Play Store version won't work with SuperSU.

If I remember correctly, there's a post somewhere on xda-developers with lots of information about SELinux Mode Changer, which I'm sure you'll find by Googling this forum.

Sorry I couldn't be of more help, but I wish you lots if luck, anyway! :)
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] :
FYI, this isn't true for the i9195. Flashing the stock rom with odin removes the message. Furthermore rooting with the root package from arco68 on the stock rom, and I still don't have that message, which was surprising as I flashed the custom recovery using odin as well as flashed the root files through the custom recovery......
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Chris4877:
Well, that may well be correct, but I have no way of knowing for sure, because, even though I quite understand that this forum is about the I9195, the poster to whom I was replying actually has a Galaxy S5 and he doesn't say which Android version he's running, whilst I, myself have a Galaxy Note 4, running Android v6.0.1 Marshmallow.

As I said in a subsequent post, (in essence), "your mileage may vary." :)

Also, I should add that I never saw any of those messages until I updated my device to Samsung's version of Marshmallow.

Thanks for the info, BTW! :D
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] :
OK, it was just a FYI for anyone reading that has a i9195. The two posts above you stated flashing the stock rom with odin won't remove the "set warranty bit kernel" message without qualifying which device you were talking about. Just trying to avoid confusion for S4 mini users. :good:
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] najeb3:
Special thanks to Chris4877

know I understand why this message appears after flashing Lineage OS 13 (I9190)

Best Regards

~~~
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] controlmypad:
I recently had this problem after rooting my N910T Note 4. It seems to be fine after rooting with the yellow message in the upper left corner on boot "set warranty bit : kernel". My experience was that after several reboots over 4-5 days after rooting, it started giving me messages on the working phone that some something.tmobile.something file was missing (message flashed too quickly). Then that is when my phone went into some type of boot loop and wouldn't ever go to the home screen. It would boot to recovery and the download screens. I had backed up before rooting, but in the 4-5 days I had a few things I wanted to retrieve and so I just re-flashed the rom from the guide and I was up and running again and was able to get my files off again. I was using this rom CF-Auto-Root-trltetmo-trltetmo-smn910t.zip from this guide "theandroidsoul(dot)com /root-t-mobile-galaxy-note-4-sm-n910t-using-cf-auto-root" (can't post links as new user).

Do you think happens this like I think it does, that it gives you only so many reboots before "sort of bricking" your device with the boot loop. Or did something strange happen with my phone?

I am curious if someone could recommend a rom, maybe a stockrom lite version that will get rid of the message and still speed up the phone. Thank you for any help.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] tracar:
does anyone know where to find the Samsung Galaxy Tab S2 SM-T818W Nougat Stock Recovery ?

i want to return it to stock.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] sim_tcr:
Hello,

I am planning to flash omnirom on my p3100 as per http://xdaforums.com/showthread.php?t=2512853. Part of the install instructions are installing DhollmenCM kernel.

Currently I am on CM 10.2 nightly. And If i flash DhollmenCM kernel, something goes wrong, How do i go back to previous?

Can CWM nandroid backup get me back to previous?

Will flashing Samsung's original stock rom take me back to previous?

Thanks,

Simon Mandy
[Galaxy Tab 2 Q&A, Help & Troubleshooting] sharingan:
if you have stock kernel then flash it i think it would definitely work

also try to wipe cache partition and dalvik cache as you might able to boot properly

good luck:good::good:
[Galaxy S III Q&A, Help & Troubleshooting] tyler.richards1987:
ok so i have been searching far and wide i am using a sprint galaxy s3 running wicked sensations 5.0 and i am having issues with the boot sounds i put in they start late when the phone is almost done with the boot animation and i can not figure out what to do to make it start when it is suposed to like with the stock os if anybody could help me with this issue that would be great also i am having issues using aosp roms when it comes to sending and receiving mms i have replaced the apns with the correct sprint apns via apn back up and restore but still nothing and i have tried go sms pro also i need to note on this that i am also using a sprint prepaid company called expo wireless and i have changed the mmsc url to the correct one again this works on tw based roms but not on aosp roms and there are a ton more aosp roms that i love the features to compared to the one i am using but this rom is a great rom dont get me wrong help please any one!?!?!?!
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Sorry no idea where the boot sounds go. Try asking in Sprint forum Q&A.

Likewise for your rom .
[Android Q&A, Help & Troubleshooting] yuvarajgta:
Hi Guys,

I have created an android app for reminding users through vibrations at specific intervals. When we are travelling in bike or in meeting, classroom we cannot take the phone to check the time(or span of time). So before starting we can set the reminders to go off at regular intervals or at different custom intervals. We can also select the type of vibration like short or long.

I am going to release this app in play store. I have attached the apk file and few screenshots, please install the app and send your feedback. It will be very helpful if you tell me which operation is hard to access, bugs and any improvements that can be added to this app.

Also tell me any important things to do before releasing the app on play store.

Thanks,

Yuvaraj
[Android Q&A, Help & Troubleshooting] autom8r:
Great concept, I'll give it a go!
[Android Q&A, Help & Troubleshooting] tabnnaj:
Thank you for your efforts, the App is working good. It will be better if you add an option to change vibration level.

The App is working smoothly, without any force closes.

Wish you all the best

Help me by hit like here :

https://www.facebook.com/BankMuscatMeethaq/posts/576114045788466
[Android Q&A, Help & Troubleshooting] yuvarajgta:
Vibration reminder

Thanks for your comment. I checked the Vibrator class it does not have any methods to control the vibration intensity.

If anyone knows how to control the vibration intensity, please share.
[Android Q&A, Help & Troubleshooting] yuvarajgta:
Vibration Intensity control

I searched and found a way to control vibration intensity using "Immersion Haptic SDK".

I implemented it in my app and it worked very well. I attached the modified apk now.

Reply your feedback guys.
[Android Q&A, Help & Troubleshooting] yuvarajgta:
Released app on google play

I have released my app on Google play. Thanks you all for your suggestions.

Please download and review it on google play.

playstore link:

https://play.google.com/store/apps/details?id=com.youwedroid.vibrationreminder
[Android Q&A, Help & Troubleshooting] yuvarajgta:
App demo video

http://www.youtube.com/watch?v=IanWY70qbPs

Scan the attached QR image from your phone to directly download this app from play store.
[JAM, MDA Compact, S100 Software Upgrading] leochan2005:
Can anyone tell me how can I use my itech stereo headset to connect a magician for mp3? I failed for many times.
[JAM, MDA Compact, S100 Software Upgrading] TheBrit:
You need to wade through this thread: http://xdaforums.com/viewtopic.php?t=33532

Download and install the patch from the thread and read the rest for advice on set-up.
[Samsung Epic 4G Touch] colbyt94:
I have had been rooting my s2 since i have gotten over a year ago, and have not had lag issues with too much RAM being used. Now the other day my phone started using 600+ mb of RAM. I was on rooted 4.1.2 With GB27 modem. I thought resetting phone completely would work, but no hope. I wiped everything, and 5 min after powering up it still uses 600+ mb of RAm

I flashed multiple JB Roms to my phone with no avail. I am currently running SenseWiz 2.0 on 4.1.2 GB27 (followed steps in the Roms thread 100% to flash this btw). It still uses no less than 500+ mb of ram. This phone has never lagged on me before and it really irritates me. Something as simple as pulling down notification bar even lags.

Please let me know what I need to do to fix this.

Also not sure if this is right forum section, but sounded like a noob question to me lol.:crying:
[Samsung Epic 4G Touch] erikalin:
Hi. Someone can give you a better answer, but something to check first is what's using it. I don't have this phone, but I think the location is:

Settings -> ________ (a tab) -> Applications -> then "swipe right" to show Running Apps. Since I don't think most people have this issue, it might be an app you installed that's just bogging down the phone. It should show as running, and maybe several processes. What app(s) do you install after flashing the ROM? (For example I install Yahoo Mail, Netflix, etc.) Or maybe some apps got in their with some crazy default app settings that make them stay awake and work all the time.

Use the Greenify app. It's amazing - puts to sleep the stuff you do not need until you open that app. For example, you don't need Angry Birds up in your business unless you want to play it, lol... that can clear RAM too...

G'luck. :good: