GROOVYJOSHCLARK
Senior Member
Or you could forget those web Facebook "skins" and just use an older Facebook version which works fine.
sent from my droid
Or you could forget those web Facebook "skins" and just use an older Facebook version which works fine.
Yeah think that the main focus right now is BT and Data for some users - Useful "solutions" for FB have been posted many times - ie: using an older version of FB - Using Folio or Metal as a more battery friendly and lighter alternative to FB.
Sent From My SM-N910W8 Running CMRemix 6.01
Yeah @ZION959 knows about it - I'm sure that it'll be fixed in the next build
Did you also post in the dev forums like I suggested?Zion, could you assist me with a kernel related question? Or anyone for that matter?
It's a good ROM, it has bugs like they all do but you can use it as a daily runner once you have the bugs worked out the way you like them. I suggest you try them all until you find one that works best for your taste. I go back and forth between CMREMIX, RR, and emotion.
It's a good ROM, it has bugs like they all do but you can use it as a daily runner once you have the bugs worked out the way you like them. I suggest you try them all until you find one that works best for your taste. I go back and forth between CMREMIX, RR, and emotion.
The only bug that drives me nuts with CMremix is the Facebook app. I use an older version but the play store always nags me to update. That annoys me but other than that it works fine for everything I need.
sent from my droid
Did you also post in the dev forums like I suggested?
I didn't see anything here:
http://forum.xda-developers.com/not...developer-discussion-developers-only-redirect
sent from my droid
I do, even though it's not as active, it still is a good idea. You may not get the help you need but you may get exactly the help you need. You won't know if you don't ask and there's no harm in asking.The last post in there was from awhile back, do you think it's worth even asking in there? I don't see it getting much visibility!
Thanks. It workedPC and PD DO NOT WORK, you need to reflash back to one of the OG-OK loaders
hey buddy my wifi will not work either. im not sure how to find the bootloader but the baseband version is N910PVPU4DPE1What baseband and bootloader are you on? Whats your method of flashing?
---------- Post added at 11:02 AM ---------- Previous post was at 11:02 AM ----------
Same goes for you, what baseband and bootloader are you on?
Revert to COG5 and your wifi will work.can someone pls help me get wifi working on this rom?>? i think i need a different baseband version or something. Any info would be appreciated greatly..
---------- Post added at 08:32 PM ---------- Previous post was at 08:23 PM ----------
hey buddy my wifi will not work either. im not sure how to find the bootloader but the baseband version is N910PVPU4DPE1
hey buddy youre all over the place ! what do you mean revert to COG5? is this a certain stock os? NVM i know what it is, will this work with ok1?
hey buddy youre all over the place ! what do you mean revert to COG5? is this a certain stock os? NVM i know what it is, will this work with ok1?
Actually no, I'm not at all, "all over the place", and far from it"!" I help newb's like yourself and answer questions like yours all the time with multiple responses to multiple questions. I respond to questions as they come in.
I've remained constant through every advice comment I've made, COG5 is the only baseband I recommend. If you don't understand this then ask for specific help but explain where you're held up and need help with otherwise the answers are in the forums. I have personally written multiple comments on how to do exactly what you're asking for in multiple AOSP boards. The answers are there, you just need to seek them out.
sent from my droid
yes you have written many comments, which are pretty simple. i mean with twrp its easy as pie but im having issues when following the directions,which i why im trying to find where i went wrong. Both roms you have assisted me with have not worked. One had a camera that would force close and musicFX would stop when playing sound and the phone wouldnt record videos. The other flashed but wouldnt function at ALL, 10 second delay in touch, homescreen wouldnt even load. ive done everything as you and others suggested in forums to no avail. Maybe i have the wrong version of TWRP or im on the wrong baseband when flashing these two MM roms? Which Baseband should i be on and what version should i use so that its stable on my device FOR this rom ?? i dont care if its a old version as long as it works
nice dude. i didnt know phone needs wiped before flashing with odin. AND do i have to "activate" the phone? it will not be used on any network but id like to unlock it in the future. the twrp keeps asking if it iw ant it to install root even when i have root. Is this normal? When removing the .md5 extension of the extracted file it makes a winrar file. I thought it had to remain an md5 to flash in odin?Two things, I dont write or maintain the ROM's, I only assist with end-user issues like you are having. Second thing is, I have VERY clearly stated (many times) COG5 is what you should be using, this is the preferred version for baseband/kernel (until you install AOSP then that kernel used) for what is available with AOSP out there right now. I will write the steps out again to better help you.
Follow these steps and you will have a fully operational AOSP with everything working (make sure you have backed up all of your texts and anything on the internal SD BEFORE going forward):
PREP before we begin:
Download N910PVPU4COG5.tar (google search it and it will be found in XDA fairly quickly), extract the file and rename to .TAR (only .TAR, remove the .MD5 extension)
Steps:
REBOOT into recovery (assuming you have TWRP already installed, if not install the latest TWRP BEFORE going further)
While in TWRP (and ONLY AFTER you have backed up anything from you want to keep from the INTERNAL SD card), wipe the following partitions 3X's:
/dalvick
/data
/system
/cache
/INTERNAL STORAGE
-------> DO NOT FORMAT EXTERNAL SD CARD <-------
Then format internal SD (internal memory), TYPE YES on the confirmation
Do this 3 times, and perform a factory reset in between (at least 3 resets). The order isn't as critical, but I always do it this way - factory reset, wipe partitions, factory reset, wipe partitions, factory reset, format internal storage. Once those steps are performed, reboot into download mode, connect phone (while in download mode) to the PC, then fire up Odin (always have the phone in download mode before opening Odin or it may not be found until you close and reopen Odin), while in Odin, select the AP tab, browse to the .TAR (COG5 you downloaded prior), push the .TAR to the phone through the AP tab. Once this is done and the phone is reset, go through a quick setup and configure the phone (only the bare minimum and basic to get you through to the launcher). Once this is done, go to settings, update, and activate the phone (this is a process called Chameleon - SELF SERVICE), update PRL, and update profile, then activate one more time and shut down.
At this point you have a fully restored N4 on Sprint network which is activated with the updated PRL information. Shutdown back into download mode, install the latest TWRP.TAR. Reboot into recovery, wipe the partitions again 3X's:
/dalvick
/data
/system
/cache
/INTERNAL STORAGE
Then format internal SD
Do this 3 times, and perform a factory reset in between (at least 3 resets).
-------> DO NOT FORMAT EXTERNAL SD CARD <-------
Reboot into recovery, and install the AOSP of your choice, I prefer Emotion Version 9 (the latest available) as this works with Bluetooth AND GPS and has ZERO issues whatsoever, or choose the latest CMRemix, or CM13, whatever you wish to use, I go back and forth between them all but mainly use EM ver9 as it is stable and fast. Once the ROM is installed, install GAPPs of your choice, I prefer the one in the Emotion OP recommendations latest version. Reboot into AOSP and configure away, you are done and have a perfectly running, activated on Spring, AOSP with the bare minimum needed to run the phone!
Enjoy
[SIZE="6"][COLOR="Purple"][FONT="Arial Narrow"][INDENT]
[CENTER]
[SIZE="4"][COLOR="Blue"]* Clang Qcom Optimization By mustermaxmueller[/COLOR][/SIZE]
[SIZE="4"][URL="https://github.com/mustermaxmueller/android_build/commit/26eacea96dfd7c266cd15878218f4d80b1328ac7"]Github Source[/URL][/SIZE]
[SIZE="4"][URL="http://forum.xda-developers.com/android/software-hacking/wip-compile-android-5-0-2-qualcomm-llvm-t3035162"]XDA Thread[/URL][/SIZE]
[COLOR="Blue"][SIZE="4"]*SaberMod Optimization By Paul Beeler[/SIZE][/COLOR]
[SIZE="4"][URL="https://gitlab.com/groups/SaberMod"]Gitlab Source[/URL][/SIZE]
[SIZE="4"][URL="http://forum.xda-developers.com/android/software-hacking/toolchains-sabermod-arm-arm64-t3064459"]XDA Thead[/URL][/SIZE]
[/CENTER][/INDENT]
[/FONT][/COLOR][/SIZE]
[SIZE="6"][COLOR="Purple"][FONT="Arial Narrow"][INDENT]
[CENTER]
[/CENTER][/INDENT]
[/FONT][/COLOR][/SIZE]
Hi thanks for this log. Really completed one .Uploading logcat zipped because it exceeds the 500kb limit on gist.github and pastebin, as well as the attachment limit on xda. Hopefully I logged it correctly. This was from v7.8 dirty flashed over 6.7.