yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] Yakuzahi:
I just bought the new 32 GB Nexus 7. When I came home and set it up, the tablet did a quick update. When it came back up, I got a message that a new system update was available and when I clicked on the icon it said Jelly Bean 4.3. I was surprised because I thought that the new Nexus 7 came with 4.3. I did the update anyway, and when the Nexus booted back up, it froze. It has now been on the Nexus logo for more than 10 minutes.
[Nexus 7 (2013) General] sfhub:
It came with 4.3 but it had developer keys instead of release keys. That first update while you initially set it up was to switch to release keys.

The 2nd update was to upgrade you from 4.3 JWR66N to 4.3 JSS15J.

If it stays stuck on the X for a while, boot into recovery and do wipe data/factory reset.

If you aren't familiar with booting to recovery on this particular device see this post:

[Info] Guide to entering safe mode, bootloader, stock recovery
[Nexus 7 (2013) General] Yakuzahi:
Thanks, in the end I just power it down and restart it.
[HTC Incredible S] jaspreet13:
Hi All,

I have unlocked my incredible s via htcdev, and s-on, now after flashing rom my phone is stuck on htc splash screen :eek:

i have tried recovery tool aswell still stuck splash screen

Is my phone gone ?

Thanks for any help
[HTC Incredible S] tpbklake:
You should have read and studied the procedure to unlock the boot loader and flash a custom ROM a bit more carefully!

The step you are missing is that you will need to manually flash the ROM's boot.img in FASTBOOT USB mode.
[HTC Incredible S] 072665995:
Dang beat me too it. What he said ^^^^^^^^^^^^
[HTC Incredible S] jaspreet13:
Thanks for quick reply

Firstly just want to confirm is my phone still alive or gone ?

If can get any help to get it back to work
[HTC Incredible S] tpbklake:
Boot it into the boot loader by holding the Volume Down key and press the Power button.

Then you can enter FASTBOOT USB mode and flash the boot.img
[HTC Incredible S] jaspreet13:
Sorry for double posting

Sorry for double posting, was in panic state.. thats how i flashed rom by holding the Volume Down key and press the Power button.

right now the screen states unlocked in pink

s-on
[HTC Incredible S] tpbklake:
Yes, so you should be able to select FASTBOOT instead of RECOVERY to flash the boot.img.
[HTC Incredible S] jaspreet13:
yes i have selected FASTBOOT now FASTBOOT USB is highlighted In RED

can you help me with ROM i have tried 2 rom but still phones not passing htc logo splash screen
[HTC Incredible S] tpbklake:
Read the sticky posts on this forum for the information you need.

They will explain what you need to do to flash a boot.img file.
[HTC Incredible S] jaspreet13:
Just want to know phone can go on working status if i flash rom properly or phones gone ?
[HTC Incredible S] tpbklake:
As long as you can get into boot loader, you can bring your phone back to life.
[HTC Incredible S] jaspreet13:
Thanks thats bit relief, do i have to s-off to flash rom or can install on s-on, its htc incredible s
[HTC Incredible S] tpbklake:
I suggest to go back and read the procedure that you used to learn about unlocking via HTCDEV.com and flashing a custom recovery. That thread should have everything you need to know.

You can flash a ROM in your current state, but there is a documented step that you missed about flashing the boot.img file.
[HTC Incredible S] jaspreet13:
Phones Dead or what ?

yeaturday night i was able to access fastboot menu(bios) of android, i left my phone in night and now it doesnt turn on so i did some research as though battery may have got discharged( which was the case ) as was not gettin amber light on.

now amber light is there but phone is not turning on
[HTC Incredible S] pavankumarpingali:
you can install custom roms on your device...after installing the ROM, do not let the device to boot to the boot animation or whatever you call it..

Instead, boot to the bootloader...enter the fastboot menu (fastboot usb if your phone is already connected to your computer)...open a command prompt/terminal and type fastboot devices. If your device is recognized, the output would be your device's serial number...

