yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] indianajonze:
you're missing the point. there are ways around all of it, including airplane mode, dnd modes if you have lollipop or CM, but these are still more steps than simply turning the phone off. i just want it off. fewer steps = better, and when its off there is zero chance that i forget to turn on one of these modes and be awakened at 3am by some nonsense facebook post. as mentioned earlier, other devices will charge wirelessly while off, so the issue is clearly with the nexus 6.

not sure why you're trying to make excuses here. get a nexus 5 or 7 and then tell me N6 is operating correctly. Those devices will charge while off (however you choose to define that). Whether you approve or not of the way N6 does things is irrelevant to me, but for myself and many others it is a broken situation
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
Lets start over. Ok?

Everything involving the device turning on involves hardware and firmware. You are not being unreasonable in assuming some similarity to WOL. The main difference here is that we actually have more information available regarding the CAUSE of the wake-up. Where the WOL packet gets sent once and its over, a Qi charger *continues* to be connected and supplying power. In addition, the bootloaders on the phone actually provide more information to the kernel than you can get on a desktop/server machine.

At the most basic level, something physical happens that triggers a power up, whether that be a magnetic field received through the Qi coil, a DC current applied to the USB port, or the power button being pressed and sending a current through the 'on' pin of the PMIC.

From there, it begins executing bootloaders in the order PBL --> SBL1 --> SBL2 --> TZ --> back to SBL2 --> SBL3 --> ABOOT.

ABOOT, which carries a LittleKernel "LK" payload, is a multi-bootloader with THREE boot modes; fastboot (part of LK) selected if LK detects VOL- being pressed, boot (standard boot, linux kernel from boot partition) selected if LK detects NO Vol button being pressed, recovery (linux kernel from recovery partition) selected if LK detects VOL+ being pressed. In addition to loading and starting the linux kernel on recovery or boot partition, it sets a number of kernel parameters, indicating various other details, such as, like we've talked about, a charging reason flag.

What I *do not* know, is what the different sets of parameters look like comparing USB charging, Qi charging, and Power button.

Not that we really even NEED to know, since there are other hacks we can use to choose a boot mode.

I.e., the kernel knows when the Qi charger is connected. If there is no difference at all between the flags set by a power-button startup and a Qi charger startup, then we need only check if (a) there is a Qi charger connected during the init, and (b) that the boot reason is NOT "reboot", and use that information to decide to boot into charging mode. Let me explain the not-reboot part: If the phone is placed on the Qi pad from a power off state, it will power on right away with a reason that is not reboot. The user would not even have a chance to press the power button to turn it on, which means that the combination of "normal" boot with the presence of a Qi charger, means that it MUST be a qi-boot. If they then press the power button from charging mode to "turn it on", it will actually BE a reboot, so we can take that to mean to go into a normal boot.

I do agree, fully, that Google/Moto will NOT be changing this behavior in an OTA, since it is clearly "working as intended".... HOWEVER, this *is* a Nexus, and the best part about having a Nexus is that you can hack it to suit yourself. As a result, the discussion on how to change this behavior is still quite valid.
[Nexus 6 Q&A, Help & Troubleshooting] Robert_W:
After reading all these posts I'm a little nervous to rejoin the convo....

Regardless of whether you call it charge mode or off, the idea is that most phones stay in that state when charging via USB or Qi, but the nexus 6 is an exception. I prefer to leave my phone off then put it on the charger over night without it booting fully up.

I would hope it was not intentionally done in development. And it is possible that a future ota can change this.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
OK. I apologise if I offended you somehow. Yes let's start over. I'll read your post in full later.
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
I *promise* you that it was done this way intentionally, and will not be changed by an OTA.

What I can tell you about this, though, is that if you put it in airplane mode on the Qi pad, it is just as "off" as being in charging mode.

---------- Post added at 09:18 PM ---------- Previous post was at 09:02 PM ----------

Nobody is making excuses or missing the point... we are talking about how to alter the behavior to do exactly what you WANT it to do.... BUT, it is important to be realistic in that even though it may not be the way YOU like it, it IS the way that Google/Moto likes it. What is broken for you, is a feature for others. That means that things like this really have to be modified to suit.

Now, there does happen to be one more detail that may apply for your use case.... I'm not trying to tell you that there IS a better way, just trying to offer a suggestion to you that you MIGHT find useful....

Priority notifications mode.

I'll explain why this can be so good for your use before you shut me out and say you just want it off; because it has a SCHEDULER.

