yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Development and Hacking General] TBCompDesign:
Thats the reason Exchange-Activesync works the way that it does. The server sends out a text message that is handled at the system level on the PPC, and this is basically an instruction to sync with the server. No unneeded traffic just to check if there is anything new.

Most Celllar service providers are using NAT technology so reporting your IP address to a server and telling it to make a connection to that IP, would just be telling the server to connect to the "gateway" back into the Cellular network. A text message sent to what is called the "SMTP Gateway" for each service provider will get to the phone no matter if the phones IP changes.
[Windows Mobile Development and Hacking General] ivorh:
TBCompDesign,

The SMS message method of initiating a sync (AUTD) is being superceded by the directpush "technology":-

http://www.microsoft.com/windowsmobile/articles/directpush.mspx

http://msexchangeteam.com/archive/2006/04/03/424028.aspx

Exchange 2007 will no longer support AUTD.

having said that... theres no reason why an open alternative wouldnt be able to offer a choice of notification methods.

sebi112,

but when your mobile device disconnects, attempting to send to its IP will fail. you'd need to make sure the internect connection stayed active, in which case you may as well hold a socket open.
[Windows Mobile Development and Hacking General] ivorh:
Version to test

Ok a first version to try out the idea can be found at:-

http://myth.ivor.org/Notify.pl

http://myth.ivor.org/OpenSync.exe

As mentioned. Very pre-beta. :)

At the moment you will need to run the service on a dedicated port if you are already using port 80.

Notes:

1. the app isn't a service, it just runs in the foreground and

2. it logs debug/status info to the screen as it runs.

3. you'll need to configure the user map that's at the start of the Notify.pl file.

4. Since this is just a test the app does not try to reconnect on disconnection.

5. On the WM5 app, just enter the server name (with no http:// prefix) and the port number (default for the perl script is 8010).

6. Select the account name you want synchronising.

7. The username is the name you enter in the map (at step 3).

8. Something is terminating the client app after a period of inactivity... does a WM5 app need to keep pumping messages when idle?
[Windows Mobile Development and Hacking General] pof:
Hey ivorh! Thanks for the great work :D

Seems to work nicely here:

Notify waiting for clients on port 8010...
New connection from 62.xx.xx.xx
URI: /OpenPush?User=pau&Cmd=Ping
Cmd: Ping, User: pau
Ping received
Start watching: /home/pau/.maildir/new
URI: /OpenPush?User=pau&Cmd=Ping
Cmd: Ping, User: pau
Ping received
URI: /OpenPush?User=pau&Cmd=Ping
Cmd: Ping, User: pau
Ping received
Swallow the callbacks
watch - /home/pau/.maildir/new/1166442176.4697_3.s0 watcher - /home/pau/.maildir/new IN_CREATE
Send notify
URI: /OpenPush?User=pau&Cmd=Ping
Cmd: Ping, User: pau
Ping received
Removing dead socket 5

...but mail was not retrieved on device, any idea ?
[Windows Mobile Development and Hacking General] ivorh:
Send notify
URI: /OpenPush?User=pau&Cmd=Ping

Hmm, well that shows the daemon sending a notify to your device and your device responding.

Have you got the correct account set in the "account to synchronise"?

Also... does the debug display on the device show the activity correctly?
[Windows Mobile Development and Hacking General] pof:
I choosed the ActiveSync account, as it is where I have my email pushed normally, but I guess I should add it as a normal IMAP account in poutlook. Will try now...

Yes, it's showing fine :)
[Windows Mobile Development and Hacking General] pof:
Yah! that was it... added a normal imap account and now is working like a charm!!!! :D :cool:

Very well done ivorh :D

Will keep it on all day and see if there's any difference in battery drain with directpush :)
[Windows Mobile Development and Hacking General] sebi112:
Do i need a emailprovider that supports imap idle or does it work with each imap email?
[Windows Mobile Development and Hacking General] abricko:
On the right track...

I applaud you for thinking in this line of thought...

I have a cyrus IMAP server running for my mail... I've been trying my hardest to figure out how to accomplish a PUSH notification to my phone. For me the DirectPush doesn't seem to be the right method to go... what's the difference between running my flexmail client and telling it to check the IMAP server every X minutes and having this directpush client doing basically the same thing... will they both not kill my battery... IDEALLY it'd be nice to send some kind of WAP push to the phone (like the emoze client will do).

For now my solution (which is expensive) is to have my server send me a SMS notification telling me I have a new mail waiting and then I can launch flexmail and do a send/receive... at least i'll not be killing my battery.

I will watch this development though because i'm sure something good will come out of this (especially if I don't have to use Outlook/Exchange)
[Windows Mobile Development and Hacking General] ivorh:
abricko,

