yashsingh1/xdaforums huggingface dataset:
[Zooper Widget General] lesept:
However, there is still one problem to tackle. Sometimes, I have the following case:

- the first event is an all day event, for today

- the second event is already begun

Then I want to know the time remaining until the 3rd event. Actually, what I want is the time until the next event that is not yet begun.

But the values of #C1SRh# and #C1SRm# give the time between the beginning of the second event and the current moment : it should be negative as the second event is already begun, but it's positive so it's not valuable.

Does anyone know a reliable way to obtain

the time remaining until the beginning of the next event that is not yet begun

?

Thanks for your help.
[Zooper Widget General] lesept:
I tried this, to simplify the problem:

$((#DD#-#C0SD#)*1440+(#DH#-#C0SH#)*60+(#Dm#-#C0Sm#))<=0?#C0SRd# d #C0SRh# h #C0SRm# min.$$((#DD#-#C0SD#)*1440+(#DH#-#C0SH#)*60+(#Dm#-#C0Sm#))>0&&((#DD#-#C1SD#)*1440+(#DH#-#C1SH#)*60+(#Dm#-#C1Sm#))<=0?#C1SRd# d #C1SRh# h #C1SRm# min.:#C2SRd# d #C2SRh# h #C2SRm# min.$

It calculates the number of minutes since new year of the current moment and compares it with the numer of minutes since new year of the first and the second event. (1440=60*24)

If current number of minutes minus 1st event's is negative, it means that the 1st event is not yet begun: then display the remaining time to 1st event.

If not and if current number of minutes minus 2nd event's is positive, it means the 2nd event is not yet begun: then display the remaining time to 2nd event; else display the remaining time to 3rd event.

This seams good to me, but is always displays the time time 3rd event : "#C2SRd# d #C2SRh# h #C2SRm# min."

Is there anything wrong with my formula?
[Zooper Widget General] lesept:
Actually, it works if I use one ( and not 2...

$(#DD#-#C0SD#)*1440+(#DH#-#C0SH#)*60+(#Dm#-#C0Sm#)<=0?#C0SRd# j #C0SRh# h #C0SRm# min.$$(#DD#-#C0SD#)*1440+(#DH#-#C0SH#)*60+(#Dm#-#C0Sm#)>0&&(#DD#-#C1SD#)*1440+(#DH#-#C1SH#)*60+(#Dm#-#C1Sm#)<=0?#C1SRd# j #C1SRh# h #C1SRm# min.:#C2SRd# j #C2SRh# h #C2SRm# min.$
[Xperia Z1 Q&A, Help & Troubleshooting] poog:
This Z1s was working fine

I used TWRP to recover a backup from another Z1s I had. I am not sure if it was a good backup.

When TWRP completed, I rebooted, and the phone failed reboot, and now will not turn on. Battery was under around 50-60% I think.

1) FLASHING RED light every second when connected to charger or PC.

2) Not recognized by Flashtool or Sony Companion.

3) Red button doesn't do anything

4) Cannot get this to do anything but flash red when connected to charger or PC/

Anyone know any ideas? Will the TEST POINT fix work for this Z1s c6916 ? There doesn't seen to be any mention of people bricking or fixing C6916 Z1s phones? THere doesn't see to be any repair files for the C6916 for unbricking .

Ideas?

Thanks
[Xperia Z1 Q&A, Help & Troubleshooting] user822:
Tried another cable/charger?

I once had the concidence it was drained fully and the cable broken at the same time. Took me a while to figure that one out...
[Xperia Z1 Q&A, Help & Troubleshooting] Fladder72:
Maybe you have a look at this:

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

EDIT: I've posted my flashing story..:

http://xdaforums.com/showpost.php?p=56196049&postcount=471

Blinking red LED means mormaly Battery is dead.

I had this problem yesterday on 80% Battery...

I think, Batery Stats or smilar is corupted

Disconnect your device from your computer and try to shut down your Z1 by pressing power button and vol+ (Alternative you can try the reset button near SIM) Maybe it needs some tries ;)

Charging on AC via wall plug may be necessary.

Reconnect in fastboot mode. Flash via fastboot a working boot.img incl. TWRP.

Reboot to recovery and restore a backup from your device. Don't try to reboot system. This will bring you back to yor blinking red LED... But the best way is to flash new Firmware via Flashtool in Flashmode.

Don't use backups from other devices. To recover containing apps and data you can try Nandroid Manager from Playstore . But sometimes restoring app data dont work (Different AndroidIDs...) You can also use Nandroid Manager to browse your backups and extract somthing. NM supports TWRP and CWM backups.
[Xperia Z1 Q&A, Help & Troubleshooting] poog:
Thanks for reply but nothing is working.

