yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Q&A, Help & Troubleshooting] elcom:
You can use the 15 toggle mod to add the torch to the pull down notification menu.

Starting from ICS you can pull down the notification menu from the lockscreen.
[Nexus 7 Android Development] jamesst20:
Hi,

I figured out how to get the init.d support on the Google Nexus 7 with some research. It works on ANY Kernel and ANY ROM (Including Stock ROM/Kernel !)

All you got to do, is to flash the zip from Recovery :)

How do I know if it worked ?

- If in /data/local/tmp/ there is a file 'init.d_log_test.txt' and inside is written the date, it worked.

Download Here
[Nexus 7 Android Development] Pariah3000:
What does init.d do?
[Nexus 7 Android Development] jamesst20:
Allow you to adds script into /system/etc/init.d and those will run at device boot. It is useful for performance tweaks and stuff like it :)
[Nexus 7 Android Development] Pariah3000:
OK. Flashed it an it installed. Super simple MOD and it works. Now what?

I found CPU Editor: http://xdaforums.com/showthread.php?t=1584508 Looks interesting,

Anyone have suggestions of other hacks that take advantage of init.d?
[Nexus 7 Android Development] jamesst20:
A script that zipalign on boot would be useful ;)
[Nexus 7 Android Development] ozzy666:
thank you so much!
[Nexus 7 Android Development] jamesst20:
No problem :D

Envoyé depuis mon Nexus 7 avec Tapatalk
[Nexus 7 Android Development] stonebear:
Hi, I flashed this on my stock (rooted and CWM) rom and then tried Jay's Buttery Goodness thing http://xdaforums.com/showthread.php?t=1855100&page=29 leaving out flashing Moteley's 1.0.5b kernel with ramdisk as I thought I should already have init.d support so it should work without doing that - but it didn't. I had to flash the 1.0.5 kernel for it to work?
[Nexus 7 Android Development] jamesst20:
You can flash this on any kernel and it should work
[Nexus 7 Android Development] gokart2:
The kernel needs init.d support, which I believe most ''aftermarket" ones do, if not all. Only ones that dont are usually the 100% stock ones.

You need to decompile the kernel, and edit a couple scripts to get it to work if it doesn't already. The kitchen will do it, but its kinda a pain if our don't know what to do.

Edit #1: Idk man. From ripping through your mod and having recently gone through all this. Pretty positive this won't work on a stock kernel unless it's modded. And the files are a little off from everything I've looked into doing my own homework on it.

Edit #2: I think I see what you did and I didn't know what that file actually was (used to it being named differently) and that this process was even possible. Believe your using "post boot" to run init.d, correct?
[Nexus 7 Android Development] stonebear:
It's not working for me with stock kernel, however it does work with Motley, I haven't tried other kernels yet.
[Nexus 7 Android Development] jamesst20:
It does work with the stock kernel, you're doing something wrong
[Nexus 7 Android Development] z1gackly:
Which version of busybox is included? It may be an issue with ramdisk support rather than init.d support, as Jay's script depends on ramdisk. If I get time later I'll try it myself on your JRO03S ROM.
[Nexus 7 Android Development] stonebear:
Yea, it must be the ramdisk thing as it works only after flashing the 1.0.5 Motley kernel with the stock ramdisk.

That was the step I was trying to cut out of Jay's instructions, I thought it might be ok to do that after flashing James' zip.
[Nexus 7 Android Development] rorreo:
All I do is flash this, but will it work on a cleardroid rom stock, I'm running big boy kernel, if that helps. I guess I better just do a backup and try it out myself lol thanks guys

---------- Post added at 08:07 PM ---------- Previous post was at 07:28 PM ----------

Thanks for your help, and work
[Nexus 7 Android Development] MetalMan2:
I just flashed this through recovery and now my Nexus 7 won't boot into anything (just sits at the Google screen) except the bootloader.

Here's what I have:

Team EOS nightly, #137