what's the difference between running my flexmail client and telling it to check the IMAP server every X minutes and having this directpush client doing basically the same thing... will they both not kill my battery...

Hi there, well one difference is that you are doing a full IMAP sync every X minutes rather than just blipping out a dinky ping. Secondly... with that method you'd only get mail notification every X minutes so you'd want the interval as short as possible and then you'd only get your new mail once every 30mins/15mins/10mins whatever.... With the direct-push what is happening is that an HTTP/1.1 request is being sent to the server, the server is then holding the connection open, and sending a reply only when an email arrives. effectively pushing mail on demand. Only then if a mail is notified is a full IMAP sync initiated.

There are various reasons for implementing the code the way it is:

is that if we implement the exact same protocol as direct-push then we know that the networks will support it and tweak their connection profiles to be optimised for it, and we know it will work.

Secondly we can expect WM and/or the vendors packaging of it to be tuned/optimised for this behaviour.

Similarly by using the exact same protocol we can be sure that at the very worst we are producing a push-email system that is JUST AS GOOD as the MS direct push version.

Now... having said that... when the software/system is working, THEN we can start playing with it and enhancing improving it by adding additional/alternative push email semantics. For example allowing you to say for this server, please use IMAP idle as the push email method. Or implementing AUTD (which is being removed from the MS solution) which then automatically pulls mail for you so you don't need to manually sync.

sebi112

No the current app/system has no imap-idle requirement... however, that is likely to be added as an optional way of working.
[Windows Mobile Development and Hacking General] ivorh:
Update

Minor update to the app to 0.0.2 :-

http://myth.ivor.org/OpenPush.exe

Minor bug setting config settings on startup and app was being closed by WM because it was being too idle.

and renamed to OpenPush to avoid confusion with the existing OpenSync project... and because well it doesn't actually sync, it just pushes. :)
[Windows Mobile Development and Hacking General] bvinson:
Was there every any update on this project? Does it seem to be working for everyone?
[Windows Mobile Development and Hacking General] ivorh:
Hi,

I've been a bit busy to do any more on this yet.. I've got distracted adding a google-maps download feature into.. http://www.callnetuk.com/home/shanks/GPSMap.html

and refining my WM development skills.

Anyway, the current version works ok as a proof of concept, but needs more work to be useful everyday.

At the same time I'm toying with implementing it using IMAP idle as an alternative, the test I did with it was very impressive.. makes you wonder why MS didn't simply implement a decent IMAP client app in the first place.
[Windows Mobile Development and Hacking General] bvinson:
I'm not surprised MS didn't implement IMAP IDLE. Currently it makes you get an Exchange server to use activesync, which is more money for MS.

Its great that toying with IMAP IDLE seems promising. If you need any testers let me know and I'd be happy to help.
[Windows Mobile Development and Hacking General] sebi112:
yeah imapidle. if you need a tester just let me know.
[Windows Mobile Development and Hacking General] mbreuer:
Thanks - excellent. One change for the script... if monitoring /var/spool/mail/<user>, you need to add IN_MODIFY to the inotify mask. Sendmail seems to keep the file open & doesn't trigger IN_CREATE or IN_ATTRIB.
[Windows Mobile Development and Hacking General] tdaly001:
Argosoft .NET

I have been working on the same problem and agree completely that a simple piece of companion software on the email server should be able to accomplish push email. I currently run Argosoft's email server. From the author of Argosoft, the new.NET server will support the IMAP IDLE functionality. I hope to try it out over the weekend, but I still have 2 questions before I dive in:

With IMAP IDLE as the method, will I need to use an email program other than the one bundled in WM 5? If so, will the messaging app bundled in Crossbow WM 6 support this natively?

Has anyone tried using Argosoft .NET version of the email server in this way?

Any news or help is appreciated.

Tom Daly
[Windows Mobile Development and Hacking General] DR400:
hi all !

