yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] PIRATA!:
[MENTION=4869382]LilTechPrincess[/MENTION] ...

I've watched at different methods here on XDA in replacing KingUser with SuperSU.

There are two manual methods, one from Gunthermic and one from najoor.

They both use the same busybox, and SuperSU.apk files, while for the su file they use different files.

najoor uses Supersu v2.46 and busybox 1.18. About Gunthermic I'm still waiting infos.

What are your versions in your method?

And about the su file version? still 2.46?

I see a lot of different su files in the SuperSU original flashable .zip file, all of them placed in different folders. Which one have you choose for your replacement method?

Why did't you managed to install even the other files included in the folder from where you have extracted the su file?

There also other methods on XDA for replicing the KingUser with SuperSU using executable scripts. I refer to the method from Mr.W0lf (his website with last versions here).

I've done the md5 to busybox, su and SuperSU.apk files of all these four methods, one yours and the three other mentioned here, two manual and two based on the execution of scripts, and they all result in using different files.

Only you also manage to install the install-recovery.sh file. Is it from the original SuperSU flashable .zip file?

See attachment down here in this post.

I know that you might not have any idea in what others are using, but if you have your personal thoughts about it please tell me, specially because I would like to know why the original SuperSU flashable .zip file installs also other files mixed at the su file, while all these replacement methods does not install any other (I refer to the files located in the folder from where the su file is extracted).

Thank you.
[Verizon Samsung Galaxy S 4] DESASTER75:
Hi 2 All!

Finally I was able to root the I8200N and just want to share 2 All:

on I8200N:

- installed the USB-drivers on PC

- USB-Debugging on

- put latest SuperSu (1.51 from Chainfire) onto phone

- turned I8200N off

on PC:

- installed Odin (I have used 3.0.7) and opened it

on I8200N:

- put I8200N to download-mode (Vol- + Home + Pwr)

- connected I8200N to PC (USB-cable)

on PC:

- Odin showed COM-connection (light blue colour)

ATTENTION: DO NOT CHANGE THE FLAGS SET BY ODIN AUTOMATICALLY!!!

- clicked 'PDA' and selected latest Touch-Recovery forI8200N (downloaded from web)

- clicked 'START' and few seconds later Recovery was installed

- Auto-Reboot of I8200N

- turned I8200N off

- disconnected I8200N from PC

on I8200N:

- went to Recovery (Vol+ + Home + Pwr -> once SAMSUNG-logo showed up I have released Pwr)

- few seconds later Recovery showed up

- picked 'install zip from (external) SDCard'

- picked 'SuperSu.zip'

- installed it

- reboot of I8200N

- went to PlayStore and installed 'RootChecker'

ROOT ACCESS + SUPERSU

-> now root-apps can be installed/used like TitBackup and others!

BR,

DES75
[Galaxy S 4 Q&A, Help & Troubleshooting] bAk3ry:
Hi. I tend to keep my phone in a silent plus no vibrate mode at work. I wanted to know if there was an app that would let me know when my phone was ringing and text messages, so that I don't miss them when they arrive.

I've seen the android desktop notification, but that only shows what is on the notification bar.

I'd like something that informs me of calls too.
[Sprint LG Optimus G] reddragon72:
ok so this is awkward.... seems google has released the new Google Search and Google Experience Launcher for all handsets running 4.1 and higher..... with Google ripping the forefront of KitKat out why move to it?

Lets get a list going as to what KitKat brings to the table behind the scenes....

1)better memory managment

2)Smoother UI experience(butter+)

3)built in printer support API!!! I love printing from my phone now!

For those that want to try the new Search and Google Experience Launcher here are the links.

Download Google Search 3.1.8 APK

Download Google Experience Launcher APK

yes this turns on "Ok Google" from the launcher and also allows Google Search to talk/ask questions back to you.

I still think we need KitKat as I have been running it and it is very smooth and seems to be snappier than the stock rom.

FYI the launcher will NOT work on our stock roms!!!

It is working on other phones with 4.1 but not our phone and stock rom(with stock kernel). You can use some modded 4.1 stock roms that replace the kernel. As I believe it is a kernel based issue there will likely never be a fix as no-one is going to put in the time or effort.
[Sprint LG Optimus G] Androidawg:
Well, the Launcher still needs to be side loaded even after the Search App updates, so it is a little different there. I like having hangouts handle sms. I also like the little things like the touch sounds and such. All of these things can be emulated, but it still takes work and a little knowledge to get a kit kat experience on a different stock rom.
[Sprint LG Optimus G] reddragon72:
This is true but the launcher will be on the play store and it has been reported that a card in now will popup asking if you want it.