I can get the phone to do a soft reset and get 3 vibrations, but phone will not go into flashmode (volume down plus POWER).

In other words, phone will not respond to FLASHTOOL or PC companion. routine. Tried multiple cables. Connected to a few different working wall chargers.

When connected to a PC, the phone will now do a connect , reconnect loop. switching from solid red, to no light, and back and forth., every minute or so.
[Xperia Z1 Q&A, Help & Troubleshooting] MasterHuanDuan:
me too

this happened to me when i was too impatient and now the battery is dead and i cant charge it

anyone know how to fix it? i dont really want to take it to sony or change a battery
[Xperia Z1 Q&A, Help & Troubleshooting] JustPlayingHard:
Volume down then plug into USB
[Xperia Z1 Q&A, Help & Troubleshooting] poog:
Did you try leaving it overnight on a charger? Did you try using PC Companion to restore the device to stock?
[Xperia Z1 Q&A, Help & Troubleshooting] MasterHuanDuan:
ok i solved it by charging it with 4 AAA batteries and a cut micro usb cable.

btw i couldn't connect to pc at all because the battery was dead, no bootloader or flash mode until i charged it with batteries
[Xperia Z1 Q&A, Help & Troubleshooting] JJrmc:
cut micro usb cable?

Hi there I'm scouring the forums for somebody in a similar position to myself....

firstly, thanks in advance if you are able to even inch me in the right direction!

What is meant by a cut micro USB cable?

It seems very odd that charging via a charger that uses triple-A batteries as a source would make a difference, what made you think to try this and what actual difference would it make?

My Issue:

I stupidly hit backup from sdcard0 in CWM after having wiped the internal memory.... So this I guess is like backing up from a blank image? However I could be wrong on this point.

Now I get:

-No flashmode or fastboot is accessible....

-The phone turns on (sometimes with a vibrate, sometimes without), shows Sony splash screen then stays on a blank black backlit screen.

-The device gets much hotter than it does during normal operation, the battery seems to run out quickly after it is unplugged.

-The hard reset (inside of the sim card slot) resets the device with the 3 short vibrates as it always has

-If placed on charge the device wont stay in an 'off' state, always boots

-When connected to windows 7 x64, the device is recognized as "C6903" and has sony_adb drivers installed against it, (MTP is disabled in devices, I have also disabled auto-install devices in group policy because this was causing mayhem, PC Companion is also not running). Flashtool by Androxyde returns me an error saying device drivers must be installed, of course I have run through the driver installer and installed the correct Z1 drivers on the PC. It also informs me that I need to make sure the device isnt in MTP mode, which is why I've disabled and uninstalled the MTP driver under devices.

-I was briefly able to get adb to recognize the device on the command line but it was accompanied by saying "Unauthorized"

I've tried to include as much detail as possible to help my cause, and your post seemed to be fairly close to mine in terms of relevancy.

I've done a lot of trawling, and learned a lot on the way, certainly about android devices for future use! I certainly wouldn't have all the knowledge I have now unless I'd screwed up in the first place!

If any can lend any help that would be much appreciated!

Kind Regards

John
[Xperia Z1 Q&A, Help & Troubleshooting] BlackSoulxxx:
Ahhh...the situation of non system mode........Normally I always have this when I wipe system then turn off the phone and plug into the charger. Flashing ROM will solve this instantly...But for your case, I think the bootloader has some serious corruption (due to eMMC or the phone it self)
[Xperia Z1 Q&A, Help & Troubleshooting] MasterHuanDuan:
First, I dont really know much about all the details, this is what i think. sorry for the late reply btw

So i think theres this thing with phone chargers, my guess is that it connects with the phone's system to see how much its charged.

when the battery is around 100 or 99% full, the charger would stop charging and wait till it dropped to 98 or 97%. (i guessed the numbers)

batteries doesnt do all this complicated stuff, and if you leave it connected for too long it will damage your batteries.

In my case i waited for around 30 minutes using 4AAA batteries,

which means its supplying the phone 1.5v time 4 =6volts, a voltage higher than the standard sony charger,

i dont think it'll damage the batteries if you only connect them for a short time.

there are lots of ways to connect batteries to phones, google it.

actually im not sure how to do it myself because i actually used an interesting electronic part removed from a device

but its kinda hard to describe what it is, tell me if you want to know

after your phone is charged for some time you should be able to connect it to pc again

if it doesnt, charge it some more until you think your phone is gonna explode