Faux 123 kernel, v012b8

TWRP recovery

So I downloaded the .zip file from the OP, and flashed it in recovery. Then wiped cache/dalvik. Hit reboot and it just sat at the Google screen, didn't come up to the boot animation. So I hold the power button until it restarts, and go into the bootloader. Then tried to go into recovery so I could factory reset and reflash the Team EOS rom/kernel, but it wouldn't go into recovery (just sat at the Google screen).

Next I thought to check to see if I'd be able to flash anything through my PC while in the bootloader. No go... 'fastboot devices' doesn't detect anything.

Any help that can be provided would be appreciated!

EDIT: A combination of powering off and booting back into the bootloader enabled fastboot to connect. Flashed the stock 4.1.2 image (downloaded straight from Google). Was able to get back in, flashed TWRP, flashed Team OES latest nightly, flashed GApps, flashed faux 123 kernel, booted up and did all of the initialization stuff.

Just booted back into recovery to install the Jamesst20 - init.d.zip file. Installed it, and rebooted. It's been sitting at the Google screen for a few minutes now, and at one point my PC detected it with ADB devices. I'll continue to wait and see if anything happens.

EDIT 2: Waited about 15mins and called it quits. This time I was able to go directly back into recovery, factory reset, install Team EOS zip, and then installed the Jamesst20 - init.d.zip file. Same issue, just won't work. So I confirmed it wasn't the faux 123 kernel causing the issue... wonder if the Team EOS ROM just doesn't like this init.d utility.
[Nexus 7 Android Development] z1gackly:
I believe the TeamEOS ROM already has init.d support, so I'm not quite sure why you would want to flash this with it anyway?
[Nexus 7 Android Development] MetalMan2:
Eventually I kinda came to that conclusion too. But I still haven't found any documentation from Team EOS saying that they support init.d specifically for the N7 (they say they're using a stock or stock-variant kernel). What makes me think it does support init.d is that I've read most "aftermarket" ROMs/kernels support init.d

So I suppose the issue here for me is that this ZIP file caused a non-bootable device, despite being advertised for "ANY ROM/Kernel". If the developer here isn't concerned with this, I'll leave it alone. Otherwise I'd be happy to provide logs or whatever it would take to troubleshoot the problem.
[Nexus 7 Android Development] jamesst20:
Hi,

Well download my init.d zip, extract it and get the script from etc/init.d folder and place it on your device in system/etc/init.d. I think the script is called datetest or something like it. Don't forget to put 7777 permissions on the script in your device and then reboot. If /data/local/tmp/init.d_log_test.txt exist with the current date and time, init.d supports is already there :)
[Nexus 7 Android Development] rorreo:
Good work I used this for badaman80 big boy kernel
[T-Mobile Samsung Galaxy S II SGH-T989] DinoSoup:
I just want to use the Nav Bar in AOKP, instead of the hardware keys. I figured out how to disable them, I just cant turn off LED. Is there a way to do it, but still let it work for notifications?
[T-Mobile Samsung Galaxy S II SGH-T989] elesbb:
Here you are my good fellow. Hope this is what you're looking for
[T-Mobile Samsung Galaxy S II SGH-T989] DinoSoup:
I'm actually already using that, I just want to disable the LEDs back lights of the keys. Its some kind of built in galaxy s tool in aokp jb!
[T-Mobile Samsung Galaxy S II SGH-T989] serge1231123:
Change the custom Backlight settings in display to have 2 settings one on all 0 and one at 100 and then put it into auto bright and lock phone till deep sleep and turn on and there you go
[T-Mobile Samsung Galaxy S II SGH-T989] elesbb:
oh i was completely confused by your thread. But in aokp i believe you have to create a shortcut to it on your home screen. In CM10 its under advanced in the settings menu.