If you don't want to be woken up at 3AM by something stupid that you don't want to know about, you can tell it to always go into priority interruptions mode on X days of the week between the hours of start and end.

I.e., priority interruptions, select *calls* and maybe *messages*, FROM starred contacts ONLY, with downtime EVERYDAY between the hours of 10PM and 6AM.

Now star ONLY the contacts you trust to only call you at stupid hour if its an actual emergency, like maybe your parents, siblings, grandparents, significant other, etc.

The nice thing about priority interruptions mode, is that the alarm clock still works, and yes, those interruptions that you deem priorities DO make it through, while filtering out the crap that would wake you up in the middle of the night for no good reason.... also, since you refer to all the workarounds as being "still more steps".... you just do this once and forget about it.
[Nexus 6 Q&A, Help & Troubleshooting] z0phi3l:
If you insist on it being "off" overnight, then plug it n like a normal person would,, no more "problem" that doesn't need fixing
[Nexus 6 Q&A, Help & Troubleshooting] Robert_W:
thats what i've resorted to :(
[Nexus 6 Q&A, Help & Troubleshooting] Robert_W:
Great news. This issue has been resolved after the 5.1 update! Now when the phone is off I can place it on the wireless charger and it remains in the same state as if it were plugged in.No full boot up.

Couldn't be happier
[Nexus 6 Q&A, Help & Troubleshooting] Philip:
That's not my experience here, unfortunately. I just switched my (newly updated to 5.1) phone off, placed it on my Qi charger and it immediately booted up into full Android.

I too would like to be able to Qi charge a (mostly) switched-off phone.
[Nexus 6 Q&A, Help & Troubleshooting] indianajonze:
same result. have 5.1 E and just turned off my phone and put ut on the charger. instantly booted up. false hopes man. false hopes...
[Nexus 6 Q&A, Help & Troubleshooting] Robert_W:
I really wonder what causes this discrepancy between phones. I'm on D, not E or M
[Nexus 6 Q&A, Help & Troubleshooting] Philip:
I'm also on D, yet my phone reboots whereas yours doesn't.

I'm using an Itian Qi charger - I wonder whether different Qi chargers behave differently, or is that just clutching at straws?
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Straws I suspect
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] QA Bot:
Q&A for [ROM][4.4.4][Official] NamelessROM [NIGHTLIES][Based on ODROID U3]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][Official] NamelessROM [NIGHTLIES][Based on ODROID U3]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] davidelolli:
Status 7 when i flash

hi, when i flash this rom 1st time i have no errors, but todaY I have the error (status 7)!

why? i have tryed different versions of rom and of recovery, but same error!

Please help me! :angel:
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] Deleted member 5818061:
Samsung Gear?

Hello everyone, I have a question, has anyone tried the Samsung Gears with this Rom? I wouldn't miss this watch.

I remember that in CyanogenMod I tried several times to put in gearmenagerstub.apk /sistem/app but then app would not connect to the watch.
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] paulorobertosc:
This rom works on GT-I9305 ?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] REALLY?!:
Q

Hello everyone!

Where from I can get latest version of this ROM?
[Galaxy S III I9305 (4G LTE + 2GB RAM) Q&A, Help & ] nikhil3298:
Download link

Guys if somebody could please share the final version it will be great.

Thanks in advance
[Micromax Canvas 4 A210] ashutoshtaikar:
Guys I've been searching for a stock rom which could run games like MC4 and vector cut the rope.

As we all know that Canvas 4 is a rebranded clone of Wiko stairway every specification is the same. :angel:

So i finally flashed the stock rom of the Wiko Stairway and its trust me guys you should flash this rom because its bugless and moreover every game which was not running on stock rom of canvas 4 is now found to be running. :) :D

Seriously a great relief to me :good:

Note: Cut the rope is not working but cut the rope 2 is working :)

Flash it guys if you want a close to stock android experience with every game running :)

here is the simple installation file:

https://drive.google.com/uc?export=download&confirm=y_Um&id=0BzeAvoIC2yhHZGZaREljbEpaeEE

for Flashing via sptools:

http://translate.google.co.in/trans...917-rom-stock-wiko-stairway-4-2-1&prev=search

WARNING: By default It will repartition the internal rom so make sure you backup the contents of internal SD card

IT WILL ERASE THE CONTENTS OF THE INTERNAL SD CARD

Partition will be in this way:

Internal storage(previously phone storage): will change from 2.5GB to 4GB