once you connect to your pc you flash the boot.img file from your desired rom, most of the time it gives you a working recovery

twrp, no matter where it came from, it never worked with me, just saying

you should charge your phone in recovery afterwards, you dont need to do anything, just leave it plugged to a wall or pc while in recoevery

hope it works!

fun trivia: if you keep swiping down while in the cwm based recovery it will give you a rainbow mode. check it out
[Xperia Z1 Q&A, Help & Troubleshooting] deniz1905:
I just want to say that i am really impressed with your idea about charging the phone with 4 AAA batteries. last year this day, 26 december, i bricked my phone while flashing that troubled version of 4.3 and went to service to get repaired it. and it took 4 months to change the phone for a new one. If i brick my device some day, i am writing your idea down to make the phone work again.
[Xperia Z1 Q&A, Help & Troubleshooting] MasterHuanDuan:
I used this

from a laptop cooler
[8125, K-JAM, P4300, MDA Vario General] bk227865:
Papizdono asked faria the following question :

lol i was thinking the same thing.(when i buy my next phone, i will buy the same one as faria)

Maybe a hint for the manufactures and microsoft if they are following this, people want to buy devices that will have support,updates and upgrades.

The main reason i did not buy a HP/Compaq pda anymore after my 2215 was the major lack off support for the device. HP offered 1 rom upgrade without major improvements. After that they offered a few patches that ate up precious memory and then completely abbandoned the device.
[8125, K-JAM, P4300, MDA Vario General] hanmin:
HTC isn't that good in terms of their support anyway, thats why you have this lovely site :D
[8125, K-JAM, P4300, MDA Vario General] papizdono:
hehe.. had 2210 also before ... then i had HP 4700, too big, then i went for loox 720, found out i need a phone :), then to S100, now to qtek 9100, and looking for a new one..... IPHONE maybe??? 9600 (tytn) ???? god knows.... want a VGA max 3.2" screen phone :)
[8125, K-JAM, P4300, MDA Vario General] ClassicalDonkey:
LOL i think everyone on here will get what ever faria getts for his new phone just so we can have better software then the company gives out!!!
[Moto 360] staveandor:
I'm running on rooted XT1060 Android 4.4 and bought a Moto 360 a days after they came out. It was amazing and everything worked great.

Last week, the Android Wear app updated to 1.0.2 and now it's constantly force closing. Is anyone else having this issue? Or can anyone please point me to the older version of the software?
[Moto 360] gregbradley:
Please post questions in the Q&A section.

Also, I believe you will get more help from posting in the Moto 360 section, so I will this thread to the Moto 360 Q&A, Help & Troubleshooting

Thread moved
[Moto 360] brotbuexe:
You have cleared app data for the app already? You could try wiping data for the google play services too. It is used for the communication with watch.
[Moto 360] staveandor:
I have cleared data and cache from the app, factory reset the watch, and reinstalled app several times no avail.

The app works fine on my nexus 7, and I've tried restoring a working backup of the 1.0.2 software from tablet my phone, and didn't work either.

I'll try clearing play cache like you suggested.
[Moto 360] staveandor:
Sorry for the late reply.

Clearing cache and data on Google Play didn't work either. I'm basically at a loss, short of just wiping my phone or waiting for Android 5.0 and praying it gets rooted on VZW Moto X 2013.
[Moto 360] mikmitch:
Same problem here, rooted VZW Moto X (XT1060) running 4.4 with Moto 360

Things I've tired so far:

Install/re-install, clearing Android Wear data & cache

Removed all other Wear apps

Cleared data & cache from Google Play Services

Factory reset Moto 360

Switched from ART to Dalvik & back

Direct install of v1.0.2.15 and v1.0.2.14

Upgrade from functioning v1.0.1.13 to v1.0.2.15 and to v1.0.2.14

Even tried to re-enable all of the pre-installed Moto bloat I had previously frozen

Multiple combinations of the above, with reboots between steps

Both of the most recent updates cause this issue for me:

Android Wear 1.0.2.1534065 (current, Oct 23 release) Google Play or apkmirror

Android Wear 1.0.2.1476973 (Oct 6 release) apkmirror

I can, however, still use the older version of the Android Wear app without issue:

Android Wear 1.0.1.1379611 (Oct 2 release) apkmirror
[Moto 360] mikmitch:
After looking through the logcat errors, it appears that Google Now is actually responsible for the repeating crash loops of the Wear app. Updating and clearing data/cache didn't seem to have any effect, but completely disabling Google Now does seems to solve the issue. Certainly not an ideal solution, but a temporary fix until Google fixes the issue.
[Moto 360] bakaz:
Same situation here. Rooted VZ Moto X w/ 4.4 and constant force closes. I've tried everything with no success. So I'm back to the old version of Android Wear.
[Moto 360] staveandor:
I wanted to write back and say that this did the trick. I can only hope Google and Moto play well together again, but losing Google Now is no big loss.
[Moto 360] staveandor:
Can you post the link to the old version for those who want it? I couldn't track it down when I was looking.

Edit: I see it was posted above. Thanks for your insight!
[Moto 360] markswoods:
Excellent Observation

Turning off Google Now does do the trick. I've lost all those handy Google Now notifications (weather, length of drive home, etc.), but at least the app isn't crashing all the time.
[Moto 360] bakaz:
To further troubleshoot the problem, I wiped my phone since it had been a while and I have lots of potential problem apps installed (like Xposed). After the first clean boot I installed the latest Android wear successfully and everything worked fine. The instant that I set up Google Search/Now, Android Wear crashed. No other apps were installed. I know there were some reported issues with Exchange services, so I hadn't even set up my exchange account yet. So it's pretty clear that on rooted moto X (4.4) there's a problem between Android Wear and Google Now.
[Moto 360] mikmitch:
Finally, a fix!

A new release of Google Now was recently discussed on XDA portal.

This version seems to update Google Now to work properly with Android Wear and stop the repeating crash issue.

I assume this update will get pushed to Google Play soon, but you can get it now from the APK below.

From the article:

"The APKs are signed with official release keys, and will update your existing app without you losing any of your data"

Direct link to the APK here:

Google Search v4.0.28
[Moto 360] bakaz:
That did the trick! Thanks!
[Miscellaneous Android Development] Ash9999:
Hi Everyone.

Today, I want to share my personal SMS Based Location System.

I used Tasker (google play) to make it possible.

So, if you receive a Text Message with a particular Content, your phone will send a SMS with your GPS Coordinates to one or more contacts.

You pay every SMS, of course :D

Here it is the video tutorial:

Youtube video

I hope that this post could be helpful!
[HTC One X] sh4d0ws1nX:
Hi guys,

So recently I got a phone from a friend, which is a Vodafone AU HTC one X. I'm not a complete novice at all this as as I have had no issues with my htc sensation xe, samsung galaxy s2 and s3 but I'm having quite abit of trouble with the HTC one x. So what I've done so far is

1. I've unlocked the Bootloader

2. Installed a TWRP recovery

3. I'm rooted

A few other details of my phone is the cidnum is: NONE according to fastboot getvar cid, or using CID getter I got VODAP021. The version-main says 1.29.862.11. The recovery I have is TWRP v2.6.0.0

My problem is that my phone is still on 4.0.4 as this phone wasn't actually mine until recently. In order for me to get OTA I need to get stock recovery. After doing countless research I am unable to find a stock recovery for my phone so I'm kind of in a pinch. How do I go about doing this. From what I'm aware the OTA update will take me to Jellybean. Also if there's a way since I've already unlocked, have custom recovery and rooted, can I upgrade to a JellyBean rom like ARHD. From further research it says I need to have the proper HBoot however I don't know which Hboot I should be updating to (my current Hboot is 0.95.0000).

EDIT: Found the RUU, flashing when the download is done, hopefully it will bring it back to stock recovery.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] QA Bot:
Q&A for [CF-ROOT][SM-G7102][4.3] Root Galaxy Grand 2

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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
[Galaxy Grand 2 Q&A, Help & Troubleshooting] sireies:
Rooting SM-G7102 with the latest Kitkat update (G7102DDUBNJ2)?

Hi, new here in XDA. Have anyone rooted SM-G7102 with Kitkat's latest firmware G7102DDUBNJ2?

I recently updated my SM-G7102 from NH6 that was rooted using CF-Root before. I just unrooted it as it was instructed in Samsung Kies 3. Thanks all.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] black.grand2:
root for galaxy grand 2 sm-g7102 kit kat

Please help me i need root for my phone galaxy grand 2 sm-g7102 kit kat 4.4.2
[Galaxy Grand 2 Q&A, Help & Troubleshooting] anand4edu:
Same here . Did anyone rooted NJ2 firmware. Seems our earlier method not working. Appreciate your help.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] schubeir:
Fail to understand how so many people actually ask a question for a reply which is already available. please search before you ask questions as the answer that you are looking for is already available in the forums. We are only bloating the forum.

If you are too lazy to search, no one will help you.

have you looked at http://xdaforums.com/galaxy-grand-2/general/guide-easily-root-galaxy-grand-2-sm-t2812807

