yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Android Development] Old Jimbo:
I know that this kernel isn't supported anymore by its developer but I gave it a shot (thanks Luucho for your work and updates!). I'm interested mainly in BLN feature to work as described, through configuring the parameters via scripts.

My phone is the 8190N version, with a debloated 4.1.2, rooted and with Init.d support. The kernel version I've installed is "Fude-1.5.1_GT-8190X_signed.zip" and the script for BLN configuration is as follows:

#!/system/bin/sh

echo Y > /sys/module/bln/parameters/bln_enabled

echo 1 > /sys/module/bln/parameters/bln_blink_mode

echo 4 > /sys/module/bln/parameters/bln_blink_time

echo 1 > /sys/module/bln/parameters/bln_blinking_time

The script was saved in a file which I put it in "/system/etc/init.d", named 09script and being the last file in that folder. The parameters in "/sys/module/bln/parameters" are being modified accordingly but the blinking is not working at all and I don't know why.

Does anyone know what I'm doing wrong or what could be the issue here?
[Galaxy S III Mini Android Development] Old Jimbo:
Did anyone manage to configure the backlight notification through "/sys/module/bln/parameters"?
[Galaxy S III Mini Android Development] vleutmans:
Did you verify if those parameters really were set after reboot?

What i notice is that for settings like minfree values i need to put a delay at the beginning of the script, like: sleep 30

If the values are present and BLN is not working...i don't know what it can be. I had issues with this kernel as it drained my battery heavily because CPU was sticking at 1000 Mhz forever.

If you really like BLN, you could have a look at CM11 if it works there (please ask first in thread :) )
[Galaxy S III Mini Android Development] Old Jimbo:
Yes, I did verify all the parameters after the reboot and they were modified according to the script. Moreover, I've tried several values to see if those parameters are changing after reboot and yes, each time they did.

In my case, this kernel seems to be more battery friendly compared to the stock one. Using abyssplug, the cpu enters the deep sleep state when not in use and stays that way almost until first process starts. For me, battery efficiency and BLN are the most important things expected from a kernel. :) Of course, besides being bug free! :D

Omni 4.4.4? Which one do you prefer?

Thanks for your time! :)
[Galaxy S III Mini Android Development] vleutmans:
I tested the kernel and found that as soon as I enable auto rotation, the CPU load raises to 50% and both CPU's will stick to 1000mhz.

Am I the only one noticing it?
[Galaxy S III Mini Android Development] Old Jimbo:
What app did you use to measure the CPU's frequency?
[Galaxy S III Mini Android Development] vleutmans:
You can check with many tools but these are my preferred :

- Kernel audiutor

- OS monitor

- no-frills cpu

Br.

Michel
[Galaxy S III Mini Android Development] Old Jimbo:
I've tried Kernel Adiutor and the results are as follows:

First, with "auto-rotate screen" option unticked (disabled), immediately after I installed KA, the frequency table looked like in the image below...

After I've activated the "auto-rotate screen" option, the CPU usage in KA looked as below...

I let my phone unoperated for more than 40 minutes and BBS showed 99,1% deep sleep...

I don't know if these screenshots will help you... but in my case, it looks like the kernel it's working fine with the "auto-rotate screen" option activated. If you think there could be more things to check, pls tell me and I'll look for it.
[Galaxy S III Mini Android Development] vleutmans:
From your screenshots i see no "issue" like i have, but i notice that max frequency seems to be 800 Mhz instead of 1000 Mhz ? Did you use battery saving to lock max. to 800 mhz ?

Did you use the "enable movement" setting from your rom ? Not GPS i mean.

Also I'm interested with which ROM you are using this kernel. I tried on R-mod v3 and Noble V2 with similar results of sticking CPU. Which debloated 4.1.2 rom are you using it on ?

Br.

Michel
[Galaxy S III Mini Android Development] Old Jimbo:
The ROM's power saving option is enabled, since I don't need performance but energy efficiency. Therefore, the max. core clock is 800Mhz. If you want to, I could check if there will be the same results with the power option disabled.

By "enable movement" I suppose you are referring to "Motion", right? If "yes", it's disabled. I'm using the stock 4.1.2 from O2 (GB), build number JZO54K.I8190NXXALL4.