Phone memory(previously Internal SD card): will change from 10GB to 8GB

Im attaching the screenshots :) Im happy :)
[Micromax Canvas 4 A210] alok singh:
what is simple instalation file? [MENTION=4976494]ashutoshtaikar[/MENTION]
[Micromax Canvas 4 A210] ashutoshtaikar:
[MENTION=5258560]alok singh[/MENTION] its an executable file (software UI) made by Wiko to flash the phone by just following the instructions and pressing the download button.
[Micromax Canvas 4 A210] alok singh:
Thanks
[Micromax Canvas 4 A210] sanjanaprasher:
hey !

is it possible to repartition the internal sd cards the way they were on stock canvas rom?
[Micromax Canvas 4 A210] ashutoshtaikar:
I've not tried it but i believe its possible to repartition the ROM by selecting the EBR files (EBR 1, EBR 2) of the stock rom of canvas 4 in conjunction with other files of wiko stairway rom and flash it via sptools

ELSE

this is simple program to modify the EBR files

http://xdaforums.com/canvas-turbo/general/howto-modify-ebr-mediatek-devices-t2769604

I've not tried yet but will try and let you know once I'm done with my exams or if u are impatient you yourself can try and let me know :p :)
[Micromax Canvas 4 A210] xfiarc:
android version ?

Edit: i just googled.. its 4.2.1 :)
[Micromax Canvas 4 A210] ashutoshtaikar:
Yeah thats right its 4.2.1 but its a bug free rom unlike the stock rom v1(v14) and v3(v16) of canvas 4
[Micromax Canvas 4 A210] xfiarc:
Hey.. I already downloaded the wiko rom.. Howz da sound quality compared to pure xperia rom ?
[Micromax Canvas 4 A210] ashutoshtaikar:
You can install viper4android or dolby after rooting :)

Its a stock rom so same equalizer as that of the canvas 4 stock rom
[Micromax Canvas 4 A210] xfiarc:
Cool.. Yeah have to install dolby.. Will try the rom today.. Thanks (y)
[Micromax Canvas 4 A210] xfiarc:
Not sure whether its the rom problem.. But after flashing to this rom im experiencing more frequent network issues :(
[Micromax Canvas 4 A210] ashutoshtaikar:
I did not face any network issues make sure your sim is inserted properly or if you have not subscribed to 3G make sure you have turned off the 3G switch for that particular sim
[Micromax Canvas 4 A210] xfiarc:
Its a bit stable now after several restarts.. I even turned off 1 sim and switched to 2g.. Lets see how it goes.. Btw i didnt experience this whn using the pure xperia rom :(
[Micromax Canvas 4 A210] ashutoshtaikar:
:( that is really strange and doesn't seem to be a ROM issue because it is the same rom as that of the C4 stock. :confused:

try flashing the same rom again or revert back to the pureXperia and see if you are facing the same network issue.
[Micromax Canvas 4 A210] xfiarc:
Hey.. Did u install the system update (ota) after flashing ? It could b because of that as well ? Now Asphalt 7 is getting stuck at checking files.. It worked only once :(

Anyways I'll try to flash the same ROM again and see how it works :)
[Micromax Canvas 4 A210] ashutoshtaikar:
[MENTION=5168065]xfiarc[/MENTION]

Hey ya sorry bro forgot to mention that yes i had installed the system update (ota) as soon as i installed the rom

Maybe that could solve the network problems :)

And i really dont like asphalt 7 so i rooted and uninstalled asphalt 7 and other preinstalled games :p

But i think the update will solve that issue too
[Micromax Canvas 4 A210] xfiarc:
Bro I also installed the update but no luck :( I think the easiest method is to do a factory reset and see.. Will update here once done :)

Edit: i switched back to Pure Xperia rom and the network issue is sorted.. not sure why am i getting it in stock wiko rom :(
[Micromax Canvas 4 A210] alok singh:
It might be because of invalid imei... I also faced the problem of invalid imei which I solve... U can search on YouTube to solve this problem
[Micromax Canvas 4 A210] xfiarc:
[MENTION=5258560]alok singh[/MENTION].. I need to check about the invalid imie matter.. Tnx bro

Btw I'm also trying different Roms these days ;) so far I didn't experience any network issues in pure xperia and rombuzz Roms :)
[Micromax Canvas 4 A210] Prometheus:
Its mayb bcoz u are using wiko's modem.img..try using the modem.img from c4..
[Micromax Canvas 4 A210] xfiarc:
Is there any way to extract the modem file of rombuzz to this? Thanks
[Micromax Canvas 4 A210] Prometheus:
just extract the zip of rombuzz..it should be in system/etc/firmware
[Micromax Canvas 4 A210] xfiarc:
Thanks :)
[Micromax Canvas 4 A210] Atharkhan101:
Problem ROM

Cannot install this ROM.

Says 'operation aborted'
[Micromax Canvas 4 A210] ashutoshtaikar:
Use the right sptools or driver if ur flashing via sptools or simply use the wiko installer
[Micromax Canvas 4 A210] Atharkhan101:
I'm not comfortable flashing via SP tools, its risky if there is a power cut. I always flash rom zip file directly via CWM. This zip file is not flashing, says 'operation aborted'. Please provide a flashable zip file. Thanks
[Micromax Canvas 4 A210] kannanrs:
Works a charm

The one-click installer worked for me and enjoying a 4gb for apps. Thank you guys.

Kannan
[Micromax Canvas 4 A210] pranjal18:
Man!! This ROM is amazing!

I have modified this awesome base and modeled romBUZZ around this.

Credits/Links added :)
[Micromax Canvas 4 A210] pranjal18:
Hi! does anyone face the following problem? or has a solution?

-the when wcdma only mode is activated in system settings > more > mobile networks > 3g service, then there in no signal.

-this does not happen in the stock rom. I have tried the stock rom modem too.
[Micromax Canvas 4 A210] Prometheus:
It does not happen to me.. i checked..i use c4 modem..wiko modem gave me no signal at boot up
[Micromax Canvas 4 A210] pranjal18:
are you using romBUZZ?

Actually I did not realize this while making the rom. So, romBUZZ v3 has wiko modem.

PS I will update it to c4 modem.

Can you please upload your files in /system/etc/ and modem.img?
[Micromax Canvas 4 A210] Prometheus:
​

You want my whole /system/etc folder or only the modem.img?
[Micromax Canvas 4 A210] pranjal18:
only the files in /system/etc

and modem.img
[Micromax Canvas 4 A210] pranjal18:
found the solution :) :)