Copy the boot.img file from the ROM's .zip file to some folder. open a cmd window in that folder/ navigate to that folder in cmd (if already opened)

type fastboot flash boot boot.img

if the boot.img is successfully flashed, you can reboot your device and you should be able to boot properly.

If you are s-on and unlocked via htcdev method, follow the above steps every time you flash a new rom.

If you are s-off, the above method is not needed. You can flash roms and use them without any hassle...

Hope this helps...

---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------

Looks like the battery has discharged completely. Allow the phone to charge for sometime and then try to turn on the device
[HTC Incredible S] jaspreet13:
Thanks Brother

my phone was working completly fine until i flashed boot image, i think this is what i have done incorrectly.

i have rom zip file on phones sd card and unpacked files of same rom my pc in a folder,

now what i understand is to first unpack and install rom from recovery and then flash from cmd ?
[HTC Incredible S] pavankumarpingali:
No, there is no need to unzip the zip file in your PC...only the boot.img file is required.

First install the ROM from the custom recovery and then boot into the bootloader by pressing the vol down button while the phone restarts. Then, flash the boot.img and you should be able to boot...

Hope this helps...
[HTC Incredible S] jaspreet13:
Oh shoot! thats what i did wrong,,..i just flashed boot img without installing rom from customer recovery and phone got stuck on HTC screen :silly:

i am waiting for phone to turn on which is not happening at all..
[HTC Incredible S] pavankumarpingali:
Charge it for an hour or so, then remove the battery, reinsert after 10-15 min and try to turn on the device again...sometimes soft reset works
[HTC Incredible S] jaspreet13:
do i have to relock bootloader before flashing rom and installing it
[Galaxy Note II Themes and Apps] tweeny80:
I saw this little Samsung widget from a You Tube video. My current ROM doesn't have it, I don't recall seeing it with past ROMs either. I searched this forum and don't see it here.

I hunted it down through Twitter of all places.

Maybe it's not included on N7100 .. anyway it's tested & works fine, lightweight. It clearly tells how many apps are active, clicking it leads to your built-in Task Manager.

It's an apk, just install normally.

https://dl.dropboxusercontent.com/u/87523367/Applicationmonitor1.0.5.apk

Cheers
[Galaxy Note II Themes and Apps] dbzgod:
This is made by Samsung and available through the the Samsung App store. They have newer release available 1.0.6

Sent from my SGH-I317M
[Galaxy Note II Themes and Apps] tweeny80:
Yes I know thanks, I searched through their store, couldn't find it! Care to post it?
[Galaxy Note II Themes and Apps] dbzgod:
I find Samsungs App store can be picky on the keyword, also they try to detect your device and determines weather or not it is compatible for the app. If it's not or unknown they don't display it. I think custom roms might have a issue in this regard lol.

Here's the new one.
[Galaxy Note II Themes and Apps] Blackie3:
Thanks for the link,mate :good:
[Galaxy Note II Themes and Apps] rayhodge02:
Thanks for posting this I couldnt find this as well:good:
[Galaxy Note II Themes and Apps] Hemant:
Thanks for the information and thread. Could you please tell whats the weather widget in your screenie?
[Galaxy Note II Themes and Apps] tweeny80:
Hi Hemant. Unless you live in New Zealand, this app won't suit you. It's a paid app by the NZ national weather service, only shows weather for NZ.

Cheers
[Galaxy Note II Themes and Apps] SIMO.69:
this widget wont work on custom roms do you no how to get it working on RemICS-JB_v5 rom as its one of them widgets that's a must have ive read and tried loads but still cant get it working any help would be great thanks in advance
[Galaxy Note II Themes and Apps] dbzgod:
Sorry I don't know how to get it to work on custom roms, my guess is the widget needs specifics from Samsung touchwiz roms possibly the framework that Samsung uses or could be the kernel, but I honestly have no idea.
[HTC EVO 3D] dastin1015:
| CyanogenMod 10.2 - Android 4.3.1 - Jellybean |

​