For a stock rom you get the stability over most other roms but I must say KK on ours has been a really big surprise.

I sideloaded the new now on KK and the feedback is pretty sweet, no more hunting to find the right number to txt or call it will ask you and you simply talk back.
[Sprint LG Optimus G] Androidawg:
For me it's all about consistency in the experience. It drives me crazy to see a stock dialer or stock messaging app when I am trying to create an AOSP experience. That's why I generally go for AOSP based ROMS. It's just jarring to have the settings menu come up with a white background. OCD
[Sprint LG Optimus G] roguejam:
Were you (or anybody) able to get this to work properly on ZVC? Tried the above, plus looking to get a potential lib, keep getting "Google Search" FC.
[Sprint LG Optimus G] reddragon72:
opppsss forgot to add that blurb. The launcher doesn't work on the LG OG stock roms. other 4.1 roms do work so it has something to do with the stock rom.

I'll add that in. The new Google search(Google Now) should be fine.

OP updated!!!!
[Sprint LG Optimus G] bowhunt2005:
Launcher didn't work for me on optimus 4.6 the OK Google feature worked but when I tried to add the search widget, OK Google went away. I don't know how to get it back yet either

Edit: turns out it went away cause I switched the language. OK Google command now works again
[Sprint LG Optimus G] reddragon72:
Just seen that there is an update for the english language pack that needs to be installed.

slid left to Google Now

scroll to the bottom

hit the three dots

select settings

select voice

select offline speech recognition

for those in the US ensure that English shows up and it is vers 28. For all others ensure you have downloaded your language.

BTW KitKat ROM users... this is NOT for you as it is all setup!
[Sprint LG Optimus G] neno2323:
Yeah this worked for me thanks
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Capone:
hi can anybody edit the new himalaya rom so that can be run on the blueangel

sorry for my bad english

greez

Capone
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] MrPhilly:
Erm.. Look here:

http://xdaforums.com/viewtopic.php?t=34746
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Capone:
?

the new himalaya 1.65c Final :wink:
[One (M7) Q&A, Help & Troubleshooting] darkblau:
Hello everyone.

Excuse me if this is the wrong forum for the topic. So far, I haven't found any solution/answer to my problem, which made me turn towards the elite :)

I have been using Paranoid Android for a long time on my SGS2

[latest version installed: PA 3.99-RC2, built on 3.0.64-CM-gbc8f4c9 for SGS2, pa_i9100-3.99-RC2-20131031.zip]

and everything worked great and I'm still a big fan of this project.

When I got my HTC One (International), I installed PA right away

[PA 3.99-RC2, built on 3.4.10-CM-gbce7128 for HTC One, pa_m7ul-3.99-RC2-20131030b.zip]

Now, both ROMs are working quite fine, it's just that I have noticed some differences in the system settings. More precisely, on HTC One, I'm missing some menu entries.

E.g., I can't set up slider shortcuts in the lock screen. (menu: Lock screen)

I can't set app-specific colours in halo. (menu: Halo)

I can't set up the Network speed indicator in the status bar (menu: User Interface) (the menu with the same icon on HTC One is called "Toolbars" instead and features only 6 entries, while on SGS2, I have 19)

I'm missing the "Adaptive backlight" entry in the Display menu.

These are just some examples. I spare you the screenshots of every menu. Also, on SGS2, some menus are english, some are in system language (german).

Can anyone tell me where these (in my eyes significant) differences come from?

Byebye

Chris
[One (M7) Q&A, Help & Troubleshooting] Ktan188:
The PA roms are still RC, which means it still in beta. Wait for a official release and see if all the tweaks and settings are there. Hope this helps
[Galaxy S 4 Accessories] bAk3ry:
I just ordered the spigen glass screen protector, the 0.28mm one. It just hit me that if the glass was thick, then I'd have difficulty hitting the home button.

Does anyone else know of this? Do I need to buy the home button attachment for this?
[Galaxy S 4 Accessories] DylanTheVillian:
My spigen case came with with 3 different colored home button stickers. makes the home button stick out, I would think they would send those if you are buying the glass screen protector.... check what is being sent in the box
[Galaxy S 4 Accessories] R4NDR01D:
It comes with home buttons, and you don't need to use them. It's all up to you if you prefer an inny or an outy. My home button fell off and I was able to use the inny no problem.
[Galaxy S 4 Accessories] Eric214:
I was actually going to unmap my home button to wake my phone because i was always waking my phone up pulling it out of my pocket when i didn't want it on. But when i got the MIME Ghost Glass screen protector and installed it i never hit the home button by mistake pulling the phone from my pocket. The Ghost Glass comes with 3 gel buttons (orange white and black) but it's easy to press the home button with it recessed slightly.