http://xdaforums.com/canvas-4/help/help-network-wcdma-mode-t2937023
[Micromax Canvas 4 A210] vinnyyyyyy:
I had flash your rom but don't know why is it freezing at any moment.

Any solutions???
[Micromax Canvas 4 A210] ashutoshtaikar:
sorry but i did not try 3G mode
[Micromax Canvas 4 A210] ashutoshtaikar:
sorry but i did not face any freezing issues :(
[Micromax Canvas 4 A210] vinnyyyyyy:
:(

I have tried rombuzz 3.0 and same problem occurring but whenever i flash buzzrom 2.0 it works without even a lag
[Micromax Canvas 4 A210] rahulsingh87:
External SD card not detected anymore

Hi,

I have recently flashed my A210 with Wiko stairway stock rom, after flashing it stopped detecting external SD card. So i format the whole SD card but no use. Then i again flash it with the Stock rom again no use.

So i again flashed it with the stairway stock rom but nothing happens and it is unable to detect the external SD card. Please help me what to do.

Also i was trying to install any other file explore to see if they were able to detect but it looks like even play store is not working anymore. It just opens and the progress bar just running for long time but do not display any thing.

Regards,

R
[Xiaomi Mi 2] RadarNyan:
Just now after a reboot, I found that Google Play Service stops working. It happened quiet a few times before, so I decided to do what I always do - remove the Google Play Service and flash it again.

So I rebooted into recovery, removed gapps backup script under /system/addon.d using Aromafm, and tried to flash the latest CM nightly - and the flash failed with status 7.

Then I found that I can no longer boot into system, but I still have access to boot loader (fastboot) and recovery. So I begin to check what's wrong with my /system partition and found that once it's mounted, I can not umount it. At first I thought it's a file system problem so I tried to fix it with e2fsck - but I can't umount it so e2fsck won't work!

So I rebooted my phone again, executed e2fsck -cfy /dev/block/platform/msm_sdcc.1/by-name/system but it didn't show any error - it's like the file system is file but I just can't umount it for some reason I can not understand (If I try umount it, I'll get "invalid arguments")

Lucky enough there's nothing wrong with the secondary system partition (I have TDB enabled before and always been using system1) so I managed to flash the latest nightly to system2 and get my phone booted, but I still can't get access to system1

Anyone, help :crying:
[Xiaomi Mi 2] RadarNyan:
Update

This is becoming weirder and weirder...

After a few days of usage, I did a lot modification to

2nd /system

partition, I noticed that sometimes I got boot loop - if I connect the phone to my laptop and use adb logcat I can see the logcat loops forever. Using adb reboot can make my phone reboot and get into Android system.

So I powered off my phone, booted to recovery, and as I expected, the same thing happens to

2nd /system

partition - it can be mounted with no problem, but I can not unmount it (except for power off the phone, of course)

I thought maybe there's something wrong with that partition, maybe bad block or whatever, so I copied the entire

2nd /system

to 1st /system partition using dd - Then the

1st /system

partition can't be unmounted as well.

Now I'm f_cked, so I decided to format

1st /system

partition once again and start fresh, after format I went and try mount then unmount

2nd /system

partition - now it can be successfully unmounted. I was shocked at the time that I thought something went wrong I acturally formatted both partitions, but turns out all data in

2nd /system

partition is fine and the "can't unmount" issue is gone.

Now boot loop doesn't happen anymore, but I'm too afraid to do any more modifications to /system partition, therefore I have skipped a few nightly updates. I won't risk brick my phone until I can get my hands on a new one (It's just too hard to find a phone that has a great performance and not that freaking huge! Seriously, I would buy another Mi 2S if they still sell it.)