PS: I've debloated the stock ROM, 107 apks were removed according to my needs.
[Galaxy S III Mini Android Development] Geodoomer:
Damm good kenrel for stock. the only issue is that cpu usage when auto rotation is on. if you fix that i will use your kernel. but for now i need to find another for stock and its too damm hard
[Galaxy S III Mini Android Development] Old Jimbo:
The kernel's development was stopped almost 8 months ago. Yes, it seems to be an issue with the cpu usage when the auto rotation is on, although I didn't see it from the moment I've started to use this kernel.
[Galaxy S III Mini Android Development] kush2.0:
kernel crashed

crash report View attachment last_kmsg.zip

also wont reboot into recovery twrp.
[Galaxy S III Mini Android Development] Old Jimbo:
I was referring to the 1.5.1 version but 1.4.1 seem to work flawlessly.

Have you tried the 1.4.1 version?
[Galaxy S III Mini Android Development] kush2.0:
I haven't. Sold the s3 mini now and back on s3 i9300
[Galaxy S III Mini Android Development] koragg97:
1 year later ... can somebody using this kernel give feedback on how it works? Any bugs or battery drain etc?
[G2 Q&A, Help & Troubleshooting] wazowpt:
Him, i want to record a football match with my g2 but it crates large files which i dont have the capacity to store on this phone because it only has 16 gb. With this being said i cant record a football match which has 90 minutes. It would fill all the memory available in my phone!

Is there any app that can record smaller video files ? Can i record 90 minutes without filling my phone's memory? Help me out please.

Thanks :o
[G2 Q&A, Help & Troubleshooting] arda99:
you can always set a lower video recording quality to get a smaller size.

another way, you can expand the phone's storage using a USB OTG cable, but I'm not sure how to have the default camera app saving to the external storage, or you can try 3rd party camera apps.
[G2 Q&A, Help & Troubleshooting] wazowpt:
setting the app to record in lower will get me 90 minutes of recording?
[Galaxy S 5 Q&A, Help & Troubleshooting] emmanueldmc:
Ok, Ok ... this in the S4 ... that you do not touch the screen and see an effect on the unlock screen ... no longer does the S5 ??

[YOUTUBE]UV6aR_45VK0[/YOUTUBE]
[Galaxy S 5 Q&A, Help & Troubleshooting] fffft:
You didn't describe the effect whatsoever so I have no idea what effect you might be alluding to. (describe, not link to some video).

Anyway, there is no reason to think that all effects would be carried over on a different model. So if the effect that you didn't describe is indeed depreciated, then do a search to see if anyone has ported S4 effects to the S5 or perhaps another app has something similar.

.
[Galaxy S 5 Q&A, Help & Troubleshooting] Masum56k:
You mentioned about S4, but the video showing it's a Note 3...

Tapatalk - Galaxy S5 (G900H)
[Galaxy S 5 Q&A, Help & Troubleshooting] emmanueldmc:
It's the same, note 3 and s4 have this hovering effect on lockscreen...but the S5? ??
[Galaxy S 5 Q&A, Help & Troubleshooting] emmanueldmc:
Any help??
[Galaxy S 5 Q&A, Help & Troubleshooting] gee2012:
Its called `ink effect`, maybe a mod dev. can port it to the S5 ad the effect you see hovering over the screen is only possible on the Note 3 because of the interactive screen detecting an object.
[Galaxy S 5 Q&A, Help & Troubleshooting] emmanueldmc:
The s4 have this....but apparently lost after updates. http://forums.androidcentral.com/ve...-missing-hovering-light-trail-lockscreen.html
[Verizon Samsung Galaxy Note II] J_3dgar_H00v3r:
hmmm

If I hadn't just killed my phone (perma red angry text of death) I would definitely help test. Of course you have me to thank as well. Why? Because I knew as soon as I broke my phone, or upgraded someone would come out with a root fix. So you're welcome. However there is still a good chance that the new "probably very used" replacement phone I get from Verizon will be 4.4.2 already so then I will try this out. Unless this is some sort of very cruel trick played on those of us that can't afford to upgrade our phones every other month, in which case shame on you, and I will still try it until I am blue in the face. And crying.
[Verizon Samsung Galaxy Note II] 25yvdgpo06:
Nope, not a trick! My username looks a bit dubious even to me, but it was randomly generated by KeePass.
[Verizon Samsung Galaxy Note II] alkitchen:
I am getting, "error: device unauthorized. Please check the confirmation dialog on your device." I am not getting anything on my phone. Any thoughts?
[Verizon Samsung Galaxy Note II] TCPDump:
Im testing this now. Will let you know in a few mins. So far, so good.

Edit: This worked like a champ for me. Root achieved. For anyone wanting to do this, please follow these steps:

