Discussion in 'Android Devices' started by struckn, Nov 6, 2013.
Thanks... Hoping to hear that.
Thanks; learn something new every day
I tried to install Carbon today with no success. Used Philz to clean and install ROM and procedure was aborted, with a error number (7).
Not sure what went wrong. Used the d2spr ROM?
Update...I noticed that I tried the d2spr 11/1/13 Rom. Should I have used the 11/17/13 instead?
Error 7 usually means that you didn't modify or remove the asserts.
Thanks for the prompt response. Could you elaborate for a newbie?
OP of this thread, it is the main reason this thread exists my friend!
Found that section and made the changes. Hope to try the install later this evening.
Thanks again for your help (and patience ).
Not a problem my friend! I think you will really like Carbon, I personally can't wait for their KitKat releases, especially since it's been more than a month since they teased them. Hopefully soon, I expect them to be amazing since it seems like the Carbon team wants to put out a polished product instead of a traditionally buggy set of nightlies.
Rule of thumb: If you want to flash ANY custom ROM based on AOSP, then you will need to modify or delete the asserts (I find deleting easier), if you want to use anything TW based, i.e. JD's stock/Knox-free MK5, Wicked Sensations, or M.O.A.R., then you can flash "as is."
Thanks for this terrific guide! I've managed to get CM 10.2 up and running using MopedRyder's "#2" APN fix. MMS send and receive are both working for me on LTE in Google Hangouts, but not in the stock app.
But there is (as always) a new wrinkle: I've found that having Google Hangout's SMS integration on messes with my voicemail; whenever I get one, I receive a couple of strange text messages through Hangouts rather than a notification in the status bar. From the googling I've done, this appears to be a problem with Hangouts, not with the custom ROM. I looked into using Google Voice for my voicemail only to discover that VM doesn't seem to allow for call forwarding, which Voice requires for voicemail.
Is there a good solution for this? My apologies if this isn't the appropriate thread for this discussion, but I couldn't find another one addressing this particular problem. I don't really get too many voicemails so it's not really a big deal, but it'd be nice to have a more elegant solution.
Is "9016" the number the texts are coming from? This has actually happened to me on all Sprint ROM's, even before I started using Hangouts. You can restore the Visual Voicemail app (app only, no data) and then blacklist the 9016 number. Visual Voicemail will work by default on anything TouchWiz, this is more of an AOSP problem.
By Tip for editing asserts using only your phone:
ES File Explorer has "Extract to" and "Compress" functions. Select the file/zip by long pressing it then tap the "more" menu (bottom right) then "extract to".. . Default location works fine.
I stick with the ES mini apps to navigate to and edit. No need to change file names or extensions. Once you have the file open you have to choose "edit" from the three dot menu. When your done use your back key and you'll get a prompt to "save".
You will now have a folder with the same name as the ORIGINAL zip. It's important to remember that the top level folder is actually new.
After editing and saving file(s), remember to select all of the files WITHIN that new folder then "Compress". If you compress/zip the top level folder the new zip will contain an additional folder that contains the files/folders that should be at top level.
This is all very simple. If you're confused then I just need to explain it better. Remember also that the extracted files are still there... Ready to make more changes, compress, etc.
FWIW, extract and compress were actually faster on my phone than my laptop...
Edit: I forgot to mention that when you compress those files "within" the folder created by extracting, it names the zip using the folder's name by default , leaving you with a new zip file inside that folder. Good and bad... Bad first. In recovery you have to look carefully as zips look just like folders (look for the slash)
The good... You have exactly the same filename as the original except in a sub folder so no need to rename... If it doesn't work, the extracted files are still there so simply delete the new zip and start over from there.
They are indeed coming from 9016! I placed that number on CyanogenMod's blacklist and restored the stock VM voicemail app, but it didn't seem to make a difference -- Hangouts is still receiving messages from that number whenever I get a voicemail. Was it the CM blacklist you were referring to, or is there another blacklist?
Also, is the VM voicemail app the same thing as Visual Voicemail? (I'm not sure if it's the name of an actual app or if it's a description of an app category, if that makes sense.) I do see an app called Visual Voicemail Plus on the App Store, but I'm not sure if that's what you meant. Sorry, just wanted to clarify.
I blacklisted with the dialer, but receive very few phone calls, let alone voice mails, so can't remember if that kept Hangouts from receiving the text or not from that number. And yes, I meant the Virgin Mobile app that comes with stock based ROM's, I would assume any third party app from Play Store wouldn't work because VM doesn't allow voicemail forwarding, which causes issues for Google Voice users as well.
I did a bit more digging around, and I think I found the source of the problem. Apparently on Sprint networks (like VM), the visual voicemail app requires the stock messaging app in order to function properly. The network notifies your phone that you have a voicemail by sending a text to your phone, which the stock messaging app knows to ignore and "pass along" to the visual voicemail app. But Hangouts doesn't have that functionality, so it receives those voicemail notification texts as regular texts and displays them to you.
There doesn't seem to be a way to fix this, at least in my case (different users reported different results in their attempts to solve the 9016 issue). I even texted Virgin Mobile at 9999 to "block 9016", and got confirmation that the number was blocked in return, but it made no difference -- the 9016 texts still show up.
So I think what I'll do is lean into the problem. I'll rename 9016 as Voicemail to get a sort of kludge-alert. Considering how few voicemails I receive, that should be fine -- and I don't want to go back to the now-clumsy-feeling stock TouchWiz ROM just for that. I'll delete Visual Voicemail as well, since it doesn't function properly for me.
Sorry for taking this topic so far afield. Thanks again for your help.
Hello and happy new year friends, I can confirm that a build of omni rom by androidsftw at xda works. It has multi window and it works pretty well, sent and recieved mms just fine with mopeds fix. [ROM][UNOFFICIAL][KITKAT][AOSP][OmniROM][DEC 31, 2013][Cherry-Picked Multi-Window] - xda-developers
Nothing to apologize for, the discussion was relevant and a learning experience for me at least!
Thanks for the info! It appeared that I was flashing MK3 vs MK5...once I flashed MK_Stock_Rooted & SPH_L710 MK_5_ Modem; everything worked as it should (well almost) Ill explain in a bit.
I also used.."Philz Touch 6.00.8-d2spr" in order to flash my files..I also found that "cm_11-20131231-nightly" also works! I prefer Philz Touch
Now...getting back to my problem with install. I installed Hellfire Kitkat rom ad all seemd to go well! I was able to see the full install go through and boot up ok! However; I was not able to get my mobile network to be recognized. It did connect through my wireless option but could not locate any viable network. So my phone dialer would never work? I tried searching for fixes for this but came up short? Anyone out there that knows of a fix for the network?
Thanks for all the help so far..at least it got me to boot up Kitkat Hellfire!
Me too (reply to struckn) . @jeebus The theory you just gave is right in line with the one I have been forming myself. That info is especially useful because you did some research then shared your thoughts... exactly what forums are for. Thanks
So just flashed the version of CyanFox Official 4.4.2 that was released today (1/2/2014) and holy cow is it fast! As I mentioned in the section of this tutorial dedicated to custom ROM's, I wasn't that impressed with their 4.3.x JellyBean builds, but the builds for 4.4.x KitKat have been very nice, making this ROM part of the small list of KitKat builds (CM11 Official, and soon to be CARBON!!) that I am willing to run on my phone. Looks like this one will be the new daily for a few days until either CM11 has a significant update or Carbon finally releases. Plus, working HALO for those of you that desire that feature. Going to give that a try for a while as well, was always impressed by the concept but never understood why I personally would need it. Who knows, maybe it will be like Hangouts and grow on me after a bit!
What are some of the things that CyanFox has that Cyanogen doesn't? I'd be willing to flash if its that much better than Cyanogen. Even though I wont think twice about flashing Carbon over CyanFox once they come out with their 4.4.x build! :thumbup:
There is some extra customization built into the UI settings, a dark UI toggle (if you aren't using a dark theme in the first place, which I almost always do, but still nice to have), and HALO will definitely be a plus for some users. Mainly, it just seemed blazing fast even before I changed kernels and applied the Dalvik patch. Been using CM11 so heavily the past month that I don't think it was some kind of placebo either; CM11 has been beyond awesome for me, but once I got CyanFox up and running it was kind of a "Whoa!" moment in terms of performance. As always, the currently popular YMMV will probably apply, but I am currently giving this two thumbs up Roeper and Ebert style! Huge ditto on the Carbon though, looks like some users on other carriers/phones are porting unofficial builds, so hopefully the official ones are real close!
On a side note, what dark theme are you using? The CM11 Betterkat theme?
Yes, and loving it. Only problem is sometimes a dialog box shows up dark with dark text, therefore unreadable, but overall very nice looking theme.
I'm sold already. I've downloaded the rom + gapps linked in the xda thread... Any advice on choice of gapps to start with?
I like the Paranoid Android versions, they have several size options. Been using the Full Modular, I linked this in my CM11 thread but there is a newer version (12/30) available from the PA page on XDA linked in the second post of this thread. I always debloat first to remove what I don't ever use.