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 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?
Code:
#include
/*
* 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.
*/
This is a preview build of Android JellyBean 4.2 from AOSP source code based on the CyaogenMod device tree for Acer A700. I have made this build to gauge how difficult it would be to port JellyBean 4.2 to current devices.
Kernel Source Code: https://github.com/pawitp/android_kernel_acer_t30/tree/jellybean-next
Device Tree: None yet available (Only notable part: patch for TinyHAL: https://gist.github.com/4104332)
Downloads
ROM: http://goo.im/devs/pawitp/a700/a700_aosp_jb42_20121116.zip
Google Apps: Currently integrated due to lack of gapps package for 4.2
SuperSU: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip (Currently, only SuperSU is compatible with 4.2)
Installation
Note: due to new /data/media layout in 4.2 for multiple user support, your data in /data/media (/sdcard) will be moved to /data/media/0. This may cause problems in restoring backups in recovery, you may fix it by moving data /data/media/0 back to /data/media via adb in recover prior to restoring data.
Install CWM recovery from http://forum.xda-developers.com/showthread.php?t=1791165
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Wipe data if coming from stock
Known Issues
Camera does not work
Bluetooth sometimes freezes bringing down Wi-Fi with it
Reporting Bugs
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. The development of this preview will also cease once enough progress has been made in CyanogenMod.
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.
gonna grab this later
Wow! This ROM is awesome. Please make it more stable. And the Performance is not so good as other ROMs.
Webitu
Webitu said:
Wow! This ROM is awesome. Please make it more stable. And the Performance is not so good as other ROMs.
Webitu
Click to expand...
Click to collapse
For stability: Please report crashes as mentioned in the OP, without logs, there'd be no way to know what broke.
For performance: Please report where and how performance differs.
Note that generic "please make this better" report do not help, please be more specific.
Runs so far, unfortunately I can not get a wifi connection. 'm Back to 4.1 back.
Fooox1 said:
Runs so far, unfortunately I can not get a wifi connection. 'm Back to 4.1 back.
Click to expand...
Click to collapse
Next time, please get a logcat.
pawitp said:
For stability: Please report crashes as mentioned in the OP, without logs, there'd be no way to know what broke.
For performance: Please report where and how performance differs.
Note that generic "please make this better" report do not help, please be more specific.
Click to expand...
Click to collapse
Okay sorry. The launcher laggs sometimes and the Antutu benchmark results are not really good.
The GPU test results are 967 points. (3D = 674, 2D = 293)
The fps are 31. In the stock ROM i had 42 fps i think.
And i havn´t any crashes but it seems like its a little bit unstable but it can be also the apps who are not official for 4.2
But very good work! :good:
Sorry for my bad English.
Webitu
The graphic issue can't really be helped, Android 4.2 requires new graphic drivers and the current binaries used are optimized for the Nexus 7. As there are closed-source binaries, there is no way to modify them. The situation may change in the future as compatibility layers are introduced or new drivers are released.
pawitp said:
The graphic issue can't really be helped, Android 4.2 requires new graphic drivers and the current binaries used are optimized for the Nexus 7. As there are closed-source binaries, there is no way to modify them. The situation may change in the future as compatibility layers are introduced or new drivers are released.
Click to expand...
Click to collapse
Okay thank you. I already thought so. Hopely Acer brings a new Update with 4.2
Webitu
Nvidia is the same xxx as samsung (
Is A701 supported?
It will work on A701, but 3G will not work.
BTW, CM10.1 preview. Nearly everything working (including Camera, etc.). Nightlies should start soon and I'll make a new thread then.
http://goo.im/devs/pawitp/a700/cm-10.1-20121216-UNOFFICIAL-a700.zip
pawitp said:
It will work on A701, but 3G will not work.
BTW, CM10.1 preview. Nearly everything working (including Camera, etc.). Nightlies should start soon and I'll make a new thread then.
http://goo.im/devs/pawitp/a700/cm-10.1-20121216-UNOFFICIAL-a700.zip
Click to expand...
Click to collapse
Yeah. Big thanks for your work! I will try it out now. Did you recognized that when you set a wallpaper on CM10 only half of the wallpaper is used on the homescreen? Don`t know how to log this issue.
OCmylife said:
Yeah. Big thanks for your work! I will try it out now. Did you recognized that when you set a wallpaper on CM10 only half of the wallpaper is used on the homescreen? Don`t know how to log this issue.
Click to expand...
Click to collapse
It's due to our screen size and peculiar wallpaper handling, so the default wallpapers don't scale too well.
pawitp said:
It's due to our screen size and peculiar wallpaper handling, so the default wallpapers don't scale too well.
Click to expand...
Click to collapse
Yeah I`ve tried logcat in the terminal, before I read your command. It shows no error-message when I changed the wallpaper. But I think I could live with this one.
I`ve encountered one minor Issue. You could change the default page size in the trebutchet settings, but it doesn`t take effect on your pages on the homescreen. Yeah really minor issue, but otherwise I haven`t found a bug so far. But I will search further.
Again. CM 10.1 looks absolutely awesome on the Acer A700 and I would recommend everybody who has CWM on his A700 to try this one out. :highfive:
Has anyone tried twrp recovery on the A700? I`m frightened every time to flash on my A700, cause I experienced the freeze issue also(one time so far, after I switched from CM10 to Iconian 2.2).
Trying to install CM10.1 but until now only bootscreen for 20 mins :/
Edit: hmm almost 40 minutes -.-
Tried Wiping Data/System/Cache now, but still Bootscreen loading and loading..
Chris0706 said:
Trying to install CM10.1 but until now only bootscreen for 20 mins :/
Edit: hmm almost 40 minutes -.-
Tried Wiping Data/System/Cache now, but still Bootscreen loading and loading..
Click to expand...
Click to collapse
Use adb to get a logcat, it'll tell you what's wrong. Normally, it's caused by not wiping data when coming from a stock ROM, but since you've said that you've wiped data, maybe there's some other cause.
pawitp said:
Use adb to get a logcat, it'll tell you what's wrong. Normally, it's caused by not wiping data when coming from a stock ROM, but since you've said that you've wiped data, maybe there's some other cause.
Click to expand...
Click to collapse
Which command parameters should i use ? Its a load of text.
If i want to save the log in a file with the -f parameter i always get the error, that the output file couldnt be openend and that my filesystem is read-only ..
Chris0706 said:
Which command parameters should i use ? Its a load of text.
If i want to save the log in a file with the -f parameter i always get the error, that the output file couldnt be openend and that my filesystem is read-only ..
Click to expand...
Click to collapse
adb logcat > log.txt
Sent from my GT-I9000 using xda app-developers app
So now i got the logcat attached, hopefully you find the error..
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, 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.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).:good:
My builds uses all official CyanogenMod sources except the kernel. But I am merging it with all fixes/features from CM kernel repo, Google and kernel.org mainline too.
Downloads
Latest HumberOS
Installation
- First time flashing CyanogenMod to your device (or coming from another ROM)?
Root your device and install CwM Recovery* or TWRP.
Reboot into Recovery
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using CwM Recovery* or TWRP
* Check troubleshooting if you are using CwM Recovery.
FAQ
Please read before posting or reporting bugs!:good:
Reporting Bugs
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.
Please read the thread for known issues before reporting.
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.)
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--
Tablet model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
----------------------------------------------------
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:
IRC
User channel
#teamhacksung-support
Developer channel
#teamhacksung
#cyanogenmod-dev
Development
HumberOS development thread
Changelog?
A rough changelog is available HERE
All Sources
HumberOS
CyanogenMod
______________________________________________________________
The CyanogenMod team would like to THANK everyone involved
in helping with testing, coding, debugging enting!
Enjoy!
Re: [ROM][JB][4.2.2][N80XX] CyanogenMod 10.1 - HumberOS - Q&A
Mmm been looking and thinking about flashing a rom might have to give this a try.
Thanks
Sent from my GT-N8013 using Tapatalk 2
Won't install.
Unable to get ROM installed on my GT-N8020
Latest version of rom tried.
Using CWM 6.0.2.8
Attempted correcting the assert failure but now aborts without error.
What am i doing wrong???
Also tried TWRP but it is unable to access the flash...
Re: [ROM][JB][4.2.2][N80XX] CyanogenMod 10.1 - HumberOS - Q&A
icuimp said:
Unable to get ROM installed on my GT-N8020
Latest version of rom tried.
Using CWM 6.0.2.8
Attempted correcting the assert failure but now aborts without error.
What am i doing wrong???
Also tried TWRP but it is unable to access the flash...
Click to expand...
Click to collapse
Hey!
I think the process is the same for all variants using CwM or TWRP.
Please, check the MD5 checksum.
Sent from my Galaxy Nexus using xda premium
TWRP is not supported on the N8020.
MD5 is fine.
Noticed when extracting the ZIP to modify the file it finds 24 files doubled up in the same place.
Is this an issue???
Is there anything i can provide to you that can help figure out why it won't install?
humberos said:
Hey!
I think the process is the same for all variants using CwM or TWRP.
Please, check the MD5 checksum.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
icuimp said:
Noticed when extracting the ZIP to modify the file it finds 24 files doubled up in the same place.
Click to expand...
Click to collapse
Which files?
Thanks!
N8020
Symlink: some symlinks failed
E:ERROR in /external_sd/cm10....
(status 7)
Installation aborted
Any advice against this ?
icuimp said:
Unable to get ROM installed on my GT-N8020
Latest version of rom tried.
Using CWM 6.0.2.8
Attempted correcting the assert failure but now aborts without error.
What am i doing wrong???
Also tried TWRP but it is unable to access the flash...
Click to expand...
Click to collapse
ttair said:
N8020
Symlink: some symlinks failed
E:ERROR in /external_sd/cm10....
(status 7)
Installation aborted
Any advice against this ?
Click to expand...
Click to collapse
Sorry guys!
My device is an N8013.
N8000, N8010 and N8013 have a similiar hardware.
But N8020 is LTE device and have some diferences between others.
I am still working on it.
Thanks!
N8013
i want to flash my rooted note 10.1 which is jellybean 4.1.1 deodexed version to this rom instead. my question is do i just straight away flash it or do i need to do something else since am on 4.1.1 ??
reddevilboyz said:
i want to flash my rooted note 10.1 which is jellybean 4.1.1 deodexed version to this rom instead. my question is do i just straight away flash it or do i need to do something else since am on 4.1.1 ??
Click to expand...
Click to collapse
Flash a recovery like this:
http://forum.xda-developers.com/showthread.php?t=2102677
Now download the ROM from here:
http://goo.im/devs/humberos/rom <-- you choose your device
and gapps from here:
http://goo.im/gapps/gapps-jb-20130301-signed.zip
Go into recovery by holding down the power button + volume up key (Release the power button when the device is turned on).
Now:
Wipe Factory Reset + Wipe Dalvin Cache + Wipe System + Wipe Preload
Install the ROM and gapps.
Wipe Cache + Wipe Dalvin Cache (optional)
Reboot
Screencast not working
Sorry for my bad english language but applying the inverse color after screencast recording screen capture solution thank you
I speak french
status update
I know that good things come to those who wait but would it be possible to have an update on when humberos for the n8020 would see the light of day? Ever since I bought my device I have been searching and reading on the internet every day and can not help but sadly left out of the possibilities to use an custom os on my device. I also have the impression to be alone in my search for answers as there is no real discussion going on on this subject and I wonder why this would be? For all I was able to find out is that the only work in progress going on specificly for the n8020 is being made by Humberto. Correct me if I am wrong. I also would like to ask as being new to Android if I can install a future release of humberos safely on my n8020 because its a t-mobile hungary branded. It's rooted however. I would like to thank anyone taking time to answer my questions.
Fuse
Cyanogenmod at this point for some reason seems to have serious issues with fused filesystems and so for one reason or another always messes up sd cards formatted with ntfs, ext4, or exfat. Most common of those being exfat as many people are using it on the large sd cards for obvious reasons. In this light after searching xda I found this and have been stably using it for weeks now in combination with your rom... http://forum.xda-developers.com/showthread.php?p=38182488#post38182488 ... its a flashable mod that supports mounting of exfat, ntfs, and ext4 formatted sd cards in CM 10.1 be it single partition or multi-partition. Till now I have encountered no errors or problems with it hence I was wondering if it might be possible for you, Humberto, to coordinate or work with that developer and include it in your rom or at least include a link on your page. Those of us using the n80xx love to use large sd cards as this is a tablet pc, samsung's recent stock firmware already takes care of exfat but cm 10.1 does not and without it... well there are several limitations and negative aspects of Fat32. Just something to consider and I know its not the most crucial part of the ROM but it would DEFINITELY be nice to be able to mount a wider variety of Filesystems without flashing 3rd party mods.
Thank you for your work
Hello Humberto,
you was a live saver for me and my N8010. I am running your rom now for a couple of weeks wirthout any big problems (beside a small installation problem since I have the N8010 version).
I have now noticed that cyanogenmod(dot)org have now nightly builds for the N80XX. My question is what are the main differences between "official" nightly builds and your rom?
If you or somebody else could answer my question I would be very happy
regards
nightly vs humberos
The main difference is in the kernel, I prefer humbertos kernel as , at least to me , it feels smoother and more stable along with providing additional options. Here are the Kernel tags for humberos so you can see the changes ...http://forum.xda-developers.com/showthread.php?p=37586691#post37586691
Aeolius said:
The main difference is in the kernel, I prefer humbertos kernel as , at least to me , it feels smoother and more stable along with providing additional options. Here are the Kernel tags for humberos so you can see the changes ...http://forum.xda-developers.com/showthread.php?p=37586691#post37586691
Click to expand...
Click to collapse
Hello Aeolius,
The Kernel Tags are to technical for me
Anyway if the hubertos kernel is more stable I will stay with it. Thanks.
goosefx said:
Hello Humberto,
you was a live saver for me and my N8010. I am running your rom now for a couple of weeks wirthout any big problems (beside a small installation problem since I have the N8010 version).
I have now noticed that cyanogenmod(dot)org have now nightly builds for the N80XX. My question is what are the main differences between "official" nightly builds and your rom?
If you or somebody else could answer my question I would be very happy
regards
Click to expand...
Click to collapse
My rom have minimal diferences between official CM builds.
Over ROM space we have some options in Settings like old Tablet UI as user option.
Over Kernel space we have a lot of diferences like OC, UV, memory management, kernel mainline sync (all security fixes), etc.
Enjoy it!
Aeolius said:
Cyanogenmod at this point for some reason seems to have serious issues with fused filesystems and so for one reason or another always messes up sd cards formatted with ntfs, ext4, or exfat. Most common of those being exfat as many people are using it on the large sd cards for obvious reasons. In this light after searching xda I found this and have been stably using it for weeks now in combination with your rom... http://forum.xda-developers.com/showthread.php?p=38182488#post38182488 ... its a flashable mod that supports mounting of exfat, ntfs, and ext4 formatted sd cards in CM 10.1 be it single partition or multi-partition. Till now I have encountered no errors or problems with it hence I was wondering if it might be possible for you, Humberto, to coordinate or work with that developer and include it in your rom or at least include a link on your page. Those of us using the n80xx love to use large sd cards as this is a tablet pc, samsung's recent stock firmware already takes care of exfat but cm 10.1 does not and without it... well there are several limitations and negative aspects of Fat32. Just something to consider and I know its not the most crucial part of the ROM but it would DEFINITELY be nice to be able to mount a wider variety of Filesystems without flashing 3rd party mods.
Click to expand...
Click to collapse
Hey dude!
I will check these features and if they are ok then I will let you know how we can include them in our project.
Thanks!
awesome
That's awesome, I hope you can get permission from the respective developers this would truly be a great feature, also I saw that you added 1700 and 1800 clock steps in the kernel tag is the only way to access those by editing the default steps in the text files myself or I'm misunderstanding the kernel tags ? Thanks for the great work!
Aeolius said:
That's awesome, I hope you can get permission from the respective developers this would truly be a great feature, also I saw that you added 1700 and 1800 clock steps in the kernel tag is the only way to access those by editing the default steps in the text files myself or I'm misunderstanding the kernel tags ? Thanks for the great work!
Click to expand...
Click to collapse
Actually both 1.7 and 1.8 Ghz are very unstable.
I removed them.
So, 1.6GHz is good for us.
Thanks!
Code:
Code:
/*
* Your probably long expired 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
* and point my finger right back at you.
*/
Installation Instructions
Make sure you have a second partition on your SD card before flashing!!!! This can be created with minitool partition wizard on Windows or gparted on Linux.
If on a BML rom (stock-based GB)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. It will reboot a couple of times, don't be worried.
4. If you want root or Gapps, flash them now
If on an MTD rom (CM7 and all ICS+)(I tested CM9, CM10.1 and CM11)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Wipe data, and cache paritions (just in case). If updating to a newer build, you can probably skip this step
3. Install zip
4. If you want root or Gapps, install them now
The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess and also provide T959P builds.
The USB connection is MTP and not mass storage as Omni has removed mass storage. In recovery there is still an option to mount as mass storage device.
This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps reportedly slow down the device significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
Video Recording
Automatic Brightness
Moving Apps to the SD Card
GPS
Encryption
Compass
SElinux in enforcing mode
What probably doesn't
Microphone mute option doesn't work during calls
What doesn't
720p recording is very laggy
What's been removed
TV-Out - It was removed upstream plus I think binary blobs are broken in Lollipop...
Live wallpapers - this is a low-ram device
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Galaxy S 4G (T959V) and Galaxy S Fascinate 4G (T959P), ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99, humberos
Source Code: http://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: All
Based On: OmniRom
Version Information
Status: No Longer Updated
Created 2015-06-30
Last Updated 2016-05-12
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Download folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch galaxys4gmtd"
Changelog
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
Notifications are sometimes wonky. To fix, in Settings, go to Performance, then Advanced. Select Force high-end graphics and reboot your phone.
Changelog for 2015/07/20 Build
The data partition is now the second partition of the SD Card as opposed to internal storage
Gapps now work. If you get error 461 when installing from Play Store, a full data wipe should fix it. You can try experimenting with clearing data for the Play Store and/or Play Services or removing and re-adding your Google account if you don't want to do a full data wipe.
HSPA vs UMTS settings in DeviceSettings has been fixed
High-End graphics are forced by default to fix notification issue
ART parameters have been tweaked
Miscellaneous other tweaks, see my Github for details
Changelog for 2015/07/24 Build
Stabilized bluetooth connection
Fixed typo in GPS initialization. Does it work?
Added ability to use f2fs file system on /data. Supposed to give better performance
Added force fast charge and touch wake to kernel. Touchwake is accessible through its sysfs path, fast charge through Performance Settings, BatterySelinux currently denies these requests...
Changelog for the 2015/07/29 Build
This is a maintenance build. Very little has changed
Some more RAM freed (disabled some debugging stuff, TV-Out driver, IR driver)
Sepolicy updated for fast charge and touch wake
GPS initialization tweaked - unsure if works. If it doesn't, a dmesg would be appreciated
Changelog for 2015/08/02 Build
SElinux changed to permissive - this build only
GPS sepolicy changed - unsure if all necessary things are implemented
Changelog for 2015/08/13 Build
Selinux back to enforcing. Thanks to @anoymonos for the dmesg and @DerPugNa for offering to send me one as well
Fixed encryption
Changelog for 2015/08/31 Build
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
Restoring /system in TWRP should now work
When installing from BML, a chance is given to install gapps and/or SuperSu before rebooting
zRam is now actually used...
Changelog for 15/10/2015 Build
Fixed typo in updater.sh (thanks @FBis251!)
Update Omni source code - plenty of little tweaks since last build
Source Code and Downloads
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-5.1-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Please let me know if the link doesn't work! There are also builds there for the T959P, in case there are any users of it left.
Gapps
Gapps do not work on builds prior to 2015/07/20. On more recent builds, they can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Thanks thanks ....
Awesome work @xc-racer99!
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
GFX.myst. said:
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
Click to expand...
Click to collapse
I hope I can keep this great little device going a little longer, however it will probably get tough. I did a repo sync earlier today and things are starting to break. The last few builds haven't even booted. With humberos no longer maintaining the i9000 and aries-common, I've had to fork the aries-common repository to try to keep going. The only upside of this is that I now have a little bit more freedom and can add things in if I want to.
Thanks for the offer of the graphics. If I can get a new build working, then I'll probably take you up on your offer. I think I've traced the problem but I'll have to wait and see...
For anyone that is trying/has tried this out, I'd be very curious on the status of the GPS on the T959V. I'm interested in creating the sepolicies for it so we can put selinux into enforcing mode but I don't want to go to the effort if it doesn't even work right now.
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
New Build Uploaded!
Download is still at the same link as before, just use the 2015-07-03 build
I managed to find out why my new builds hadn't been booting - it was because the syntax for using a custom kernel toolchain had changed.
Anyway...
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
On another note, I've had a look at re-implementing TV-Out support. It doesn't look promising as several of the functions in the android frameworks that it used have been tweaked.... Still working on it but don't hold your breath.
Also, if somebody could test dock audio that would be appreciated. I don't have any way of testing it. If it doesn't work, I do have an idea on how to fix it (for those interested, another almost-aries device, the Infuse 4G, had to modify things slightly to get it to work. I would try to emulate their solution).
Omg download nowwww....thanks my friend
Alright, I'm having some issues on the latest build with notifications and the lockscreen. I'm still working on tracing down the reason for the problem...
DickyG said:
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
Click to expand...
Click to collapse
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
billowusu47 said:
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
Click to expand...
Click to collapse
Good to hear that that's its (mostly) been working for you. I was hoping that the gapps problem was just me
Out of curiosity, which of the alternate gapps did you try?
A brief google of the error brings up a couple of possibilities...
Try an older gapps version. The ones from devloz on the i9000 thread devloz and the oldest revision for 5.1.1 are probably your best bet. Please be aware that Google Play store will automatically update!!! In order to prevent this, you will need to create a folder called "com.android.vending-1.apk" in /data/app (use a root explorer such as ES File Explorer or adb if you know how). If a file with that name already exists, delete it first.
Another thing to try would be to unmount your sdcard first before trying to install an app. I know, its a terrible work-around but it should work. This is because the error is that Google Play is trying to save some data on your sdcard but then for some reason it fails (I'm not sure why).
I'll hopefully get around to seeing if its a permissions problem after I find out what's been causing the issue with the notifications on the latest build.
P.S. Does the GPS work?
Early update...
...ROM flashed fine...a little slow to boot...about 3 minutes...but it booted.
...Gapps flashed fine...used 20150513_5.1.x package
...Installed Super SU (although I don't think that's necessary) and TB.
...So far only gave a quick test to camera and web browser...no problems.
...Am now in the process of re-installing user apps and data from TB...this will take a while.
When I'm done with that, I use Link2SD to link most of my user files to the SD card. After that is all set up, I'll test stuff like GPS, root access, etc. I'll post back later...maybe tomorrow.
But so far so good.
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
DickyG said:
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
Click to expand...
Click to collapse
Alright, thanks very much for the update. I'll do some more testing here and see if I can solve anything. For me, bluetooth file transfers to the phone work but not from the phone.
I've been looking at the notification "error" where the lockscreen notifications do not appear correctly. It appears to have been introduced upstream with a merge. I'm having difficulty finding out exactly what changed and since no errors are being thrown in the logcat, it could be a while...
For testing the GPS, there's an app from the Play Store called GPS Test which does a nice job of showing satellites and whether or not you have a lock on them.
you're the man!
nice one! its nice that this device are still alive.! and now were on 5.1
DerPuGNa said:
nice one! its nice that this device are still alive.! and now were on 5.1
Click to expand...
Click to collapse
No, it should be Humberos is the man! I basically re-hashed his code for the i9000 and used bits and pieces from people like Bhundven, noiphonehere, maxfierke, Dao, and FB to get things to work properly.
For a status update, I figured out the lockscreen notification problem. I have a new build being made that I hopefully will be able to upload in the next couple of days (internet dependent). TV-Out looks totally broken as the proprietary blobs no longer function. I don't have the know-how to make ugly hacks to get them to work. The new build will have SElinux in enforcing mode and have the different GPS initialization (like the last build) until someone tells me that it doesn't work
Uh-oh, looks like I jumped the gun.... Having problems once again
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
AgainstTheFlow said:
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
Click to expand...
Click to collapse
Darn, so its still not working. Not surprising. I've been struggling on the notification issue and am at my wit's end as to what the problem is. I don't think its only our phone as several i9000 users have been reporting it as well. Whether it is only the first-gen Galaxy S series that is having the problem or not is anyone's guess. My programming skills are insufficient to fix the issue!
I'll have another look at gapps over the next couple of days and see if I can figure out a combination that works 100% of the time.
I'm assuming the error message is still 963 or does it silently fail now? Its probably related to the fact that we have only an external sd card and no internal sd card like most devices...
All the problems with the notifications that I've found are:
Only one notification will show up at a time
Large notifications such as the music player do not render properly. They are cut off at the normal notification size and occasionally it seems as if there are two layers there (one for the small version, one for the bigger version) (see attached picture, taken with VLC as the media player, but also appears with Apollo)
Notifications don't always show up. A little icon appears in the top left corner of the status bar but no notification is present. Seems hit or miss
The words No notifications appears in the lockscreen just above the clock when there are no notifications. Otherwise, a notification (and only one) which can't be clicked covers part of the clock
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: