Related
Will multitaks on mango, allow an app such as whatsapp or any messiging client run in the background like in android?
Thanks
Yes, it will. But it's more like iOS than Android. Android doesnt freeze the app. That's why Android use more battery usually.
It will freeze and let you come back to where you stopped.
I know that, it freezes the app, but can i still recieve messages while the app is frozen in the background like andorid. i hate ios.
Yes, you can, it doesn't kill the process, so it keep you connected.
Running in the background and the sockets API's will allow the IM programs we are used to. You will get messages while its not open just like your txt messages.
Apps will be forzen but will be allowed to run "live agents" in the backgrounds. These live agents can recieve messages and can give you a toast notification. These notifications will be deep linked... i.e. clicking on the notification will take you directly to the conversation. So overall it will behave just like any chat program on Android, but the whole app will not be running and thus will save battery and won't impact performance of the phone.
arkavat said:
Apps will be forzen but will be allowed to run "live agents" in the backgrounds. These live agents can recieve messages and can give you a toast notification. These notifications will be deep linked... i.e. clicking on the notification will take you directly to the conversation. So overall it will behave just like any chat program on Android, but the whole app will not be running and thus will save battery and won't impact performance of the phone.
Click to expand...
Click to collapse
This is only partially correct. Live Agents aren't especially useful for things like IM and messengers because there are restrictions on how often they can run and for how long. I think the most a Live Agent can run is once every 30 minutes and for 15 seconds.
Most of the apps you guys are asking about (i.e. WhatsApp) will work like they do on iOS, with push notifications.
Thanks everyone, I rember live agents now. Thanks, Otherwise I would have had to switch back to andorid. And Tbh I lost WP7 a alot.
andoridkiller said:
Thanks everyone, I rember live agents now. Thanks, Otherwise I would have had to switch back to andorid. And Tbh I lost WP7 a alot.
Click to expand...
Click to collapse
How are push notifications and Live tiles on Vodafone? Do they break too for you? Wondering if it's carrier specific.
I wish i could anwser that question accurately but im a ROM junkie so every month i either hard reset or change my rom. However regarding vodafone nothing has broken, all fine, but i think its because i reset my phone a lot, mainly to get free some space up.
Peew971 said:
How are push notifications and Live tiles on Vodafone? Do they break too for you? Wondering if it's carrier specific.
Click to expand...
Click to collapse
I often hear people talking about push and carrier. But I live in Brazil, where WP7 is not supported yet, and I have absolutely no problem with push.
And does carrier really matters to push?! If you turn plain mode on and turn wifi on, will it change something?
mikeeam said:
I often hear people talking about push and carrier. But I live in Brazil, where WP7 is not supported yet, and I have absolutely no problem with push.
And does carrier really matters to push?! If you turn plain mode on and turn wifi on, will it change something?
Click to expand...
Click to collapse
Please listen to the facts. It IS highly dependent on how your carrier handels and cuts-off data connections. This is mainly a European carrier problem because of the techniques some carriers use to free up the network...
And indeed using wifi only (without a SIM card in your phone) will keep push working the way its supposed to work. Well unless you have a router which does not work well wit wp7.
Here is the explaination and what they did to make it function correctly in Europe
http://channel9.msdn.com/Blogs/Windows-Phone-7/Inside-the-Mango-Dev-Tools
If you watch channel 9 it is explained.
Well, it's not non-sense. We don't have problems with cut-off data here. So i'm not "spreading nonsense". It's just a problem that I never had with any smartphone.
Still, yes, you're right, carrier can do that. Good luck to you (;
mikeeam said:
Well, it's not non-sense. We don't have problems with cut-off data here. So i'm not "spreading nonsense". It's just a problem that I never had with any smartphone.
Still, yes, you're right, carrier can do that. Good luck to you (;
Click to expand...
Click to collapse
True, sorry. Its just a bit frustrating if you are facing the problem yourself and there are people telling you well are you sure its this and that, since we dont have that problem at all here
Yeah we know... I just found out the hard way, my carrier is just one of the unfortunates. All other dutch carriers apparently are being handled fine by WP7.
I dont know an exact list of all carriers with whom WP7 PN does not work, however TMobile NL and I have heard Tre Italia and O2 UK and apparently the carrier of Peew are problem cases as well. Not sure though, but it does not really matter as apparently they fixed these problems with Mango so lets just wait and see. And I have a one year contract so I can ditch them if its not fixed, it sucks for the people who are tied into a 2 year contract though.
Tested with Skype version 3.2.0.6673 (released 1st July 2013) on various
Android devices (Sony Xperia Z, Samsung Galaxy Note 2, Huawei Premia 4G
The Skype for Android application appears to have a bug which permits the
Android inbuilt lockscreen (ie. pattern, PIN, password) to be bypassed
relatively easily, if the device is logged into Skype, and the "attacker"
is able to call the "victim" on Skype.
This can be reproduced as follows with 2 Skype accounts, and 2 separate
devices to use with Skype. The target phone is presumed to have an Android
lockscreen configured and in use, and to be locked during the test.
1. Initiate a Skype call to the target device, which will cause it to
wake, ring, and display a prompt on the screen to answer or reject the call
2. Accept the call from the target device using the green answer button
on the screen
3. End the call from the initiating device (ie. the device used to call
the target phone)
4. The target device will end the call, and should display the
lockscreen.
5. Turn off the screen of the target device using the power key, and
turn it on again
6. The lockscreen will now be bypassed. It will remain bypassed until
the device is rebooted
Similar to (ironically enough):
http://arstechnica.com/security/201...een-lock-on-up-to-100-million-android-phones/.
Seems that internet based calling apps might well be "unlucky".
I suggest logging out of skype when not using it, until there is a fix.
Thanks to Turl for originally bringing this to my attention.
Greetings pulser_g2,
Thanks for posting this. I found that all these screenlock bypass vulns (including yours) won't work if a enterprise policy is enforced on the target device. I've tested with 2 different smartphones, Note 8.0 and Note 2. Both with the current stock firmware. Can you or anyone else confirm this?
Cheers,
Michael
c0rnholio said:
Greetings pulser_g2,
Thanks for posting this. I found that all these screenlock bypass vulns (including yours) won't work if a enterprise policy is enforced on the target device. I've tested with 2 different smartphones, Note 8.0 and Note 2. Both with the current stock firmware. Can you or anyone else confirm this?
Cheers,
Michael
Click to expand...
Click to collapse
Hi Michael,
Thanks for the tip. However, forcing enterprise policy onto a device that does not need it should not be a solution for a bug like this (not ranting against you, please don't take it that way). Skype was already informed about this a couple of weeks ago and nothing has been done afaik.
I received a Skype update today from the market, so I guess it might be worth checking if the bug can be repeated or if it has been fixed.
Hi egzthunder1,
I don't take your post personal. My post was not made with the intent to be a bugfix. I just want someone else who also has access to provisioned devices to confirm my observation. Additionally if my observation is correct then it should be mentioned in a security advisory that enterprise provisioned devices with an enforced password seem to not be affected by all these lockscreen bypasses. I'm just discussing here
Does andybody know which wrong usage of the Android-API might be used here? I'm developing myself an app which switches the Screen on and shows information without the need to unlock the device. Know I'm concerned that I might use the API wrong, too. There were also such bugs in other apps in the past month, so there must be some wrong usage type. Saidly I didn't find anything about it via googling. If you have links, please share.
SamsungPisser said:
Does andybody know which wrong usage of the Android-API might be used here? I'm developing myself an app which switches the Screen on and shows information without the need to unlock the device. Know I'm concerned that I might use the API wrong, too. There were also such bugs in other apps in the past month, so there must be some wrong usage type. Saidly I didn't find anything about it via googling. If you have links, please share.
Click to expand...
Click to collapse
It seems to be related to the use of the permission to disable the lockscreen.
I.e. http://stackoverflow.com/questions/12021800/disable-delay-android-lock-screen-programmatically
You want to ensure you definitely disable the option once done. I suggest you create a test plan and ensure even if everything goes wrong, the lock will still get enabled again in the end.
c0rnholio said:
Hi egzthunder1,
I don't take your post personal. My post was not made with the intent to be a bugfix. I just want someone else who also has access to provisioned devices to confirm my observation. Additionally if my observation is correct then it should be mentioned in a security advisory that enterprise provisioned devices with an enforced password seem to not be affected by all these lockscreen bypasses. I'm just discussing here
Click to expand...
Click to collapse
Hmmm that is interesting actually.
I need to see if I can replicate this by forcing provisioning manually.
I don't have an exchange server unfortunately (I use my own mail server that uses the protocol but doesn't do the complex provisioning.)
I'll have a look though as I think it supports provisioning in the configuration where it emulates Exchange. I believe this likely is a workaround for enterprise users.
This would be enough motivation actually to look at setting up proper provisioning of my devices.
Thanks for letting me know
I am starting this thread to be a place for Terrain owners to come for the latest info on how to root and flash their phones. The Terrain is one of the best "rugged" phones on the market, but it has been abandoned by it's manufacturer, leaving owners to find their own solutions to problems and upgrades. This is actually a good thing price wise as you can now buy a brand new Terrain for less then $85. The Terrain has about as of hardware specs as any other ruggedized smartphone on the market currently, but at one third or a 1/4 of the cost. This makes this phone a huge attraction to anyone who is looking for a rugged waterproof phone on a budget and is why this guide is essential for users.
The NEC Terrain still has plenty of life left and this is why we need to come together and find solutions for it. Please feel free to post you success stories in rooting and flashing your terrain to this thread for the benefit of all. Hopefully, will be able to form a complete guide from all the information that get's posted here.
Thanks.
Hi!
I myself just today recieved this phone, and it would be great at least to debloat it.
Previous threads on XDA, just for reference:
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
[Q] Rooting NEC Terrain
[Q] Unlocking of NEC Terrain SIM/Root
gamerka said:
Hi!
I myself just today recieved this phone, and it would be great at least to debloat it.
Previous threads on XDA, just for reference:
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
[Q] Rooting NEC Terrain
[Q] Unlocking of NEC Terrain SIM/Root
Click to expand...
Click to collapse
Thanks for the post and the links. It appreas that much of the information on these links are still a work in progress. Hopefully this work will continue and we can create a How To guide from this.
For those that may be interested. You can buy the NEC Terrain Unlock on Amazon for $79.99. Here is the link.
http://www.amazon.com/NEC-Terrain-UNLOCKED-WaterProof-DustProof/dp/B00KZPI04S/ref=sr_1_1?s=wireless&ie=UTF8&qid=1405614968&sr=1-1&keywords=nec+terrain
For full specs on this great phone you can go here.
http://www.gsmarena.com/nec_terrain-5553.php
Well, I almost bricked it few days ago. :good:
I read a thread about a patch to unlock GSM in CDMA phones and saw there a code to enter some hidden menu. I entered that menu and messed a little with band settings (wanted to get LTE to work with my operator). Next thing I know Terrain stopped receiving any GSM signal and for next hour I tried to fix it. Factory reset got me 2G signal and that's all.
It turned out that the only way to fully fix it is to re-flash firmware or radio module and as we know that can't be done.
Well, this is not about unlocking or flashing, but it is a solution to another problem I and many other have been having with the predictive text bar blocking critical function keys from being accessed. The predictive txt bar is a function of the Adaptxt keyboard app and disabling it does remove that bar, but the keyboard also loses all special character function, upper case letters and numbers. After trying more then a dozen keyboard apps to replace adaptxt, I found one that works and brings back all keyboard functions without the stupid predictive text bar. It is called TouchPal.
https://play.google.com/store/apps/details?id=com.cootek.smartinputv5&hl=en
Forgive me for this slight OT-posting, but it's not that easy to find people with this device - let alone an unlocked one. I'm located in Germany and the device runs just fine - except for the fact that Tethering does not work - neither USB nor WIFI. The PC can connect to the phone, however the connection in Windows 7 always is shown as being limited (no internet access), while internet on the phone works fine.
GMail - as well as some other functions of google also rarely sync and basically just do so on request, while they sync just fine when being connected to Wifi. And no, background data are not restricted in the settings.
Has anyone experienced something similar?
laserdrome said:
device runs just fine - except for the fact that Tethering does not work - neither USB nor WIFI.
Click to expand...
Click to collapse
I have the same problem! After few minutes of "thinking" phone reports "There is a temporary nework problem... bla, bla, bla"
Is there any suggestions how to fix it?
iDomino said:
I have the same problem! After few minutes of "thinking" phone reports "There is a temporary nework problem... bla, bla, bla"
Is there any suggestions how to fix it?
Click to expand...
Click to collapse
Well actually I know that message as well. For me changing the APN helped. You could also try to restart the phone. I just remember I also had this problem sometimes. But like I said - even without that particular message I would not get tethering to work.
iDomino: Do you also experience the problem with syncing that I had?
That's funny, actually I haven't noticed syncing problems untill I read your posts. I myself have all the same problems that you mention.
Even more of that, Terrain has some silly feature that TURNS OFF WI-FI if it thinks that that hotspot has no internet connection. It is massively annoying and can drain all your data traffic. The only solution that I found is to install the app "Smart Wi-Fi Toggler", it constantly turns wi-fi on if terrain turns it off, but only in places where I turned wi-fi on myself (like home and work).
It's a pity the phone has so many flaws and due to its tight security and the locked down NEC mobile devision no one can do anything about it. I wonder if this just affects the users who use an unlocked phone outside the US or if people in the US have similar problems. I have tried contacting NEC about this - actually about providing us with some kind of unlock mechanism - but all I got was this:
"Dear Sir,
Thank you for inquiry.
We, however, regret to inform you that our phone is not available about your request.
If you have any issue, would you try to contact the company or shop where you have purchased this model, who might be of help to you.
Thanks and Best Regards,
Fujii /NEC"
By the way, I discovered a new bug: When Roaming the actually used Network-Provider is not shown and I also didn't find a way to choose one...
Do you also experience the problem with syncing that I had?
Click to expand...
Click to collapse
I had some sync problems and I don't know working methods to fix it.
First time I solved it this way:
turning off apps sync -> open Gmail app -> it will show notification offering to enable synchronization -> use it -> sync works.
But this solution worked just once. (
Other time sync turns on by itself after one day disabled.
P.S. My Nec reboots while connecting via USB to ubuntu laptop.
Battery life
Can someone tell me how your Terrains battery hold up charge? Because mine discharges completely in about 10 hours (without using phone at all). I think it's wakelock problem.
iDomino said:
P.S. My Nec reboots while connecting via USB to ubuntu laptop.
Click to expand...
Click to collapse
Does it crashes once or infinite loop begins? I had infinite loop problem while connecting NEC Terrain to Ubuntu, Linux Mint, Debian or CentOS. Removing "ModemManager" package solved it.
FFDA said:
Can someone tell me how your Terrains battery hold up charge? Because mine discharges completely in about 10 hours (without using phone at all). I think it's wakelock problem.
Does it crashes once or infinite loop begins? I had infinite loop problem while connecting NEC Terrain to Ubuntu, Linux Mint, Debian or CentOS. Removing "ModemManager" package solved it.
Click to expand...
Click to collapse
My phone works about 25-30 hours (30 min. calls, 5-10 sms, 30 min. messaging, 2 hours e-mail, internet & other applications. No video/gaming/music at all).
Infinite loop. Removing "modemmanager" helps! Thank you! :laugh:
Also got spontaneous rebooting after installing FTP Client made by Zifero. :silly: Removing app solved the problem.
Dreaming about root and working wi-fi tethering.
Who have usb driver of nec terrain? I need it, thanks
zolahn said:
Who have usb driver of nec terrain? I need it, thanks
Click to expand...
Click to collapse
Maybe this topic will help.
Cpu-z shows only 665MB RAM on device... Where are another 335MB???
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
Another Terrain user here!
Hi guys!
i am Kharl
i am another Nec Terrain user here!
due my lifestyle, i needed a phone which could gives me reliability and power under ANY circunstance, that could be done by any rugged phone, BUT i needed querty keyboard, fm radio, gps, gyroscope, accelerometer, loud speakers, that could work worldwide and touchscreen... the only one with those features was the Terrain... and with the extra, that it is amazingly cool, i dont know opther but i find this phone really cute, very sober and elegant design.
well, i live outside USA so, for me, to work it couldnt be locked to ATT, so i was able to get one unlocked.
my phone has almost all the problems you mentioned, althught i am still happy with it and i am not going to change it because its problems does nto interfere a lot with me, BUT of course id like to get those problems sovled.
trying to solve the problem i bough three of thes phones and all the three had the same problems
the first one was by mistake, locked to att, but it had the same problems, random restart and locked hotspot, i sold it, i got a second one, works with any sim, everything fines, but with the same problem, random restart and no hotspot, i bought a third one to see if the problem was with my particular phone... and n luck the same problems.
it has some other minors problems, like no stereo audio recording despite it has two mics and IT STATES IT CAN record in stereo, but thats not a problem, i can deal with that, and sometimes the people at the other side (while in a call) says my voice sounds like from within a box (lack of trebble or too much bass) and when i press the check too much to the phone boddy there is also clarity sound problem.... but thats ok....
regarding the two main problems
random reboot and hotspot
many of us suspect what the cause is
for the random reboot many could think it is a installe app which is causing it... NO, because it does it at factory state, to solve that i dotn think root is needed, there is a certain factory process that is causin to reboot, the reboot is VERY random, could doit threee times in a day or could happen only three times in a week, what i have notice is that it happe lessoften in cold weather.
the hotspot problem IT IS cause because att locked that function, even when the phone is ulocked, that part remain locked because ATT.
what about you guys?
u can try hard reset for begging
Hi All,
It is my request that if you have not tried this or witnessed it first hand, do not reply. I've siphoned through entirely too many threads with those quick to respond no only to have the "no" be proven wrong within the same thread.
That being said: Project Fi
Officially only supported on several devices. The biggest feature lost to those who do not use a supported device is the ability to switch between networks. While I'm still on the fence with rooting my S9 (assuming I'll have to), one thread I found with several confirmations seemed a bit promising to keep the roaming feature.
Editing build.prop to reflect a Pixel 2 allows the device to be activated. While several individuals confirmed this works to activate, none have confirmed whether the roaming feature works as well. Theoretically, it should. Others have lost this feature because the IMEI of the 'surrogate' phone is whats being registered. Makes sense since Sprint (and I believe US Cellular as well) is like Verizon in that they register the device vs the sim (Of course more complex than that, just typing through the logic).
Therefore, if editing the build.prop allows you to activate Google Fi then theoretically the IMEI of said device should also be registered and should work. I'm looking for confirmation on this. There's also a big question about the ability to edit build.prop without rooting and implications on KNOX, Samsung Pay, etc which is why I'm hesitating. Just looking for this first bit of information first.
iAmJG said:
Hi All,
It is my request that if you have not tried this or witnessed it first hand, do not reply. I've siphoned through entirely too many threads with those quick to respond no only to have the "no" be proven wrong within the same thread.
That being said: Project Fi
Officially only supported on several devices. The biggest feature lost to those who do not use a supported device is the ability to switch between networks. While I'm still on the fence with rooting my S9 (assuming I'll have to), one thread I found with several confirmations seemed a bit promising to keep the roaming feature.
Editing build.prop to reflect a Pixel 2 allows the device to be activated. While several individuals confirmed this works to activate, none have confirmed whether the roaming feature works as well. Theoretically, it should. Others have lost this feature because the IMEI of the 'surrogate' phone is whats being registered. Makes sense since Sprint (and I believe US Cellular as well) is like Verizon in that they register the device vs the sim (Of course more complex than that, just typing through the logic).
Therefore, if editing the build.prop allows you to activate Google Fi then theoretically the IMEI of said device should also be registered and should work. I'm looking for confirmation on this. There's also a big question about the ability to edit build.prop without rooting and implications on KNOX, Samsung Pay, etc which is why I'm hesitating. Just looking for this first bit of information first.
Click to expand...
Click to collapse
Are you talking in terms of just activating service? if so, i have a vzw s9+ and i switched to fi, just flashed to xaa and popped in the fi sim. no problems.
iAmJG said:
Hi All,
It is my request that if you have not tried this or witnessed it first hand, do not reply. I've siphoned through entirely too many threads with those quick to respond no only to have the "no" be proven wrong within the same thread.
That being said: Project Fi
Officially only supported on several devices. The biggest feature lost to those who do not use a supported device is the ability to switch between networks. While I'm still on the fence with rooting my S9 (assuming I'll have to), one thread I found with several confirmations seemed a bit promising to keep the roaming feature.
Editing build.prop to reflect a Pixel 2 allows the device to be activated. While several individuals confirmed this works to activate, none have confirmed whether the roaming feature works as well. Theoretically, it should. Others have lost this feature because the IMEI of the 'surrogate' phone is whats being registered. Makes sense since Sprint (and I believe US Cellular as well) is like Verizon in that they register the device vs the sim (Of course more complex than that, just typing through the logic).
Therefore, if editing the build.prop allows you to activate Google Fi then theoretically the IMEI of said device should also be registered and should work. I'm looking for confirmation on this. There's also a big question about the ability to edit build.prop without rooting and implications on KNOX, Samsung Pay, etc which is why I'm hesitating. Just looking for this first bit of information first.
Click to expand...
Click to collapse
I read here on XDA that Google Fi would be able to be activated on other devices and I'm almost positive the S9/9+ were included. You wouldn't need to edit build.prop or anything. You wouldn't get automatic network switching though since that's a hardware / firmware thing from what I remember reading. The service itself would work and you wouldn't need a surrogate phone to make it work initially.
Whether that's live or not yet I don't know. Rooting any Samsung device past the S4 or S5 I believe trips Knox permanently. That's also assuming you don't have a u965 / u960 device, which can't be unlocked / rooted.
Edit: appears to be love for the "majority of Android phones". https://www.google.com/url?sa=t&sou...BBAB&usg=AOvVaw0Yb-mP_-PqDTtcLG7TWkwM&cf=1
Hi all,
I have searched for any past references to this issue quite a bit but found nothing in here so thought I would ask. Maybe my searching skills are not good
Whenever an app that requires aGPS starts, both my sims and my wifi disconnect and reconnect in a continuous loop. This has started happening since I factory reset my phone and then installed my company's work profile in the summer. I had a look on the OnePlus forums and it's a known issue since the beginning of the year but OP have done nothing about it. I need my work profile because of course I work a lot from my phone and even though a recommended fix is to switch off location services so that this doesn't happen, location for me is a very important function on my phone.
Does anybody know of any solution to this that I couldn't find? Am I going to have to go the route of a custom ROM to address this? I haven't had a phone with a custom ROM since my XDA IIs so really don't want to do this
Thank you in advance!
nobody? . . .