#include
/*
* Your warranty is now likely void.
*
* I am not responsible for bricked devices, dead SD cards,
* spontaneous combustion, or any other host of cosmic penalties
* which may befall you, your family, or your phone.
*
*/

Built from CM source

Service

Text

Call

Audio

WiFi

Google Now

Bluetooth

GPS

MMS

Video playback

Audio playback

Camera

Camcorder

UMS

Data

You tell me

4G WiMAX

Standard CM 10.2 issues.

I don't have an activated device so I can't test everything and I'm paying for college out of pocket so no accessories.

Do NOT use superwipes

Any HBOOT lower than 1.57

S-OFF

Very latest 4ext recovery

Have latest Sprint firmware installed.

Wipe everything except sdcards

Flash ROM

Flash GAPPS

Reboot

???

Profit

To enable Developer Options and Performance go to Settings, About Phone and repeatedly press Build Number.

If you use ADB read this: PSA by CM

If you use reboot to recovery read this: PSA by CM

Regarding new Superuser: PSA by CM

Read the FAQ thread here before posting any questions in this thread: FAQ

First and foremost my girlfriend Monica for supporting me and encouraging me along the way as well as being the best girlfriend I could ask for!

Everyone who contributes to CM as this is based on their hard work!

EpicCM as I expanded their work to make it work for CM 10.1!

NineInchNails for being an awesome dev partner, moral support and friend!

Albinoman887 for being an awesome dev partner and friend!

NV-LTE for being an awesome dev partner and for the OP banner!

Preludedrew for his support and mentoring!

Abadasstanker69 for the hosting!

The Fer-Shiz-Nizzle for allowing me access to a working line to test all capabilities!

All my supporters!

Donation Link
[HTC EVO 3D] dastin1015:
GAPPS: Here

Netflix Workaround: Here

Kernel source for GPL

Kernel: https://github.com/Team-Hydra/android_kernel_htc_msm8660

Repo: https://github.com/Team-Hydra

Toolchain:

$ ./arm-eabi-gcc --version
arm-eabi-gcc (GCC) 4.7
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

The name of this ROM comes from A$AP Ferg's newest single Hood Pope.

[YOUTUBE]GtNqtgL754I[/YOUTUBE]

| Oct. 21, 2013 |

JLS36I (4.3.1)

Fix boot for Japanese KDDI Evo 3D (shooterk)

Fix Bluetooth tethering

Fix Torch

Kernel: Linux 3.0.100

CM upstream: Here

| Oct. 1, 2013 |

JLS36G

Add suppport for Japanese KDDI Evo 3D (shooterk)

Data / WiFi handoff working completely

Kernel: Fix network traffic indicators

CM upstream: Here

| Sep. 14, 2013 |

Camera code cleanup

Working data

Vibration and hardware light tuning

Kernel: patch to 3.0.94, enable CPU freq scaling sync across all cores

CM upstream: Here

| Sep. 1, 2013 |

Camera bugs

Fix camera again

JSS15Q

CM upstream: Here

| Aug. 23, 2013 |

Fix up WiFi

Data (hopefully)

CM upstream: Here

| Aug. 12, 2013 |

Camera

Camcorder

UMS

CM upstream: Here

| Aug. 10, 2013 |

Initial release

CM upstream: Here

| Oct. 21, 2013 |

Shooter (Sprint) ROM: thinktankdesigns.org/dastin1015/shooter/HOOD-POPE-10212013-shooter.zip

md5sum: 2485129e74b63f9de0a8776429b86a8f

Shootervm (Virgin Mobile) ROM: thinktankdesigns.org/dastin1015/shootervm/HOOD-POPE-10212013-shootervm.zip

md5sum: 9b4c17725d85b93263a38b3b577cf833

Shooterk (KDDI [Japan]) ROM: thinktankdesigns.org/dastin1015/shooterk/HOOD-POPE-10212013-shooterk.zip

md5sum: fdf35f0e36d99f12e2a583426aa3dde9

| Oct. 1, 2013 |