No improvment since last post (21-03-07) ?

I desperately look for sth this useful ...

BTW I'm a guinee pig for any trial of any kind in respect of ivorh's soft (just let me know ...)
[Windows Mobile Development and Hacking General] Z3rO`:
I'm really eager to try this out too. Is there any development going on lately?

Will it work with any imap idle server? E.g. GMX?

I'm by no way a programmer, but wouldn't it be the easiest way to write a little app that sits there and waits for the imap (idle) server to send out the "you have new mail"-packet, then tell poutlook to do a send/receive?

If that's the way your app works then i would gladly like to test it out, since Flexmail isnt really an option (want to keep poutlook) and vgsmail is crashing a lot.

Greets

Z3rO
[G2 Q&A, Help & Troubleshooting] Formhault:
I'm using a Galaxy S4 (Black Edition, just got it - I really shouldn't) now... been using a white one for almost a year, then decided I should get rid of it and get an all black one, with warranty. I should have tried some other different model instead, I guess...

I might be able to sell it. With nothing else to get at this price point (aside from the Nexus 5, which is a no go due to poor speakers and battery performance and the HTC One which would be a more like a sidegrade if not a downgrade), I've turned my head towards the LG G2.

I know the LG G2 does not have a microSD card slot, and I also know it comes in both 16GB and 32GB flavors.

----------

So... first batch of questions (I sure will think of more :D ). Thanks in advance!

1) Is there any difference between the 16GB and 32GB variant, aside from the actual storage? In terms of ROMs and kernels support, I mean. The last thing I want is to buy the 32GB model and realise I can't flash anything on it because all the awesome development (dorimanx? :D ) is happening on the 16GB model and nothing of that works on the 32GB one :eek:

2) How fast did you get used to the physical button layout? I hear once you get used to them, they're freaking awesome.

3) Battery life... is stellar, right (dorimanx awesomeness? :D )? Like... 6~7+ hours of screen-on time, like I saw reports of in some places?

I can get 4 hours of screen-on time out of my Galaxy S4, maybe 5 at best (with very low screen brightness and little to no gaming, perhaps).
[G2 Q&A, Help & Troubleshooting] bender_007:
1) Basically just the storage, you can get a small "meenova" stick. Roms are vice - versa :)

2) Buttons !.. YES ! :) Knock on / knock off (sweep to sleep-dorimanx) etc etc etc...You'll keep tapping every other device (which hasn't got the knock on/off) and wonder why the heck it isn't implemented into all devices. Also vol up + down - genial..

3) Battery life is very good. Depends on what you're doing.

Since you're switching devices there might be some vice and versa opinions on your behalf. But at the end, the g2 wins.
[G2 Q&A, Help & Troubleshooting] njstein:
1) I'm not sure. But I keep up in the development forums and never have I seen a 16gb only version of something vs a 32gb.

2) Very quickly. I love the back buttons, very accessible when needed.

3) superb battery life. I'm running stock with dorimanx kernel and get those kind of numbers with automatic screen brightness, constant Web and app surfing and a little bit of gaming. I do listen to music on mine A LOT (2-3 hours with v4a and neutron) and still get great battery life.

I recommend it, I doubt you'll be disappointed!
[G2 Q&A, Help & Troubleshooting] Formhault:
What? I don't get it :D. So... do all ROMs, kernels etc. work on both the 16GB and 32GB variants? :D

That's what I hear from everybody, but of course, me, being used to the standard layout (volume rocker on one side, power button on the other), I'm quite skeptical. The button layout is not a problem, though, but I was just curious so I asked :silly:.

Well, basically, some Tapatalking, browsing the Internet and playing a game (Castle Clash - yes, it got me addicted, f*** my life) throughout the day, on Wi-Fi or 3G... which usually yields 3h30m of screen-on time with ~1 hour of gameplay. I'm sure the G2 will be able to top that by at least an extra hour, though, at least that's what I make from all battery reports out there :silly:.

Yeah... there's always gonna be that awkward feeling I get every time I switch devices. 1) leaving community 2) entering new community 3) getting used to the device 4) missing the old device :silly:

The G2 wins for me because of the expanded storage (32GB vs. only 16GB on the S4 - no more microSD crap, having to deal with two storage devices), better performance and screen (I'm so sick of this AMOLED... even this new one is rubbish, but with AMOLED it's all about luck, as 1 out of 3 devices have weird / uneven colors when it comes to white / gray).
[G2 Q&A, Help & Troubleshooting] Formhault:
I can't get a 16GB variant. No way! 32GB for the win!

Buttons, yeah, nevermind, they're so awesome I shouldn't have brought them up as they're not an issue :D.

Battery life... just the answer I expected :). DorimanX is the best - another reason why I'm switching to this device (kind of late, hope he doesn't buy a new device soon, lol).

I won't be dissapointed by the G2... if I manage to sell the S4 and get a G2 in the condition I want (brand new, with warranty and all that). By the looks of it so far, it appears that in less than 24 hours I could be selling this and buying the G2. Hope that works well...
[G2 Q&A, Help & Troubleshooting] bender_007:
In general, you just have to match the rom to your variant

d800, d801, d802, d803 etc...

we don't diff 16 vs 32 gig for custom roms.

And I also come from samsung and htc and this knock on, off, back rockers are just perfect..no problems at all getting used to them :)
[G2 Q&A, Help & Troubleshooting] Formhault:
How about AOSP based ROMs? Are they working well? And... knock... has that been implemented on anything else except LG ROMs?

I know I could find this info if I searched through the forum but I figure someone who already has the device has already gone through all these and is able to provide an all in one answer, so to say.

RIP English, lol.
[G2 Q&A, Help & Troubleshooting] bender_007:
They do work pretty good, but the stock ones work so nice.

You've got plenty of roms to try. But you need to read. The g2 is really really brickable.

Someone should write a book: "1001 ways to brick the g2"

knock on works on most aosp roms, knock off works mostly only by tapping the notification bar.
[G2 Q&A, Help & Troubleshooting] Formhault:
I love SlimKat, so... go go AOSP and sc**w everything else :D.

Sh*t. Care to elaborate? :losinginterestallthesuddenthisshouldbeanactualemoticon:
[G2 Q&A, Help & Troubleshooting] bender_007:
Enough to see the q/a thread. If you follow some main guides you are safe. Also people help out a lot so mostly everything is fine.
[G2 Q&A, Help & Troubleshooting] jamesd1085:
Which carrier are you using? I have tmo and came from Verizon s4 and have no regrets...the stock ui is very much like aosp/vanilla and is very fluid...love the aosp ROMs as well...battery life is amazing on Mahdi ROM...13 hours on battery today and still at 91% with some calls and texts as well as browsing xda forums on my breaks at work...switching from s4 you won't have any regrets
[G2 Q&A, Help & Troubleshooting] Formhault:
I'm on Cosmote (Romania). Irrelevant, though. :p

You know Odin? Is there such a tool for LG? Guess not, huh? :laugh:
[G2 Q&A, Help & Troubleshooting] jamesd1085:
There are a couple tools similar to Odin to flash back to stock which will fix most major issues...but there are also a lot of great ops to fix other issues
[G2 Q&A, Help & Troubleshooting] Formhault:
So... the G2 is very easily brickable... That's a bummer. How about revivability? :D
[G2 Q&A, Help & Troubleshooting] jamesd1085:
I have had mine about a month and am a flashaholic...not once have I bricked my device...its the people who aren't reading everything before flashing that are having issues...and I haven't heard of a large amount of permabricks so I should say so...I had more issues on my s4 learning than on g2
[G2 Q&A, Help & Troubleshooting] Formhault:
I did my S4 in like 5 minutes. Flash PhilZ recovery in Odin, boot up recovery, full wipe, flash ROM :p. Piece of cake. The S4 is not really brickable, by the way. Unless you flash a wrong bootloader, I guess...
[G2 Q&A, Help & Troubleshooting] jamesd1085:
Not the case with the Verizon s4...it was a nightmare...but nonetheless I will never buy a Samsung device again due to my experience... After buying my g2 though I'm pretty sure I'm going to stick to lg
[G2 Q&A, Help & Troubleshooting] Formhault:
Yeah, lucky I don't have to meddle with locked bootloaders, hehe.

How fast and easy was to get G2 going with unlocking the bootloader and throwing a custom ROM on it? :p
[G2 Q&A, Help & Troubleshooting] jamesd1085:
When I got mine it required a bit more...but now you can 1 click root with towelroot and install recovery with autorec...after that you just read up before installing anything and flash away
[G2 Q&A, Help & Troubleshooting] Odysseus1962:
I got my G2 about 3 weeks ago and love it. I previously had an Amaze 4G and prior to that an HD2. There are no comparisons between the devices. I happened into it by chance. My Amaze was stolen and I needed a replacement with a good camera for work quickly. I went into the T-Mobile store intending to buy a Nexus 5, but the G2 was on sale for the same price. After comparing the specs, it was a no brainer decision.

I'm currently running the stock Kit Kat ROM and kernel (rooted and debloated) and find the native OS to be the most pleasing manufacturer's UI I've used to date. Very close to AOSP and only a fraction of the crapware found on other UIs. This is the first handset I've owned where I didn't want to immediately remove the stock ROM because it's so well integrated. Whatever features that LG didn't include that I wanted are easily installed with Xposed and appropriate modules. All in all the G2 is probably the best bang for the buck (value for your money) on the market.

Good luck
[G2 Q&A, Help & Troubleshooting] jhamdw:
1) I've been roaming around the threads and forums for a couple months and I have never seen 16gb vs 32gb based development. Only variant. Also, lg uses two different types of displays, lgd and jdi. when flashing roms, jdi panels may result in on-screen white lines, but theres usually a jdi kernel provided to flash after flashing the ROM to fix this issue. I haven't really looked into this, since mine is lgd, but just fyi.

2) very fast. I find my index finger just naturally resting around that area on the back of the phone whenever i'm using one hand. also the knock on/off feature is extremely convenient.

3) for me personally, I have never been able to get more than ~5 1/2 hours of sot. little gaming, mostly chatting (kakaotalk), some browsing, automatic brightness on. even with greenifying, disabling location, gps, auto-sync, bluetooth, etc. But taking out kakao, I'd say around 7, MAYBE 8 hours is definitely possible.

I'm on the verizon variant and it takes only about a couple minutes really. ioroot to root the phone (not sure about your variant), installed autorec.apk to install twrp recovery (again, not sure about your variant). Then you'll be able to flash roms right away. For stock based ROMS, I use CloudyG3 (there's also another G3 port by a different developer, OptimusG3) with dorimanx kernel, and as for AOSP I usually go with Mahdi.

this is true about people not reading. just know exactly what you're flashing and you'll be fine.

no Odin, but there are a couple stickied threads on this forum that tell you how to flash back to complete stock (basically unrooting/unbricking) in case you ever need to.
[G2 Q&A, Help & Troubleshooting] Formhault:
I'm not sure I want to stick to a JDI kernel forever, if I happen to get a JDI variant... all I want is DorimanX awesomeness :p

Do kernel devs patch their kernels to work on the JDI versions, as well?
[G2 Q&A, Help & Troubleshooting] jhamdw:
the jdi stuff is primarily with aosp I believe. dorimanx is for stock so you shouldn't need to worry, as you would not be able to run dori's kernel on aosp anyways. There is, however, a modded version of dorimanx out there that is compatible with aosp vanir rom.

basically, if you want dori, you'll be flashing stock-based roms. Stock-based roms won't have the issue (as far as I know)
[G2 Q&A, Help & Troubleshooting] bender_007:
The patching is quite easy, savoca made a flashable for it, I've made the installer for it. There wont be any troubles.

Like someone said: "brickable" = if you read carefully and don't take ota for example(having custom recovery and ota..) you're mostly safe.

And don't crossflash variants.
[G2 Q&A, Help & Troubleshooting] Formhault:
Oh... I thought it's a patch that needs to be implemented manually, in the decompiled kernel... if it's just a separate flashable .zip which works on any kernel, awesome :).

Like those people who skip steps like "make sure you don't drop a rock on the phone while flashing" :silly: rofl

Huh? Oh, you mean flashing something that's designed for the Sprint LG G2 on a D802? :silly: :laugh:
[G2 Q&A, Help & Troubleshooting] bender_007:
1.

2.

3.

exactly.

You're from samsung world. Let's say you flash a note 2 philz recovery on your device or like me, on s3.

It contains the kernel also, also it has the higher voltages for the larger digitizer and screen. And kaboom, your digitizer is dead forever and ever and ever :)

Just an example.