Database Info

Stock vs Custom ROM

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.

[Q] net::ERR_EMPTY RESPONSE

Every time I flash a 4.4.4 ROM I get net::ERR_EMPTY RESPONSE or net:: ERR_SSL_PROTOCOL_ERROR whenever I visit a Google website.
This problem not only effects any browser I use, but also the Google apps.
Gmail, for example, will sync to my phone but images do not show and anything done on my phone will not show anywhere else(read emails still unread).
Essentially, updating to any ROM that is 4.4.4(CM, Liquidsmooth, CarbonROM) makes my phone hate connecting to Google.
Is there any solution for this?
I have images of the problem on imgur if it helps. Can't post image so just put these in the url
/9OkRFS6.png
/8DmING1.png

I've had this happen with the AOSP browser, but I've never had this issue with Chrome or any other apps for that matter.

is CM11M8 a 4.4.4 rom? m7 is 4.4.2 and i have no issues with it. i haven't upgraded to m8 yet since everything seems to be fine in m7 and now that nard's not working on cm anymore, i hesitate to upgrade it.

I faced the same issue after using mobile TOR (Orbot). When connected via Tor all was allright, but after switching it off the connection broke. Opening any URL from any app haven't succeed.

Original Shield Tablet Freezes When Connected to WiFi

Hi there!
I've contacted nvidia regarding this issue (reps seems oblivious) and posted it on their official forums to no avail, so I'll try and give it a shot here.
Basically whenever my tablet connects to WiFi after being disconnected for some time (a few hours to a few days), the tablet freezes when it downloads notifications. The freezes can be minimal (like a 5 second freeze) or be quiet substantial (it can lock up for as long as 10 mins). Once all notifications are downloaded and displayed, the tablet then performs like a charm. I even got my tablet replaced from nvidia and it has the same problem as the one I sent in. Uninstalling Facebook and Facebook Messenger improves performance drastically, but when my tablet checks for notifications it freezes still freezes for a few seconds (with Facebook installed, it could lock up for 10 mins and crash the launcher multiple times). Running on max performance did nothing. I'm really curious if this is a hardware or software issue since some people doesn't seem to have this problem.
I'm running on nvidia's stock firmware (4.2) unrooted.
So here is my question. Have any of you guys experienced this problem? Were you able to solve it? How did you solve it (did a custom rom solve this)?
The main reason why I haven't installed a custom rom yet is because I use the stylus frequently and I use the touch-block feature in nvidia's stock roms and couldn't find ports of it.
Here is a video of the issue. (youtube.com/watch?v=cJrUPV7mY6s) Now there are a lot of widgets on the video, but I assure you removing all of them does nothing. I tried.

Facebook Messenger. That says it all. What other apps have you running in the background?
This definitely sounds like a software issue to me.
Maybe you're being hijacked. Who knows.

I've had this same issues since I got the tablet (K1). System reset, no non-Google apps. Happens regardless of FW; I'm on the latest update. Don't be quick to blame the OP.
Basically, every time the tablet gets a new network connection, the system hangs and becomes unresponsive for 10 seconds to 2 minutes at a time. It's obvious that it's updating all the apps' network requests. However, the thread priority should make the system hang. I've only seen this issue on the K1; never on any other Android device. Either they're using a custom network stack, or they've messed with networking priorities.

I'm on the latest update
Click to expand...
Click to collapse
Of Facebook Messenger? Or OS? Or all apps?
Either way, it makes no matter no such issues on Lollipop. I am just saying.

Google connection

