Related
My push notifications from thirdparty apps and live tiles stop working very regularyly which is a shame since the platform heavily depends on this.
It fails to open a channel etc.
Is microsoft fixing this bug in the os? Since now they say yeah just do a factory rest and it should be fine. But i dont wat to lose my settings.
And a restart temporarely fixes it but after an hour or so its terrible again.
or are the ms servers just over crowded already? I dont like apple but my dads iphone just kept working while mine stopped receiving the toasts
...
Marvin_S said:
My push notifications from thirdparty apps and live tiles stop working very regularyly which is a shame since the platform heavily depends on this.
It fails to open a channel etc.
Is microsoft fixing this bug in the os? Since now they say yeah just do a factory rest and it should be fine. But i dont wat to lose my settings.
And a restart temporarely fixes it but after an hour or so its terrible again.
or are the ms servers just over crowded already? I dont like apple but my dads iphone just kept working while mine stopped receiving the toasts
...
Click to expand...
Click to collapse
Toasts and tile updates come from the app developers servers, so depending on the platform they use there may be some down time. The Beezz twitter client occasionally stops working, but it's a free app and not ad supported so we should be lucky it has toasts and tile notifications at all.
sulphuricaciduk said:
Toasts and tile updates come from the app developers servers, so depending on the platform they use there may be some down time. The Beezz twitter client occasionally stops working, but it's a free app and not ad supported so we should be lucky it has toasts and tile notifications at all.
Click to expand...
Click to collapse
not really since tested with the same apps at the same time. Its probably because it goes to the ms servers and fails to deliver timely. Also the unable to open a channel is not related to their servers i believe? Its related to a channel not able to open on the ms servers. Downtime should probably be equal when using the same apps on ios and wp7 sending out to each other, the messages do get delivered in app just no or really really delayed notifications. Like 20 minutes and then it just works normal for a while.. Then stops again. Other than this i really like the platform.
So i wonder does anybody else experience trouble? And which is the program you use which seems to be stable all times?
I'm experiencing the same troubles on my omnia 7.
Following programs do have some problems:
-Fim: Unable to open the channel - push notifications don't work anymore.
-TextMe: Push Notifications sometimes work - but with a delay of approx. 20 minutes
Following programs don't have any problems:
-Hotmail
-Messenger by Miyo
----------------------------------------
This is really annoying - since a "usual" restart of the device doesn't help, i think i will have to do a hard reset (i wonder if this will help at all). But i don't want to lose all my settings, installed applications, short messages etc. So this really is a PITA.
stylopath said:
I'm experiencing the same troubles on my omnia 7.
Following programs do have some problems:
-Fim: Unable to open the channel - push notifications don't work anymore.
-TextMe: Push Notifications sometimes work - but with a delay of approx. 20 minutes
Following programs don't have any problems:
-Hotmail
-Messenger by Miyo
----------------------------------------
This is really annoying - since a "usual" restart of the device doesn't help, i think i will have to do a hard reset (i wonder if this will help at all). But i don't want to lose all my settings, installed applications, short messages etc. So this really is a PITA.
Click to expand...
Click to collapse
hardreset, would that really help? I think it wont really help. I have the same phone same apps and same problems also with tigertext send to wp7 and notes to tile.
i dont have the time and or want to hardreset. It might be a driver thing with the 3g etc. If nobody with other phones is experiencing this. I think hardreset changes nothig and will return to same behaviour. I will hardreset when the update comes or see if this will fix it.
20 Minutes is just strange conpared to instant on iphone and happens a lot
Pff
Did a hardreset. Tested the push again, ait a damn thing changed besides that I lost all my settings and stuff. Its just not working right. And probably a samsung driver or a ms server/os issue....
Does nobody else experience push notification downtime? Or delays? It's just not the way it should work. IM apps and Text replacement apps can never work properly in the background with these delays...
@Marvin_S which apps, specifically are you having trouble with? It could very well be that the developers servers have been down or slow.
I haven't had any Live Tile problems that couldn't directly be traced back to either the app dev's server or the way they've implemented notifications. Not on my Omnia 7 nor the HD2. Afaik, and I'm pretty sure I'd have heard about it - the wife's Omnia7 is doing just fine also. Have you tried flashing the new updated ROM? That seemed to fix a bunch of data issues.
Oh, as for the 20 minute thing, I've never seen this. Beezz for example notifies me (via toasts) in about a second or so.
Beezz has never worked for me. I always get an error whenever I try to enable push. The same happens for GReadie. I get a fail to open channel error. The weatherbug app also stopped working.
Right now my HTC hub live tile works. Its the only 3rd party live tile app I use.
emigrating said:
@Marvin_S which apps, specifically are you having trouble with? It could very well be that the developers servers have been down or slow.
I haven't had any Live Tile problems that couldn't directly be traced back to either the app dev's server or the way they've implemented notifications. Not on my Omnia 7 nor the HD2. Afaik, and I'm pretty sure I'd have heard about it - the wife's Omnia7 is doing just fine also. Have you tried flashing the new updated ROM? That seemed to fix a bunch of data issues.
Oh, as for the 20 minute thing, I've never seen this. Beezz for example notifies me (via toasts) in about a second or so.
Click to expand...
Click to collapse
Well I seem to be running the latest version pre-installed by samsung... i asked in the omnia7 forum what kind of rom I was running.
Well the thing is, it builds up all the notifications and than releases them all after each other 20 minutes later.
Basically these apps: Textme and tigertext (which I tried later to see if it could replace textme, very kind and responsive developers btw)
Also send to wp7, which often than comes up with the failed to open channel stuff.
If this rom should rely fix it, then I will just reflash it eve though its exactly the same rom... I think it has something to do with losing 3g+ signal, or wifi drops.
I'm testing the reliablility heavily since I such problems by sending constant test messages to myself (or to the echo server) the messages are received fine, but the toast is so unreliable.
Can you maybe type the versions of your firmware so I can compare it with mine? Because its for sure not an app problem since the messages all come later from diffrent apps. My test flow is like this: Open app, send message, close, send message with the second app, close and than wait. If it takes to long, open app again, resend. Sometimes it works quite right for a while, than teribly bad.
And note that I'm from a crowded area with lots of cellphone towers and have also good wifi coverage in the places I tested it. Same apps on the iphone work without problems, I compared side by side as well.
So it might just be my omnia, thats why I would like to hear which versions you are running. Since hardreset did not change a thing, I'm starting to believe its or a driver problem or ms-servers are overcrowded. I would like to try beez and see if its diffrent, however I dont havee twitter and i guess its required.
I don't think the newer ROM from Samsung fixes anything, because i installed it. Version 2424.10.11.1
but perhaps the region affects this problem, e.g. North-American Azure-Servers work fine while European Servers are struggling.
I personally have massive problems with push notifications since monday or so, and it's really starting to pi** me off!
Hard resetting idny going to fix anything permenitly because it is not the phone it is the apps just gotta wait for and update to fix
Sent from my EVO 4G using XDA App
Weird. I'm using Beezz, SendToWP7, uController, eBay, Weatherbug and probably a few others using toast and/or live tile notification. Beezz server seems to go down every so often, but both uController and SendToWP7 notifies me real quick.
I'm running the latest Omnia 7 ROM as people said it was slightly faster and had a better data connection - that said, I was entirely happy with the phone even before updating.
I did a hard reset/reinstall of my apps and such, I'm still having intermittent push problems with some apps, and with others the push won't work at all. I will say that it seems to be the same apps having the same problems, and the ones that always have worked (weather bug) still work.
I'm thinking (hoping, praying!) this is a problem simply because of the infancy of the OS...I remember the first iphone, which I bought on day one, had all sorts of problems and "gaps" in technology
emigrating said:
Weird. I'm using Beezz, SendToWP7, uController, eBay, Weatherbug and probably a few others using toast and/or live tile notification. Beezz server seems to go down every so often, but both uController and SendToWP7 notifies me real quick.
I'm running the latest Omnia 7 ROM as people said it was slightly faster and had a better data connection - that said, I was entirely happy with the phone even before updating.
Click to expand...
Click to collapse
oKe im running the latest rom since the beginning. Created fake twitter account sended a ton of messages. Crap as hell, very unreliable and today i was not able to load fb app data on 3g full bars. So it can be a phone problem on drivers with data over 3g, while 3g+ works fine. Probably euopean servers are overloaded than. Does changing my location from USA based (im dutch) To germany change the servers as well? Bc germany is much closer thus more reliable?
jmerrey said:
I did a hard reset/reinstall of my apps and such, I'm still having intermittent push problems with some apps, and with others the push won't work at all. I will say that it seems to be the same apps having the same problems, and the ones that always have worked (weather bug) still work.
I'm thinking (hoping, praying!) this is a problem simply because of the infancy of the OS...I remember the first iphone, which I bought on day one, had all sorts of problems and "gaps" in technology
Click to expand...
Click to collapse
Its the apps not the phone the apps need to be updated inorder to work on the os not the other way around
Sent from my EVO 4G using XDA App
v hubris v said:
Its the apps not the phone the apps need to be updated inorder to work on the os not the other way around
Sent from my EVO 4G using XDA App
Click to expand...
Click to collapse
this is not the case, read my post. Has nothing to do with the apps since ALL apps behave like this, it has nothing to do with the apps itself but probably slow ms servers. So no this is really an os or server or device firmware problem and not an app. Since all notifications come at the same time all after eachother highly delayed.
Apps have own servers they Sony go threw ms os is not mad for apparently apparently are made for os if apparently no work on os they need update
Sent from my EVO 4G using XDA App
v hubris v said:
Apps have own servers they Sony go threw ms os is not mad for apparently apparently are made for os if apparently no work on os they need update
Sent from my EVO 4G using XDA App
Click to expand...
Click to collapse
its not the problem of the apps! Since all apps fail at the same time to update. This is no coincidence, only a restart or waiting will solve this and than all notifications not yet delivered by multiple apps come at once! Now tell me how this is an app poblem,its the phone who is not able to receive the push even on wifi. The apps do deliver, but there is a huge delay even with beez which i checked with fake twiter account.
Every once in a while the phone just fails to receive any data based push notifications! All of them. While i do have wifi and or 3g. On 3g+ it seems to be more stable.
This could be europe related or omnia related. And narrowing this down will help dtermine the issue, since the apps are not the problem. These work fine for the others...
Marvin_S said:
This could be europe related or omnia related. And narrowing this down will help dtermine the issue, since the apps are not the problem. These work fine for the others...
Click to expand...
Click to collapse
It is neither Europe or Omnia related as I'm using the 16GB Omnia7 in Europe (slightly north of you) at the moment without fail.
If it really is all apps, I would suggest there is a problem with your data connection - are you able to browse the web properly and without pages having to reload or taking a long time to open? If not, make sure you are indeed within range of, either, 3G/HSDPA or WiFi - if you are, and it works fine on another phone/laptop I would say you have a hardware fault and need to take the device back for a replacement.
Several things to be aware of with live tiles and notifications.
I am a developer of a few apps and offer push notification and live tile updates i have done alot of testing and know the ins and outs of this..
1st there is a such thing of the phone not being able to "open a notification channel" and Hard Reset is the only way to correct this.
2nd it is possable that the app developer side to also be the problem not sending because of their service going down server problems etc.
3rd when your batt. get to be less than 1/4 percent the notification service shuts down on the phone and you will not recieve updates. once the batt is above the 1/4 percent the service will then start working again.
4th sometimes the push service is delayed due to MS.
Hope this helps to better understand.
My Apps
World Weather (Live Tile)
TV Show Alert (uses Push Notification)
To Doos (Comming soon Push, Live Tile)
Ok noob alert..just a prelude I've done alot of searching and reading, and *think I have some answers, but if some kind soul were to take a quick look and maybe verify what I've found, I'd be eternally grateful. I used to have a LG Optimus and easily rooted/upgraded to CM7 by reading this forum and didn't have to ask any questions.
Now I've gone and signed up for WIND (Canada) and picked up an XT720. It's my budget and I'm not overly concerned about whether or not I have ICS immediately. I'd rather have something stable and $$ saving.
OK so I'm noticing a serious difference in the way the XT720 handles the WIFI/mobile data situation compared to the LG: it doesn't. First off, there's no easy way to turn off mobile data. Secondly, enabling WIFI gets me a connection to my router, yes, but browsers and apps that require a connection just refuse to use the WIFI unless: 1. there is 3G data connection - in other words, it ain't using WIFI 2. I put the phone in Airplane Mode, and turn WIFI back on. Great, but now no phone calls or SMS. Not a viable workaround. Option 3 involves hard resetting the phone with a battery pull which sometimes works and sometimes doesn't.
From scouring around various sites, this seems to have been a common problem with 2.1 and this model of phone. And thus the workarounds I tried were also employed by others.
From what I know of all versions custom ROMs etc from 2.2 onward for other models of phones, though, this wasn't an issue, and also in 2.2 and onward you can switch off Mobile Data which will force the WIFI connection if turned on.
So is this something that I will see an improvement on if I install say CM 6.3 onward or whatever? I'll get the ability to turn off mobile data, right? And then there theoretically shouldn't be a conflict, right?
That's my biggest issue. I don't get enough 3G signal in my house to just use the mobile data connection, I absolutely have to be able to use WIFI and receive phone calls/texts at the same time, so if custom roms aren't going to help me, I'd best return the phone.
Some other things I'm curious about:
- do most of the normal functions of the phone work with CM 6.3? HD recording, camera, HDMI out etc? Anything I've missed?
- I see quite a bit of talk about people running out of RAM and using sd swapping etc is this a common problem? Even with about 20 or so apps and CM7 on my LG Optimus I was still able to maintain about 110 mb RAM free at all times by judicious use of installing apps on SD card...will I be ok?
- Probably the biggest question before I root/install...most of the guides I'm reading talk about installing various stock sbfs etc etc...I'm coming in from a WIND stock rom so I don't *THINK* I need to do this, right? I should be nandroid'ing, Open Recovery, flash custom rom....right?
Here's my specs
Xt720 Wind Canada
s/w STR_U2_05.1F.2
f/w 2.1-update1
f/w config GAS_NA_NAWIND_P012
Baseband 3GSMEPU91A_U_91.075EI
kernel 2.6.29-omap1
I realize that some of this is covered in other threads. To be honest tho some respondents/contributors aren't English first language and I just want to make sure I haven't misunderstood anything. Anyone who has done similar to what I'm trying to do, especially coming from a WIND perspective, lemme know your thoughts, please and thanks alot!
acrobat69 said:
Now I've gone and signed up for WIND (Canada) and picked up an XT720. It's my budget and I'm not overly concerned about whether or not I have ICS immediately. I'd rather have something stable and $$ saving.
Click to expand...
Click to collapse
I've picked up the XT720 myself from Wind a few days ago at the clearance price ($150 outright, no plan). They even told me there are no guarantees with the phone with its stock ROM and seemed glad to hear that I was gonna use it with a custom ROM. I knew what I was getting into and the only reason I still bought the phone is this:
http://forum.xda-developers.com/showthread.php?t=1300246
We are extremely lucky to get Gingearbread on our phones, so don't even think of ICS at this moment. As you noticed already the stock 2.1 is useless and I flashed mine the 1st day.
acrobat69 said:
That's my biggest issue. I don't get enough 3G signal in my house to just use the mobile data connection, I absolutely have to be able to use WIFI and receive phone calls/texts at the same time, so if custom roms aren't going to help me, I'd best return the phone.
Click to expand...
Click to collapse
The ROM I linked above (the only 2.3, actually CM 7.1 available for XT720) works as you'd expect with wifi and 3g, that is it uses wifi when connected to both. Any decent ROM will do that.
acrobat69 said:
- do most of the normal functions of the phone work with CM 6.3? HD recording, camera, HDMI out etc? Anything I've missed?
Click to expand...
Click to collapse
HD recording - not yet (you don't lose much anyway, the camcorder quality would be crappy, check reviews with the stock OS)
camera - yes (pretty good quality)
HDMI - not yet (I'm guessing it will be fixed very soon, the devs are working on exactly this)
everything else - yes
acrobat69 said:
- I see quite a bit of talk about people running out of RAM and using sd swapping etc is this a common problem? Even with about 20 or so apps and CM7 on my LG Optimus I was still able to maintain about 110 mb RAM free at all times by judicious use of installing apps on SD card...will I be ok?
Click to expand...
Click to collapse
This one is tricky, the phone only has about 225mb usable RAM, there's not much multi-tasking you can do with that amount but it's workable. There are some performance tweaks you can do (overclocking, CM settings, V6 SuperCharger, etc.) to make it decent. Moving apps on sd card is a good idea in order to save storage space on the phone (another limited resource at only 174mb) but has nothing to do with RAM.
acrobat69 said:
- Probably the biggest question before I root/install...most of the guides I'm reading talk about installing various stock sbfs etc etc...I'm coming in from a WIND stock rom so I don't *THINK* I need to do this, right? I should be nandroid'ing, Open Recovery, flash custom rom....right?
Click to expand...
Click to collapse
I've been wondering the same thing, what's up with all the SBFs people are talking about left and right? The answer is don't worry about them, you don't need any SBF. They are just that, stock ROMs, all 2.1. You would only need one (the Wind version) if you wanted to take the phone back for servicing and wanted to return to the original non-rooted state. Apparently even if you take a full nandroid backup with your stock ROM now and restore it later, the phone will still be rooted and this is where a stock SBF would help. I'm not gonna bother, even if I do take it back (highly doubt it, with the custom ROM it's a very good phone for $150 outright), I'm just gonna restore my stock nandroid backup.
So what you need is:
1. root the phone (personally I used SuperOneClick, google for the latest version)
2. install OpenRecovery: http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
I can send you the file you need if you pm your email address. I HATE it when I have to register on some forum just to get 1 stupid file. And you absolutely CANNOT get that stupid file anywhere else on the face of the Earth/internet.
3. install this mod for OpenRecovery: http://forum.xda-developers.com/showthread.php?t=1242259
4. go to the ROM's thread, dl the latest build linked in the 1st post, copy the zip file to your sdcard\openrecovery\updates, reboot into recovery mode, apply update, format data&cache, reboot. Done. Enjoy!
BuddyBud said:
2. install OpenRecovery: http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
I can send you the file you need if you pm your email address. I HATE it when I have to register on some forum just to get 1 stupid file. And you absolutely CANNOT get that stupid file anywhere else on the face of the Earth/internet.
Click to expand...
Click to collapse
There's an OpenRecovery apk floating around here to install ther OR bootstrap, no need to register at ModMyMobile.
:Edit:
Woodrube has it attached to this thread. Install the apk from the sdcard, reboot, then run the apk & install OR. (Now you can switch out the OR files with Mioze's modded OR)
here you go
I knew that thread would come in handy one of these days. Plus Buddy and Acro there are other handy APKs in there too.
Mioze actually have all the necessary Open Recovery files linked in his CM6.3 topic
that's the most updated version
THANK YOU THANK YOU THANK YOU to James and everyone who has responded so far - even going so far as to direct link me to files I'll need? You guys are the best!!.
I really appreciate the encouragement. I think tonight's the night.
I'll try and log my procedures and steps and make note of anything I run into for future noobs like me I might be able to help..that's how community works, right?
Wish me luck!
Good luck
One more tip: If you find that Market keeps crashing after you flash fjfalcon's ROM, flash this updated Google Apps package - gapps-gb-20111216 (dl link here).
It worked for me. Put the zip file on the sdcard right next to the ROM file and flash it just like the ROM file.
PS: Who's James?
Ah BuddyBud sorry, there is another Canadian Wind guy named Biker Bob (real name James) who was posting about his experiences in another thread, and I mixed the two of you up..
About to try this...couple questions
Has anyone watched/used Reverend's tutorial video? Results?
I don't need to unlock the phone first, right? Please tell me no, I just got it! lol
The Revs videos are a good reference & if you are talking about a sim unlock that's not necessary.
Yes Revs videos are good to show.a visual of what you should do. Don't worry about it. I know it is scary the first time but once you do it, it will become second nature. Don't forget to wipe cache, dalvik and factory reset. If you bootloop, that is probably why.
No you don't need to be unlocked. That just deals with carriers and not ROMs.
Im on the edge of the decision precipice..am not too nervous about doing this, as in fact I'm pretty technically proficient..it just seemed that this process was a bit more convoluted than the one I picked up on easily for the LG.
Decisions decisions...6.3 or go all the way to 7.1
I think I need stability...and I'm not sure I want to get into a whole bunch of swapping locations etc. I noticed The Reverend mentioned he didn't bother with swaps. Mind you, I don't even think he made an ext partition either, which boggles my mind, I was almost sure you had to make at least one for any custom ROM. I might be showing just how little I know here! lol
Is it just that 7.1 is more of an ongoing thing, or by now are most of the +/- s of both pretty much on par? I know, I should be reading all 78 pages of the damn thread, right??
Oh boy, I just read through the Bravo thread...and the LED notification sounds SOOO tempting. No LED notification bugged the hell outta me on the LG. Hmmmm...
Ok...have settled on the ROM in this thread (Bravo):
http://forum.xda-developers.com/showthread.php?t=1332410
I just want to make sure of one thing...the VERY helpful steps that you all have outlined ie BuddyBuds...they stay the same up to step 4 (ROM + update) no matter what ROM I choose, pretty much.
Brians instructions are just a slight bit confusing in that Im not sure if I have to apply just the most recent update for LED ie v1.6...or if I have to install ALL the updates from the start on up (I think there are 4 of them). To me it would seem logical that each new version would be cumulative ie include the stuff from previous versions...but I just want to make sure!
One more thing..I didnt notice any mention of gapps in the download in that thread (nor did I see a gapps apk in the files I unzipped, but might have missed it..)...if not, Ill need to apply that too, right..any special version to useÉ
Ok so...
I went with Brian's BRAVO. I followed some of the steps provided in this thread, coupled with Reverand's video. I used his OpenRecovery install method (ie original from the Dexter build, copy new over top that) because I've never installed OpenRecovery before and it just seemed confusing on other threads.
To root, I used UltimateAndroot, in order to have the ability to unroot the machine (you'll see why...)
The first thing I checked, of course, was the pull down power/status bar to see about turning off various connections (ie Wifi, Bluetooth, Refresh, Mobile Data, etc). Unlike other 2.2 Froyo's I've used, specifically..LG..there is no pull down/status bar. Damn. Went thru every Setting imaginable, but won't work. This isn't looking great.
Next thing I tested was my 3G/Wifi issue. To my dismay...the issue remains. Browser and apps are still trying to use 3G first and foremost, as far as I can see. How do I know? Because if I leave Data Network Settting to "Allowed", browser/apps work, and *seem to be using the WiFi, but the second the 3G signal fades or is dropped, I get connection issues, and WiFi is still on. If I turn Data Network Setting to "Not Allowed", it might/might not use the WiFi for a bit and then pretty consistently stop. When I mean "stop", I mean the phone is still showing connected to WiFi yet there are data connection errors on all browsers/apps that need data etc. Sometimes, if the 3G signal returns, I get the pop-up asking me to Allow the data, and if I say yes it works for a bit (but then, because of the 3G signal issue, it cuts out again).
The fix - again - turn on Airplane mode, which disconnects all connections, turn on WiFi, then go back into Call Settings and search for the Home Network again. This is crazy, I can't do this every time, and eventually it craps out again and I have to do it all over.
The other really frustrating thing is I powered it down to do a full recharge overnight...when I booted back up it didn't find my Home Network at all and I had to rescan for it. Testing that out, sure enough, rebooting the phone I have to reselect the Network. Argh.
Any thoughts? The whole necessity of being able to turn 3G data off is so I can avoid this very problem. Basically, I walk in my front door, turn off data over the mobile network, and let my WiFi do it all while I'm home. I wish I could do this as effectively as with my LG on 2.2 (and later, CM7)
acrobat69 said:
Ok...have settled on the ROM in this thread (Bravo):
http://forum.xda-developers.com/showthread.php?t=1332410
I just want to make sure of one thing...the VERY helpful steps that you all have outlined ie BuddyBuds...they stay the same up to step 4 (ROM + update) no matter what ROM I choose, pretty much.
Click to expand...
Click to collapse
Once you get to step 4 inn Buddy's list check out this. It will explain it a little bit better. Brought someone back from the brink on this thread. Where is says Dexter, just replace that with Bravo.
Brians instructions are just a slight bit confusing in that Im not sure if I have to apply just the most recent update for LED ie v1.6...or if I have to install ALL the updates from the start on up (I think there are 4 of them). To me it would seem logical that each new version would be cumulative ie include the stuff from previous versions...but I just want to make sure!
Click to expand...
Click to collapse
Per Brian's OP the v1.9 has all the patches.
v1.9,A new Nandroid IMG backup,All patches included(20111217).
Click to expand...
Click to collapse
One more thing..I didnt notice any mention of gapps in the download in that thread (nor did I see a gapps apk in the files I unzipped, but might have missed it..)...if not, Ill need to apply that too, right..any special version to useÉ
Click to expand...
Click to collapse
Gapps is for CM builds. Bravo is a 2.2 build.
Side note: If you are going to partition it is up to you. I and a few other don't but it is really a personal preference. When I did, I used MiniTool Partition Wizard and it worked like a charm.
A few things though:
1: Your partitions must be set up this way---> Fat then EXT2/3 then Swap (if you choose-I don't and never did-requires you to fastboot a custom kernel and since this is your first experience, I would not suggest it)
2: Sizes. Many noobs will set their EXT2/3 partition to 1gb. That is way too big and you are just wasting space. I find that somewhere between 350-400mb is more than enough.
3: Do not convert your Ext partition to EXT4 unless the ROM you choose supports it. If/when the time comes, use MZ's open recovery utility to do it and not GPArted or MiniTool. The creat a Hugefile that has to be deleted and is a PITA.
4: If you do decide to partition, you will have to boot up fully, then go into your root explorer and in the SD-ext, you will need to create a folder called App (not apps-no S) so it will look like this sdcard/sdext/app. Then reboot and your apps will auto-install there.
Sorry for the long post and good luck.
---------- Post added at 11:30 AM ---------- Previous post was at 10:42 AM ----------
acrobat69 said:
Any thoughts? The whole necessity of being able to turn 3G data off is so I can avoid this very problem. Basically, I walk in my front door, turn off data over the mobile network, and let my WiFi do it all while I'm home. I wish I could do this as effectively as with my LG on 2.2 (and later, CM7)
Click to expand...
Click to collapse
Once you click on WIFI it should take over as your primary source of data. Not sure why unless I think I might have figured it out. Go into settings>wireless>tick your WIFI and once your router pops up leave it alone and hit your menu button. Set your WIFI sleep policy to NEVER and I bet that takes care of it. Pretty sure that is toggling off your WIFI when 3g is present.
Other solution is Widgetsoid and Elixir both have a widget to toggle off data (so does Beautiful widgets too for that matter). You can use those but I really think the above solution should work for you.
Woodrube said:
Per Brian's OP the v1.9 has all the patches.
Click to expand...
Click to collapse
Ah, figured..however when I go into LED Notification, it says "revision 1.6" (or some wording to that effect) at the bottom. Maybe that's just an error, but I just used that to gauge whether or not I had installed the latest revisions etc.
LED Notification works for text messages. I haven't seen it work for calls yet, but maybe I'm doing something wrong. I call the phone, the screen lights up that there's a call, and then ultimately closes when noone answers it. It was at this point that I'd assume the LED notification would come on. Screen is out, so LED, right?
Woodrube said:
Gapps is for CM builds. Bravo is a 2.2 build.
Click to expand...
Click to collapse
Ok I guess I goofed then, because I tried to update with Gapps after I installed Bravo. One thing I noticed is that I wasn't prompted to sign up/into my Google accounts or set up the phone when I rebooted following the Bravo ROM + Gapps install..that had always happened on my LG when I did CM installs...your explanation makes sense!
But...isn't CM6 basically 2.2 and Bravo basically 2.2? Or maybe I misread that.
At any rate, the real reason I updated Gapps is because I wanted the "new" Market look. I don't like the old one very much, really like the My Apps function. Is there way I can just patch this in to Bravo?
Woodrube said:
Side note: If you are going to partition it is up to you. I and a few other don't but it is really a personal preference.
Click to expand...
Click to collapse
Why do people partition? I did it on my LG, but never used it. Partitioning has nothing to do with installing user apps to the SD card, right? I can do that anyways, true?
Speaking of which..in CM there is the ability to set the default install location. I searched to find something similar in Bravo, to no avail. Is there a way to do this?
Wait...I think you just gave me the answer to both these questions...duh me..
Woodrube said:
4: If you do decide to partition, you will have to boot up fully, then go into your root explorer and in the SD-ext, you will need to create a folder called App (not apps-no S) so it will look like this sdcard/sdext/app. Then reboot and your apps will auto-install there.
Click to expand...
Click to collapse
I guess I do in fact want to partition, then. I can't imagine how one wouldn't want to, I mean you don't want apps clogging up internal memory, right?
Woodrube said:
Sorry for the long post and good luck.
Click to expand...
Click to collapse
Never apologize for long posts...I'm the worst at it and I love pouring over every single last detail. I'm sure there are lurkers who appreciate also, I know I really did when learning on my LG. Thanks a million!!
Woodrube said:
Once you click on WIFI it should take over as your primary source of data. Not sure why unless I think I might have figured it out. Go into settings>wireless>tick your WIFI and once your router pops up leave it alone and hit your menu button. Set your WIFI sleep policy to NEVER and I bet that takes care of it. Pretty sure that is toggling off your WIFI when 3g is present.
Other solution is Widgetsoid and Elixir both have a widget to toggle off data (so does Beautiful widgets too for that matter). You can use those but I really think the above solution should work for you.
Click to expand...
Click to collapse
DOHHHHH!!!! I knew I had forgotten something about past settings that made my LG work so well.. I have modified the Wi-Fi sleep policy and hopefully it will work better now! One constant in all the issues I was having, now that you've mentioned this, is that the screen was sleeping/timing out while things were going on. I'd bring it back up, and be all "like, wtf" when my browser wouldn't work or apps that were downloading hung, etc. Mind you, it probably should have reconnected by itself, but whatever, if it doesn't, there's no harm in using Never Sleep for WiFi. I'm not that much of a stickler for battery usage. I go to bed, I charge the phone, I wake up, repeat. I don't need 4 days battery life and if I ever am in a situation where I do, I'm camping or somewhere remote ie no WiFi hence this doesn't apply as I'd just toggle WiFi off completely anyways.
You're right, I could use a Widget to manage my connections and I managed to grab Beautiful when it was 10 cents..but those reside on the screen and I would love to get that pull-down bar back, just so handy to drag down no matter what app/screen you're in...I know, I'm picky
You know what? I got a Notification Toggle app on my PC at home that I'll upload here tonight. I just remembered it while I was at lunch. It is from an older ROM so not sure it will work but worth a try. Usual directions. Push it to /system/apps reboot. It should be just what you are looking for if it works. Might not though so you'll just have to see.
CM6 is 2.2 and so is Bravo only Bravo was made from the official Korean update that was handed down and Mioze has created the CM6 from source. So yes they are both 2.2 but very different.
Edit: I have the latest Market.apk too. It is floating around here somewhere but I can't find in for some reason. I'll upload them tonight.
acrobat69 said:
Decisions decisions...6.3 or go all the way to 7.1
Click to expand...
Click to collapse
try them both first, then see which one you want to use as your daily driver.
i personally like the 6.3 better because it runs the fastest even on stock speed 720 Mhz
you can use Open Recovery to do a full backup, and switch back and forth between 7.1 and 6.3 until you decide which one you like best
7.1 has more themes to choose from and is more up to date, but... less free resources vs. 6.3 which is indirectly related to why it feels less quick than 6.3
7.1 feels similar to the speed you get on the stock ROM from Wind, 6.3 feels like a brand new device
Hello guys,
this is goin' to be my first post on xda-developers sure that this should normally be placed in another thread but permissions to do that are still missing.
I don't want to create useless board blowing posts only to reach more than 10 to get the permission to disclose some bugs I found in the current CM11_saga_flinny_alpha5..
First of all I wanna thank all developers for spending there spare time for such great projects!!
Issues I recognized:
1) Apps moved and located on the sd-card will loose the desktop link after reboot of the system as often as I place it onto the primary screen.
2) The current Brower often crashes whenever I'm on for example facebook watching pictures it crashes, reproducable.
3) in options under developer options activating error report doesn't bring any report up for sending via email
4) could anyone please evaluate if downloading i.e. Redphone or Textsecure works within the GooglePlay Store? I can't although it is compatible to android 4.4.2 so I guess that there is a mismatch between the googleplay and the alpha5 permissions
thanks.
0x23marco
2) The current Brower often crashes whenever I'm on for example facebook watching pictures it crashes, reproducable.
Hey
I had the second bug to. I reflashed and wiped cache and co and it was gone. No idea why.
I have Problems wieht the Headphones control. Does it work at your device? I get no symbol in the statusbar that the headphone is in still can hear music and sounds but the thee control bottums of the headset don´t work neither the microphon.
@Flinny and @devilkin
Known/recognized issues on both ROMs:
Please evaluate if downloading i.e. Redphone,Textsecure, WhatsApp works within the GooglePlay Store!?
I can't although it is compatible to android 4.4.2 so I guess that there is still a mismatch between the AndroidManifest.xml and both of your ROMs. Permissions or something like that..?
Calling somebody and than trying to "mute" the doesn't work so there's an incorrect function.
Moving apps located(moved to) on the sd-card will loose the desktop link after reboot of the system as often as I place it onto the primary screen.
Gererating Error Report doesn't work seems to be no function behind it..
Hope you guys will fix these bugs...anyway thanks for your great work on supporting such an old phone. Still love my Desire S
I'm currently using the recommended 20140517—version and am having some problems with mobile data, so i assume this is a bug.
Mobile data in 3G networks works flawlessly, but in 2G networks it won't connect to any site/page or service. Though sometimes I get some incoming Whatssapp messages or push-news-content. Never Bad this problems with stock Roms. Provider is Vodafone Germany.
I was having some issues with my Galaxy s6, so I figured if they stopped supporting my phone, I might as well get a new OS on it myself.
I rooted and installed 9.0
https://forum.xda-developers.com/ga...20x-5x-nexusos-9-0-samsung-galaxy-s6-t3843199
At first I tried to install previous versions of Lineage, but kept having issues with registering through google, but this one worked pretty easily. I am now using Nova launcher.
The issues I have with it are:
Slower GPS location, like much slower. I am now traveling in Toronto, and it's ridiculously slow to find where I am compared when i was in NYC. I'll continue testing though, maybe it was just a temporary bug
Battery drain seems faster. I was hoping to get an improvement on this issue.
I get no notifications when I get messages through "google voice' I have to open the app to look at it
There is no number in a red circle next to the app to tell me number of messages for it
Substratum not working, keep getting "could not fall back to rooted mode" although according to root checker, I'm rooted. I have no experience with this app, but it seems like it's worth checking it out lol
I think there may be more 'issues' but those are the main ones right now.
I use the latest OFFICIAL LineageOS 14.1, these works fine for me.
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Lagarde said:
Been in the ROM/kernel scene for waaaaaaay too long and have constantly been told that I should use LineageOS (and its predecessor), esp on the Pixel devices that are no longer supported officially. However, LineageOS consistently fails me on every device, despite my being able to get everything BUT LineageOS to work. I've got to be missing something. Going to go through my experiences below...maybe someone can advice how the heck they get LineageOS to work for them on pixel devices?
Round 1: Nexus 6 (CM)
- Installed great
- No initial issues
- Randomly, phone would report "no sim" and stop working
- Reboots sometimes fixed the SIM issue, but sometimes didn't
- Calls lost because the SIM vanished, phone dropped data during a long drive, thus losing GPS access
- Random "service stopped" errors, usually regarding bluetooth
- Never resolved, even over a dozen different versions of CM (this was before Lineage, but same base)
Round 2: Pixel 2 (LOS 16?)
- Installed great, but had to be careful which gapps to use, as most were larger than the system partition
- No SIM errors right away, but a few reboots cleared it up
- Project Fi issues nonstop, with the phone unregistering several times a day
- SIM errors came back, saying my SIM is missing or damaged
- Overheating problems with the CPU. Appears to be the known bug with the CPU, but only appears in LineageOS
- Random "service stopped" errors, usually about the launcher
- Never resolved over different versions of LineageOS (last version tried was I think 16)
Round 3: Pixel 3 (LOS 17.1)
- ROM installs fine, but the notes say you need the Super Gapps to use Project Fi...but that Gapps doesn't fit in system. This seems like an oversight. Installed with smaller Gapps for testing, knowing there may be some Project Fi issues later. Each "try" below is a fresh reformat.
- First try, it popped up an error that there was a SIM, but it was damaged and unreadable. Could not continue. Told me to order a new SIM (the SIM's fine...). Lots and lots of errors about services crashing.
- Second try, it popped up an error that there was no SIM at all. It offered to just use wifi, which I accepted for testing. After downloading updates, it said the wifi doesn't work. Reboots, retries, just wouldn't work...even though it obviously had up to that point.
- Third try, it said my SIM was damaged again. This time it offered to activate eSIM online. Not sure why it hadn't said that previously, but ok. I tell it to activate...and it says the wifi is down. But...it isn't. Wifi working great, but can't activate the phone.
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
nasch007 said:
I just did a brand new install of a Lineage OS 18.1 nightly on my Pixel 3. I used NikGapps core since it has support for Android 11. I don't use Project Fi so I can't attest to that. So far everything has been running perfectly, with the exception of a few missing features or bugs I cannot figure out (small quality of life issues- nothing major). I too had issues in the past with CyanogenMod and I killed my old Motorola that way (probably user error though). I know you said your SIM is fine, but being that it has happened on 3 different devices... is it actually the same exact SIM? Might be worth the $10 fee or whatever to replace it. I haven't had a single error about any services crashing or stopping, perhaps I'm just lucky? One of the roms or gapps packages I was reading the notes on said you could install it in 1 or 2 different partitions, essentially making the size a non-issue. Stupidly, I can't remember which item I read that on, but it is apparently out there if you're willing to look.
I set up all my apps and stuff over WiFi and got the phone how I want it before plugging in my SIM card. I'm on T-Mobile. When I plugged in the SIM I didn't have to do any configuration at all it just works, even has WiFi calling. I don't have any apps on autoupdate and was careful about what "System" apps I toggled or installed from the play store. I'm afraid I can't help you much other than to tell you the nightly from 05-18-2021 doesn't give me the issues it seems to give you. Sorry bud!
Click to expand...
Click to collapse
Appreciate you looking at that. I haven't tried 18.1 yet, as I'm a bit gunshy after how bad 17.1 went for me. I'm strongly suspecting most of my issues go back to Project Fi...but it's not the SIM. I've actually bought 2 extra SIMs over the years trying to resolve this very issue. They all do the same thing on LOS.
Hadn't seen the splitting of gapps. That's news to me. Will look into that, as Project Fi requires the largest of the gapps...which is too big to fit into the system partition.
Lagarde said:
Overall, super frustrating and I can't imagine others are getting these errors, or LOS would have died out looong ago. How are others getting around these?!?
Click to expand...
Click to collapse
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
shaunoleary said:
I'm running LOS 18.1 on my P3 blueline, running it for ages. I use OpenGapps Pico, and haven't had any issues to speak of. It took me a bit to figure out how to flash ROMs etc. on my P3 when I first bought it about 12 months ago, but once I got the hang of it, haven't had any issues.
LOS 18.1 seems very fast and responsive. Rooting with Magisk 23, running LSPosed through Riru, and even have Google Pay working like a charm. Android Auto working perfectly (patched with AIO and Scren2Auto so I can run virtually any apps on my car display if I want to).
Updates are fairly smooth; the only catch is I have to be careful to reflash the Magisk-patched boot.img before rebooting into the system, otherwise I lose root, and by extension, GPay stops working. I just update the ROM using ADB instead of the on-device updater, flash in TWRP recovery, then flash the patched boot.img in Fastboot ... reboot ... and Bob's your uncle.
I also have an old Nexus 7 (2013), and run LOS 18.1 on that 8-year-old tablet very nicely. It can be a tad sluggish on occasion, but for the most part it runs perfectly. The N7 is mostly my games/play machine. I use WiFi hotspot from the P3 when out and about to give the N7 internet access when needed - no problems.
All that to say ... Don't be afraid to try LOS 18.1. It's a fantastic ROM. Can't wait until LOS 19 builds start cropping up.
Click to expand...
Click to collapse
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
AsItLies said:
Good info. Have 18.1 also and have it set up to allow OTA updates and keep magisk and my gapps. Have only done 1 update that way but works perfectly, keeps magisk modules also.
Curious, which twrp are u using? Didn't think there was one available?
cheers
Click to expand...
Click to collapse
Not using TWRP, I'm just using LOS recovery. Sadly, it doesn't allow for doing backups, but it does the job otherwise.
Just an update BTW - currently running into issues with Google Pay/SafetyNet, but it's due to Google playing silly buggers with GPay again, not the fault of LOS.