Does anyone know what could possibly happening here... I'm so confused...
[X 2014 Q&A, Help & Troubleshooting] Anfeldt24:
I have updated to the lollipop update like many and my phone is warm and sometimes hot.

I am not using my phone and it still gets warm and drains the battery life.

In 4 hours I will go from 100% to dead with no use.

My screen was off but shows it as being on. **See attached photo

I searched the MOTO threads and cant find anything as of now to resolve this issue.

Anyone else having this issue and find a fix?

Tried wifi channels to see if this issue fixes this, cleared cache and nothing........

Hope help comes quick!

If I can get some help I will buy them a beer or coffee!
[X 2014 Q&A, Help & Troubleshooting] Anfeldt24:
Okay here's an updated seems to fix the issue......

I disabled the WiFi location settings, download clean master -- https://play.google.com/store/apps/details?id=com.cleanmaster.mguard -- and seemed to have fixed the issue so far.

Keep you posted as the day goes on.
[X 2014 Q&A, Help & Troubleshooting] d u o XIV:
After you updated, did you do a factory reset? If not, and before you do, what apps do you have installed? You might have an unruly app that's just constantly running. I hear Google Fit hasn't been too friendly...

Since Google services is pretty high on the usage list, it could have something to do with syncing errors or maybe problems with updating Google Play services/Play Store. Make sure you have the latest versions.

Google Play services (6.5.85) - http://www.apkmirror.com/apk/google.../google-play-services-6-5-85-1589008-438-apk/

Google Play Store (5.0.38) - http://www.apkmirror.com/apk/google-inc/google-play-store/

Also, unsync any services in your Google account that you aren't using.

Don't forget to turn off extraneous radios like WiFi (if you don't use it for location), GPS, NFC, and Bluetooth when you're not using them.

If all else fails, factory reset and pay attention to the apps that are being downloaded. Uninstall garbage and disable what you can't uninstall, but don't use. Hopefully this helps.

EDIT: Seems you fixed it. Nice! Well, use this as a reference for your next step if things don't stay behaved.
[X 2014 Q&A, Help & Troubleshooting] Note10.1Dude:
Clear cache and reboot. If you still have the problem, do a factory reset. Also, has the phone stabilized? Have you been through a couple of charge/use cycles? There could be a load of background processes setting up for the first day or so.
[X 2014 Q&A, Help & Troubleshooting] Anfeldt24:
Seems the Qualcomm battery guru is a culprit as is the xfinity WiFi app.

Motorola said do a factory reset but I don't want to if something else can be done.
[X 2014 Q&A, Help & Troubleshooting] Anfeldt24:
Think it's fixed by the WiFi location and the clean matter app showing the apps that kill the battery.
[X 2014 Q&A, Help & Troubleshooting] Anfeldt24:
Here is a great article about asps that keep restarting in lollipop. It's a bug in ART. Google is working on a fix.

http://www.androidpit.com/android-5-0-lollipop-bug-apps-frequently-restart-in-background
[X 2014 Q&A, Help & Troubleshooting] Anfeldt24:
Another great way to help save battery. http://www.androidpit.com/android-5-0-lollipop-problems-and-solutions