Sorry i cant remember, i dont use aokp.
[T-Mobile Samsung Galaxy S II SGH-T989] Rod3:
In AOKP JB, the easiest option is to go to settings, device options, sensors, and uncheck "enable keys backlight."
[Xoom General] oldblue910:
I've been running the leaked VZW Xoom JRO03H ROM that they still haven't released. As far as I can tell, this ROM is identical to the WiFi-only ROM except that it has 3/4G enabled. The ROM is rock solid, runs great, it's fast, etc...but I can't help but feel that Google totally mailed it in with this ROM, at least from an visual standponit.

1. Why would they leave the ICS boot animation in place? I get that the stock Jelly Bean boot animation is the multi-colored X representing the Nexus branding, which obviously wouldn't fit for the Xoom (even though it's a Nexus in all but name). That said, there was a cool alternate boot animation that shipped on the JFN53N build on the Nexus 7 tablets given away at I/O 2012. They could have easily used that and it would have fit fine for the Xoom since it made no reference visually to the Nexus branding whatsoever.

2. They didn't provide the stock Jelly Bean wallpapers found on the Galaxy Nexus, Nexus S, and Nexus 7. Instead they just left the ICS wallpapers in place and changed the default one from the rainbow colored design to the green leaf design. Would it have really been that hard to just put the stock JB wallpapers into the launcher APK?

3. The lack of the Sound Search widget. What would possess them to leave that out? Again, if they can include it on the Nexus S (which is older than the Xoom), why can't they include it on the Xoom? The Nexus 7 even ships with a version of the widget that is resizable. Again, this is two files in the /system folder. Is it really that difficult?

4. Tapping the "clear all notifications" simply erases them from view instead of having them disappear using the little swanky animation that the other devices have.

I realize that all of these issues I bring up are visual, nit-picky things. I also realize that these issues can all be overcome manually. My only point here is that there was seemingly no reason to overlook these things other than Google just not giving a $h1+. Yeah, the Xoom is over 18 months old now, but there is still no 10" Google-Experience tablet to replace it yet. That means it's still Google's reference device for showcasing Android in full tablet configuration. Have some pride, guys. Geez.

Rant over.
[Xoom General] Winesnob:
Well stated. I have the same thoughts on the WiFi Xoom JB update. I did however find the .apk for the sound search widget, installed (not rooted) and it works just fine. If I can locate the file I'll post it. Aside from that, yeah, they kind of missed the mark on this one but it did transform the Xoom into a slick new device. Very impressed with the responsiveness added by JB on an aging device.
[Xoom General] oldblue910:
Agreed. In terms of pure performance, no one could argue that JB has made the Xoom as fast and smooth as it has ever been.
[Xoom General] Trooper Thorn:
Maybe somewhat off topic...

But I noticed oldblue's reference to the JB update for the 3/4G Xoom...is there an .RUU for that somewhere? I don't really want to root my MZ600 3G Xoom, but I would like the JB update. Is that a viable option here? Sorry this is a bit off topic, but I didn't realize there was a leaked build for it.
[Xoom General] oldblue910:
Unfortunately there isn't. The leak is a nandroid backup that was created using an old, outdated recovery. You'd have to unlock your bootloader.
[Xoom General] tumpy:
I have three rom that i load on my 3G xooom, when there is anything new coming out for xoom wifi only i use my 604 wifi backup, when a yankeeys game is on and the wife is looking at the tv i will load my Verizon 3g jb so i can use timewarner app to see the yankeeys game, my daily rom is CM10.. i never lock my bootloader it is a waste of time doing so you can still get all update with it unlock only my cm10 rom is rooted..
[Xoom General] Spogatz:
I agree. I am on my JB Xoom right now.
[Xoom General] DsturbD:
yeah i agree too, i feel with all the hype about JB there would have been some cosmetic changes to set it apart. to be honest it seems more liken upgrade for ICS than a new version. they named all the 3.x releases honeycomb, maybe all the 4.x ones should be ICS, then name the 5.x series JB
[Xoom General] oldblue910:
So now that Verizon, Google, and Motorola finally managed to get 4.1.2 out the door for the CDMA/LTE variants, I went back and revisited this thread. I still stand behind this post 100%. With that said, however, it was nice to see that #3 is no longer an issue since it's now available in the Play Store.