Run clean.cmd

Run prepare.cmd

Run root.cmd

Do these in this order. I went ahead and added a pause to each batch (Except root.bat that already had one) to ensure everything was kicking off as expected. Sorry if this was outlined in the OP, but Im sort of a "D personality" and wont read a lot of fluff.

Thanks!
[Verizon Samsung Galaxy Note II] Matttrix:
Seems to be running good here to ... some more fiddling and see how things go but I now have root on 4.4.2. Thanks

Update: no problems also Knox has NOT been tripped and no other issues.
[Verizon Samsung Galaxy Note II] akleeuw:
Worked for me!

I tried this, and it worked like a charm. So far, no issues.

Thank you!!!
[Verizon Samsung Galaxy Note II] rod_ol_fo:
=D

i dont think i've been this excited since safestrap was in the works for the N2!!! cant wait to try this when i get home!!! thanks dev
[Verizon Samsung Galaxy Note II] Droc1983:
I still don't have root. Not sure what went wrong. My phone restarted like it was supposed to but not root.
[Verizon Samsung Galaxy Note II] Tkun:
Does clean.cmd wipe all data? I only ran root.cmd and the phone rebooted like it was supposed to, but Titanium Backup doesn't register my device as rooted.
[Verizon Samsung Galaxy Note II] TCPDump:
It just cleans up old root files that might have been part of previous root methods, or failed attempts.
[Verizon Samsung Galaxy Note II] Tkun:
Thanks! Using your steps it worked and my phone is rooted!

Also, thanks OP for providing this solution! I was worried us 4.4.2 users would never again have root. I can finally backup and restore my apps again using Titanium Backup. :D
[Verizon Samsung Galaxy Note II] TCPDump:
Glad I could help, I went ahead and read through the source code before I did it, so had a pretty good idea of what it was doing.

---------- Post added at 10:38 PM ---------- Previous post was at 10:36 PM ----------

Where did you pick this up at? I want to go ahead and rewrite it to be more efficient later tonight, but I kind of need to know where it came from?

---------- Post added at 10:39 PM ---------- Previous post was at 10:38 PM ----------

Oh well, screw it... I'll go ahead and clean it up later.
[Verizon Samsung Galaxy Note II] Droc1983:
I had to Uninstall towel root apk. Now I have root access. Thank you.
[Verizon Samsung Galaxy Note II] alkitchen:
My apologies...

My apologies, disregard my post... I ran it again this evening and it WORKED!! Thanks so much.

Now to try Safestrap...
[Verizon Samsung Galaxy Note II] TCPDump:
I'll wait til you clean it up and then repackage. I don't care about credit either. I'll pm you my gtalk shortly.
[Verizon Samsung Galaxy Note II] empty20:
I would like to try this. I have downloaded the SDK, however I do not have any idea what the ADB step means. Basically, I have no idea what I am doing and would appreciate a little help as far as making sure I have everything that needs downloaded. Thanks.

edit: Got it figured out!
[Verizon Samsung Galaxy Note II] Droc1983:
Having trouble with safestrap. I installed apk and ran install recovery and grant root access but it says recovery not installed in the app.
[Verizon Samsung Galaxy Note II] mlw4428:
Not working...

I'm seeing:

Any help would be appreciated.
[Verizon Samsung Galaxy Note II] sviper:
Finally...

Just wanted to post my 2 cents to potentially help others. I was finally able to get root. Ran into a lot of the "could not push files" errors.

Just to give some background: I started out at the MJ9 firmware rooted (4.3). I installed the ND7 firmware using odin as the SDM had problems automatically updating my phone.

Definitely needed to download pdanet to get the correct drivers. Before installing pdanet, the "adb devices" command didn't find my phone. Afterwards, it comes back with the hex code for my phone. This is a test basically to determine if adb can find your phone.

After that, I ran the install.cmd of ghettoroot 0.3.2. I needed to perform this step to authorize my computer's connection to my phone. This of course failed out.

Finally, I ran the ghettoroot.bat multiple times with failures, but what finally got it working was that I HAD TO RUN IT AS ADMINISTRATOR!! I could have saved myself a lot of time if I would have started out with elevated credentials.

FYI, I'm on Win7x64.
[Verizon Samsung Galaxy Note II] doctor-cool:
Thanks , I feel vindicated for creating this thread HERE: http://xdaforums.com/showpost.php?p=55351133&postcount=1