So like he said it's all if you want an inny or an outty... i prefer the inny as well.
[Galaxy S 4 Accessories] x111:
on my i9505, use spigen thicker glass protector without extra layer for home button.

but, I don't really use home button cause use screen buttons, which are much more efficient.

p.s. dream when Samsung stop put any buttons on front panel.
[Galaxy S 4 Accessories] bAk3ry:
I guess you had the buttons shipped to you as well :)
[Galaxy S 4 Accessories] x111:
Yep, I got some, but they are so bad and I don't see necessity to install anything extra on stock button.
[Galaxy S 4 Accessories] bAk3ry:
Thanks. That's kinda what I was looking for. :)
[Galaxy S 4 Accessories] Jimmy2u:
Well its completely your choice.....as you have an option to use it or not....when I got my glass screen Protector...I also got three home button stickers but I have not used even one as I felt its not necessary to use them on home button.....
[Galaxy S 4 Accessories] zen0s:
I personally have spigen aluminum home button (silver) put on my home button. It sits flush with the glas.t and gives it a real nice finish look! So, it's not necessary but if you want your phone to look sexy, it's a must! Hehe
[Galaxy S 4 Accessories] Fourty8:
Yep, was going to say the same thing. I LOVE LOVE LOVE the aluminum home buttons that can be purchased from Spigen. I have the Glas.TR Slim and the aluminum button sits perfectly flush with the glass.
[Galaxy S 4 Accessories] xreflection:
I have a jelly button on mine with the glass screen protector, honestly, I like the color (orange), but its irritating to find my battery draining becuase the home button keeps getting pressed whenever I sit down, bend over or whatever. Phone gets crazy warm at times too. I'm debating on ripping it off, lol.
[Galaxy S 4 Accessories] cindylee60:
I have a .4mm thick glass screen protector I got off ebay and that makes the home button quite recessed. Even so, I don't have any problem using it naked.
[Nexus 4 Q&A, Help & Troubleshooting] JanusDC:
Please, delete this thread.
[Nexus 10 Q&A, Help & Troubleshooting] hunter99507:
Has anyone made a flashable zip for 4.4?i can't seem to find one.
[Nexus 10 Q&A, Help & Troubleshooting] lvnatic:
+1
[Nexus 10 Q&A, Help & Troubleshooting] atan420:
twrp flashable zip

+2
[Nexus 10 Q&A, Help & Troubleshooting] joshhayden10:
+3
[Nexus 10 Q&A, Help & Troubleshooting] EnIXmA:
+4
[Nexus 10 Q&A, Help & Troubleshooting] ClashOfTheNexi:
+5
[Nexus 10 Q&A, Help & Troubleshooting] tgrgrd00:
+6
[Nexus 10 Q&A, Help & Troubleshooting] danmorley0702:
+7
[Nexus 10 Q&A, Help & Troubleshooting] ThomasBags:
Why has XDA become a pile of ****? ****, you get better advice from 4chan's /g/.
[Verizon Samsung Galaxy S III] jspector:
So I used casual to install twrp and everything seemed to be working great. I was having some issues before but I figured out odin not that tough but I was able to get back to stock so casual would work. Anyways My phone is stuck at the dirty unicorns splash screen. The logo is moving but I cannot shut off the phone without a battery pull. Is there a key command to get back into twrp? If I hold down home, vol dwn, and power it goes into odin mode. Do I have to load stock and try again? What is my next move?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Three finger combos:

Download mode: Volume down, home, and power

Recovery (CWM or TWRP): Volume up, home, and power
[Verizon Samsung Galaxy S III] jspector:
Exactly what I wanted to know!! Thank you !
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Happy to help! Hope you get that situation all squared away.
[Galaxy Note II Themes and Apps] jacob_stallone1:
Hi,

I flashed the Note 3 Launcher, the original one I previously had on 4.3 had the ability to hide apps in app drawer, but the N3 one doesnt. Can someone guide me on how to hide them without an app? Or can someone modify it?

Please I dont want another launcher, just the N3 launcher with this ability. Thanks :)
[Galaxy Note II Themes and Apps] Mikekelso421:
No frikin idea why they got rid of that...there's like 10 apps I always hide from the drawer...I'm using the LG G2 launcher till that feature is brought back..its pretty solid. Except for the lock screen settings which don't work.don't need em anyways since the functionality isn't there.
[Galaxy Note II Themes and Apps] nishantrohela:
Try using Audio manager from play store..!