Because the original post was written when 4.1.1 was still current, I now have a fifth bullet point to add, which is specific to 4.1.2...

5. In Android 4.1.2, Google added the ability to expand notifications with one finger instead of requiring a two-finger pinch-to-zoom gesture like 4.1.1 did. That feature made it to the Nexus S, Nexus 7 and Galaxy Nexus but was left out of the Xoom builds. Go figure.

In retrospect, the Xoom really only got Jelly Bean because the Nexus 10 wasn't ready yet. The Android team knew that they were completely overhauling the 10" tablet interface and scrapping the Honeycomb-style interface altogether. This made Android 4.1 on the Xoom nothing but a stopgap to hold them over until the N10, and by extension the new interface in Android 4.2, was ready. For that reason, it's no wonder that Google put so little effort into making Android 4.1 a polished experience on the Xoom.

While it may be lacking visually and functionally compared to other devices that got the update, one thing is still for certain...Jelly Bean made the Xoom run as fast and smooth as it ever did and that's an excellent note on which to end support for such a great device.
[Verizon Samsung Galaxy S III] pnt1402:
I read this thread http://xdaforums.com/showthread.php?p=16635544#post16635544 !! But there are so many things I can't understand (not really good at English, especially technology terms :( )

So is there any easy way to install Supercharger on my ICS 4.0.4, what to download, how to install ?

Thanks all.
[Verizon Samsung Galaxy S III] pdinphx:
My bad ... thought I was still in the S3 forums.
[Verizon Samsung Galaxy S III] goddie392:
I need help too, can't seem to understand the supercharged guide on how to install it
[Galaxy S II Q&A, Help & Troubleshooting] jonjem_86:
hi..i just want to know if the jellybean 4.1 for galaxy s2 i9100 available now in the philippines..thank you..
[Galaxy S II Q&A, Help & Troubleshooting] TheATHEiST:
JB isnt available for ANY Galaxy S2 yet apart from unofficial builds/ports.
[Galaxy S II Q&A, Help & Troubleshooting] Jokesy:
OMG! Why did you open a double thread on a useless topic?

Is one thread not enough?
[Asus  Eee Pad Transformer Prime] noob_2010:
For example like a blackberry charge would charge most motorolla phones. Most HTC CHARGERS also fits some LG phones.......So the thing is i'm looking for other chargers that will also charge the Prime. I'm out of country and they dont have any transformer primes here so I'm wondering is their another device that also takes the SAME CHARGER as a transformer prime. Maybe Samsung Galaxy Tab?
[Asus  Eee Pad Transformer Prime] orcnd:
http://dx.com/s/tf201

i bought charger from dx. works well
[7" Kindle Fire HD Q&A, Help & Troubleshooting] sajaldash:
Hi

I have almost zero knowledge on android devices. Recently I wanted to install jelly beans on my kindle fire. I followed a "how to..." video. Using Kindle Fire Utility Kit, I first rooted my tablet, then installed google apps and then I installed TWRP. Using TWRP I installed a jelly bean (CM10) ROM. But, in this process, I did not back up my original kindle fire OS. The installation was successful. But, I wanted to go back to Kindle fire's original OS. So, I sent kindle fire OS 6.3.1 upgrade (by changing the extension to .zip from .bin) to the root. Then using TWRP, I installed kindle fire 6.3.1.

Now, the kindle fire home screen appears, couple of error message pop us (Sorry! The application Calendar Storage (process com.android.providers.calendar) has stopped unexpectedly. ) and then reboots. It goes on and on. I can no longer access TWRP. WhenI try to reroot the device, the program in my computer just sits indefinitely waiting for the device.

So, folks, is there a way, I can get my back tablet? Any suggestion will be highly appreciated.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] timurg:
What device exactly do you have kindle fire or kindle fire HD? If first, it's a wrong forum, if other... there are no custom recovery for HD yet, so try to do a factory reset first.

