Hi All,
I believe that there is a bug in the Windows Phone push notifications subsystem and I found a few reliable ways of reproducing it. I would be thankful if someone can vote for this bug on uservoice to raise an awareness about this bug at Microsoft. Bug details by the following link: wpdev.uservoice.com/forums/110705-dev-platform/suggestions/7263372-fix-push-notifications-issue
Thanks a lot!
Related
Hi all,
i was thinking about a software that would be a mix up between a callerID (caller2Picture) style software and a call-sms blocking engine.
Wouldn't it be awesome to have ?
I searched for something similar but no results so far.
I only found out a topic opened this days at
http://www.teksoftco.com/forum/viewtopic.php?t=37
they are wainting for some ideas about what we expect from this kind of software
They promissed to monitor this thread also... so lets give them something to work on
Rain
You should try Inesoft AddressBook.
The Caller ID part is very nice but the block call doesn't satisfy my needs and many others arround here...A white/black list would be more apropiate for me also the posibility to send an SMS after i block a call, a log of blocked calls...
I would like something like a mix between what Mort and Morphy started to develop here if you followed their topics
Hi all,
I just want share my problem with HTC 6800 Mogul (Sprint).
It uses WM6.1.
My problem is every single item SMS in thread system list, always for 2016 (year), as attached, "thread_list.jpg"
i was setting my regional setting and clock time, as attached, "clock_system.jpg"
If anybody have a suggestion for me to set system up, due to miss-date (year-->2016), please feel free to comment this thread.
Should need any further info, don't hesitate to contact me
Thanks a lot friend
strange, I just got this same date error. Yesterday was fine. Looks to me like a sprint SMS server problem.
yeaahh this case very strange to me.
This was happend in new year eve, from 12/31/09 become 1/1/16 (until now).
I think this is not SMS Server problem since another mogul, which is belong to my friend, there was no problem with this case
there is already a fix for this. A quick search on here or google will get you the cab fix
Brother, would you like give me clue a keyword for searching? since before i posted this thread, i already search but didn't found anything.
And also, if you don't mind, did you know what the root cause this problem? i just wanna know
anyway, thanks a lot for your helping brother.
Thanks my problem already solved
Please find out the attachment below (Ziggy2016Fix.cab)
or add new registry
[HKEY_LOCAL_MACHINE\Software\OEM\SMS]
"RecvTimeStamp"=dword:00000001
Thanks
hey devs!
we've been having a discussion at the blackstone android subforum about a touchscreen bug and on initial contact, the location isnt correct. this fixes micro seconds later to the actual finger location and android interprets it as a swipe.
it seems a few users are experiencing the problem now.
anyway, thats not the point of this post, but from something within that thread...
bug tracker.
would it be worth while (for both devs and users) to use something like this? users can see known issues, devs can see quantity of users experiencing that issue (some sort of vote system?), and if no bug is present, users can submit one (in the case of blackstone owners, touchscreen issues).
it would also bring the added benefit as an official central location for known issues in the android project, rather than having this subforum, and all the device-specific subforums.
going purely off our touchscreen issues, it seems it may be unknown to the devs and only now it's been mentioned, users are coming forward to say they too have issues.
anyway, just a sugestion - what do people think? (im not volunteering, just putting an idea forward for someone more knowledgeable to take action on)
veehexx said:
hey devs!
we've been having a discussion at the blackstone android subforum about a touchscreen bug and on initial contact, the location isnt correct. this fixes micro seconds later to the actual finger location and android interprets it as a swipe.
it seems a few users are experiencing the problem now.
anyway, thats not the point of this post, but from something within that thread...
bug tracker.
would it be worth while (for both devs and users) to use something like this? users can see known issues, devs can see quantity of users experiencing that issue (some sort of vote system?), and if no bug is present, users can submit one (in the case of blackstone owners, touchscreen issues).
it would also bring the added benefit as an official central location for known issues in the android project, rather than having this subforum, and all the device-specific subforums.
going purely off our touchscreen issues, it seems it may be unknown to the devs and only now it's been mentioned, users are coming forward to say they too have issues.
anyway, just a sugestion - what do people think? (im not volunteering, just putting an idea forward for someone more knowledgeable to take action on)
Click to expand...
Click to collapse
actually, i would like to know some details about the module for touch screen.
maybe there is a chance to activate/implement a debug log ...
does anybody know ?
cu camel
This was Fixed by SergeyLAR
However, there are still two minor problems, see the picture
1.Call records sink
2.Save to Contacts sink
If someone can fix,it perfect!
Thanks very much!
PACKAGE_TOPAZ_S2_Phone_Canvas_Enhancement_Fix_4_2_51620111831_0.rar
There is already a thread with this problem, use that for submit your problem and search before posting a knew question.
http://forum.xda-developers.com/showthread.php?t=656962
Thread Closed
Since I'm a new member here too, I cant reply to the main thread. So I will report bug to HDHR here
Great Rom but
Found Bugs :
The volume of phone call is small, other ROM work well can you fix it, thanks!
Linhpv52 said:
Since I'm a new member here too, I cant reply to the main thread. So I will report bug to HDHR here
Great Rom but
Found Bugs :
The volume of phone call is small, other ROM work well can you fix it, thanks!
Click to expand...
Click to collapse
You can inbox him or use Dolby Atmos.