Its the best thing to hide anything and everything :angel:;)
[Galaxy Note II Themes and Apps] vikceo:
how?

i am not sure how will you hide apps using it? i downloaded it but dont see a way to hide an app using it. please guide
[Galaxy Note II Themes and Apps] nishantrohela:
link

Here is the link..!

Download this..its basically a hiding thingie but it works as a audio manager too :good:

https://play.google.com/store/apps/details?id=com.smartanuj.hideitpro
[Galaxy Note II Themes and Apps] JoJo2211:
That doesn't hide apps... it disables them (and hides them). We need something that only hides the app for example I want to hide the SuperSU app, adaway app... which Samsungs built in hide apps allowed us to do.
[Galaxy Note II Themes and Apps] :
Here's the note 3 twizz launcher with blue text by Claude. It has the ability to hide apps as well. If not you could always use nova launcher

https://www.dropbox.com/s/szwmpvzukcz1u7f/Launcher4_Blue-Text-signed.zip
[Galaxy Note II Themes and Apps] MAX 404:
Hi Mate ,

I was looking for something like this for the I9500 ( S4) , this works on the S4 with Omega V19 but it disables the app and when you ask to see the dsabled apps it FC , where you got this from, looks promising needs polishing but looks good
[HTC One Mini] Mmgala:
Hi

i have just experinced a problem when texting.

suddenly it zooms in, like when web browsing, and i can´t disable the zoom before i go out of the message program.

any ideas
[HTC One Mini] RuffBuster:
Have you had a look at the accessibility options under settings? I know there are some zooming gesture options there.
[Omni Features Development] Entropy512:
This is going to be for discussion of various issues with using older sensor HAL blobs on 4.4, and how to properly implement backwards compatibility.

To participate in this thread, you MUST have the Sensor Kinetics and Z-DeviceTest apps installed.

https://play.google.com/store/apps/details?id=com.innoventions.sensorkinetics - Sensor Kinetics

https://play.google.com/store/apps/details?id=zausan.zdevicetest - Z-DeviceTest

Current status:

Oppo Find 5

In Sensor Kinetics, 3D and Scalar sensors work. Derived sensors such as "Rotation Vector" do not work.

This manifests itself with a number of user-facing issues:

1) No compass in Ingress

2) No level/compass function in GPS Status and Toolbox

Fixes tried:

So far - None

Samsung Galaxy S4 family

I do not own this device. This section is based on reports from jumoog and others.

Some sensors don't work. I have yet to have anyone tell me which ones work and which ones don't. I need this information (especially if the behavior matches what I described above for Find 5)

If a number of sensorservice patches from 4.4 are reverted, some or all sensors begin working:

https://github.com/TEAM-Gummy/andro...a80c19/core/java/android/hardware/Sensor.java

(need to find the rest, out of time)

It is unknown what happens if only some of the sensor patches are reverted. Some of them seem benign and unlikely to cause issues
[Omni Features Development] jumoog:
Sensors that dont work on: jflte (Samsung Galaxy S4)

All Sensor's detected

But this Sensor's give no value back:

Hardware

Gyroscope

K330 Gyroscope Sensor

Magnetometer

YAS532 Magnetic Sensor

Proximity Sensor

MAX88920

Barometer Sensor

Bosch

Software

Gravatiy Sensor

Linear Acceleration

Rotation Sensor
[Omni Features Development] Entropy512:
OK, so it's worse than find5 (raw mag/prox/gyro/accel work on find5) - do ANY sensors work?
[Omni Features Development] jumoog:
Working Sensors:

Accelerometer

Ambient Temperature

Light Sensor

Pressure Sensor

Relativ Humidity

With TEAM-Gummy patch: broken left (only software Sensors)

Gravatiy Sensor

Linear Acceleration

Rotation Sensor
[Omni Features Development] Entropy512:
Ok, so your hacks bring it, at best, to a state where it matches the find5 :(
[Omni Features Development] jumoog:
Maybe this works with find5 too
[Omni Features Development] MWisBest:
Just to make sure, you are aware that there's more to sensors than just frameworks/base, such as hardware/libhardware, right?
[Omni Features Development] jumoog:
thats true but dont need a patch for me

i use this https://github.com/chenxiaolong/hudson/commit/fecb144b093262b74010d7cdbcc532d1339cf0d2
[Omni Features Development] Entropy512:
What do you think I meant by "need to find the rest, out of time"? :)
[Omni Features Development] MWisBest:
Ah, my apologies, I missed that! If you need some help finding things I'd be more than willing to assist, I learned quite a bit about the sensors when I added an ambient temperature sensor to the Galaxy Nexus (albeit somewhat unuseful due to the heat pollution from the rest of the phone's components >.<).
[Omni Features Development] Entropy512:
Heh. It's been quite a while since I last touched sensors, back since the old days when I was fixing up the sensor HAL for Exynos 4210 devices and adding the pressure sensor for the N7000.