NO. you haven't.

schubeir
[Galaxy Grand 2 Q&A, Help & Troubleshooting] anand4edu:
Let's not be aggressive Mr. Schubeir. Hope you didn't have the opportunity to understand the real need. I am aware there is a rooting possibility. However it breaks the warranty by updating knox binary. If you have a solution for rooting without voiding the warranty , then help the people else don't jump with your hard words. In this world no one is having complete knowledge . Neither me nor you.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] WaseemAlkurdi:
Tried downgrading to NH6?

You can root that safely.
[Galaxy Grand 2 Q&A, Help & Troubleshooting] anand4edu:
Poor me got to know after i tried upgrading to NJ2 and rooting. My Knox updated 0x1 and my warranty is voided. Tried downgrading but d knox not resetting. any solution for me?
[Galaxy Grand 2 Q&A, Help & Troubleshooting] setälä:
help smg 7105

There is no link for this phone on CF how can I root this SmG7105
[Galaxy Grand 2 Q&A, Help & Troubleshooting] virenpawar:
It gets install first then the error starts occuring, plz help in this matter.

Respected Sir, I had installed the CF-Autoroot on my Grand 2 device. But worked fine first for 4-5 days, but later when I restarted the phone, the internal memory & external memory both were locked, infact there was lot of space to work. plz do something in the CF-AUTOROOT software, so that it can work well on my device. yes and the Mobile was INDIAN Model.

Wishing a POSITIVE reply. Thank You :)
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Suva Ghelu:
Smg 7102

Hy friends

After root can i connect otg cable &pendrive in my smg 7102.

Anwer fast.

Thanks
[Galaxy Grand 2 Q&A, Help & Troubleshooting] kuldude:
No it doesn't work like that
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Decheah:
sorry for my noob question, but will this cf-root trip the KNOX?
[Galaxy Grand 2 Q&A, Help & Troubleshooting] mmtzyx:
It's working..

I love you guys.. :)
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Aashir_HZ:
Need help!

Guys I did as mentioned but after rebooting when i go to root checker and check, It says that "Root access is not properly installed on this device".

Also when i try to open SuperSU, it says there is no SU binary installed and SuperSU cannot install it. This is a problem.

What should I do now? That means the root was unsuccessful right? :(
[Galaxy Grand 2 Q&A, Help & Troubleshooting] vb1111:
Rooting my SM-G7102

I've tried rooting my grand 2 SM-G7102 using odin.exe but when i tried using the .tar file it was like :

<id:0 005=""> Added!!

<id:0 005=""> Odin v.3 engine (ID:5)..

<id:0 005=""> File analysis..

<id:0 005=""> SetupConnection..

<id:0 005=""> Initialzation..

<id:0 005=""> Get PIT for mapping..

<id:0 005=""> Firmware update start..

<id:0 005=""> aboot.mbn

<id:0 005=""> NAND Write Start!!

<id:0 005=""> FAIL! (Auth)

<osm> All threads completed. (succeed 0 / failed 1)

how to solve??
[Galaxy Grand 2 Q&A, Help & Troubleshooting] Aashir_HZ:
Would anybody reply please!!!
[Motorola Photon 4G] nubleeet:
I needed to see about getting my electrify courier unlocked from USC. Phone was bootloader unlocked, rooted and running Paranoid Android 2.99. Guys at USC could not unlock because the phone did not have motorola tools on it? So they suggested that I put the phone back to factory and then bring it back. So I snagged the 2.3.4 stock USC image and attempted to RSD it to the phone. Got through about half of the flash and the phone crashed? Log states "Error switching phone to BP Pass through mode." Now the device states "Failed to boot 1" when powering on normally, cannot access RSD mode but I can access fastboot mode. Is there anything I can do?
[Motorola Photon 4G] nubleeet:
read through several threads over the past few days. Got the phone to RSD using temp bootloader unlock and tried to flash 2.3.5 sbf just so I could get going. Now I am stuck with locked bootloader and no access to RSD :( looks like the electrify is a paperweight now.
[Motorola Photon 4G] jshamlet:
This forum is pretty dead, like most of the phones. However, your critical failure was in applying the 2.3.5 SBF. Motorola booby trapped it such that it locked the boot loader permanently. There are no workarounds for an OTA/SBF installed version of 2.3.5, so even if you were able to get it up and running, you are forever stuck with it.

That said, you can probably still get into RSD mode using the bootloader to attempt a reflash of 2.3.5. There is a boot menu option for enabling it. I can't seem to find the thread, but it's around here somewhere.