Sent from my KFHD rooted
[7" Kindle Fire HD Q&A, Help & Troubleshooting] sajaldash:
Kindle Fire. Apparently I am in the wrong forum. Thanks for your reply though.
[Android Q&A, Help & Troubleshooting] makrand96:
So far i have managed to root my device, but i cannot find any method to customize the theme or anything like that.. i cant even find custom roms.. can someone please helo by pointing out some themes or roms which are compatible?
[Android Q&A, Help & Troubleshooting] makrand96:
edpilo another

and how do i unlock my bootloader (full s-off)?
[Galaxy S II Q&A, Help & Troubleshooting] jonjem_86:
hi..i just want to know if jellybean 4.1 available now in galaxy s2 i9100 at the philippines..thank you
[Galaxy S II Q&A, Help & Troubleshooting] Orkane1989:
Wow have heard about searching?

JB is not out for any country and won't be for a couple months at the very least. You should try giggling s2 jelly bean update... I'm sure the first sites that pops up will tell you this.

Sent from Jelly Fuelled SGS2
[Galaxy S II Q&A, Help & Troubleshooting] Omaxe:
According to SamMobile JB will be out on November

Peace

Hit Thanks & It will Disappear

Sent from S II Running Fully Modified Official ICS 4.0.4

Next Device: Upcoming Nexus
[Galaxy S II Q&A, Help & Troubleshooting] Jokesy:
Next time search the forum very well first before opening a useless one.

People have already answered your question but i seriously don't understand how you missed this sticky thread

Edit: OMG! Why did you open a double thread on a useless topic?

Is one thread not enough?
[Galaxy S II Q&A, Help & Troubleshooting] lexyzmass:
Update Samsung Galaxy S2 I9100 to Official Jelly Bean AOKP custom ROM

There is "Update Samsung Galaxy S2 I9100 to Official Jelly Bean AOKP custom ROM" ... search it in google.
[Galaxy Note GT-N7000 General] thomasvdalen90:
Easy Guide to Root youre gNote and flash a custom rom!

Approximate Time for Newbies: +/- 30 min.

I am not responsible for any damage ony oure device, by reading further youre warrenty is now avoid!

All respects for those that learned my to do this.

Recommended Roms: ParanoidAndroid Imilka, ParanoidAndroid Utacka

Recommended Kernals: HydraCore Kernal 4.3b

if you ever get tired of youre flashed Rom just start with this again in exact way and to be very safe always head back to Gingerbread Original OS before flashing new ROM

CWM: YOU NEED TO FULLWIPE FIRST IF YOU ARE COMING FROM CUSTOM ROM

a. (vol.up+home+power button)

b. Select wipe data/factory reset & wipe cache partition

1. INSTALL SAMSUNG KIES AND CHECK FOR UPDATES

direct link

2. START FROM STOCK ROM

a. Use Odin to GB flash to stock GingerBread odin here

b. Reboot Note in download mode (vol. down+home+power buttons) and then connect

c. PC odin ID:COM turns yellow (ALL THE BEST NOW..!!!)

d. Download youre desired stock gingerbread rom below

d. Auto Reboot and F.Reset Time ---> Ticked and all Others --> Unticked, Click PDA and select the stock gingerbread rom downloaded

f. (vol.up+home+power button) wipe data/ clean cache

2. ROOT YOUR DEVICE

Which kernel You have?

(Go to Settings -> About phone -> Kernel Version. Note the string present there: 2.6.35.7-N7000XXKJ4-CL641703 Here Red is kernel version)

Now download tool from below according kernel you have.

I have Kernel KJ1 - Download This– and Extract

I have Kernel KJ4 - Download This - and Extract

I Have Kernel KJ6/KJ7/KJ8 - Download this - and extract

I have Kernel KK1/KK2/KK3/KK4/KK5 - Download This - and Extract

I have Kernel KKA - Download This - and Extract

I have Kernel KK9 - Download This - and Extract

I have kernel KL3 - Download This - and Extract

I have Kernel KL1 - Download This - and Extract

Not in the list? forget this step and follow this guide for the rooting part. Rooting

Before u begin:

(1) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(2) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(3) [OPTIONAL] increase screen timeout to 10 minutes
(4) Close kies SW completely, close if any antivrus SW running

Procedure :

a. Connect device to PC

b. Execute "not-rooted-yet.bat" and follow the instructions.

c. Device will reboot after successfull root, and you can see superuser and CWM application in drawer.

3. INSTALL SAFE KERNEL

a. got to cwm (vol.up+home+power button)

b. select Kernel and select the HYDRACOREKERNEL download here 4.3b is stable! (or take another safe kernal)

c. Device will reboot

d. Voila..You are now EMMC bug free.

4. WIPE DATA

a. Reboot to recovery (vol.up+home+power button)

b. Select wipe data/factory reset & wipe cache partition

5. FLASH ROM

a. Reboot to recovery (vol.up+home+power button)

b. Select Install zip from Memory or sdcard

c. 1st select youre custom rom

d. Then select Gapps

e. Reboot
[Galaxy Note GT-N7000 General] thomasvdalen90:
reserved@ thomasvdalen90
[Galaxy Note GT-N7000 General] thomasvdalen90:
reserved #2 @ thomasvdalen90
[Galaxy Note GT-N7000 General] sahilarora2003:
We already have it. And don't try to make duplicate threads which have no means..

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

Reported.
[Galaxy Note GT-N7000 General] thomasvdalen90:
its not noob friendly mine is made in the eyes of a noob
[Galaxy Note GT-N7000 General] oka1:
Please do not copy others work and then repost...... it is unnecessary and it is impolite to the original posting member...........

.............THREAD IS CLOSED...........
[Sprint HTC EVO 4G LTE] detatched:
I'm looking for a Bluetooth earpiece that will do phone commands and such. Has anyone used one with an LTEVO? Some feedback would be nice. Reviews on Amazon are kind of all over the place. Thanks!
[Sprint HTC EVO 4G LTE] toastman74:
I used it for a long time and i loved it and voice commands worked great with no settings adjusted in any way at all. i highly recommend that earpiece. the only reason i sold mine was to try the bose one and while voice clarity was awesome the earpiece itself sucked.
[Sprint HTC EVO 4G LTE] bog3nator:
i have the jawbone era and it does everything i need it to
[Verizon Samsung Galaxy S III] Brian Gove:
I don't see why people are having such an issue with blocking the update. I just had to Odin back to stock because of some issues with eclipse ROM and the update downloaded. I panicked and tried stopping it as it was downloading with no luck.(I didn't want to have to re-flash again). I couldn't stop it but when it finally downloaded it asked me if I wanted to install it now or defer it to a specific time. Obviously I deferred it to way in the future and wen't along with my flashing of custom ROM's lol.

Now that I have experienced a taste of the OTA I have no clue why everyone that has gotten it is scared about it. Defer it and keep your phone the way it is... lol.
[Verizon Samsung Galaxy S III] PaulG1488:
This could have easily been posted in one of many ota threads rather than make a new one.

Sent from my Galaxy SIII
[Verizon Samsung Galaxy S III] leroybrute:
Thats the reason he started a thread. Because there are so many ota threads no one would ever find this post.

OP didn't deserve being flamed but you do for such a lame post.
[Verizon Samsung Galaxy S III] Brian Gove:
Oh, you mean 1 of the 20 other posts made about the same subject??? Is that what you mean?

Thank you for sticking up for me, but I made the thread to be a smart A$$ about how many OTA update threads there are...