Guest Azurren Posted August 15, 2010 Report Posted August 15, 2010 What apps do you have that require 1.6+? I don't use my phone for much aside from txting, ringing and facebook, and all these run perfectly on 1.5. :D Facebook now requires 1.6 or 2.1 (Can't remember but it is defo higher than 1.5) Twitter All decent launcher replacements And probably much more
Guest Rem1x Posted August 15, 2010 Report Posted August 15, 2010 Facebook now requires 1.6 or 2.1 (Can't remember but it is defo higher than 1.5) Twitter All decent launcher replacements And probably much more TweetDeck
Guest Jimmy0 Posted August 15, 2010 Report Posted August 15, 2010 Facebook now requires 1.6 or 2.1 (Can't remember but it is defo higher than 1.5) Twitter All decent launcher replacements And probably much more Fair enough, I've always just visited facebook through the touch website instead, never did much like the application.
Guest Sh4d0w940 Posted August 15, 2010 Report Posted August 15, 2010 I've gone back to 1.5 some time ago because of this problem and I like it more this way. I was hoping that the uk update would solve the problem. But still, for me its better to miss some apps than my messages. As craigflow already said it's sounds really stupid when you say: "Sorry I didn't recieve your sms. I can fix this but I rather have some cool apps on my phone than read your messages." Sh4d0w940
Guest Rem1x Posted August 15, 2010 Report Posted August 15, 2010 This is happening on stock 2.1? Class action lawsuit, anyone?
Guest DanWilson Posted August 15, 2010 Report Posted August 15, 2010 This is happening on stock 2.1? Class action lawsuit, anyone? Wow dawg! +Infinity. That'd buy us all Desires. And the next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-gen phone for the world. Wait. I thought we were getting £Infinity. Damn I can't stay on track with my own posts!
Guest Sh4d0w940 Posted August 15, 2010 Report Posted August 15, 2010 This is happening on stock 2.1? Class action lawsuit, anyone? Probably not a good idea since T-Mobile doesn't have to release updates. If you sue them they could just remove the update and put the old version back on their site. Sh4d0w940
Guest DanWilson Posted August 15, 2010 Report Posted August 15, 2010 Probably not a good idea since T-Mobile doesn't have to release updates. If you sue them they could just remove the update and put the old version back on their site. Sh4d0w940 Whats the point in that though? They could have spent 12 years making that (Exaggeration I know) just to take it off. Nah bro I don't think so.
Guest Azurren Posted August 15, 2010 Report Posted August 15, 2010 Actually I was told that the pulse would be getting 2.1 before I bought it.. This was the only reason I bought it (After googling android 1.5 and finding it was outdated / rage of people that were stuck on it) So.. A promised 2.1 update that just doesn't work. :D I may just send a letter to T-Mobile and see what they suggest. They are offering the Spica for less than what I pay for my contract, do you think they may swap it for my mint condition pulse? A Good will gesture?
Guest Epic-Emodude Posted August 15, 2010 Report Posted August 15, 2010 Wow dawg! +Infinity. That'd buy us all Desires. And the next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-next-gen phone for the world. Wait. I thought we were getting £Infinity. Damn I can't stay on track with my own posts! we could create our own phones with 1. 3ghz dual core processors 2gb RAM 4inch screen and like a 10000mah battery. and if it doesn't exist we could develop it
Guest DanWilson Posted August 15, 2010 Report Posted August 15, 2010 (edited) I may just send a letter to T-Mobile and see what they suggest. They are offering the Spica for less than what I pay for my contract, do you think they may swap it for my mint condition pulse? A Good will gesture? If they do, tell us - I might do the same. Hopefully they can't fix my Pulse, and have none left. A Spica would do me good. (And if they do have Pulses left, it'd be mint anyway!) The only problem is I'm Pay as you Go... :D we could create our own phones with 1. 3ghz dual core processors 2gb RAM 4inch screen and like a 10000mah battery. and if it doesn't exist we could develop it Nah bro. 1. 12ghz 12core. 2. 1TB of RAM 3. 4" screen 4. Mega life battery (neva running outz!) 5. 1000TB of memory to use. 6. Android 9.9 7. Partay button. BTW @Mods - This is very on topic. We are discussing how to fix The Text Problem. The three solutions are - Strap RAM to the battery cover / Get a Spica / Develop my mega phone. Edited August 15, 2010 by DanWilson
Guest Azurren Posted August 15, 2010 Report Posted August 15, 2010 A micro nuclear fusion reactor should sort our battery woes :D All it would need is a warning sticker. Plus then scientists can proof that mobile phones give cancer
Guest Cazomino05 Posted August 15, 2010 Report Posted August 15, 2010 (edited) as I mentioned in another topic it happened to me using the new 2.1 ROM from t-mobile UK without any customization other than the fact I downloaded ADW from the market it could be unrelated and just a coincidence but this didn't happen with FLB Tre that's for sure Edited August 15, 2010 by Cazomino05
Guest Azurren Posted August 15, 2010 Report Posted August 15, 2010 (edited) as I mentioned in another topic it happened to me using the new 2.1 ROM from t-mobile UK without any customization other than the fact I downloaded ADW from the market it could be unrelated and just a coincidence but this didn't happen with FLB Tre that's for sure I think it is safe to say that this bug is caused by lack of ram. You can tell sometimes when you wake the phone it takes ages before it is usable (Probably multiple apps updating choking the phone for ram) When the phone chokes it doesn't receive text messages :D So it was better on FLB (Lighter rom, less ram usage) but it still chocked from time to time. If a text message comes when the phone is chocking.. Yeah :D Edited August 15, 2010 by Azurren
Guest Cazomino05 Posted August 15, 2010 Report Posted August 15, 2010 I'm going to try posting on t-mobiles support forum they obviously know about this issue hopefully they can try some things their end other phones don't have this issue hopefully it'l encourage them to make the app's less hungry :D well assuming the forum will let me register... my activation code fails and my login details don't work but I can't login... nice
Guest themadwacky1 Posted August 15, 2010 Report Posted August 15, 2010 i have notified t-mob cust services, and their response was: " I have passed the concerns on to our software testers, this will be looked into and advised upon soon when tested. Thanks."
Guest DanWilson Posted August 15, 2010 Report Posted August 15, 2010 i have notified t-mob cust services, and their response was: " I have passed the concerns on to our software testers, this will be looked into and advised upon soon when tested. Thanks." So they will. There is more hope of me reaching 200 years old tomorrow, then making the .32 kernel from scratch, port Gingerbread to the Pulse (even though it's not out and even the Desire might not have the specs) in a week. Remembering that I'm 200. :StraightFace:
Guest stealthstealer Posted August 15, 2010 Report Posted August 15, 2010 i guess asking t mobile to fix it is a good solution, because we could all call in our warranties and say the phone doesn't receive texts if they dont release a fix. seeing as there isnt any official way to go back to 1.5 on theie site aswell...
Guest DanWilson Posted August 15, 2010 Report Posted August 15, 2010 i guess asking t mobile to fix it is a good solution, because we could all call in our warranties and say the phone doesn't receive texts if they dont release a fix. seeing as there isnt any official way to go back to 1.5 on theie site aswell... But they'd just give us new (or refurbished) (or the same) Pulse back. Or worse - a Pulse Mini... I want a Spica now... ;) But I want to keep the Pulse... :D I need £100. :D
Guest Azurren Posted August 16, 2010 Report Posted August 16, 2010 Actually I was told that the pulse would be getting 2.1 before I bought it.. This was the only reason I bought it (After googling android 1.5 and finding it was outdated / rage of people that were stuck on it) So.. A promised 2.1 update that just doesn't work. :D I may just send a letter to T-Mobile and see what they suggest. They are offering the Spica for less than what I pay for my contract, do you think they may swap it for my mint condition pulse? A Good will gesture? So far I have just received Copy + Paste responses. Decided to e-mail otherwise I would receive this through the post Hopefully I'll keep my cool, be nice and polite and hope they run-out of Copy+Paste responses :D Little hope.
Guest meinnit Posted August 17, 2010 Report Posted August 17, 2010 I have managed to reproduce the text problem! I ran a memory intensive app which lowered my free memory down to approx 15MB (used adb and top to check). I then sent a text to my Pulse and it failed to receive it. So a simple solution, try and kill all these useless processes running in the background..which we already have a thread for :D Now to narrow this down a little further, I am using Handcent. Is anyone using the stock messaging app and still getting this problem?
Guest david_dawkins Posted August 17, 2010 Report Posted August 17, 2010 I have managed to reproduce the text problem! I ran a memory intensive app which lowered my free memory down to approx 15MB (used adb and top to check). I then sent a text to my Pulse and it failed to receive it. So a simple solution, try and kill all these useless processes running in the background..which we already have a thread for :D Now to narrow this down a little further, I am using Handcent. Is anyone using the stock messaging app and still getting this problem? Nice job! How about trying your test with Handcent uninstalled, against the stock messaging app? It would be interesting to know if your memory intensive app then needs to allocate more memory to get to 15Mb free (where we would expect the same problem to occur - if it doesn't then we have some other factors); this would show that Handcent is more bloated than the stock. There may be better ways to detect that though!
Guest stealthstealer Posted August 18, 2010 Report Posted August 18, 2010 Nice job! How about trying your test with Handcent uninstalled, against the stock messaging app? It would be interesting to know if your memory intensive app then needs to allocate more memory to get to 15Mb free (where we would expect the same problem to occur - if it doesn't then we have some other factors); this would show that Handcent is more bloated than the stock. There may be better ways to detect that though! thats great! confirms the low memory theory, and now we can really concentrate on solving it. Surely there is a way to try and keep the sms service in memory, like the home app? Plus i get this problem constantly even with stock app on stock roms, so its not just a handcent problem. Now i just need the best configuration to gain RAM on flb, to try and make sure i get all my texts!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now