Related
After using custom ROM for 2 months now I quiet fed up. I have been using mainly Carbon, tried also CM10.1 but I have persistent problems:
- bluetooth handset is pretty much unusable. In 75% of the cases when I connect it the phone freezes. I have to shut it down and start it again. Most of the times I have to repeat the procedure multiple times.
- Poor battery life. I know that Photon Q is not a champion in the battery department but I can not survive a day of periodically synchronizing mail in the background + some browsing + 1h bluetooth audio.
- Application freezing. Touchdown always freezes when I compose a mail for more than a 3 minutes.
- When on bluetooth and listening to music and call comes in, the phone freezes either during the call or after the call has ended
I was hoping when CM10.1 is announced stable there will be no more problems but this didn't happen and now the development is shifted to 10.2 and I don't want to wait any more. After monitoring my phone use for a few days I started to wonder "do I really need a custom ROM"? Hence the thread. Definitely pure stock is not an option and I see here are a few modified ROMS based on the stock but I would like to save myself some time in testing .
What I expect from the stock based ROM is:
- Possibility to hide the buttons! This is absolute must. I can not stand the buttons eating my screen space.
- PIE control (LMT seems to be working quiet nicely although the CARBON PIE is the best)
- CM Themes! I would like to change the battery and clock colours. I have the Android blue colour for the notification bar:silly: Changing the wallpaper and icons is not enough for me.
- longer battery life - one day easily
- stability and reliability - I should be able to trust my phone
- functioning bluetooth
- removal of the Sprint crapware ( I am using GSM moded phone) I guess this can be achieve by uninstalling the corresponding apps.
Could you please recommend a better option than the custom ROM.
Do you have observations and comparison between the custom ROM and the stock in the above topics? Mainly battery life?
Thank you in advance.
P.S. I am very thankful to the developers working on the custom ROMs but I couldn't make it work for my device.
Run stock and theme it to taste.
Sounds like the only option for you.
In my experience all ROMs have their own quarks.
Good Luck
Screwed by Google. Canceled ICS upgrade on my Moto Photon 4G.
Yes the CM 10.2 gives you poor battery life. Compares to my HTC one, Photon Q's battery life is unbearable, even with Mobile data off.
Sent from my One using xda app-developers app
I like ROMS
But you say that you have had all these problems have you checked out the CM roms or others types of roms... so far i think CM is the only one yet to make ROMS for this device you can check only nightly builds ... I just checked yes dev arrrghhh has made the PAC Man ROM for this device just google photon q pac man rom & it will come hope I was able to help.. I''m running Pac man rom on my Fascinate verzion so far I love have all 3 roms in 1 AOKP CM ParanoidAndroid it's best I feel build 8/21/13 Jellybean 4.3
I'm running the latest CM10.1 Skrilax build and it's so stable. I love the option to use sdcard as primary storage. It's been my daily driver since it was released on august 21st.
Sent from my XT912 using Tapatalk 2
I'm running stock, but have removed a lot of bloat.
I'll have a look & see if I can find the thread where a member pulls out all the sprint stuff. That's what I followed.
Just need to figure out how to send MMS.
Sent from my XT897 using xda app-developers app
schmandroid said:
I'm running stock, but have removed a lot of bloat.
I'll have a look & see if I can find the thread where a member pulls out all the sprint stuff. That's what I followed.
Just need to figure out how to send MMS.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Maybe change the APN settings will solve the MMS problem.
I can't send & receive MMS on my sprint one even after I changed the APN settings.
Sent from my XT897 using xda app-developers app
j_rivers said:
Maybe change the APN settings will solve the MMS problem.
I can't send & receive MMS on my sprint one even after I changed the APN settings.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Yeah, it doesn't work. The hidden DATA menu has extra settings for accts & MMS etc. I have changed these, but there is still something else stopping it. Typically need to have the acct number to edit these (although there are other ways).
Its due to the Sprint acct settings, I'm sure.
I CAN receive MMS though.
Sent from my XT897 using xda app-developers app
yeah, but the thing that stock is NOT perfect is the reason why we are using customs...
every roms have their own kink to iron out and we have to bear with them.
In my case, sound volumes of recorded videos are obviously not like them with stock, but I choose to go with CM10.2 just to be on par with other things.
Go SMS Pro allows me to send MMS on stock, so this solves the stock ROM in a round about way for me.
Now to find a custom ROM that will connect to my WiFi ap for my other Q.
Sent from my XT897 using xda app-developers app
To answer my question - definitely stock. The battery life is incomparable to the CM based ROMs. I can easily survive the day and may be have some juice for the morning. No restarts and force closes. I am not afraid any more that I will get a phone call while listening to music on bluetooth headset.
The main disadvantage of the stock for me is the lack of customizations. But with the expose framework and some other apps I am almost at same level as with the custom ROM.
As I am with modded GSM version I just have to find out how to remove the annoying Sprint activation message at each phone start.
Hey there - I have removed a lot of sprint bloat out of stock, and I no longer get the activation request on boot. Can't remember the thread where one of the guys (German I think) listed all the bits to pull out, but you'll find it if you look.
Sent from my XT897 using xda app-developers app
WIFI is now connecting with CM Rom if using WPA2-PSK
Just a quick note to say that I have now resolved the WIFI connectivity with my WiFi AP while running CM Rom (10.2-20131129 by Skrillax).
In a nutshell, after adjusting many settings on my AP (TX power %, Wireless Mode, etc, etc), it is the security mode.
CM don't want to connect when running WPA-PSK. Changing to WPA2-PSK has fixed it.
I get a 'connecting' notify, then 'saved' if I switch back to WPA-PSK. Just don't know if this is due to the recent build, as I was running CM from around June, previously.
Pretty certain I tried the different security modes before, even turning security off didn't help. Manually assigning IP's in the phone also didn't help.
I DID however have the TX power set at 25% when it first connected, but I have reset all settings back to normal/default, & it is still going strong.
You can decide for yourself whether it is better that CM won't connect when using WPA-PSK, for me it has been a pain in the A$$. Stock Rom connected fine on WPA-PSK.
Hope this sheds some light on poss wifi issues for the propeller heads, and other connectivity frustrated individuals. May even help others that suffer dropped connections??
I am using the stock ICS ROM and I am getting 169hrs of standby time.
I use a combination of Tasker and Smart Actions to automate my phone. Tasker controls plugins for Greenify, Secure Settings and Taskill (for some apps)
I am easily getting a full day out of my phone with 60% battery usage. I do use my phone quite often.
The screen brightness and keyboard backlight are the real killers of battery life. Set these to as low as you can handle.
Every time the screen is OFF, my (WiFi, Mobile Data, Bluetooth and GPS) is set OFF.
WiFi is my main data connection when I am near a WiFi spot.
Mobile Data only turns on when I need it.
Bluetooth on when I am charging to connect to my car. Everything gets Greenified on automatic exit of Car Mode
GPS is only set on when I am in the car.
Certain Apps only sync when I turn the screen on, others only when I open them. Even though I can set an interval for this.
When I jump in my car, Car Home V3 is launched with my custom widget setup and plays Spotify Automatically.
With root and xposed framework, Greenify will allow data sync at set intervals. The main thing is it Hibernates all chosen apps and their data usage. Set Tasker to Greenify (hibernate) apps for certain triggers, i.e. Leave home Wifi = Greenify (Hibernate) All Apps.
I also deleted a lot of the Sprint bloatware.
"Better Battery Stats" helped me get to the bottom of my battery draining apps.
I also have a "Battery Graph Widget" installed so I can keep an eye on my levels.
Link to download it here (credit to AICP CM devs on their google plus page): https://plus.google.com/101577397694816898663/posts/GS4FcdKVomX
From the comments of the post, this is a write up of what is working:
I did dirty flash and all still works. I'd love to see a change log but I know that's asking a lot.
Boot time was fairly quick after flash approx 60 secs.
File explorer still can't see the sd card but as optix told me before, you can use rootbrowser app or just go to settings storage and you can see and manipulate sd.(I believe it's due to a superuser issue not related to ROM.)
BT worked fine for me last night on previous build except when not using it auto disconnected but as soon as media was played again it auto connected and plays normal. Will test BT further.
Also I know that cm theme manager is based on cm's C-apps and it's code base hasn't been updated to work in SDK 24 ie n-7.0 but I'm sure that will come soon.
There is a delay when connecting calls. The delay seems less when placing calls then when receiving. As long as the caller is patient it does connect. This might not be a Rom issue as I use Greenify and I've read some where that this issue had been encountered on other Roms.
As long as you can deal with the stock N theme, 20-30 ssecond call cconnect delay, and not having Xposed untill it's updated to work on SDK 24 then this is totaly daily driveable.
PS thank you to the Devs, please tell me how I can be of service helping or testing and I'm all yours.
Click to expand...
Click to collapse
Who wants to try?
not i, said the fly. still happy with MOAR 7.0
following nightlys
I have the sprint g900p and am following the nightlys build for cm 14, so far I've ran into a few issues, rotate doesn't always work, it is dependent on app. YouTube works but the stock cm chrome will not. Also I cannot send any SMS unless I force the radio to move from LTE to 3g.
And of course the SD card issue.
Just so you know, started with stock ROM, updated everything, clean Odin flash with twrp.
If you need any info let me know otherwise I'll post as I find bugs.
Hi guys,
In the kernel I developed (Elite-Boeffla-Kernel for i9300) I implemented a setting that controls if the kernel prints messages or not (the messages that are accessible via the "dmesg" command). If I turn it off so that my kernel doesn't create any messages I have some small issues like videos not playing after a few hours. When I turn these messages on again the issues persist until the next reboot. The only way I know to avoid them is not turning off kernel messages.
My question is:
Why are these issues caused and why don't they occur immediately, but after a few hours?
This feature works as follows:
There's a file in the /sys folder that contains either 1 or 0. When this is set to 1 the kernel works as it would work if this feature wasn't implemented. But when I set it to 0 the program that creates the kernel messages is stopped immediately after executing (using an if statement). In the source tree this program is called "printk.c".
Hi all, long lurking rom-installer who can self-fix most problems here. Got a problem I can't fix that's bothering me. Recently upgraded to an S7 so naturally rooted it on day one and been trying to get it my-kind-of-working fully ever since. I do like to bugger about with things in a vain attempt to shield some private data from some orgs and realise I'm in a particularly specific hole that I'll probably have to climb out of on my own, but if you don't ask...
Internet using apps pretend to work, sometimes for days, then just refuse to open. Screenshot example of the second and persistent error (after simply "Lightning has stopped" the first time) is attached.
Model: G930F
Current ROM: ambasadii 7.0 TW Nougat (here)
Xposed: 88.2
Root: Magisk
Significant mods:
1) use xPrivacy
2) disabled significant number of remaining packages using Package Disabler Pro (list attached)
3) run Orbot
4) run AFWall
5) modify app permissions in Settings/Apps to restrict where I think I safely can
6) run BackgroundRestrictor
The behaviour still emerges even if I don't apply 4), 5) or 6), it has started prior to me finishing my tweaking.
I know xPrivacy is not supported for Nougat but it seems to work ok for the most part with some retweaking of settings since moving from Marshmallow on my old phone. I understand it could be the cause of the problem but I'm wedded to (some of) my privacy enough to persevere before abandoning it. For the record I've checked the usage log for restrictions on any calls around e.g. internet that might be interfering but I've been unusually generous with permissions trying to fix this and there's no restrictions on any apps with internet access around that, or much else really at this point. I've also had a look in general usage log rather than app specific, looking for system components that may be working alongside the app and failing with a restriction but can't see anything being denied. Any system apps haven't been touched by me, I fetched what I could from xprivacy crowdsourced restrictions on the base ROM apps and then only applied my template to apps I've downloaded myself.
Some other background on the problem: everything will be set up as I like it - ROM installed, debloated, all the rest of above modding applied. It will be working super-fine. Nice and fast, little bloat left, just enough Google to get Play Store, apps installed and working, all will be and appear fine. After an undetermined & fluctuating length of time all of the internet-facing apps will suddenly not open. This includes but isn't limited to the Browser (stock and Lightning, Brave, Pale Moon, etc.), Twitter, Signal and the Official TWRP App.
Interestingly, internet-connecting apps that will connect on demand but don't seem to make a call on every app open (mostly due to prior settings changes) do not fail. They will still open fine and work fine, connecting when asked and not crashing. For example, K9 Mail and Pocket.
Another weird data-point: Signal will fail but will often do so later than the other internet-connected apps - possibly it has a token with GCM or something that when it expires will try to renew on app open which is when it starts to fail like the others?
The apps will work again if uninstalled and reinstalled but once the behaviour starts again, and it will, it will repeat. Sometimes twice or more in a day. So reinstalling every time is not going to make for a usable phone. It's like they have an error renewing their wifi lease or something.
It can take up to three days to begin - this build it worked fine for days whilst I was away and slowly, progressively building the system back up with regular TWRP backups. I can restore a TWRP backup from about 6 hours before the problem started and it'll work fine again, but still wait a random amount of time before the problem begins again.
I did think it may be something to do with the router here and home WiFi as it behaved much better whilst away and didn't break until my return, though that is likely coincidence. I'm in pattern-observing mindframe so false positives are everywhere. I thought it was connecting to the PC via USB that was doing it at one point.
Last data point: it's happened with a different base rom too (Decent here), same thing, but came on sooner each time. I would change the base rom again to see if it's something there but I suspect that should be one of the last things I try given it's happened across two roms now.
Anyway, if anyone has any insight on Nougat TW ROMs on an S7 with this kind of set up and/or any clues or ideas as to why internet connects would suddenly be crashing all these apps... I'd be grateful. Otherwise I have many reinstalls and possibilities to eliminate. Which means waiting many sets of days before I can repeat, which makes progress frustratingly slow when you depend on the phone (Signal particularly) to connect with people.
AFWall stands out if you're having problem with net connections to apps etc
Yes good point, thank you. I think i've run the ROM with same problems without any rules applied but I've disabled it fully now just to be sure. Much obliged.
If it persists, the proper way of troubleshooting would be to clean install the ROM only, no tweaks, Xposed, firewalls or anything, just the ROM and your apps you're having problems with
If that all works together fine, then add ONE new thing to the mix, test for a few days, rinse and repeat until you add something that causes the problem again
With testing for a few days between each new addition you're be 100% sure what is causing it once it starts again
Thank you! Yes that's the plan but I thought I'd ask first as there's a lot of waiting down that route. I did do it to a point during last build but only waited overnight after each phase. I think I'll start that.now. I can always restore this backup if the solution presents in the meantime.
Yea that's what I was thinking, backup this ROM, clean install, work out the issue, restore this ROM and fix it
Good luck
Thank you I'll report back if/when I work it out, for any other possible future readers.
I changed the base ROM & installed Xposed in a different way and rooted in a different way and tweaked Permissions to be more permissive and and and... I've read rovo89's farewell so I won't say "It's xprivacy" but it's definitely how xposed & xprivacy interact, whether by flashable zip or systemless magisk. It'll work fine for a good while but then starts corrupting everything internet connecting. Removing it removes the problem & restores the app functionality.
Sadly it's the same even if you restrict nothing in xprivacy & just leave it installed & switched on. I've had to remove it. Considering trying to go back to MM as I know it worked on my previous phone.
As was shown here: https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/ you could enable WiFi calling as your preferred calling method with this nice little ADB command. I can confirm with Oreo it worked, and stuck through reboots and all. I have however now sideloaded my Verizon Pixel with the Developer Preview of Android P. It was a smooth upgrade, however I can no longer get WiFi calling to be preferred with the ADB command. It was originally still listed there, and was still containing the "2" value, but the setting no longer worked. I did a factory reset to start fresh, and I notice that the setting is no longer present when doing the “settings list global” command. I tried adding the line and it still does not work. Anyone have a workaround or any ideas on what I can try to get the WiFi calling to be preferred again? I really rely upon it at work, as we have almost no cell signal, and I have come to love the previous ability I had to have it be the Preferred method for all my calls. Since I have one of the jacked Verizon Pixels, I was never able to unlock the Bootloader, so there is no going back for me! I do also want to say on that note though, for the last week, since I did the factory reset and re-did everything, my phone has been rock solid on the "P" Developer Preview!
Stealth111 said:
As was shown here: https://www.xda-developers.com/enable-preferred-wifi-calling-option-verizon-pixel-pixel-xl/ you could enable WiFi calling as your preferred calling method with this nice little ADB command. I can confirm with Oreo it worked, and stuck through reboots and all. I have however now sideloaded my Verizon Pixel with the Developer Preview of Android P. It was a smooth upgrade, however I can no longer get WiFi calling to be preferred with the ADB command. It was originally still listed there, and was still containing the "2" value, but the setting no longer worked. I did a factory reset to start fresh, and I notice that the setting is no longer present when doing the “settings list global” command. I tried adding the line and it still does not work. Anyone have a workaround or any ideas on what I can try to get the WiFi calling to be preferred again? I really rely upon it at work, as we have almost no cell signal, and I have come to love the previous ability I had to have it be the Preferred method for all my calls. Since I have one of the jacked Verizon Pixels, I was never able to unlock the Bootloader, so there is no going back for me! I do also want to say on that note though, for the last week, since I did the factory reset and re-did everything, my phone has been rock solid on the "P" Developer Preview!
Click to expand...
Click to collapse
I know there was a flashable magisk module that enabled the options, but it doesn't help with the actual ims status(*#*#4636#*#*, phone settings, ims status). It might be that you need the official Verizon rom that includes the necessary lib files, or that the dev preview doesn't include those and therefore you can't yet enable it?
Xdevillived666 said:
I know there was a flashable magisk module that enabled the options, but it doesn't help with the actual ims status(*#*#4636#*#*, phone settings, ims status). It might be that you need the official Verizon rom that includes the necessary lib files, or that the dev preview doesn't include those and therefore you can't yet enable it?
Click to expand...
Click to collapse
I though about the Verizon thing as well, but I also used the Developer Preview for Oreo, and it worked with it just fine, so I am thinkning they have just moved it somewhere else in the "P", or something of that nature, but I am hoping that someone here can possibly figure it out!
Stealth111 said:
I though about the Verizon thing as well, but I also used the Developer Preview for Oreo, and it worked with it just fine, so I am thinkning they have just moved it somewhere else in the "P", or something of that nature, but I am hoping that someone here can possibly figure it out!
Click to expand...
Click to collapse
I'm having the same problem after a recent update. WiFi calling no longer works, and the option has disappeared from settings.
Dialing *#*#4636#*#* no longer brings up the menu, either.
I tried via adb shell to set wfc_ims_mode=2, but that doesn't work. `settings list global` shows that it is set to 2, but even after reboot wifi calling still doesn't work.
euhn said:
I'm having the same problem after a recent update. WiFi calling no longer works, and the option has disappeared from settings.
Dialing *#*#4636#*#* no longer brings up the menu, either.
I tried via adb shell to set wfc_ims_mode=2, but that doesn't work. `settings list global` shows that it is set to 2, but even after reboot wifi calling still doesn't work.
Click to expand...
Click to collapse
Probably just something that handy yet been implemented, being it is a Dev preview . Same thing with the lockscreen shortcut icons for camera and phone.
Just an update. I stuck a T-Mobile SIM card in my phone and after using the magisk module I mentioned, the options appeared for the advanced and wifi calling. I'll do it again tomorrow and pay a screen . It's almost midnight here so gonna crash
I'm running stock p on verizon. Hoping someone comes up with a solution.
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first
Xdevillived666 said:
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first
Click to expand...
Click to collapse
Experiencing this issue after upgrading my Pixel XL and my wife's Pixel 2 to the Verizon Pie.
Details for my Pixel XL:
Android Version 9
Android Security Patch Level: August 5th, 2018
Kernel Version: 3.18.10-ga765425
Build Number: PPR1.180610.009
I used to use the ADB hack flawlessly, now I can't seem to make WiFi Calling Preferred over mobile network. So even though I have one bar that goes in and out, it uses the network then drops.
murraj2 said:
Experiencing this issue after upgrading my Pixel XL and my wife's Pixel 2 to the Verizon Pie.
Details for my Pixel XL:
Android Version 9
Android Security Patch Level: August 5th, 2018
Kernel Version: 3.18.10-ga765425
Build Number: PPR1.180610.009
I used to use the ADB hack flawlessly, now I can't seem to make WiFi Calling Preferred over mobile network. So even though I have one bar that goes in and out, it uses the network then drops.
Click to expand...
Click to collapse
I'm gonna pm ya
I haven't even updated to P yet and mine stopped working on the last security patch. I can set it back using adb. Reboot and wifi calling comes on. The first phone call works for about 5 minutes, then drops. The settings database values go back to default. The only way to get it to work again is to go through the whole process again.
Too much trouble. Sure would be nice to just turn it on and have it work.
Sent from my Pixel using Tapatalk
If you've already had WiFi calling working previously with pixel (I can only confirm first gen works with this)
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first and then add the following (see doc).
Doc here
Just copy paste all lines according to instructions from previous post. Check and make sure under phone menu that you are instructions registered
Xdevillived666 said:
If you've already had WiFi calling working previously with pixel (I can only confirm first gen works with this)
Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first and then add the following (see doc).
Click to expand...
Click to collapse
I'm new to all this, what do you mean by, "Add this : system/buildprop under additional properties -Make sure to enable read write on "system" first"
XDA won't let me put the text needed in the comments. Dload my PDF and copy paste the text from there to your buildprop
Does Google Pay still work after you edit the build.prop file?
Sent from my Pixel 2 XL using Tapatalk
abuttino said:
Does Google Pay still work after you edit the build.prop file?
Click to expand...
Click to collapse
I didn't not know. Can't use it in France anyways so I'm not worried about it.
Doesn't work in DP5
Hoping that someone else here can verify it in the regular version of pie.
I didn't switch to the RTM because WiFi calling is too important and I did want to test it though.
Sent from my Pixel 2 XL using Tapatalk