yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] itchyro001:
dead phone.. no power

Good day sir.. my problem is my cherry mobile flare XL is dead..i can't switch on now ,.and i try to charge, but no light in my phone.. it cause by flashing scatter file for flare.. hope you help me
[Android Q&A, Help & Troubleshooting] lance1987:
good day,, i have a problem, my flare s3 dead boot,not charging,cant turn on, not detect on computer, is there anyway to fix my phone?
[Android Q&A, Help & Troubleshooting] Jay4ü:
not working! I tried on XP SP3 /7/8/10 32 bit. It says cookie not recieved! help!
[Android Q&A, Help & Troubleshooting] ennivek005:
why i cant download coc on my CMF s3 octa even hard reset is not working using power button and volume up somebody please help?
[Android Q&A, Help & Troubleshooting] EJ822:
cm flare j2s v2

guys kindly help me with bricked flare j2s v2 I cant find a stock rom need badly please pips
[Android Q&A, Help & Troubleshooting] hatha:
Bro, sorry pero dinadala ako sa Mediafire.com kapag pinipindot ko ang Download "here" pano ba yan boss?
[JAM, MDA Compact, S100 General] alexfendi:
hi everyone. i have come across the magician radio 1.13 file in this forum and i was wondering...... if i could do this upgrade on my phone. i am using the xda mini and here are my current configurations:

rom version: 1.11.00 wwe

rom date: 03/14/05

radio version: 1.11.00
[JAM, MDA Compact, S100 General] John R:
Yes you should be able to, look out for Rom 1.12 as well. :wink:
[JAM, MDA Compact, S100 General] alexfendi:
one more question before i decide to go on with the upgrade. im currently located in Indonesia. Are you sure i can do this radio upgrade? is this radio upgrade good for all magician, mini, mda compact and such or is this upgrade country or operator specific?

thanks for the reply. i just need to make sure before i do this upgrade because i have read some pretty terrifying upgrade stories in this forum.
[JAM, MDA Compact, S100 General] John R:
This upgrade is not operator/country specific. But like all upgrades it is your choice to do it. (But worth it).This is how I got my radio 1.13, from the forum.
[JAM, MDA Compact, S100 General] huyvan:
U Go here (xda/xda)

ftp://ftp.xda-developers.com/Magician/Radio/MagicianRadio_1.13.00_maupgrade.zip

Have fun
[JAM, MDA Compact, S100 General] alexfendi:
Okay guys, thanks for all of your help. i think you guys just gave me that little extra boost i needed to feel comfortable trying this upgrade. im downloading the file now and will install it soon.

once again, thank you very much!
[G2 Q&A, Help & Troubleshooting] burningembers:
Since day 1, despite factory resets and freezing bloat, my LG G2 has experienced some *insane* wakelocks around NlpCollectorWakelock and NlpWakeLock. We're talking about 2 hours every 10 hours or so of uptime, basically destroying my battery life.

Now, the simple fix for this is to turn off Wifi/Mobile Network Location, voila, phone deep sleeps, life is good. Except this doesn't fly for me, because I still want to use Google Now, and I can use it just fine on my S4 without this insanity.

To get a little better insight, metric-wise, I pulled Velvet.apk from /system/app and self-installed Google Search straight from the market (essentially Google Now) so that I could keep tabs on it in Greenify.

Turns out Google Search was running as much as 200 times per hour and causing wake-up ~5-10 times per hour. I could practically refresh and just watch the count go up and up.

So on a whim, being rooted and a little bit of a risk-taker, I used Titanium Backup and uninstalled Google Play Services. Null. Gone. Kaput.

Then when I launched Google Now again, it requested I nab Google Play Services from the market. So I did. I installed, rebooted.

To my surprise, in the last five hours since doing that, Google Search has run 12 times, and woken up 12 times. Better Battery Stats is reporting NlpCollectorWakeLock at 2 minutes and 8 seconds for ~5 hours uptime, and NlpWakeLock at 2 minutes and 43 seconds.