Shooter (Sprint) ROM: thinktankdesigns.org/dastin1015/shooter/HOOD-POPE-10012013-shooter.zip

md5sum: cbca0fb08a1d459d10686f932b01f828

Shootervm (Virgin Mobile) ROM: thinktankdesigns.org/dastin1015/shootervm/HOOD-POPE-10012013-shootervm.zip

md5sum: 58169b62137d4d19583f1e14d027677d

Shooterk (KDDI [Japan]) ROM: thinktankdesigns.org/dastin1015/shooterk/HOOD-POPE-10012013-shooterk.zip

md5sum: 2592b1feef01f4b75d073634e530717d

| Sep. 14, 2013 |

Shooter ROM: thinktankdesigns.org/dastin1015/shooter/HOOD-POPE-09142013-shooter.zip

md5sum: 47e5354f16f6512e421cc0edb4960181

Shootervm ROM:

md5sum:

| Sep. 1, 2013 |

Shooter ROM: thinktankdesigns.org/dastin1015/shooter/HOOD-POPE-09012013-shooter.zip

md5sum: 57a043e5da16f905743ffb181b6875bc

Shootervm ROM:

md5sum:

| Aug. 23, 2013 |

Shooter ROM: thinktankdesigns.org/dastin1015/shooter/HOOD-POPE-08232013-shooter.zip

md5sum: 5af832b2d39cb19730538e6953eeef2b

Shootervm ROM:

md5sum:

| Aug. 12, 2013 |

Shooter ROM: thinktankdesigns.org/dastin1015/shooter/HOOD-POPE-08122013-shooter.zip

md5sum: d1aa61c7afc25fffa0e014f206b44338

Shootervm ROM: thinktankdesigns.org/dastin1015/shootervm/HOOD-POPE-08122013-shootervm.zip

md5sum: d990a10e8d4d5ecf8db70d653f53c454

| Aug. 10, 2013 |

ROM: thinktankdesigns.org/dastin1015/shooter/HOOD-POPE-08102013-shooter.zip

md5sum: bab2150110bfab2dd73a199d488be03c
[HTC EVO 3D] xiton:
Super excited. Thank you!
[HTC EVO 3D] mattcoz:
Woo! This phone ain't dead yet! You rock!
[HTC EVO 3D] #WB:
aye mayne.
[HTC EVO 3D] gunfromsako:
Firing up Evo3d from the dead thanks buddy!
[HTC EVO 3D] Ryuk666:
Woo!!! I was wondering when you guys would come out of hiding with this one ;) so stoked to try. Thanks for your hard work guys :)
[HTC EVO 3D] Hedied4me:
Good looking out Dastin!!!
[HTC EVO 3D] gonk24:
Oh. Hell. Yes
[HTC EVO 3D] Flashalot:
Looks like some one put in "Work" :) with this ROM

Downloading now good work wish you had a one s
[HTC EVO 3D] HideTheCookies:
thanks for all the hard work!! trying now let you know how it goes.

*cant get to boot just white htc screen
[HTC EVO 3D] HappyBirthday:
Hellllllllzzzzzzzzyyyyyyeeeeaaaahhhhh
[HTC EVO 3D] hossman:
would not boot past splash screen for me.

I'm on vm.

Hboot 1.50.5050
[HTC EVO 3D] muziling:
I can boot into system , THX & TESTING
[HTC EVO 3D] jlmancuso:
Sprint 3vo - eng-hboot - 2.89 firmware

Is booted. Checking out features now.

Edit: native superuser works. Es file explorer 3.03 force closes after enabling root access but stock cm file manager works with root access.
[HTC EVO 3D] cityeyes:
Same Hboot here, same problem.

Sprint phone on 1.50.5050, can't get past the HTC screen.
[HTC EVO 3D] dastin1015:
Go to a lower HBOOT, lastest firmware and verify you have the latest 4ext recovery

私のONEから送信される。
[HTC EVO 3D] muziling:
Does menu & back button work?
[HTC EVO 3D] wigginst:
Looking forward to seeing the progress here!
[HTC EVO 3D] cityeyes:
Thanks! I'll try that out and get back.

Edit: Ok, dropped the HBOOT down to ENG, have the latest firmware. Pretty sure I'm very nearly on the newest 4ext, but I'm restoring my Nandroid to re-check that fact. Still getting reboots on the newest version so far though.
[Galaxy Grand Duos i9082 Accessories] simplyanin:
Total post count 12 .....

Total thread count 12 .....
[Galaxy Grand Duos i9082 Accessories] rejocie001:
Nice one.. :thumbup:

Sent from my GT-I9082
[Galaxy Grand Duos i9082 Accessories] athulpmenon:
You create a whole new thread for every doubt you have????:confused::confused:
[Galaxy Grand Duos i9082 Accessories] aaa111sss:
Hi Grand does not Support MHL Cable,

reference for you.

http://www.mhltech.org/productlist/mobile-devices/
[MDA II, XDA II, 2060 ROM Development] ibeqa:
I read text message at the ftp site and I just want to know will those files be deleted or what? I'm using diamond rom for the moment but I would like to have the WM2005 rom just in case I decide to upgrade.

Thanks.
[MDA II, XDA II, 2060 ROM Development] dragon_soft:
http://xdaforums.com/viewtopic.php?p=131769#131769
[Galaxy S 4 Q&A, Help & Troubleshooting] DannySchaukens:
Hello,

Can I disable the home button for activity so it doesn't wake up the phone?

Just the power button hqs to wake up the phone.

Any ideas?

thx a lot!!!

--- Send from my phone ---

GRTZ FROM BELGIUM! Danny Schaukens Service.
[Galaxy S 4 Q&A, Help & Troubleshooting] vpwrf:
1) Open Root Explorer

2) Navigate to: /system/usr/keylayout/

3) Press 'Mount R/W'

4) Long hold 'gpio-keys.kl' and choose "Open in Text Editor"

5) Remove "WAKE" from the line "key 172 HOME WAKE"

6) Back out, Save, Reboot
[Galaxy S 4 Q&A, Help & Troubleshooting] DannySchaukens:
TOP!!! :good::good:

THX FOR THE INFO!

Grtz!
[Samsung Galaxy Nexus] stevensoaj:
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->

https://code.google.com/p/android/issues/detail?id=58230

If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.

Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.

Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.

Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.

Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.

First we will create a Task called "Wifi fix." This task will have 2 simple actions.

Disconnect Wifi

Reconnect Wifi

Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."

This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.

First we will use Wifi State Connected, with the Invert Checkbox checked

Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.

Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.

After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.

Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.

Theory:

Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.

Hope this helps some of you!
[Samsung Galaxy Nexus] geckocavemen:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
[Samsung Galaxy Nexus] NCguy:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
[Samsung Galaxy Nexus] stevensoaj:
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.

I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
[Samsung Galaxy Nexus] diesel2k:
http://xdaforums.com/showthread.php?t=2380403

Sendt fra min Nexus 7 med Tapatalk2
[Samsung Galaxy Nexus] Nexusaurus:
What I really wanto to know if this issue is posted in the official google bugs tracker
[Samsung Galaxy Nexus] stevensoaj:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
[Samsung Galaxy Nexus] Nexusaurus:
Expose your case here:

https://code.google.com/p/android/issues/list

Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
[Samsung Galaxy Nexus] FlickFlack:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.

Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:

The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.

Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
[Samsung Galaxy Nexus] Big ZD:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
[Samsung Galaxy Nexus] FlickFlack:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
[Samsung Galaxy Nexus] Big ZD:
I stand corrected. My apologies for not reading more thoroughly.
[Samsung Galaxy Nexus] stevensoaj:
OP edited with link to Official Google Bug tracker, thanks for finding this!

I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
[Samsung Galaxy Nexus] FlickFlack:
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.

For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
[Samsung Galaxy Nexus] memnoc:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
[Samsung Galaxy Nexus] stevensoaj:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.

As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
[Samsung Galaxy Nexus] stevensoaj:
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?