Hi All,
I am trying to convert my old d2vzw into a wifi only device for my daughter. The sim card has been removed, but the issue I describe below existed before when it did have a sim card installed... This only happens with my d2vzw, so I figured I would inquire here. I have only tried this on a few different CM based roms (android 4.4.4 vanir, and cm13) ... the issue is as such:
When trying to connect with google (either searching from the address bar or even going directly to google.com) using opera mobile (it is the only browser left that provides dynamic text reflow) it kicks back with one of several different errors, outlined in the screenshots below. This happens on at least 4 different wifi networks I connect to, all of which work fine with other browsers on this phones, and opera on other phones. Currently installed is a brand new install of CM13, the 20161113 build of invisiblek's official nightlies. I did change the hostname and rebooted though... I don't know if that would have any effect, it did not on my Nexus5... I am hoping this is a common issue that someone has run into? It is odd to me that this only happens with this particular phone, and only with opera, regardless of whether data savings is activated or not. Upon refreshing the page several (sometimes quite a few) times, the page will load up. Often, the page only loads partially. Other times, the page will flash up like it is starting to build, then it will bounce back to one of the errors seen in the screenshots below.
I apologize if this is rambling, I am just trying to provide as much detail as possible. This only seems to happen with google itself, not any other website ...
...Any ideas?
Thank you for your time...
screenshots attached

appye said:
Hi All,
I am trying to convert my old d2vzw into a wifi only device for my daughter. The sim card has been removed, but the issue I describe below existed before when it did have a sim card installed... This only happens with my d2vzw, so I figured I would inquire here. I have only tried this on a few different CM based roms (android 4.4.4 vanir, and cm13) ... the issue is as such:
When trying to connect with google (either searching from the address bar or even going directly to google.com) using opera mobile (it is the only browser left that provides dynamic text reflow) it kicks back with one of several different errors, outlined in the screenshots below. This happens on at least 4 different wifi networks I connect to, all of which work fine with other browsers on this phones, and opera on other phones. Currently installed is a brand new install of CM13, the 20161113 build of invisiblek's official nightlies. I did change the hostname and rebooted though... I don't know if that would have any effect, it did not on my Nexus5... I am hoping this is a common issue that someone has run into? It is odd to me that this only happens with this particular phone, and only with opera, regardless of whether data savings is activated or not. Upon refreshing the page several (sometimes quite a few) times, the page will load up. Often, the page only loads partially. Other times, the page will flash up like it is starting to build, then it will bounce back to one of the errors seen in the screenshots below.
I apologize if this is rambling, I am just trying to provide as much detail as possible. This only seems to happen with google itself, not any other website ...
...Any ideas?
Thank you for your time...
screenshots attached
Click to expand...
Click to collapse
So use a different browser.
Sent from my SCH-I535 using Tapatalk

Snotty ass computer forums...

appye said:
Snotty ass computer forums...
Click to expand...
Click to collapse
Well he does have a point. Nothing wrong with trying something different
Sent from my Nexus 6

AOSP Or Lineage ROMs for Sprint

If I'm understanding correctly none of the current roms work on Sprint's network. Is that correct?
I've tried lineageOS and couldn't hold a signal so if there's one that works please point me in that direction.
Thanks.

I hadn't had any luck with ROMs on Sprint either until today. I decided to restore my TWRP backup of LineageOS 14.1 official, then I re-flashed the bootloader and radio from the most recent stock build (I had been on 4.4.3 to test something). The device was not active on my account at the time, but when it booted up, I got an alert from Signal Check Pro that it had an LTE signal, and the LTE indicator was on. So then I signed on and swapped devices to try to reactivate it, and immediately went into carrier settings and tapped update network settings. I got an alert shortly after saying com.android.phone had stopped, but it appeared to work, and I had a signal and LTE indicator. There was a Lineage update showing (May 17), so I downloaded it (over LTE) and installed it. Everything has been working so far, both before and after the update: voice, LTE (all bands), SMS, MMS, and RCS. So I really didn't do anything different, it's just working now.
Note, I have had SMS problems on every stock build starting with the first 6.0.1 build, and all security releases after it. I haven't had any problems on any older Android version. What happens is it works fine for a while, but at least once a day. SMS stops working until I reboot or update network settings. That's why I installed Lineage, trying to determine if it's a bug in Android or the radio. So far, no problems, but it has only been a few hours.
Sent from my Nexus 5 using Tapatalk

LOL it course the SMS bug struck after about 24 hours.. except this time it took a couple of tries to get data working again, and SMS wouldn't work again.. I knew better.. back to stock again..
Sent from my Nexus 5 using Tapatalk