WorkAround to get drivers for GhettoRoot
[Verizon Samsung Galaxy Note II] TCPDump:
What is your device firmware version? Can you send a screenshot of your software details? Also, can you please dump the whole root process results to a post here so I can look at it?

Thanks!
[Verizon Samsung Galaxy Note II] harp3736:
I have gone thru the process here and thought I got it working ( I am getting messages about Knox Setup Wizard stopped, Syscope stopped when the phone starts)

But it doesnt appear to have installed superuser or completed the whole root process

Has anyone had this problem or have any suggestions ?

If you need any more information please let me know

Thanks

update: added screen shot of device info and also the debug file from Ghettoroot
[Verizon Samsung Galaxy Note II] seeker07:
for all

I have tried several times but did not work until i have installed Samsung Kies 3

and i have used http://xdaforums.com/showpost.php?p=55210343&postcount=27

I hope this will be helpful for all

sorry for my bad english :)
[Verizon Samsung Galaxy Note II] Ezrae19:
Hi!

I've tried this several times now, from both Win764bit and MacOSX with the same errors on each. I've attached my debug file.

I've run the INSTALL scripts, followed all of the manual steps in the thread, and in every case I still get the same result.

adb can see my device, the root script executes but fails to mount the /system, /data and rootfs. After that nothing but errors since it can't access.

Any ideas? I've attached my debug.txt file with the output.

ETA: I have the Verizon SCH-I605 version 4.4.2 I605VRUFND7
[Verizon Samsung Galaxy Note II] larry_thagr81:
The program doesn't know how to find the necessary files to root your device. I'd suggest creating a universal path so that ADB can find the files it needs to root your device. Check out this video https://www.youtube.com/watch?v=yjutSsQn2Ic and let me know if you have any questions via PM.

---------- Post added at 08:36 PM ---------- Previous post was at 08:33 PM ----------

