Related
I've purchased a Milestone X720 for my wife, but I found the internal WiFi to work erratically at best.
It seems like it has no problem connecting to Google.com webpage (also it can sync mails and contacts), but when trying to access any other webpages (bbc.co.uk, espn.com, etc.) using the browser, it's always timing out. I know it's not a problem with my WiFi / internal network / router /internet connection, because I can navigate just fine using my HTC Desire or home laptops.
It worked for a while yesterday afternoon, then this morning wasn't able to connect to any website.
The wifi connection is using DHCP, and it shows a correct internal IP address and an excellent signal level. I don't think there's much more things I can tweak in the phone configuration, or isn't there?
Maybe it is a defective phone? Did someone experienced something like this? Should I return it and exchange it for a new one?
I'd appreciate any help.
Alex.
Actually, I've been having problems with my wifi. My wifi will stop working on any webpage at seemingly random intervals (I used to think it was when it went into sleep, but it happens when it's not in sleep now also). Eventually after restarting wifi so many times it'll glitch up and I have to restart the phone.
Providing your phone's stock (as in you haven't rooted it or the like) I'd recommend going to your carrier about the problem.
EDIT: I just checked through the posts on this board and some guy was having another problem with his wifi (different from both of ours though), he suggested getting WifiPowerSavingOff off the market, I'll try it and tell you if it fixes my problem. The only problem is it requires root access, I don't even know if it will fix your problem so you're better off sending the phone back (especially since rooting voids your warrenty). One other thing you could try is just a factory reset, it sounds like a software problem so that might work wonders, you might have to reactivate your phone afterwards though.
Well, thank you for your response.
WiFi was working OK when I came back from work, but is not working now.
The phone is unbranded unlocked, so I'll probably have to talk to the seller.
I tried to see if there was an update from Motorola, but every time I go to the System Updates it says that it is unable to connect to the server, so there's probably no available update for this phone yet.
lovecraft said:
Well, thank you for your response.
WiFi was working OK when I came back from work, but is not working now.
The phone is unbranded unlocked, so I'll probably have to talk to the seller.
I tried to see if there was an update from Motorola, but every time I go to the System Updates it says that it is unable to connect to the server, so there's probably no available update for this phone yet.
Click to expand...
Click to collapse
If it's unlocked OTA updates (updating through the settings) are probably disabled, because installing OTA updates will make you lose root (I'm assuming your phone also is rooted if it was unlocked by the seller). do you know what baseband your using right now? Also, have you installed rom manager or anything that can make nandroid backups?
I might be wrong, but I don't think it's rooted, I think it's just the way it's sold, SIM free and unlocked from factory, not by the seller.
Baseband is 3GSMEPU91A_U_91.07.56I
Well if you wanna double check, just look to see if a superuser permissions app is installed (if you don't find one it's not rooted), I never knew they sold them unlocked (although I'm in the US... so I doubt they do here). All I can say is to try a factory reset then, if that doesn't work then talk to the seller. It sounds like more of a software problem since Google works.
In the end it seems there is some kind of incompatibility between the phone and my WiFi router (a Belkin G). Yesterday I managed to borrow another WiFi router (Netgear) and it works flawlessly when connected to this AP.
I will keep testing during the weekend but I'm pretty sure this was the cause.
Thanks Shiny for your help.
Hi. I picked up a milestone via Ebay two days ago and had similar wi-fi issues. After reading a number of forums I discovered that the problem lay with my router - Siemans Gigaset SE587 (Tiscali). The wireless channel or regulatory domain was set to auto channel 1. I think this confuses the phone so with the help of the router manual I disabled auto and reset it to channel 13.
Wi-fi works flawlessly now and it hasn't affected my other devices. The link below might help.
At various points my Focus S seems to lose the ability to use it's data connection- either Wifi or 3G. I can't work out why- has anyone else experienced this? Web pages don't load, etc.
I installed a patch that allowed me to use Internet Sharing, I'm concerned this might have been the cause of it...
I've found that if I do not reboot my phone at least once a day I get random problems like that.
untogether said:
At various points my Focus S seems to lose the ability to use it's data connection- either Wifi or 3G. I can't work out why- has anyone else experienced this? Web pages don't load, etc.
I installed a patch that allowed me to use Internet Sharing, I'm concerned this might have been the cause of it...
Click to expand...
Click to collapse
I don't reboot my phone all that often. I've never seen it lose ALL data connection capability tho...
A regular power cycle doesn't hurt tho...
Can this be the issue?
I'm experiencing the same thing, but mainly when I'm connected to 3G. My phone shows it has full bars and 3G or 4G availability but I find 60% of the time my phone has little to no data going to my phone, so none of my apps or news feeds get updated or they get updated slowly. When I'm on wifi the phone works flawlessly.
I read this article,
http://pocketnow.com/windows-phone/hack-fixes-mms-on-unlocked-samsung-wp7-handsets
One of the odder quirks of Windows Phone 7 to appear since the platform's launch has been the absence of Automatic Data Configuration for users who swap SIM chips and network-hop with their unlocked handsets.
ADC should let the phone communicate with the network it's connected to in order to retrieve all the settings it needs in order to use the network's services. Samsung defended disabling ADC by saying that its phones are intended to only be used with a specific carrier
Now I know this is talking about MMS, but does anyone think it's related to 3G connectivity from a different service provider?
i am having the same problem, it started 2 days ago after i unlocked my phone, at&t gave me the unlock code, i had to enable hot spot & de brand by loading a file, i don't have problem with WiFi just 4G, it will be fixed if i re start the phone.
problem for me with wifi+3G
Not sure if this is the same as the OP. I run with both WiFi and 3G enabled most of the time. Basically everything will be working fine for a while, then I'll try to open a web page from Twitter and it will time out. Sometimes retrying will work, but it will take an abnormally long time to load the page. Other times it never works, and when I go to another app (e.g. mail) and try to sync, and that will also time out. When that happens I usually turn off either WiFi or 3G, then toggle the state of the one I left on (e.g. turn 3G off, then back on), and it clears up. I've never needed to reboot the phone. I don't have ICS enabled, but my phone is fully unlocked.
I've guessed this problem was caused by a lost or bad connection on one of the wireless protocols (like WiFi), where the phone thinks it is connected to WiFi and won't switch over to the other protocol (3G).
One more thing: I'm running 8107 and I don't remember this issue occurring before the upgrade.
M
mlekas said:
Not sure if this is the same as the OP. I run with both WiFi and 3G enabled most of the time. Basically everything will be working fine for a while, then I'll try to open a web page from Twitter and it will time out. Sometimes retrying will work, but it will take an abnormally long time to load the page. Other times it never works, and when I go to another app (e.g. mail) and try to sync, and that will also time out. When that happens I usually turn off either WiFi or 3G, then toggle the state of the one I left on (e.g. turn 3G off, then back on), and it clears up. I've never needed to reboot the phone. I don't have ICS enabled, but my phone is fully unlocked.
I've guessed this problem was caused by a lost or bad connection on one of the wireless protocols (like WiFi), where the phone thinks it is connected to WiFi and won't switch over to the other protocol (3G).
One more thing: I'm running 8107 and I don't remember this issue occurring before the upgrade.
M
Click to expand...
Click to collapse
I have the EXACT same issue as you state here. The problem has existed since day one with this phone. I updated through to 8107 and the issues still exist.
So now for some interesting/good news... my dad works for a large company that has direct access to AT&T Wireless Engineers, so he got in contact with an an engineer and explained this issue as both him and I experience the same issues. The engineer was able to get a hold of a Samsung Focus S and experienced the same problems for himself. He then escalated the issue directly to Samsung who in-turn escalated this to Microsoft. Apparently Microsoft claimed the issue was theirs and they are now working on an update to rectify the problem. Samsung also apparently has some updates that they were going to push but have since held off on pushing them until Microsoft has the fix for this data issue fixed.
I've been so frustrated by these issues and the lack of information regarding them that I thought you might be interested in knowing that Samsung, Microsoft, and AT&T ARE working to get the problem resolved.
Wow! This is really great news as I am having the exact same problem. I usually just on and back off Airplane mode and that fixes it, but its a real hassle. So, the word is that Samsung is, possibly, combining all the current issues like this data, the extra settings/quirky display, and the 8107/disappearing keyboard all in to one?
matt
The AT&T engineer didn't say what was going to be included in the Samsung update, just that Samsung was holding off on releasing the update until after Microsoft supplied a fix for the data issues. Hopefully Samsung's update fixes all of the Focus S quirks (data issues, delayed keyboard sounds, quirky display/auto brightness) in one shot.
Thanks for posting this, i feel better that Microsoft & Samsung are working on fixing this issue.
Any updates/news about this specific issue? I have the exact issue with my Focus S since I got my phone
I too have been having this issue and still haven't found a solution. I hope Samsung and Microsoft come up with a solution soon because it is very irritating.
Keep this post updated
trupajay said:
I too have been having this issue and still haven't found a solution. I hope Samsung and Microsoft come up with a solution soon because it is very irritating.
Keep this post updated
Click to expand...
Click to collapse
Am I mistaken...but the majority of people posting in this thread, have the problem after installing something non standard?
8107 is not released by Samsung/AT&T, so the possibility that an associated file is not included, does exist.
Was the hotspot patch and official release, or was it intended for sideload or something?
I'm just curious. I had the luxary to have my Dell Venue Pro sent to Microsoft and examined by the Test and OEM team for WP. This was several months ago. They were able to determine I had used the force update trick to update my Device. From pieces of various emails, I was able determine the update included multiple files. The multiple files consisted of Device specific instructions and additional files needed for the that operator, in addition to the Update provided by MS.
If this is the case, forcing an update into place may indeed load the update, but it might not include other needed files.
Now, I'm not an expert, a dev or anything else important. I cannot validate that what I said is true. But, i do have the benefit of having my older device looked at by MS several months ago. This does not prove 2+2=4. But it does raise enough doubt in my mind that I won't be foruce updating my devices until alot more people get a look at this methodology and perhaps come up with some answers, or at least explanations.
Does the internet connection issue appear only after the forced 8107 update?
I had been using a Chevron-unlocked Samsung Focus S on the 7720 and had experienced no issues. Just updated to 8107 following Heathcliff74's method so I hope this issue doesn't start to plague me.
Also, has anyone had success with voluptuary's wifi internet connection sharing and interop-unlock method? I am hesitant to apply that hack exactly because of worries about issues with internet...
I'm a big chicken. I am just going to wait for AT&T to release the update. I just have this funny feeling that there's a little something extra included with the at&t update. I've done plenty of customizing over the years, but just have a feeling about this. I do wish they would step on it, though.
matt
Sent from my SGH-i937 using XDA Windows Phone 7 App
Extra as in something to block out interop unlocks (bad) or firmware updates (good)? Definitely hoping for a camera firmware upgrade.....
armodons said:
Extra as in something to block out interop unlocks (bad) or firmware updates (good)? Definitely hoping for to get a camera firmware upgrade.....
Click to expand...
Click to collapse
when I said extra, I meant a focus s specific file that might act as a customization or configuration file. I don't think a block file of any sort might be included. But I do know that at&t is proprietary enough to want a unique identifier of some sort. In Gen 1, at&t had special builds just for them, turning on or off features. I know the hd7 had a specific 'config' type file, as did the venue pro. Would I call these extra files? No. I would call them required files. Build 8107 was a single build for WP. Do you think that all phones with mango had the same needs, samex files, same configs? Or is it possible that a related file acted as a config or control.
I'm not smart enough to know for sure. My gut says...maybe. .
Same Problem
Any news on this? I am having the same issue on my Focus S
gravitynoise said:
Any news on this? I am having the same issue on my Focus S
Click to expand...
Click to collapse
We just need AT&T to release the update. That's all. Rumor is all comes with the Tango update.
matt
Sent from my SGH-i937 using XDA Windows Phone 7 App
I hope so. Thanks for the fast response
I opened a VOC (voice of customer) with LG and told them a few things I'd want on the phone and I was told it would be forwarded on. One thing I told them is I'd like to see people who have non branded unlocked phones be allowed to unlock the bootloader. HTC have been doing this and it's been great being able to do what ever you want on your phone.
If enough of us told LG we wanted this do you guys think they'll really allow us to unlock the bootloader for the 4X and Future phones?
I just wish they for once had working, sensible Software for PCs. First, their upgrade tool installs the USB drivers again, despite already having them in the same version and working on the PC, then I get a "USB connection lost" in the middle of the upgrade, just after it had told you to under absolutly no circumstance disconnect it while it's upgrading .... and asks you to unplug the USB cable at the same time. Then it retries and fails again. Downright horrible.
At least it doesn't brick and can still be booted and the OTA update works..... but those LG PC solutions are always utter, utter, utter crap Then again, so are many of the other mobile phone makers software "solutions".
I know what you mean, I had a similar experience with my old HTC Hermes, but then again it was a worn out mini USB cable. It would disconnect if I moved the cable even slightly, updating it was scary.
But if the software is doing this then you should tell LG about it and hopefully they'd fix the damn thing, if they're not aware of it then they won’t try to fix it. Telling them about the problem in detail should help them find a solution.
I recently bought a Verizon Note 9 (first Samsung phone) so I'm not well versed on things. I have noticed from time to time when I am not receiving carrier signal (still connected to wifi) my texts will start failing with the error "Invalid teleservice id".
After some digging I noticed that my phone number in "About Phone" was incorrectly set to an invalid number 1-265-000-000.
I have cleared all caches and reset all settings I can think of. This problems occurs on all SMS applications. So far I have tried: Google Messages; Samsung Messages; Verizon Messages+.
Where does the "About Phone" page get populated from?
My hunch is the internal number of the phone is getting set by some screwy logic and that is throwing off everything that relies on it.
Invalid teleservide id soulution found
I need people to test this solution to make sure it works across all devices as the error seems to affect all android devices under certain conditions. If you would like to read how I came to this solution to help me check my work or you are just interested please keep reading, If you just want the solution feel free to skip to the bottom paragraph beginning with SOLUTION. If you try this solution, which I actually believe to be a solution and not a hotfix, please respond with 3 pieces of information: 1) Did it work. 2) What Android device you use and the version of Android you are using and 3) Your ISP (Internet Service Provider).
This data is very important.
STORY:
So, last month I switched to Android for a couple of reasons after having used iPhones since the iPhone 5. The two most important things to me were being able to stream music using the LDAC Bluetooth codec and having a crack at Samsung Dex to see if I could avoid buying a laptop next year. I was immediately happy with these features that had been the impetus for switching, but then something unexpected happened: the thing that I have always taken for granted, i.e. my phone sending/receiving calls and texts, was incredibly unreliable on this phone (Galaxy S20 Ultra). After doing some googling and finding the official forums (there seem to be 2 devoted to this issue and I will post this both places) I found the incredibly disheartening ‘hotfix’ of disabling WiFi calling to be completely unnaceptable. Not only because I don’t actually get cell service in my apartment but because a $1400 flagship smartphone should certianly not have less functionality in any area that an iPod Touch circa a decade ago.
Normally I would just take my faulty device down to a Verizon store because although I am in IT I specialize in computers more than phones, however since we have been in isolation this began an approximately 20 hour saga via the phone over the span of May 25th to June 19th. After trying everything I could glean might work from google, and following every step that Verizon tech support asked me to try and actually convincing them to update the carrier settings on my account I was finally given the OK to get a replacement device. It is important to note at this point that I had only been searching this error for my model phone and mistakenly had the idea that it was an incredibly rare issue that was a problem with a select few devices.
So, you can imagine my complete and udder shock after getting the replacement phone, setting it up, and getting the Invalid Teleservice ID Error 4 on the second text message I tried to send on the device. It took me about an hour to really get my wits together because at this point I was trying to come to terms with the very possible reality that I was not going to be able to use my phone at home reliably because I don’t have good reception over WiFi. When my faculties returned, I resolved to read every post I could find on this issue.
What I found is that this problem has been around since certain people started installing Android 8 on their phones and that they have been trying to get Verizon to offer an actual solution since 2017. So here we are 3.5 years later and almost 4 generations of Android later and “the best network” has so far failed to offer any sort of real solution to this problem. However, from getting the error on my new phone and seeing that the error was effecting essentially every model device Verizon sells (that runs Android) gave me a key piece of data: the problem has nothing to do with the device.
After getting deeper and deeper into some forums I noticed that one person reported that this problem only occurs for them when they use an Xfinity WiFi hotspot. That was my lightbulb moment. I am also an Xfinity customer. I then started searching the problem from that perspective and found that most of the people reporting the error and mentioning their ISP were either Xfinity or Spectrum customers, and now I was starting to feel like I might be onto something.
In terms of IT, networking is my weakest area. Nevertheless I dove into some forums that have tried to approach this problem from a networking perspective and although a lot of it was over my head I started to suspect there was something about the firewall on Xfinity and Spectrum routers that is causing the problem. After 72 hours of exhaustive testing ( not only is 24 hours approximately my previous record for not having the error, but I used that time to send out as much information via text messaging as possible to try to cause the error) I am ready to posit a hypothesis as to what is actually causing the problem and post the solution that is currently working for me.
As I have noticed that the problem is most likely to crop up for me when I am using Dex and a physical keyboard and have tried to send many texts in quick succession, the idea came to me that somehow trying to send a large volume of data exacerbates a problem that Xfinity and Spectrum routers have reliably delivering packets in the right order and format over the internet to the Verizon network. So, this is what I decided to try, and it has now worked for approximately 84 hours straight and has performed flawlessly under stress testing (Spamming 500 word texts and hi res photos to multiple people in quick succession using copy/paste).
SOLUTION:
I’m sure many of you who play video games have used a function on your routers to get around NAT issues called the DMZ. The DMZ allows you to put a device using a specific IP address on your personal network outside of the firewall and connect it directly to the internet. For a device that exists on this network wirelessly there is a simple step you must take first. You must assign your device a static IP. If you go into your router settings you will likely find that all devices on your network are assigned IP addresses via a system called DHCP. This essentially means your device will probably have a new IP every time you leave the house and return, so we need to make it the same every time so that the DMZ will function the way we want it to. Every router is going to have a slightly different settings menu, but you should be able to find a tab that lists the CONNECTED DEVICES on your network. What you need to do is change your phone from being a DHCP connected device and assign it a STATIC IP address. Finding the option to do this may be harder than actually doing it, all you need to do when you find the option is change the connection type from DHCP to Static and pick and IP address that will work for you. My network uses 10.0.0.XX for the devices on my home network so I assigned my phone to 10.0.0.99. Then I placed the 10.0.0.99 in the DMZ. In my router menu, the DMZ is under ADVANCED SETTINGS and when you select the DMZ tab, simply enter the IP address you chose for your phone.
To recap:
1) Set your phone to a static IP
2) Put that IP in the DMZ
That’s it. A valid criticism of this solution is that your phone is less secure, however I would respond that the likelihood of your phone being hacked is much smaller that that of a PC and if this slightly loosened security really bothers you, just use a VPN. A VPN will keep you safe in a Starbucks on their free public WiFi and it can protect you here (I actually had a VPN when I got my device and originally I thought it was the cause of the Invalid Teleservice error). CAUTION: There has been a crop of predatory VPN services lately that provide working VPNs, but will charge you a ridiculous amount. I use NordVPN (I found a code on YouTube that gave me 70% off six devices on a 3 year plan, that ended up costing about $100) but there are plenty of good services that will allow you to connect to the internet via a VPN on one device for approximately $2-3 a month.
So please, try this and report back. This error has been the bane of my existence since switching to Android and it is completely unacceptable that Verizon has had literally years to do figure out a solution to this problem and yet they have not. My end goal is not to receive credit but to make sure that in the future Verizon Tech Support actually knows how to help people solve this problem, and their techs don’t take your calls and then look the problem up on google, proceeding to be completely transparent in terms of having no actual knowledge of this issue and literally reading the same forums I have already been over and suggesting the non-solutions posted there in order, i.e. turn off WiFi calling and if that doesn’t work turn off ‘Advanced Calling’.
REMEMBER: If this solution does not work for you, please double check that your changes the router you use have stuck. I have previously had routers that will for reasons I don’t understand change the DMZ domain or switch a device back to DHCP from static or simply fail to save your changes properly.
I await responses eagerly.
You need to take your device to your local high street retail branch of your cell provider and ask them to check your SMS/MMS settings
I would love to be able to actually go into a brick and mortar Verizon store but that's currently not possible in WA state. I had to have a tech walk me through checking those settings myself (after doing my own research as well) and had somebody at level 3 of tech support at Verizon manipulate my carrier settings. That's pretty much all I can do during the pandemic.
My solution is still working for me though, however 33 min after I put the same post on the official Verizon forum they closed the thread which had had regular posts over the last 3 years so now I'll never know if it works for anybody else. Additionally, there was somebody on the forum who approached the problem from SMS/MMS settings perspective and it had to do with deleting server settings and whatnot. It was so complicated that I doubt many end users could follow the same steps.
K_A_Beausoleil said:
I would love to be able to actually go into a brick and mortar Verizon store but that's currently not possible in WA state. I had to have a tech walk me through checking those settings myself (after doing my own research as well) and had somebody at level 3 of tech support at Verizon manipulate my carrier settings. That's pretty much all I can do during the pandemic.
My solution is still working for me though, however 33 min after I put the same post on the official Verizon forum they closed the thread which had had regular posts over the last 3 years so now I'll never know if it works for anybody else. Additionally, there was somebody on the forum who approached the problem from SMS/MMS settings perspective and it had to do with deleting server settings and whatnot. It was so complicated that I doubt many end users could follow the same steps.
Click to expand...
Click to collapse
Thanks for your efforts. I've had this same issue on my Note 9 for 2 years... Your solution did not work for me.
However, I found a solution this morning. My ISP is not Xfinity or Spectrum. But my network which is spread across a small community blocks some IPsec ports that are required for wifi calling. Enabling those ports on my router does not fix the problem since it is a network/modem setting that I don't have access to.
What does work is having a vpn profile that implements IKEv2/IPsec VPN tunnels on your Android device. I have a NordVPN subscription and downloaded the StrongSwan VPN client from the Play Store. This client only uses IPsec encryption. Using a NordVPN server that has this encryption with the StrongSwan VPN client has allowed me to bypass this network restriction and my wifi calling phone calls and texts go through just fine now.
Hoping this helps someone else...
---------- Post added at 04:37 PM ---------- Previous post was at 04:05 PM ----------
hkjxda said:
Thanks for your efforts. I've had this same issue on my Note 9 for 2 years... Your solution did not work for me.
However, I found a solution this morning. My ISP is not Xfinity or Spectrum. But my network which is spread across a small community blocks some IPsec ports that are required for wifi calling. Enabling those ports on my router does not fix the problem since it is a network/modem setting that I don't have access to.
What does work is having a vpn profile that implements IKEv2/IPsec VPN tunnels on your Android device. I have a NordVPN subscription and downloaded the StrongSwan VPN client from the Play Store. This client only uses IPsec encryption. Using a NordVPN server that has this encryption with the StrongSwan VPN client has allowed me to bypass this network restriction and my wifi calling phone calls and texts go through just fine now.
Hoping this helps someone else...
Click to expand...
Click to collapse
Scratch this... Wifi calling uses it's own IPsec VPN tunnel, VPN clients only encrypt internet traffic, not cell service. Back to square one...
I downloaded the 12.5 version while testing out some other ROMs since I like using MIUI unlike many people and I know Xiaomi would not full fill their global update promise for mi8 since its been like a year after they announced that 12.5 would come for mi8 as the last update. Only problem I have with it is the fact that I need to go into wifi settings and pick the wifi I want to connect for it to connect it, every god damn time. Then it says there is no internet connection and if I want to keep it or not and I say keep it then it starts functioning like it should. I don't understand why it keeps saying "there is no internet connection" in a wifi network while obviously there is nothing wrong with the wifi itself. In the original MIUI 12 version it instantly connected to existing wifi networks when it entered their range, automatically without me having to open the wifi settings. I tried resetting wifi settings and opening and closing the auto connect option as it was recommended in some videos but nothing helped.
So at the end it doesn't connect wifi networks because it thinks there is no internet connection at them and keeps using mobile data until I manually force it to connect. I eventually got use to it after a month or so but it is still bugging me. The phone is rooted and I am using add away, which did cause other problems in the past so I am kinda suspicious of it. Spotify is kinda busted with this ROM and I get like 2 hours and a half hours of screen time while scrolling through reddit at most which is stupid but the general inconvenience of using this is not greater then going through the suffering of loading a new ROM and reinstalling all of the stuff so can anyone help me to make it a less suffering experience. My battery is new but it is old stock from 2018 so it is as **** as the one it had inside for 3 years since Xiaomi doesn't provide new ones like Apple and Samsung as much as I understand. I will not buy a new phone since technological improvements stopped 4 years ago except useless cameras which I never use because the sensor size is too small anyway and you can't beat physics no matter how much post progressing you apply in phone camera software. Sorry for the long rant, I just felt the need of writing that last part out of boredom.