Anyone else want to take the dive with me and see if this gives them as significant of a before/after as it did for me? My phone is deep sleeping like a champ now and I really hope this keeps up.

tl;dr: Uninstall Google Play Services from /system/app using Titanium Backup, launch Maps or Google Now and then re-install Google Play Services from the market. Reboot. See if location service related wakelocks drop significantly. Rejoice if they do. Lament further if they don't.
[G2 Q&A, Help & Troubleshooting] lastdeadmouse:
Well, I removed Google play services and installed via market this morning. I'm still seeing a ****load of NLP wakelocks, but on the att version I haven't figured out how to completely remove search. Could that be the issue?
[G2 Q&A, Help & Troubleshooting] burningembers:
Oops, I guess I forgot to mention that I also removed Velvet.apk from /system/app (LG's pre-installed Google Search), and reinstalled that from the market as well. Not sure if that is related.

I, too, have the AT&T version. I will run some more tests today. But so far today with 1 hour screen-on, I have an up time of a little north of 2 hours, with an estimated 60 hours remaining. Obviously that isn't realistic, but by this time before I would be seeing an estimated time of about 9 hours remaining and be sub-90% battery life.
[G2 Q&A, Help & Troubleshooting] lastdeadmouse:
I have no velvet.apk in /system/app

I've been trying to get the market's search installed for the widget for days, lol.
[G2 Q&A, Help & Troubleshooting] zxrax:
I don't have a velvet.apk either but I just did what you did aside from that. We'll see how things go.
[G2 Q&A, Help & Troubleshooting] burningembers:
Weird! I wonder why I have/had a Velvet.apk.

Anyway, since my initial post, I've continued monitoring. My runs/wakes are WAY down, trending to about 1-3 per hour, down from a crap ton. My overall wakelock time is roughly 20 seconds per hour, or roughly 8 minutes or so per day, way down from nearly 2 hours/day before. My battery life has gone way up, I'm super happy.
[G2 Q&A, Help & Troubleshooting] kjplaysguitar:
will not uninstall

Tried to do the same with the Verizon G2 and when trying to uninstall this i get a message from titanium back saying it will reboot twice for this to complete, but upon first reboot it boots in to team win recovery? how do i get this complete its process because Google services is always the highest on battery usage on my phone.
[G2 Q&A, Help & Troubleshooting] burningembers:
Huh, unfortunately I'm on the AT&T, so it is hard for me to comment.

When I did it via TB, it uninstalled in the same session, no reboot. No notification about rebooting twice.

Any other VZW users out there that can comment?
[G2 Q&A, Help & Troubleshooting] zxrax:
After an hour of idle time my time held awake by NLP wakelocks specifically is only three minutes, a far cry from the eight to ten I was seeing earlier. Will continue to monitor.
[G2 Q&A, Help & Troubleshooting] Geekybiker:
Do you have google search to uninstall in titanium backup? I'd try that if you can't find the APK. I had it in my /system/apps and did the uninstall in TB.
[G2 Q&A, Help & Troubleshooting] zxrax:
I already uninstalled Google search via TB, should I still see this velvet.apk?
[G2 Q&A, Help & Troubleshooting] iowabowtech:
I'm on vzw and didn't have a problem deleting Google Play Services. Wakelocks are way down for me too since using the Play Store version. Good find. I was noticing very high wakelock on this for the last several days.
[G2 Q&A, Help & Troubleshooting] zxrax:
OP, what are your settings on these three pages?

http://imgur.com/a/jc8lo

I'm still getting a ton of wakelocks. Not as much time spent held awake but nowhere near as low down as 1-3 wakes per hour . In 1h48m of non-screen time (out of the past 2h23m), I've got NLPCollectorWakelock waking my device 82 times for ~4 minutes of time held awake and NLPWakelock waking my device **284**(!!) times for 3 and a half minutes of time held awake...

EDIT: just uninstalled an app called "LGSearchProvider.apk" using Titanium Backup. Perhaps this is the same thing as the velvet.apk you were talking about earlier by a different name?
[G2 Q&A, Help & Troubleshooting] burningembers:
Nope, Velvet.apk was the /system/app's Google Search from factory.

My settings match yours except I have Remote Wipe ability turned off, I still have my phone reporting a location to ADB, though.

Since my last post, I've seen a huge uptick in Google Search runs in Greenify (about 100 in an hour). However, only 5 wakes, and only 26 seconds of wakelock in that same hour. Will report more later.
[G2 Q&A, Help & Troubleshooting] akong702:
I uninstalled the search, and Google play services, restarted, reinstalled, and restarted again. So far this is what I have is it normal?
[G2 Q&A, Help & Troubleshooting] burningembers:
I'm not sure there. It looks like you just have some initial Audio wakelocks from maybe a music player or your start-up noise.

You should check Android System or Google Services for things related to NlpCollectorWakelock or NlpWakelock.

---

Updates on my own report. For some reason Google Keep has shot to the top trending at 4 minutes/hour of wakelock time. I have no idea why, I'm not actively using it, or its widget. I'm greenifying it now to get rid of the noise.
[G2 Q&A, Help & Troubleshooting] zxrax:
Well, in 1h50m of uptime (30m screentime), according to GSam, NlpCollectorWakelock has kept my phone awake for ~6m. It's the only thing under Google Services that's kept my phone awake longer than 30 seconds. Nlpwakelock is virtually nonexistent, 9.8s of awake time.

edit: when i click 'manage' on GSam on the "Google Services" that's causing wakelocks it takes me to Google Bookmark Sync in particular. Coincidence? I froze bookmark sync since it's something I don't use anyways, we'll see what happens...I don't see how it could possibly be the culprit but you never know.
[G2 Q&A, Help & Troubleshooting] burningembers:
Interesting. I hadn't gone that deep via GSam, I may do it now though just to see. Good call.

edit: Mine just takes me to Google Services, sad panda.
[G2 Q&A, Help & Troubleshooting] NegativeOne:
nlpcollectorwakelock is google services, not google play services for me...
[G2 Q&A, Help & Troubleshooting] thanasisc4:
I have the T-Mobile variant and wanted to confirm that OP's instructions fix the issue. My device started out with great battery life and one day suddenly took a dive thanks to this issue.

I used TiBu to uninstall Google play services and Google search (which turned out to be velvet.apk) and reinstalled both via play store.

Screen went back to bring number 1 battery drainer for me whereas before Google pay services was in the lead by a wide margin.

Thanks OP.
[HTC Rezound] scy1192:
I'm getting no voice nor data signal except for roaming. Wiping the ROM and flashing a different one (I tried CM9, currently on CM10.1) didn't help. I fear for the worst, because RUU-ing isn't an option since Fastboot isn't working for me at all so I can't re-lock. Anyone have any ideas?

edit: What I did: made a Ubuntu live USB drive. Fastboot worked on Ubuntu so I was able to RUU. RUU fixed my problem.
[HTC Rezound] REV3NT3CH:
tell me step by step what your doing when trying to fastboot...ill resolve this for you...also are you verizon or gsm carrier?
[HTC Rezound] scy1192:
Verizon. Basically with Fastboot, Windows says "USB device not recognized", and device manager says "Device enumeration failed". Multiple OS installs, multiple USB ports, multiple computers. From what I can tell, Fastboot ain't gonna work anymore. I'm currently on Windows 8.1 with Koush's universal drivers installed, and using the Android SDK that came with Android Studio. Going to try the latest Sense 3.6 stock ROM and see what happens.
[HTC Rezound] REV3NT3CH:
no rom will fix it....its your drivers.....if you have access to windows 7 its preferred as 8 can be very buggy with drivers not specifacally meant for it....let me get them for you give me a few
[HTC Rezound] scy1192:
I've tried it on a Windows 7 PC. ADB also works just fine with 8.1.
[HTC Rezound] REV3NT3CH:
ive used a different driver and adb works fine with them...and my device always reads....i tried koush's universal last year and they never worked for me

---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------

PM Me
[HTC Rezound] scy1192:
can't get any Sense ROM to flash either... I think I'm just going to put CM10.1 back on, hopefully when I wake up tomorrow it'll just have been a service outage in my area. If not, well... new phone for me I guess

edit: odd, Speedtest.net is showing that I'm on LTE (Verizon being the only one in the US with 700Mhz LTE) and my external IP address is in 70.0.0.0/8 which is a Verizon-owned address space. Maybe I am on Verizon but it just thinks it's roaming.
[HTC Rezound] Uzephi:
Try S-Off and RUU. You can on AOSP as long as you RUU right after (do not put PH98 RUU on SD card until after S-Off, I had to reformaty SD card).

I just recently ran JB 0.1 windows version while on 2.28 Hboot and Infection (CM10.1 based ROM). My boot partition went wonky, but I was able to downgrade RUU ad it fixed everything. With S-Off you have no worry about needing to do fastboot.
[HTC Rezound] scy1192:
Thanks, I'll try it out. I considered doing S-Off, but I wasn't able to get it back to stock. Now that I know it works, I'll try it.
[HTC Rezound] REV3NT3CH:
I have the proper drivers not koush's universal....quite a few people have had problems with those drivers and if I'm not mistaken s-off still requires the phone to connect through cmd prompt...it won't let me upload here so please pm me so I can help
[HTC Rezound] scy1192:
R3vent3ch, thank you for your offer but I think I got it. I was able to fastboot oem lock it using a Live Ubuntu flash drive (used this guide to install adb and fastboot). After I RUU, hopefully it'll work. If not, it's off to the Verizon store to see my options.
[HTC Rezound] scy1192:
Looks like the RUU worked
[HTC Rezound] REV3NT3CH:
glad you got it working bud
[Verizon Samsung Galaxy S 4] scott62185:
I was restoring one of my nandroids (of euroskank's CM 10.2) and it said it appears as if I'm not rooted and if I want to install super SU and I said yes. Then I got stuck on the Samsung splash screen. When I pull the battery it gives me this screen I've never seen before that says (paraphrashing) that installing a "custom OS" is dangerous and push volume up to do so and down reboot. I tried to install the "custom OS" and it just keeps saying "Downloading. Do not turn off target." But it just stays there.

I'm on MDK and TWRP 5.0.2
[Verizon Samsung Galaxy S 4] hexitnow:
Thats download mode, its used to flash stock firmwares using odin. Before you restored your nandroid did you wipe system, factory data reset, and wipe both cachea?

Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
[Verizon Samsung Galaxy S 4] scott62185:
Yes, I did all those things prior to restoring my nandroid...
[Verizon Samsung Galaxy S 4] vt0r:
This nandroid backup is likely not a good one, as seeing download mode at boot usually indicates a bad flash.

How many times have you tried restoring using the nandroid backup you have?

If you've tried multiple times with the same result (and you're sure you wiped data/cache/dalvik as well), you will probably need to flash a full tar.md5 image from ODIN (like a stock-rooted ROM, etc).
[Xperia Play General] deepa2119:
Hai guys.

I recently found a page on web that android kitkat is going to be updated for most of the xperia phones

i linked it.[/CENTER]

http://au.ibtimes.com/articles/506245/20130916/android-4-kitkat-os-18-smartphones-tablets.htm#.Uj583canqnQ

Android 4.4 KitKat will support more phones and tablets including ones which already aged long ago. Know the HTC, LG, Samsung and Sony Android devices which are eligible to Google's new Android OS.

HTC Smartphones

HTC smartphones are well known for its Sense UI which is virtually lagless compared with other Android devices out there. HTC imparted powerful hardware components and premium materials to promote stability and elegance. Certain HTC phones are qualified to get Android 4.4 KitKat and hopefully the company can push software upgrades to them soon.

1. The One Family including HTC One, HTC One X and HTC One X+

2. New Desire family released in 2013

3. Desire line up including Desire X and Desire V

4. DROID DNA, HTC J and Butterfly

Most of these devices have at least 512 MB of RAM and runs Android 4.1 Jelly Bean OS. Android 4.4 KitKat has been speculated to feature Linux kernel 3.8 for low-memory requirements.

LG Smartphones

Several models from the LG Optimus line are qualified to run Android 4.4 KitKat with at least 512 MB of RAM. Some of these units include:

1. G2

2. Nexus 4

3. Optimus L7, L5 and L3

4. Optimus G and G Pro

5. Optimus VU

LG remains quite if when they are going to push Jelly Bean updates to their smartphones and still unclear when they will announce official KitKat release.

Samsung Galaxy Line

Samsung's vast smartphones and tablets line up are expected to receive Android 4.4 KitKat as well. However, the company seems to stagger updates on their devices due to overpopulation.

1. Galaxy S4 line: Galaxy S4 original, Zoom and Active

2. Galaxy S line: Galaxy S3 and S2

3. Galaxy Note: Note phablets and Note tablets

4. Galaxy Mega 5.8 and 6.3

5. Galaxy Tab: Galaxy Tab 3, Galaxy Tab 2 and Galaxy Tab 1

6. Mid-range devices such as Galaxy Young, Galaxy Fame, Galaxy Mini and Galaxy Ace

Samsung recently decided to skip Android 4.2.2 Jelly Bean on Galaxy S3 and instead will push Android 4.3 to save time and effort. The company may also release Android 4.1 Jelly Bean to selected device but it remains unclear which one and when.

Sony Xperia Smartphones

Sony Xperia phones feature combined multimedia applications and Exmor camera sensors with fast processors from Qualcomm. The Japanese tech company is now developing Android 4.3 Jelly Bean for selected Xperia phones which be pushed primarily on the Xperia Z family. Android 4.4 KitKat is expected soon to arrive to the following devices:

1. Xperia Z family: Z original, ZR, ZL, Z Ultra and Z1 Honami

2. Xperia tablet S and tablet Z

3. Xperia mid-range phones: Xperia M, C, SP, L, S, SL, U and many more

Sony mobile devices are commonly equipped with 512 MB of RAM and a single-core Qualcomm processor.​
[Xperia Play General] CriGiu:
IMHO this isn't going to happen.

As you can see, Sony has never mentioned 2011 Xperia's for Jelly Bean updates, as they were made by Sony and Ericsson and since the partnership has been dissolved I do not think they will update some "dead" phones.
[Xperia Play General] bhavei:
False Hope, this is not useful for us Xperia PLAYERS.

sent from Xperia PLAY™ via Tapatalk™
[Xperia Play General] deepa2119:
if it is false hope.thn i think we may atleast have more port options as other similar mobiles get the update
[Xperia Play General] Doonooroid:
Custom Rom

Can we atleast hope for some customs?
[Xperia Play General] Jecmenn:
Yes, we can. Everything can be ported, so i think that we will taste the KitKat. :D
[Xperia Play General] arsham x_play:
I think it will not come to our plays

Like ics
[Xperia Play General] mehdi.moha:
no way !
[Xperia Play General] anay3000:
if sony doesn't, Cyanogenmod will

I believe that if possible, Cyanogenmod based on 4.4 will be available, though i have not read the cyanogen wiki / news about this recently.

if its compatible, then it would be nice to have 4.4 on this device.
[Xperia Play General] TheCraig:
I use to have an Xperia Play and I'm incredibly doubtful that you will ever get 4.4 even with custom roms. Awesome phone when I had it but it never even had ICS.

Currently have a Galaxy S3 and probably going to get a Xperia Z1 next.
[Xperia Play General] ltkj:
actually someone posted on Android Development Thread wrote that he may do it for our xperia play.

here's the thread :http://xdaforums.com/showthread.php?t=2513088
[Xperia Play General] korrectmethod:
OP just adding links to built from source roms as they rollout the official updates and wait for an official CM release.

The guy that mentioned xperia play only had 5 posts (so he's not a developer). I think you confused his broken English thinking he was saying xperia play 4.4 soon, when really he was asking for it to be done soon. It's typical for new members who don't know the rules or what's going on in development for the device. 4.4 isn't coming to XP, at least not until we can get more devs behind it, it's not even being worked on as far I know. :) I hope that clears things up.
[Xperia Play General] Reiven89:
if there will be a 4.4 xperia arc rom, can be ported to xperia play as many roms we have? android 4.4 work great with 512mb ram devices
[Xperia Play General] saqibkhan:
we only need a working kernel.. once that's done.. we will get a working ROM asap. our kernel is Mid way.. just a little bit more and we are done.
[Xperia Play General] olokos:
Our kernel development is stopped as our main developer is not able to get touchscreen fixed and nobody else got it working. I honestly think that we will never have android 4.4, not even custom made [MENTION=243864]xda[/MENTION] :<

Wysyłane z mojego R800i za pomocą Tapatalk 2
[Xperia Play General] JunDavis:
Well the device never even made it to Jellybean and only got a beta for ICS. Gingerbread is what this device was made for. It runs beautifully with it.
[Xperia Play General] saqibkhan:
:crying: .. someone do it plzzzzzz.. if only I had enuf knowledge about it.. if only someone of you can help me Dual Boot Ubuntu with Windows 8 on my laptop.. I will start messing with the kernel to see if something comes up.. I might be a Senior Noob,lolz. but maybe I could try.
[Xperia Play General] ChunkFlip:
http://www.technologytell.com/gadge...id-4-4-kitkat-update-for-several-old-devices/

It's a rumor but... If samsung could do it maybe Sony will do this too
[Xperia Play General] CriGiu:
You should try wubi (ubuntu installer on windows) but yeah, if it was that simple to build a kernel then everyone would have done it
[Nexus 7 Q&A, Help & Troubleshooting] davelikestacos:
So, my 32GB 2012 Nexus 7 fell from my desk today. About a 3 foot fall and now has a small set of cracks in the bottom right corner of the screen. I actually thought the digitizer was dead as well because it would not respond, but I rebooted the device and it still responds. I guess I "lucked out" with the position of the crack as well since it is on the bezel and does not interfere with anything on the screen besides the recents button on the nav bar.

Still, I am kind of meticulous when it comes to keeping my devices in tip top shape. Seeing that crack, even though it doesn't interfere with anything I view, kind of makes me either want to fix the device or get a new one. At the same time, I am thinking the former may not even be worth it. On eBay and Amazon, the cheapest I've seen a Digitizer/LCD combo was $99.99 + shipping.

The point of this post is just to gain some others opinions if they were in my situation. Would you buy a LCD/Digitizer to fix the device? Would you just use the device as is, ignoring the small crack in the bottom right corner? Would you say screw it and use it an excuse to get the 2013 Nexus 7? Or is there some other option that I'm not thinking of?

Also, I figured I'd ask here to see if anyone either has a broken Nexus with a good LCD/Digitizer that they'd like to sell or know where to get one cheaper than $100.
[Nexus 7 Q&A, Help & Troubleshooting] Darth:
Yes

Sent from my cellular telephone
[Nexus 7 Q&A, Help & Troubleshooting] davelikestacos:
Troll?
[Nexus 7 Q&A, Help & Troubleshooting] Darth:
We aren't you and everybody is different. Why ask us what we'd do? You're gonna do what you want to do in the end anyway.

This is no different than all the should I buy ______ threads.

Sorry, but its a silly thread. ;) so I was being silly. :)

Sent from my cellular telephone