Blob compatibility is always a pain in the ass because sometimes you have no idea why it isn't working. It's strange because if you look at all of Google's commits, the new sensor stuff should retain backwards compatibility with old HAL APIs...
[Omni Features Development] UtkarshGupta:
On n7100, following doesn't work -

Compass

Light sensor

Proximity sensor

Rest all works.
[Omni Features Development] Entropy512:
Interesting. It looks like Google did a branch merge - as a result, there are commits buried deeper in the history than you might expect.

https://github.com/omnirom/android_frameworks_native/commit/cdd7d8bc145bbbd21a1689ed87a381287aeec229

It looks like the branch started after the April 17 commit in sensorservice's history (which can be viewed at https://github.com/omnirom/android_frameworks_native/commits/android-4.4/services/sensorservice )
[Omni Features Development] UtkarshGupta:
After calibrating proximity sensor, it works.
[Omni Features Development] UtkarshGupta:
Could someone upload gummy patches to gerrit ?
[Omni Features Development] Entropy512:
calibrating? So N7100 is fully working?

Which ones?

At this point, issues with fused sensors are fixed - https://gerrit.omnirom.org/#/c/2757/ (needs device tree change to enable) - this is confirmed on find5 and n1, and will likely fix the issues with jflte that remained after doing their sensorservice reverts. Obviously jflte needs something "extra" the question is - what?
[Omni Features Development] UtkarshGupta:
There was a apparent fix for n7100 by calibrating. I did it and some how proximity sensor worked for 1-2 hours and then it was dead again. N1 and find5 are different from exynos so I think the fix for them would be different.

I'll try device tree part and see.

Also http://review.cyanogenmod.org/#/c/54482/ , seems hopeful. Since they are open source now, issues can be ironed out. But it would need a lot of work before its done.
[Omni Features Development] Entropy512:
Can you give some details as to this "calibration" process? I have noticed on find5 that no data is reported until after the sensor triggers once.

As to the setrate-on-enable - While I can confirm it affects qcoms, the reasons qcom put it in there indicate that other vendors are highly likely to have similar workarounds for pre-kitkat behavior. e.g. other sensor HALs may assume that they receive two setrate calls for each sensor and ignore the first one for "fused"/"derived" sensors like rotation vector and such.

The opensource sensors is another good approach, although after all I've learned, I'm wondering how much is given up with those sensors. I'm 90% certain the old galaxys2 family didn't have derived sensors implemented at the HAL level - but it sounds like N7100 does. In theory, motion fusion in the HAL is better tuned to the device than the generic one in the frameworks.
[Omni Features Development] UtkarshGupta:
The process was for tw Roms only, which was reported later.

https://gerrit.omnirom.org/#/c/2389/ - this should fix software sensors I hope.

And yes setrate is for qcom devices. It can't effect exynos devices.
[Omni Features Development] Entropy512:
Have you tried it? I would not be surprised at all if Samsung used the same hack in their Exynos sensor HALs that qcom did in theirs.

There is NOTHING qcom-specific about the change - the only "qcom" connection is that most devices with in-HAL sensor fusion are qcom-based. It really depends on what the HAL author did to handle multiple setrates on a fused/derived sensor - qcom ignored the first one, I wouldn't be surprised if Samsung used the same approach.

The setrate logic is one of the largest differences, from the perspective of a legacy sensor HAL, between 4.3 and 4.4 - Even if the workarounds for 4.3's double-setrate are different in other HALs, the fact that 4.3 and earlier did double setrates means that a lot of HALs are likely to assume that it happens and behave badly if only a single setrate is issued.

So for this "calibration" - you had to calibrate it in TW then flash over??? If that's the case, the calibration process may need to be reverse engineered and implemented in omni. (We did something similar for accel cal on the galaxys2 family ages ago...)
[Omni Features Development] mithun46:
Fusion3 Devices from Sony Mobile

Everything works :)

Except Camcorder :p
[Omni Features Development] UtkarshGupta:
With ignore device hal sensors, everything is fixed.