Check out this video https://www.youtube.com/watch?v=yjutSsQn2Ic and let me know via PM if you have any questions.
[Verizon Samsung Galaxy Note II] Ezrae19:
I already had the environment variables set on both Windows and OSX to allow the OS to find adb, so unfortunately that video does not help. :(

Thanks!
[Verizon Samsung Galaxy Note II] doctor-cool:
<iframe width="560" height="315" src="//www.youtube.com/embed/yjutSsQn2Ic" frameborder="0" allowfullscreen></iframe>

Thanks for the answer !

I thought the problems might be related to the path. Any ideas why some of us were able to run GhettoRoot "out of the box" and some of us can not.

I think if they install SDK ADT Bundle For Windows properly and run adb.exe at least once afterwards their computer will be able to find the path on it's own.

Check this out.

How To Download & Install SDK ADT Bundle For Windows-

https://www.youtube.COM/watch?v=PKY5bbytBGE

I recommend the whole video but at 16:36 he tells you how to open the adb command window. Once you have it open type in "adb devices" hit enter and it will show you a list of devices connected. Your phone should be there.
[Verizon Samsung Galaxy Note II] larry_thagr81:
Ok, so if the super user isn't listed in your app drawer, download root checker by joeykrim and run that program. If it says that it has successfully gained access to the root of your phone, then you're rooted. You'll just need to download an updated super user program like the program offered by chainfire.
[Verizon Samsung Galaxy Note II] Ezrae19:
It's not rooted. See screenshot and all of the errors I previously posted.
[Verizon Samsung Galaxy Note II] wheeless:
ADB and Path Not Issue - Maybe Permissions????

I've really appreciated the advice to changing the environment path to try and resolve my issue of my I605 not getting root.

I did that and verified that adb was recognized by my Windows 8.1 system. Also ran the adb device command and verified the device was recognized. Ran GhettoRoot again. Got exactly the same result - GhettoRoot does something to the Note II device (I get the Knox and Syscope error messages again) but doesn't root.

So I think maybe there is a issue on the Windows machine - so I move AndroidSKD and GhettoRoot_v0.3.2 to the C:root on my windows machine (had them on the desktop). Again, change the path variable, verify that adb is recognized by windows and recognizes my device. Run GhettoRoot again. Same result - the same massive list of "unable to chmod," "no such file or directory," and "unable to chown." And I did run Root Checker - it confirmed what I knew SU-not found; Root Access - no access.

I'm about to the point of saying this isn't worth it since I now have to do my third ODIN back to stock to get rid of the "Knox stopped" and "Syscope stopped" error messages - but since I hate unsolved puzzles, could the problem be one of permissions on my Windows machine or on my I605 device? Just doesn't make any sense that adb is recognized on the windows machine and adb recognizes the I605 device and does something to it (creating error messages with Knox and Syscope) - yet the adb process cannot find files and take ownership.

Any other puzzle solvers who want to take a final shot (for me at least) at this?

"ADKQUOTE=doctor-cool;55558607]<iframe width="560" height="315" src="//www.youtube.com/embed/yjutSsQn2Ic" frameborder="0" allowfullscreen></iframe>

Thanks for the answer !

I thought the problems might be related to the path. Any ideas why some of us were able to run GhettoRoot "out of the box" and some of us can not.

I think if they install SDK ADT Bundle For Windows properly and run adb.exe at least once afterwards their computer will be able to find the path on it's own.

Check this out.

How To Download & Install SDK ADT Bundle For Windows-

https://www.youtube.COM/watch?v=PKY5bbytBGE

I recommend the whole video but at 16:36 he tells you how to open the adb command window. Once you have it open type in "adb devices" hit enter and it will show you a list of devices connected. Your phone should be there.[/QUOTE]
[Verizon Samsung Galaxy Note II] larry_thagr81:
Are you running the program with administrative privileges? Which version of the latest towelroot are you running? There are two out there and one is completely automated while the other ask you 3 or 4 yes or no questions before it attempts to root your device. Does the program tell you that it's can communicate with your device? Did you store the towelroot file within the platform-tools folder of the SDK folder? If necessary, PM me and I can send you the files that I used, which would include everything you need to get your phone rooted.
[Verizon Samsung Galaxy Note II] Ezrae19:
Yes, I'm running as root and/or Administrator, depending on which computer I try this with. I get the same thing from OSX Mavericks and Win7 64 bit.

I'm using ghettoroot version 0.3.2. If I run the scripts included in the zip I do get the yes/no prompts.

Yes adb can see and communicate with my device without issues - take a look at my previous posts with the command line outputs for details there. I'm able to use adb (from both OSX and Windows) to communicate with my device, transfer files back and forth, etc. I don't think there's a problem there.

Thanks!
[Verizon Samsung Galaxy Note II] larry_thagr81:
[/QUOTE]

Yes I have a theory, if you don't have the correct samsung drivers installed ADB won't be able to communicate with the phone. Simply connecting your phone to the computer and having windows install the necessary drivers for your device to be able to transfer files aren't the correct drivers that are needed for the ADB environment. I went to samsung website and downloaded the drivers from there.

If you don't have the correct pathway set ADB won't be able to find the files it needs to access. I went a step further and placed the ghettoroot file into the platform-tools folder of the SDK folder.

I've had my galaxy note 2 rooted with an unlocked bootloader. Unfortunately a corrupted boot file prevented me one day from being able to boot into the OS as well and restore my phone through custom recovery to a previously saved backup. So I had all the necessary files to reroot my phone. The only issue I ran into was that windows wasn't installing the necessary drivers for the ADB environment to be able to communicate with my device and once I realized that was the issue, I was able to root my phone.

---------- Post added at 12:41 PM ---------- Previous post was at 12:32 PM ----------

What have you tried after the restart to know if your phone is rooted or not?
[Verizon Samsung Galaxy Note II] liftedplane:
I'm not sure if this can help however I was having problems as well, I used usbdev view and just deleted everything including my keyboard and mouse, i then plugged them back in to reinstall and then plugged my I've in, I was finally able to install the drivers that I had previously installed (samsung drivers that Windows wasn't recognizing) then ran adb WITHOUT admin elevation. I then had to run a command prompt and kill the asb server and restart to have my phone recognized, once I did that it rooted without issue. I've had to root it twice already since I'm an idiot and effed up the system ui.

not sure if this will help but worth a try.

I'm on win7 x64 ultimate as well
[Verizon Samsung Galaxy Note II] TCPDump:
Do the following:

adb shell

ls -la /data/local/tmp/ghetto/META-INF/com/google/android/

copy/paste the output here.
[Verizon Samsung Galaxy Note II] Ezrae19:
Here it is!

shell@t0ltevzw:/ $ ls -la /data/local/tmp/ghetto/META-INF/com/google/android

ls -la /data/local/tmp/ghetto/META-INF/com/google/android

-rw-rw-rw- root root 5265 2014-09-20 14:54 update-binary

-rw-rw-rw- root root 4693 2014-09-20 14:54 update-binary-2

-rw-rw-rw- root root 78 2014-09-20 14:54 updater-script

shell@t0ltevzw:/ $

Thanks!