I flashed the last 4.4.4 Final L900 Note 2 Rom as I wanted a stable rom on my wifes phone so she wouldn't have any issues. I have this same rom on another sprint phone and it allows prl/profile updates.
On the Note 2 this option isn't there. it has a mobile networks, then clicking on carrier settings causes a crash and I get an error unfortunately com.android.phone stopped and thats it.
It says it is running PRL# 2407. Is that the latest PRL for this device?
As of now the data, calls, messaging all work. I just want to have prl update available. I used voice dialer and searched for APN to get access, and it shows the attached, but none selected. Perhaps selecting one would enable the network settings so it don't crash? But I don't want to select one then lose any connectivity?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know this thread won't get much viewing probably, but hoping to find a solution, otherwise I may try cyanogen, but prefer to stick with this rom. I want to make sure she can update PRL if needed. Thanks!!!
I got on my other phone (Sprint galaxy nexus) with omnirom 4.4.4 final and it had this app (see picture). The note 2 omni doesn't have it. I may flash this apk and see if it allows prl/profile updates. Think that's safe to try?
Note2 builds for all LTE-capable devices were a unified "t0lte" build.
I'm not sure how to handle PRL updates for such unified devices, you should look around the Sprint Note 2 forums as this probably is a Sprintism that affects multiple projects.
t0lte support in Omni is pretty much dropped due to lack of a qualified maintainer with the appropriate skills to maintain a device (knows/understands both C and Java sufficiently to fix problems without just hoping CM will fix it.) It's unlikely to return for 5.0/5.1 and 4.4 won't be receiving any further fixes.
Thanks, I guess as long as her phone works with the most current prl she should be fine. I read you can always flash back to a touchwiz rom, then update the prl, then reload omni. A pain, but manageable I guess.
Related
I am assuming once you root the phone and push a custom ROM onto the phone, this will fix HTC's introduced bugs?
Bluetooth
SMS battery drain
Reverting apps versions
Stuff like this.
No, because the custom ROM is just the Sprint ROM with a few additions and modifications.
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Treefallingquietly said:
Ouch.
ok, anyone working on compiling a 2.0 kernal?
Click to expand...
Click to collapse
HTC
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Although the bugs are not fixed, rooting allow one to use various workarounds that would not be possible without, and in fact for EACH of the issues you have listed:
Bluetooth: http://community.sprint.com/baw/thread/23854?tstart=0
While I cannot personally vouge for this, I have seen many posts on Sprint and here that detail the workaround described in the post as effective.
SMS Battery Drain: I think this may have actually been the first big bug discovered, and also fixed without root! Unfortunately, the default messaging app is defective, so in the meantime it is recommended to use either chompSMS or Handcent SMS from the Market until an update is released.
See this post: http://community.sprint.com/baw/thread/23043
Finally...
Reverting Apps: This is addressed on both forums, but a workaround only exists with root, and is similar in fashion to the bluetooth fix but for a different directory.
http://forum.xda-developers.com/showthread.php?t=582176
http://forum.xda-developers.com/showthread.php?t=581806
Hope this helps! I intend on posting a very detailed guide on every step of rooting, backing up, and working around most of the detailed problems in the very near future, stay tuned!
What I'd like is a kernel that will have this working as intended. But really, I am not afraid of the work arounds and the hands on work required, but if my wife had this phone with these problems, she would have chucked it out the window within days.
One more...
You left out the original bug (mentioned by briankwest, one of the first rooters), the TCP timestamp issue:
echo 0 > /proc/sys/net/ipv4/tcp_timestamps
This could also be added to the MoDaCo init.rc so it is set at each boot (otherwise it will revert back to "1").
If some developers could try and add their ROM's to test this out that would be a big help.
http://roms.scottymeuk.co.uk
Features
Add Device
Add ROM to Device
Add Version (Release) to ROM
Changelog
Comment System
Like/Dislikes
http://roms.scottymeuk.co.uk
This is probably been attempted before but I got bored and decided to make a ROM Directory type thing. It took me a day to develop and is written in PHP using the CakePHP framework for anyone that is interested.
If anyone has any feedback or anything please let me know.
The reason there is only 1 ROM added is because they are the files i have on my PC as i use that ROM.
Below are some pictures of it:
http://roms.scottymeuk.co.uk
Add Device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Add ROM Version
Device Home
Device Page
Login
ROM Page
Submit ROM
Change Log (Per Version)
http://roms.scottymeuk.co.uk
Very nice set up I would definitely use it. Ive been doing alot of work lately on my friends and family's android phones and if you can get this up it wont take forever to find a rom that they like and i can set it up for them
http://roms.scottymeuk.co.uk
It would definitely be nice to have one stop place for all the latest ROMs. But, in my opinion creating the website isn't the hard part, the hard part is to keep your directory updated with the latest ROMs.
Because there are lots of ROMs available (different phones, different versions etc) and many people use nightly builds too like in case of Cyanogen. So, that would mean you will have to update the data/urls/change logs etc regularly.
How do you plan to aggregate and update all this data? Manually? Or fetch data as a feed from their respective website? Or hoping for the web 2.0 way?
But, if you manage to do that then it would be really great.
People who create the ROM's will be able to do all of that them self. The way it works is that the ROM is submitted by someone (doesn't have to be the developer) and then that ROM is locked to their account, it is then approved by an admin and then they are then free to add as many versions as they want, where they can upload a zip file, and add change log for THAT version.
The change log is not one big database entry, it is the "versions" of the roms. For each version you submit there is a change log.
Since the L720TVPUCOD1 Lollipop rom is out now what's the chance someone could port it to work on the OG Samsung Galaxy S4 (L720) sprint has pissed a lot of people off that own the L720 (Like myself) that they updated the spark version before the non spark version
Zero, OTAs can't be ported. Just be patient, newer phones get updated first every time.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
romeo143211 said:
Since the L720TVPUCOD1 Lollipop rom is out now what's the chance someone could port it to work on the OG Samsung Galaxy S4 (L720) sprint has pissed a lot of people off that own the L720 (Like myself) that they updated the spark version before the non spark version
Click to expand...
Click to collapse
I guess you didn't see this: http://forum.xda-developers.com/showthread.php?t=2262381&page=15
OD1 was pulled. OD2 is coming out for both the 720 and 720T
RDFs just mean they are testing builds, nothing has been released.
[WQUOTE=bilgerryan;60294664]Zero, OTAs can't be ported. Just be patient, newer phones get updated first every time.
[/QUOTE]
I guess what I meant to say is if it would be possible to use the base of the spark ota ROM and modify, root, etc to make it work on the l720
romeo143211 said:
I guess what I meant to say is if it would be possible to use the base of the spark ota ROM and modify, root, etc to make it work on the l720
Click to expand...
Click to collapse
Again no. The RDFs have started for the L720 as well so you have nothing to worry about, we should get it about the same time as them. Nothing has been released yet anyways. It will take a few weeks for it to get rooted, deodexed, etc.
OD1 for the 720T was initiially on Sprint's OS upgrade page but was pulled by Sprint even though source code for OD1 still remains on Samsungs Open Source Release Center website. At any rate, neither version is in site even though AT&T has had their 5.0 for 2 weeks now It's very sad when AT&Y beats out any other carrier with an OTA update.
Hello,
I have a Sprint Galaxy S4 (but you knew that.) that is currently running 4.4.2 Android. I have rooted my phone, but I never installed any roms, I am still using the stock touchwiz. For a while now, my phone has been telling me "system update downloaded" and wants me to install it.
Basically: How do I go about updating my phone without breaking something due to my root status. Should I un-root? Should I just hit update? I'm skeptical because I don't know much about fixing my phone if I accidentally brick it.
Alternatively, would I be better just getting a rom, like Cyanogen? I don't hate touchwiz as much as I probably should, haha.
Side note, I apologize if this has been raised before, I have been searching for answers to this since the first time my phone notified me of the update, between Google searches and searching this forum, I haven't found a topic that addresses my issue.
Akalron said:
Hello,
I have a Sprint Galaxy S4 (but you knew that.) that is currently running 4.4.2 Android. I have rooted my phone, but I never installed any roms, I am still using the stock touchwiz. For a while now, my phone has been telling me "system update downloaded" and wants me to install it.
Basically: How do I go about updating my phone without breaking something due to my root status. Should I un-root? Should I just hit update? I'm skeptical because I don't know much about fixing my phone if I accidentally brick it.
Alternatively, would I be better just getting a rom, like Cyanogen? I don't hate touchwiz as much as I probably should, haha.
Side note, I apologize if this has been raised before, I have been searching for answers to this since the first time my phone notified me of the update, between Google searches and searching this forum, I haven't found a topic that addresses my issue.
Click to expand...
Click to collapse
You coins just try a custom Touchwiz ROM like mine (Wicked X). You can't install the OTA on a rooted system, you need to unroot to take the OTA.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everything is working great, I am not seeing any issues at all.... but I am using Jasmine 6.1 which is based on OF1 lollipop 5.0. I had been running 4.4.2 when I unlocked the bootloader and then installed TWRP and then Jasmine6.1.
I was digging through my phone's status via the Phone INFO app and (not really surprised) that my bootloader was still NC4 and my modem was NK1 (I flashed the OF1 modem when I flashed lean kernel).
Like I said, all is working well... I tend to leave things alone if there're not broken..... SO.... Is there any reason I should update bootloader or modem?
Thanks in advance...
Don
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N900V using Tapatalk
I would advocate the "if it ain't broke, don't fix it." approach.
Assuming you archive the various Odin stock releases so you'll have them in the future, you always have the option of rolling forward, but mostly won't have the option of rolling back.*
For earlier releases of firmware than what you are using (e.g. MJ7 and MJE) there seems to be an inability to boot stock kernels from later releases. And even non-stock kernels as well (I can't boot twrp-3.0.2-0-hltevzw-4.4 for instance, even though it doesn't have a "stock" heritage).
But I'm not sure this is a fundamental technical incompatibility or something that is merely sensitive to the kernel configuration options used during their builds.
It is a significant practical issue for folks on old firmware that might prevent them from using a "debloated" newer stock release, however. If folks who are willing to build kernels for us (I am trying OB6 and NK1 kernel builds with zero success at the moment) figure out what the technical issues are we might makes some progress here; if not the practical issues will remain.
But who is to say that something like this might or might not happen in the future to folks currently unlocked on "4.4" bootloaders? Keep those Odin stock bundles archived until you get rid of the phone!
* I realize there are some exceptions.
Yea... For now... That's my plan... Was just wondering if someone knew for sure one way or the other.
Sent from my SM-N900V using Tapatalk