THE PROJECT IS ABANDONED
This ROM is for the AT&T SGH-I437 ONLY! It is NOT for the GT-I8730! Just because Samsung named them both "Express" does not mean they have identicle internal hardware!
My work is the continuation of jt1134’s. It’s basically his work. The things I had to fix (I still have to upload them :/ ) are very irrelevant compared to his work, for which I thank him.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads and installation
You can find the download links and the installation instructions here. (last update: April 24, 2015)
A test build of CyanogenMod 12.1 is up! Make sure you back-up and carefully read the post. You can find the downloads here. (updated July 30 2015).
Reporting Bugs
You are allowed to report bugs only in this thread and in my blog post as comments. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY OR IN MY BLOG POST.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Recovery used to flash the ROM:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
FAQ
Can I request a feature?
If it is a feature in general CyanogenMod, please post the request at the CyanogenMod bug tracker.
http://jira.cyanogenmod.org
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 12.0 for Samsung ExpressATT (SGH-I437), ROM for the Android General
Contributors
davideddu96, jt1134
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2015-04-02
Last Updated 2018-02-04
davideddu96 said:
Downloads and installation
You can find the download links and the installation instructions here.
Click to expand...
Click to collapse
Thank's for the new thread. But we can't download the new build causse the we have the message "http://goo.gl/HCNeuX – this goo.gl shortlink has been disabled"
The 03.12 build has better wifi than all febrary and december builds but in this build bluetooth stop working for me (it was working on all precedents cm12 builds made available here).
I can't comment on your blog, it's keep telling me that my comment is a spam.
Can't download as link disabled.
Changelog would be nice if u can provide.
Thanks @davideddu96
Rodney SANK said:
Thank's for the new thread. But we can't download the new build causse the we have the message "http://goo.gl/HCNeuX – this goo.gl shortlink has been disabled"
The 03.12 build has better wifi than all febrary and december builds but in this build bluetooth stop working for me (it was working on all precedents cm12 builds made available here).
I can't comment on your blog, it's keep telling me that my comment is a spam.
Click to expand...
Click to collapse
pandyag said:
Can't download as link disabled.
Changelog would be nice if u can provide.
Click to expand...
Click to collapse
Sorry guys, I didn't know about that policy. I had to change the link shortener. I decided to use adfly, which has less stupid policies and supports my work.
I hope you're OK with that.
OK just install 5.0 now it dose not have any root access before I reboot recover it ask to fix root I hit yes and still no root even type it terminal eliminator su
Go to developer option in setting and select root..
cwbcwb said:
OK just install 5.0 now it dose not have any root access before I reboot recover it ask to fix root I hit yes and still no root even type it terminal eliminator su
Click to expand...
Click to collapse
Do not use the root fixer with cm. Reinstall the ROM and enable root from development settings like pandyag said. Root settings are now in appops (settings,privacy).
@davideddu96 the 5.0 runs smooth love it keep up the work I had it install about a day and no issues
I have a question about Heimdall. I've always used Odin before, but figured that I'd just go ahead and try to install using your exact instructions. Your TWRP comes as an .img file but Heimdall seems to want a tar.gz file. I gave a quick internet search and it seems like a pit file is needed to flash an .img?
I'm probably missing something, and I doubt that I'm the only one so some instructions on exactly how to flash your recovery using Heimdall might be useful not just to me. I'd hate to brick my phone messing around with pit files. I never needed one with Odin.
I have an older version of Clockwork Mod installed and I"m just going to go ahead and try to install using that. It should be ok, right?
invert_nexus said:
I have a question about Heimdall. I've always used Odin before, but figured that I'd just go ahead and try to install using your exact instructions. Your TWRP comes as an .img file but Heimdall seems to want a tar.gz file. I gave a quick internet search and it seems like a pit file is needed to flash an .img?
I'm probably missing something, and I doubt that I'm the only one so some instructions on exactly how to flash your recovery using Heimdall might be useful not just to me. I'd hate to brick my phone messing around with pit files. I never needed one with Odin.
I have an older version of Clockwork Mod installed and I"m just going to go ahead and try to install using that. It should be ok, right?
Click to expand...
Click to collapse
Ok, here's how to do it with Heimdall (aren't there guides online?)
You boot your phone in download mode and connect it to the computer
Open heimdall, go to the utilities tab and download the pit to your computer (you only need to do it once, the next times you can use the same pit). Hit "save as", choose a path and a file name and then click "Download"
You may have to reboot your phone the hard way (take the battery out, put it back in) into download mode again after downloading PIT. My phone can only do one operation at a time for some reason
Now go to Flash, open the PIT you downloaded, press Add under partitions, select "RECOVERY" in the "Partition Name" menu and open the recovery image you got from my blog.
Hit flash!
If you have stock, make sure you don't let the phone reboot to Android or it will wipe your recovery! Either start holding Volume up and home while it's flashing, so that it will boot straight to recovery or take the battery out as soon as it's done.
EDIT: by the way yes, CWM should work, if it's not too old. TWRP is what I use and that's mainly why I advise you to use it: if you have an issue with it, chances are that I have it too, and you're going to save me from flashing your recovery to troubleshoot it.
A new build is online! The download link has already been updated: http://davideddu.org/blog/posts/cyanogenmod-12-for-expressatt/
From now on the first post title will have the last build release date at the beginning. This way, when you get a notification from XDA, you'll know at a glance if you have the latest version
Also, to save you from looking up the download links on Google, I've added a shortcut to the downloads in my homepage at http://davideddu.org . It's in the middle of the page, at the end of the first white box
I also posted a more complete, step-by-step guide on how to flash recoveries with Heimdall using both the GUI and the command line (which I definitely prefer).
http://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/
davideddu96 said:
Ok, here's how to do it with Heimdall (aren't there guides online?)
You boot your phone in download mode and connect it to the computer
Open heimdall, go to the utilities tab and download the pit to your computer (you only need to do it once, the next times you can use the same pit). Hit "save as", choose a path and a file name and then click "Download"
You may have to reboot your phone the hard way (take the battery out, put it back in) into download mode again after downloading PIT. My phone can only do one operation at a time for some reason
Now go to Flash, open the PIT you downloaded, press Add under partitions, select "RECOVERY" in the "Partition Name" menu and open the recovery image you got from my blog.
Hit flash!
If you have stock, make sure you don't let the phone reboot to Android or it will wipe your recovery! Either start holding Volume up and home while it's flashing, so that it will boot straight to recovery or take the battery out as soon as it's done.
EDIT: by the way yes, CWM should work, if it's not too old. TWRP is what I use and that's mainly why I advise you to use it: if you have an issue with it, chances are that I have it too, and you're going to save me from flashing your recovery to troubleshoot it.
Click to expand...
Click to collapse
Thanks.
It was the pit file that bothered me. I puzzled my way through the controls and gathered that that was how to do it, but I wanted confirmation who'd done exactly that thing to this particular phone because... well... you know, sometimes things don't always work the same. Plus, I figured that I'd probably not be the only one with some questions in this regard, so I'd be the fall guy.
Went ahead and installed with the older CWM recovery and all is working fine as of now. I noticed some passing comment in the other thread that Google Maps didn't work, but it works fine with me.
---------- Post added at 02:52 PM ---------- Previous post was at 02:45 PM ----------
davideddu96 said:
A new build is online! The download link has already been updated: http://davideddu.org/blog/posts/cyanogenmod-12-for-expressatt/
From now on the first post title will have the last build release date at the beginning. This way, when you get a notification from XDA, you'll know at a glance if you have the latest version
Also, to save you from looking up the download links on Google, I've added a shortcut to the downloads in my homepage at http://davideddu.org . It's in the middle of the page, at the end of the first white box
Click to expand...
Click to collapse
I'm having issues downloading the new build. It downloads a 0 kb file.
Also, does this have the new kernel you mentioned?
Use flashify to do recovery u can get it in market
Sorry for the download issue, the ROM has been uploaded but it has not been copied to the mirror.
I'm working on it.
EDIT: I just contacted the technical support and I'm waiting for an answer. The previous build is still available, however; you can get it from here.
Yes, it's including the most recent kernel.
I don't have issues with Google Maps either.
invert_nexus said:
I'm having issues downloading the new build. It downloads a 0 kb file.
Also, does this have the new kernel you mentioned?
Click to expand...
Click to collapse
I got back from the technical support and I've been told it's all regular. As it's a big file, its upload to the mirrors is being delayed. Please check again in a few hours. I'm sorry for the issue, I wasn't aware of this policy.
EDIT: I just checked again and the file is in the process of being uploaded. Just wait for ~30 minutes and you should be able to get it.
EDIT2: The file has been uploaded. It is now downloadable.
As I said in the previous answer, yes it does have the new kernel, which means I didn't have to patch the installer. You can turn back on signature checking if you turned it off.
Thanks for the ROM
Hi David, thanks for the love you are giving for this device, anyways I can't download the rom, maybe can you upload it anywhere else? The webpage is not opening so maybe try dev-host as its the best.
Samkitpalecha said:
Hi David, thanks for the love you are giving for this device, anyways I can't download the rom, maybe can you upload it anywhere else? The webpage is not opening so maybe try dev-host as its the best.
Click to expand...
Click to collapse
Try to turn off AdBlock; that's probably why you can't get to the downloads. I decided to route them through AdFly because it takes a lot of electricity to build the ROMs (it takes around 6 hours during which I'm not home and the computer is running, hotter than an oven with the fans that sound like a vacuum cleaner). If it still doesn't work for you, you can find a direct link right below the standard links, after the bulleted list. You don't have to, but I would appreciate it if you would add an exception to your ad blocker for "davideddu.org" and "go.davideddu.org"
I tested the downloads yesterday and they are working.
Let me know if you still have issues with the downloads, so that I can contact my hosting provider!
EDIT: I just tested the download links and they work fine. Let me know if you still have issues. Have a nice day
davideddu96 said:
Try to turn off AdBlock; that's probably why you can't get to the downloads. I decided to route them through AdFly because it takes a lot of electricity to build the ROMs (it takes around 6 hours during which I'm not home and the computer is running, hotter than an oven with the fans that sound like a vacuum cleaner). If it still doesn't work for you, you can find a direct link right below the standard links, after the bulleted list. You don't have to, but I would appreciate it if you would add an exception to your ad blocker for "davideddu.org" and "go.davideddu.org"
I tested the downloads yesterday and they are working.
Let me know if you still have issues with the downloads, so that I can contact my hosting provider!
Click to expand...
Click to collapse
Adfly doesn't works in India.
Sent from my SM-G900H using XDA Free mobile app
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the Samsung Mesmerize, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0-Mesmerize
Download: link
Mirror: link
MD5sum: 36356d5b03d3713e55489cd0d263ef26
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
I flashed to the version listed above and had two major issues that required me to switch back to the stock USCC 2.3.4.
Could not send or receive text messages
GPS would not acquire signal
I really (REALLY) want to go back to CyanogenMod 7 - I was loving it! If I did not rely on my phone so much, I would have left it on until someone posted a fix.
Is this something that I am doing wrong or is it a bug?
Flash a fascinate modem.
Sent from my MIUI SCH-i500
sageDieu said:
Flash a fascinate modem.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Is there a guide on how to do that? Also, will that fix both the GPS and texting issues or just the texting issues?
Honestly flashing the EE19 modem should fix any SMS and MMS issues you're having. That's what has fixed it for others as well as myself.
This build wasn't buildt for the eh09 modem. That is supposed to be added shortley.
scarmon25 said:
Honestly flashing the EE19 modem should fix any SMS and MMS issues you're having. That's what has fixed it for others as well as myself.
This build wasn't buildt for the eh09 modem. That is supposed to be added shortley.
Click to expand...
Click to collapse
So is there a modem I can flash to that will get it working or do I have to wait? If there is a fix - can you provide me with a link to it please?
Thanks so much.
7earitup said:
So is there a modem I can flash to that will get it working or do I have to wait? If there is a fix - can you provide me with a link to it please?
Thanks so much.
Click to expand...
Click to collapse
Here is the EE19 modem. Unzip and flash the file in the PDA slot in Odin
http://db.tt/1YqerUvT
This is just the modem. It wont mess with any data on the phone like apps or things like that.
scarmon25 said:
Here is the EE19 modem. Unzip and flash the file in the PDA slot in Odin
This is just the modem. It wont mess with any data on the phone like apps or things like that.
Click to expand...
Click to collapse
Thanks. I am going to reflash it with C7 now.
---------- Post added at 06:39 PM ---------- Previous post was at 05:53 PM ----------
Whelp - that fixed the texting - thanks!
Now I cannot get the Google Apps pack to install. It succeeds when I install it through the Clockworkmod but none of the apps show up once the system loads.
I have tried reflashing and everything. It just makes no sense.
7earitup said:
Thanks. I am going to reflash it with C7 now.
---------- Post added at 06:39 PM ---------- Previous post was at 05:53 PM ----------
Whelp - that fixed the texting - thanks!
Now I cannot get the Google Apps pack to install. It succeeds when I install it through the Clockworkmod but none of the apps show up once the system loads.
I have tried reflashing and everything. It just makes no sense.
Click to expand...
Click to collapse
Try this gapps package
http://db.tt/mSU9a0MP
scarmon25 said:
Try this gapps package
Click to expand...
Click to collapse
Even though I had the latest package from the CyanogenMod web site, yours is the one that worked.
Thanks again! I think I am all set now.
I am back again - sorry!
I am having some issues with Wi-Fi. Every now and then, I will just stop receiving access to the Internet. The phone stays connected to my router, I just stop receiving any data. If I turn it off for a couple of minutes and then turn it back on, it usually comes back, but this is a hassle. It never happened on the stock ROM so it has to be a driver or something.
Any ideas?
Thanks again.
7earitup said:
I am back again - sorry!
I am having some issues with Wi-Fi. Every now and then, I will just stop receiving access to the Internet. The phone stays connected to my router, I just stop receiving any data. If I turn it off for a couple of minutes and then turn it back on, it usually comes back, but this is a hassle. It never happened on the stock ROM so it has to be a driver or something.
Any ideas?
Thanks again.
Click to expand...
Click to collapse
Go into settings - cm settings - interface- notification power widget- widget button and put a check in mobile data. That will put the mobile data toggle in the notification widget. When you have wifi on make sure to turn off mobile data. Then when you turn wifi off turn it back on. Wait a few seconds in between turning one off and the other on. Also while you are in interface there is alot of things you can adjust in there to make it look the way you want so check it out. If that doesn't work then there might be something else at play but that is normally the cause of it.
scarmon25 said:
Go into settings - cm settings - interface- notification power widget- widget button and put a check in mobile data. That will put the mobile data toggle in the notification widget. When you have wifi on make sure to turn off mobile data. Then when you turn wifi off turn it back on. Wait a few seconds in between turning one off and the other on. Also while you are in interface there is a lot of things you can adjust in there to make it look the way you want so check it out. If that doesn't work then there might be something else at play but that is normally the cause of it.
Click to expand...
Click to collapse
I will give that a shot. It is handy to have a way to turn off mobile data anyway.
Another small issue I have come across - maybe you have seen it as well. Whenever I answer calls, the in-call volume is at max and it literally blows me away when someone says something. I have to adjust it with the rocker to make it go down every time, even though I have the in-call volume adjusted lower in the settings.
Any tips for that one?
That's a known issue. I say it wilk be fixed at some point. The only thing I can tell ya is set it to where you want it and then when you answerbor make a call. Hit the volume rocker down once then back up once and it will put it back to where it was. Hopefully once Nightlies start rolling out we will see fixes for that.
scarmon25 said:
That's a known issue. I say it wilk be fixed at some point. The only thing I can tell ya is set it to where you want it and then when you answerbor make a call. Hit the volume rocker down once then back up once and it will put it back to where it was. Hopefully once Nightlies start rolling out we will see fixes for that.
Click to expand...
Click to collapse
Good to know I am not the only one having the issue then. Lol
Do you have any reception issues with Wi-Fi by chance? It seems like I lost a lot of range with this ROM.
I really can't say. I am never more than aabout ten feet away from where my router is and when I am I'm using mobile data. But with that said I haven't seen any signal loss.
Any idea why my GPS no longer works? I cannot receive a signal using Runkeeper. Kind of a bummer.
Sent from my SCH-I500 using XDA App
7earitup said:
Any idea why my GPS no longer works? I cannot receive a signal using Runkeeper. Kind of a bummer.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Not sure. I am actually getting a lock rather quickley. You nay try this. Navigate to System/etc and delete GPS.conf. tthen unzip the linked file and place both files back in system/etc and set permissions to rs,r,r in both files and reboot. You will need root explorer to do this.
http://db.tt/rtSBRVQD
scarmon25 said:
Not sure. I am actually getting a lock rather quickley. You nay try this. Navigate to System/etc and delete GPS.conf. tthen unzip the linked file and place both files back in system/etc and set permissions to rs,r,r in both files and reboot. You will need root explorer to do this.
http://db.tt/rtSBRVQD
Click to expand...
Click to collapse
Any free alternatives to Root Explorer?
Sent from my SCH-I500 using XDA App
There's one called file expert I believe but i don't know if it will allow you to set permissions. You can try it though. Can't hurt. Just check and see if you can before deleting anything.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the HTC Aria, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0-Liberty
Download: link
Mirror: link
MD5sum: 006197debecd916dc8ce3feadea1e74a
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
hey, just want to say… GREAT JOB GUYS. YES, THANK YOU SO MUCH FOR THIS AWESOME ROM!!!
Looking good so far. Will post if I run into any issues. Glad I can finally have a stable build and not need to flash for a little while!
Thanks for all the effort.
Having issues with data. It worked fine for a while on the first boot but once I rebooted the phone, I can't get the phone to connect on data. Anyone having this issue, and most importantly how do I resolve it?
Other than that, amazing. Thanks for this great rom.
Edit: I looked into the access point name under the mobile network section and noticed a bunch of info was wrong. Notably the password was missing. I added the password and rebooted the phone and now everything is working fine. FYI the password is CINGULAR1.
android market wont let me download aanything!!! Please help!
_jfo_ said:
Having issues with data. It worked fine for a while on the first boot but once I rebooted the phone, I can't get the phone to connect on data. Anyone having this issue, and most importantly how do I resolve it?
Other than that, amazing. Thanks for this great rom.
Click to expand...
Click to collapse
No issues here.
supetawesomedude said:
android market wont let me download aanything!!! Please help!
Click to expand...
Click to collapse
Again, not any issues here.
supetawesomedude said:
android market wont let me download aanything!!! Please help!
Click to expand...
Click to collapse
clear data and reboot?
Installed over an old nightly fine, no problems whatsoever after a full day of use.
Nice work guys.
brswattt said:
clear data and reboot?
Click to expand...
Click to collapse
What the heck? It's workking first fine now!
thnxz. looking good
Hmm...i wanted to try using this "juwe" script but it won't boot...i'm assuming some sort of conflict with darktremor. I also wanted to go to S2E but the last time i tried to go from DT to S2E, everything went haywire and i had to restore an old back up because i rookishly forgot to make one before i started fuxing with S2E...hmph guess i'm stuck with 8-9-1 & DT...life goes on though...
zervic said:
Hmm...i wanted to try using this "juwe" script but it won't boot...i'm assuming some sort of conflict with darktremor. I also wanted to go to S2E but the last time i tried to go from DT to S2E, everything went haywire and i had to restore an old back up because i rookishly forgot to make one before i started fuxing with S2E...hmph guess i'm stuck with 8-9-1 & DT...life goes on though...
Click to expand...
Click to collapse
Your best bet would be to do a Titanium Backup of all user apps, install the ROM fresh, then install S2E, reboot, then restore the backups of user apps and your S2E transition is complete.
Sent from my Liberty using XDA Premium App
^^^ titanium is godly! S2E is worth it, imo. do a fix permission in ROM manager afterwards and a couple re-boots and bam! Butter smoothness
Anybody with the vibration mode not working when receiving calls? I turned vibrate on pretty much everywhere and yet when receiving call, the phone does not vibrate. However, it does vibrate when I receive a text message. Help!
Sent from my Liberty using XDA App
EDIT: I just toggled from the "Default" profile to "Work" and then back to "Default" and now it works. Strange...
Very legit! My girl loves Cynogen!
Almost did a battery pull on first boot. Coming from an older Nightly. Right as I was pulling off the backplate though, the screen went dim and the keys lit up, and everything loaded. So be patient guys on first boot.
My you guys have been busy. Very polished, so many new features.
Just came back to CM7 after about 3 mo. on the Sense ROM. I use GPS constantly, so I have been testing it extensively today. Happy to say Maps, Nav, and this geotagging app I have all work really well.
Zero problems so far, congrats!
Ok guys (and girls), here's a problem I've been dealing with for over a week now. Any help would be appreciated. I have been keeping up with the nightly builds and on nightly 213 and forward (including this stable release), I have found that my phone will stop receiving data after around 8 hours after a reboot. The only way for the data to work again is to reboot. This occurs on both mobile data (3G) and wifi connections. I have rolled back to nightly 208 and the problem doesn't occur. I have uninstalled all new apps since this started occurring, so I know it is not an application problem. I installed 7.1.0 stable with a full wipe, so that's not the problem. I don't think it is similar to the problem reported in post #4 of this thread because my Access Point information under Mobile network settings are the same in my working N208 as they are in the non-working 7.1.0. Also, neither version had a password, so following the directions in post #4 I put in the password CINGUALR1 on the 7.1.0 stable version, and the problem still persisted.
I am running DC's 8.9.1 and Juwe's RAM script, though I have been told neither of those could be the culprit.
Any suggestions, please?
something with your setup - have been running since last night and have not rebooted since and have had no connectivity issues at all.
What's the earliest nightly build that has the problem for you?
Did you format your system partition before the clean install?
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kitkat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 11.0 your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Experience issues?
* Nightlies: bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
* M-series: file a bug in Jira.
Download Links
CyanogenMod: download.cyanogenmod.org
Google apps addon:
Download: http://goo.im/gapps (use latest kk gapps)
Mirror: http://download.crpalmer.org/downloads/gapps/
Useful Links
Unofficial changelog
Picassowifi wiki
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
CyanogenMod 11.0 for Tab Pro 10.1 PicassoWiFi, ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
Version Information
Status: Stable
Created 2014-09-26
Last Updated 2014-09-25
Reserved
Reserved
@crpalmer, let me be the first to congratulate you on this! It's amazing how we have official CM support now!
Thank you very much!
Congrats again on your hard work paying off, and making it into AP. http://www.androidpolice.com/2014/0...-extended-to-the-samsung-galaxy-tab-pro-10-1/
Nice work. Think I'm about ready to do my first flash. . :good:
Congratulations on being official
It's with great interest I have followed the development of your T-520 version of the cm11, even though I don't have one myself. Why? Firstly, I'm amazed by the short time frame in which you actually accomplished this, and conquered the Exynos SoC. But, I'm also A proud owner of a T-900, and from what I can tell there is only the screen size that differs the T-520 from the T-900. In my mind, it should be feasible to port, though I might be wrong.... Maybe, you have some ideas of how to correct/evolve Shaheen's port of your ROM. Who knows, maybe at this point you're bored and need a new challenge, as the major obstacle is breached and, before the work with Android L begins... Besides, neither Shaheen, nor you own a T-900, why this should be a very simple task:laugh:
The current error report is as follows:
arcadia2uk said:
Thanks for reviving this one Shaheer,
After some problems in getting the full ROM onto the drive (all on my side), I finally got it up and working. The ROM is a lot snappier that prior versions, and is stable over all. Below is my summary of working/non-working functions. Additionally, with the all new TWRP 2.8.0.0, see post #55, the format of system and cache are instant, why ROM testing is a breeze.
I have noticed the following issues:
- WiFi connects, but loses password on reboot, same issue as earlier build
- Bluetooth: devices are seen, but do not connect - Error message: Can't connect
- External SD is not detected by device - see post #54, below, for more detailed info
- mtp - device does not mount on PC
- adb - device does not mount on PC
- Camera is broken - Error message
- Torch is broken - Error message
- Lid sensor - No reaction
- Capacitive lights - No reaction
- Sensors - No reaction
- IR blaster - No reaction
- Offmode charging - but it will not work on the picasso-wifi either, at least until tomorrow, 20140926
- Home button doesn't work correctly. It wakes up the device, but does not go to the home-screen
- Battery drain is significant - However, it might be my impression from heavy use of the screen while testing
Only two outstanding items (non-tested) from the list Shaheer posted below. I would appreciate if someone would test them and confirm if they are working, or not:
- Miracast displays - Most likely functional, given that the Chromecast dongle is working | Best Guess: yes
- Google Play Movies: downloading a video and then playing the downloaded copy. Apparently, crpalmer has received a CyanogenMod commit and the issue is fixed as of now, 20140925 | Best Guess: No
Click to expand...
Click to collapse
Anyhow, we (T-900 owners) would really appreciate your input, and I believe speaking for Shaheer as well, and to tap into your substantial knowledge and experience.
Once again, I'm really impressed by your accomplishments, and I sincerely congratulate you to the well deserved status as an officially recognized cm-developer.
Finally, if a tester is needed, I'll be around.
Thanks in advance.
Congrats! I appreciate your hard and nice work. Thanks :good:
I am so thrilled to see official CM support for Galaxy Tab PRO 10.1. Ordered mine couple of days.. and still in transit. They day I ordered.. I am thinking how will i live with touchwhiz..
I guess now i don't have to worry.. will root and flash right away once its here. Looks like everything is working. I don't care about small bugs if battery life is as good as stock
Thanks again
Good work !
I am on GraveD stock ROM, running very well for a month.
But I plan to try CM11 asap.
Sent from my SM-T520 using XDA Free mobile app
Subscribed in hopes this will trickle back to klimtwifi (Tab S with Exynos 5420)
Wow, thanks for the great news @crpalmer!
WiFi easy fix
sorry wrong thread
@crpalmer,
I followed the instructions "How To Build CyanogenMod Android for Samsung Galaxy Tab Pro 10.1 Wi-Fi ("picassowifi")" (http://wiki.cyanogenmod.org/w/Build_for_picassowifi).
I faced issues with drmserver and gpsd on extract-files.sh : "Permission Denied"
I managed this by copying them to internal memory and them adb pull to their destination locations.
It's compiling now...
Which ir app are you guys using? I can't find one that works.
If you want to disable the soft buttons and use the on-screen buttons (I use the tablet a lot in portrait mode and the soft buttons get in the way all the time).
1. Enable soft keys : edit the /system/build.prop file to include the following line qemu.hw.mainkeys=0
2. Disable the soft keys : edit the system/usr/keylayout/sec_touchscreen.kl file and add # in front of the two lines
3. Turn buttons light off : go to settings -> buttons and disable backlight
4. Reboot
I don't think it was posted all in one place before.
cviniciusm said:
@crpalmer,
I followed the instructions "How To Build CyanogenMod Android for Samsung Galaxy Tab Pro 10.1 Wi-Fi ("picassowifi")" (http://wiki.cyanogenmod.org/w/Build_for_picassowifi).
I faced issues with drmserver and gpsd on extract-files.sh : "Permission Denied"
I managed this by copying them to internal memory and them adb pull to their destination locations.
It's compiling now...
Click to expand...
Click to collapse
Hmmmm. That's a good one. Very few vendor blobs tend to have restricted read permissions but apparently we hit two of them. I assume that it was actually drmserver.samsung though right? That's important if your build is going to have working DRM.
I made myself a note to figure out how to make that work better and/or document it better.
FYI, you can also download an existing build, unzip that file somewhere, and then run
./extract-files.sh /path-that-you-unznipped-to/
and it will pull all the files from that unzipped directory.
burnski said:
Which ir app are you guys using? I can't find one that works.
Click to expand...
Click to collapse
I currently like Smart IR Remote. It's not free but they seem to be good people and I appreciate that.
crpalmer said:
Hmmmm. That's a good one. Very few vendor blobs tend to have restricted read permissions but apparently we hit two of them. I assume that it was actually drmserver.samsung though right? That's important if your build is going to have working DRM.
I made myself a note to figure out how to make that work better and/or document it better.
FYI, you can also download an existing build, unzip that file somewhere, and then run
./extract-files.sh /path-that-you-unznipped-to/
and it will pull all the files from that unzipped directory.
Click to expand...
Click to collapse
Hello,
Thanks.
Unfortunately, I need more RAM, only 2 GB RAM and 2 GB Swap don't fit the load.
crpalmer said:
I currently like Smart IR Remote. It's not free but they seem to be good people and I appreciate that.
Click to expand...
Click to collapse
Cool thanks I'll check it out
Did you get Infra Red ever to work? I use Touchsquid and it always worked with every ROM i tried.
But in CM11 it looks like it is broken. Maybe I am too impatient and i should wait a bit for CM to get IR working and go back to GraveD's ROM for a while.
Thanks for the hard work crpalmer!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction
This is a UNOFFICIAL build of LineageOS for the Samsung Galaxy Core Plus.
It's not ready yet and has some bugs in it which could cause problems to some users.
The ROM will only work on the SM-G350 Version of the Phone (without any Numbers/Letters behind).
This ROM could be used for daily use now (though you should look at the list of what doesn't work first).
Known Bugs
Camera sometimes switches to green-purple. The resulting picture doesn't have the weird color, but it may be flipped and/or distorted at the edges.
Video Recording
Codecs (some work, some don't. I tested MP4 and AVI, both work. I should really make a list...)
Installation Instructions
Special thanks to @Giovix92 for making this tutorial!
Requirements:
1: A computer with Windows.
2: An Internet connection.
3: A backup of your phone data (contacts, photo, music, videos, and other).
4: About 300 MB free space on your SD card.
5: Phone charged at least 80%.
Download links are below
I do NOT take any responsibility for bricked devices!
Let's start!
1: Download the Samsung USB Drivers.
2: Download the ODIN3. (Only for Windows)
3: Download the TWRP Odin package to your desktop and download the LineageOS 13 zip to your SD card.
4: Make a backup of your files, because the storage will be wiped. (External SD card will not be wiped)
5: Reboot your phone in to the Download mode (Volume Down- , Home- and Power button). Press the Volume Up button when asked. Then open the ODIN3 and connect your phone to your PC.
6: Press AP and choose the TWRP Odin package (recovery.tar) and make sure re-partition is NOT ticked. "Auto-Reboot" should not be ticked either, otherwise you will need to be quick to boot into the recovery immediately after flashing.
7: Press start! Wait a few seconds. Then your phone will be rebooted. Now you can disconnect the cable and power off your phone.
8: Boot your phone in to the TWRP Recovery (Volume Up-, Home- and Power button).
9: Go to Wipe, and Swipe to Factory Reset.
10. After wiping go to the home screen by pressing the home button.
11: Go to Install. Choose the "external_sd" from the top bar. (It says "Storage: Internal Storage (xxxxMB)" by default)
12: Choose the LineageOS 13 ZIP and Swipe to Confirm Flash. Make sure you don't power off while flashing!
13: After the zip has been flashed choose "Reboot System".
14: Wait 5-15 minutes to boot the phone. If the phone keeps booting take out the battery and do a Factory Reset again.
15: When the phone boots the first time, go through the Setup Wizard and you are ready to use your phone!
If there was something you didn't understand, please don't hesitate to ask
Changelog
23-01-2021:
Security patches until April of 2019
Updated Chromium from 67.0.3396.87 to 87.0.4280.101
Disabled latinimegoogle (which is compiled against an incompatible instruction set and results in crashes)
Fix offline charging
Old Changelogs:
02-05-2019:
Include all security patches up to January 2019 (and most of February and March, except for the PNG vulnerability)
NFC
Fix up some of the codecs (h264 and ac3, which should enable you to watch most videos)
Remove Gello (the old, bloated Browser) in favour of Jelly
Using way less hacks than previously (again)
05-04-2018:
Include all security patches up to March 2018
SELinux is now enforcing
OTA Updates the third (now using the internal Updater)
Using way less hacks than previously
24-05-2017:
Now compile with newest toolchain (Commit)
Fix SD Card (Device commit, Kernel commit)
Removed PMEM from the kernel (as this saves some RAM) (Commit)
OTA Updates (Commit)
18-04-2017:
Switch to LineageOS
4 Months of Security Patches
10-04-2017:
Fixed GApps (through a modified WebView)
07-04-2017:
Fixed Network (Commit)
Enabled permissive SELinux (Patch, Commit)
10-10-2016:
Bringup
Downloads
Samsung USB Drivers
Odin v3.09
Odin v3.11.1
TWRP 3
TWRP 2.8.1.0
lineage-13.0-20210123-UNOFFICIAL-cs02.zip
Sources
Device tree
Kernel tree
Proprietary files
WebView
Thanks To/Credits
Thanks to ...
... androidlover5842, ishantvivek, SandPox, ZIM555 and everyone else working on Samsung's hawaii-Boards
... berkantkz and santeri3700 for teaching me the basics of ROM developing
First Version of CM 13 is up
First! Good rom man!
Inviato dal mio ASUS_Z00A utilizzando Tapatalk
Hey !
i was happy when i saw that cm13 was out for our galaxy core plus so now i'm downloading it. After i will flash it if you want i can be a beta tester.
Thanks for this rom !
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
I installed it and for me the bigest problem is the wifi.
gaetano76le said:
Hey !
i was happy when i saw that cm13 was out for our galaxy core plus so now i'm downloading it. After i will flash it if you want i can be a beta tester.
Thanks for this rom !
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
I installed it and for me the bigest problem is the wifi.
Click to expand...
Click to collapse
Still working on that.
I just noticed that the sound sometimes "breaks" and sounds like damaged speakers (just for a part of a second, nothing permanent). I don't know if this is a software problem or just my phone. Can someone confirm that? It sometimes happens when doing a call or pressing random numbers at the Dialer. It also seems to happen only with standard sound level or higher.
I'll check it after I fixed (or tried to fix) Internet and SD Card
This is the same on stock when listening YT idk why it happens.
For the sdcard fix check if there are correct mounts for vold.fstab or framework
BTW. Videoplayback isnt working good on YT on Internet browser and is glitched too on chrome.
TimSchumi said:
I just noticed that the sound sometimes "breaks" and sounds like damaged speakers (just for a part of a second, nothing permanent). I don't know if this is a software problem or just my phone. Can someone confirm that? It sometimes happens when doing a call or pressing random numbers at the Dialer. It also seems to happen only with standard sound level or higher.
I'll check it after I fixed (or tried to fix) Internet and SD Card
Click to expand...
Click to collapse
bump
@TimSchumi
http://forum.xda-developers.com/s7582/development/rom-cm13-0-galaxy-s-duos-2-trend-plus-t3307986
Maybe talk with this guys to allow to use their source? Will be easier to fix rom and you will can to support them too
So, any changes about the network?
QGM said:
bump
@TimSchumi
http://forum.xda-developers.com/s7582/development/rom-cm13-0-galaxy-s-duos-2-trend-plus-t3307986
Maybe talk with this guys to allow to use their source? Will be easier to fix rom and you will can to support them too
Click to expand...
Click to collapse
Thanks for searching :good:
I'll write to developer and ask for the fix!
john_sdr said:
So, any changes about the network?
Click to expand...
Click to collapse
Not now, still working on it. I don't even know where to search.
something about the vpn? or maybe something isnt compatible with cm13?
I searched on google and disable the firewall could be a solution.
john_sdr said:
something about the vpn? or maybe something isnt compatible with cm13?
Click to expand...
Click to collapse
Seems to be a more general problem. I'll look through the device/kernel/vendor trees of similiar devices for a fix.
SpYneX_ said:
I searched on google and disable the firewall could be a solution.
Click to expand...
Click to collapse
Could you test it?
TimSchumi said:
Seems to be a more general problem. I'll look through the device/kernel/vendor trees of similiar devices for a fix.
Could you test it?
Click to expand...
Click to collapse
How could you even disable a device's firewall?
Well, i just red here "https://forums.oneplus.net/threads/official-cm13-nightly-builds-rolling-out-for-opo.411202/page-103" that its may be fault of the recovery. I dont think that we all got the same twrp though, is something you can test? i used santori's twrp, i had it flashed quite a time. maybe an update or a modification will solve that issue
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Hey, I'm new here at xda forums. I just installed this ROM on my galaxy core plus, and it works great. My phone is now super snappy. But many features don't work as of now, the bluetooth actually worked for me, I didnt expect it to after reading the post. When will these bugs be fixed, and more importantly how can I follow so that I can get my hands on the new release as soon as it gets out? Thanks a lot!
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
john_sdr said:
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Click to expand...
Click to collapse
I also could try to make CM Recovery first, and if it won't work, I'll give TWRP a try.
Abiti7 said:
Hey, I'm new here at xda forums. I just installed this ROM on my galaxy core plus, and it works great. My phone is now super snappy. But many features don't work as of now, the bluetooth actually worked for me, I didnt expect it to after reading the post. When will these bugs be fixed, and more importantly how can I follow so that I can get my hands on the new release as soon as it gets out? Thanks a lot!
Click to expand...
Click to collapse
I still need to search what causes the Internet and SD Card to fail. Bluetooth does work, only Bluetooth Calls, Car connection and other devices are untested.
You can subscribe to this thread or subscribe to the DevDB project, to get a notification if it's updated. To get updates on your Smartphone, you could install XDA Legacy (Tapatalk) or XDA Labs (just called XDA) from Play Store.
john_sdr said:
allright, i'll check up for a twrp for our phone :angel:
EDIT: on the official twrp/devices, there is not our device. so, what's up next?
Click to expand...
Click to collapse
zenida said:
I knew we need TWRP 3.x.x to install an Android 6.0+ Rom. So, the network issue, could be related to the recovery version.
We should to update the recovery first, to install Marshmallow (and up) on a smartphone
Click to expand...
Click to collapse
CM Recovery didn't fix the problem. And I somehow can't get TWRP to boot.
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Download Links
LineageOS:
Downloads: https://download.lineageos.org/d2vzw
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Changelog:
Link: https://download.lineageos.org/d2vzw/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/d2vzw/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05
reserved
Hallelujah!
Is this the eighth or ninth life of this great phone?
@invisiblek, are there plans for the release of a Snapshot of CM13.0 for the d2vzw?
Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!
Nice job! Wich partitions can I mount as f2fs?
Just out of curiosity regarding the CM14.1...
Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?
Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?
I had already sent the issues I'm having along with all my log files to @invisiblek and was curious as to any others experiencing the same/similar issues I experienced.
Thank you all for your time and understanding!
Thank you @invisiblek and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes
I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.
Thanks for the great work. Much appreciated!
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Ibuprophen said:
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Master Cylinder said:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Click to expand...
Click to collapse
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Ibuprophen said:
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Stealth111 said:
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Click to expand...
Click to collapse
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".
A: Portable Storage.
Q: Also what type of filesystem do you have the card formatted with?
A: VFAT
Q: What file manager are you using to try to access your card with?
A: Stock & ES File Explorer Pro
Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?
A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.
I really appreciate your assistance and please don't hesitate to defer to @invisiblek if necessary.
Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...
Thank you very much!!!
I wonder if the GApps issue is the underlying issue. I hope @MastahF & @Rapper_skull is aware of and working on it?
Sent from my d2vzw using XDA Labs
Stealth111 said:
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials.
Stealth111
Click to expand...
Click to collapse
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Ibuprophen said:
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Click to expand...
Click to collapse
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Click to expand...
Click to collapse
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....
Who knows.... :laugh:
Other than that, I agree, purring like a kitten!
Stealth111
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Click to expand...
Click to collapse
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Sent from my Pixel using XDA Forums Pro.
Ibuprophen said:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Pierre2324 said:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Click to expand...
Click to collapse
Here's a link that, i believe, will answer your question:
http://forum.xda-developers.com/showthread.php?t=2537119
Good Luck!
Sent from my d2vzw using XDA Labs
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
Master Cylinder said:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Click to expand...
Click to collapse
There was a member in the GApps thread who had mentioned that he had a similar issue.
He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.
I believe that others had to flash their GApps packages from about 30 days ago had worked for them.
I know that this is an issue for many others who also reported it to the Dev(s).
I can't think of what in the world is going on...
Sent from my d2vzw using XDA Labs
Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good: