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!
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 Motorola Defy, 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-jordan
Download: link
Mirror: link
MD5sum: 79d6dc94930c36117f0326315ed0556f
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!
Using it already. Its great an fast!
Thank you for your effort!
You guys saved my defy!
God reward you!
Waiting for next update.
Sent from my MB525 using xda premium
I installed it a few minutes earlier! By far faster and more responsive than the stock froyo I used to have! Thanks to all the ones that have contributed to this project!
Hello, I was using the 7.1 version but it was updated from the atest nightly.
When I tried to flash from stratch it just boot loops...
EDIT: I tried wiping data and now it works.
feh_pexto said:
Hello, I was using the 7.1 version but it was updated from the atest nightly.
When I tried to flash from stratch it just boot loops...
EDIT: I tried wiping data and now it works.
Click to expand...
Click to collapse
Always need wipe data when you go to another kind of roms !!!! (which is not same as rom update)
This is the 99% reason for flashing bootloop's
I couldn't make calendar lockscreen widget works. Any idea?
I may stick with the nightlies in that case. Is there any material difference, anyway?
so.. im running the leaked gb rom. is this what i should do to get this running on my phone?
1. flash official 2.2.2 (india)
2. wipe everything (factory reset)
3. using recovery install the cyanogenmod as an update from sd card
and this is reversible right? as in i can just wipe and flash any other rom if for some stupid reason i dont like this?
jayeshrc said:
so.. im running the leaked gb rom. is this what i should do to get this running on my phone?
1. flash official 2.2.2 (india)
2. wipe everything (factory reset)
3. using recovery install the cyanogenmod as an update from sd card
and this is reversible right? as in i can just wipe and flash any other rom if for some stupid reason i dont like this?
Click to expand...
Click to collapse
Yup...assuming you implied the rooting+2ndInit after flashing 2.2.2
You can refer here for more details:
http://forum.xda-developers.com/showthread.php?t=1065798
It hasn't been updated to include the official stable release but the instructions remain the same.
Today is the happiest day in my Android life ... finally a device I own is the offical Cyanogenmod tree
\o/
Anybody having trouble with gmail app? Always fc here
Sent from my MB525 using XDA App
felipeap said:
Today is the happiest day in my Android life ... finally a device I own is the offical Cyanogenmod tree
\o/
Click to expand...
Click to collapse
+1
thanks to CM team + quarx + epsylon + maniac...!
i did the update for cm7, but the phone doesnt boot into anything past the boot animation. it just keeps looping that animation and nothing else!
EDIT: oops, realized i hadnt wiped before updating.. so i just pulled the battery out, booted into the cem recovery and wiped. rebooted again and it worked. sisnt have to redo the whole flashing process.
there are still 2 bugs (at least):
1. camera FC bug if, during a video recording, the home button is pressed. The video file will be corrupt.
2. WIFI signal strenght doesn't update.
okay, one question. why is there no market app on this? is it because i wiped as i said?
How to change WCDMA prefered, GSM only settings
There used to be an option in even 7.1rc1.5 to select the band in mobile network settings (Between national data roaming and access point names) to select 2g or 3g (WCDMA prefered, gms only etc.)
Now i dont have it on cm7.1 official. Is there a way to change these settings?
Also *#*#4636#*#* does not work for cm7
OK here is my first report
It's much much stable now.
Not getting all the FC's which I was getting in 1.5
smooth interface
I had huge issues with my contacts earlier which is now sorted
Issue:
Camera is giving FC's sometimes.
Finally
an official version
Bye bye Beta, bye byte RC
Sent from my MB525 with CM7.1 and Swype
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
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.
*/
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.
Device-specific source code for the Acer A700 are available from https://github.com/CyanogenMod/android_device_acer_a700 and https://github.com/CyanogenMod/android_kernel_acer_t30
Do not submit bug on CyanogenMod issue tracker
Downloads
Latest Build: http://download.cyanogenmod.org/?device=a700
Google Apps: http://wiki.cyanogenmod.org/w/Gapps
Installation
Install CWM recovery from http://forum.xda-developers.com/showthread.php?t=1791165 (note that the old touch version will not work because of incorrect default.prop from CWM builder)
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Wipe data if coming from stock
Changelog
A rough changelog will available here once nightlies have started:
http://www.cmxlog.com/11/a700/
Reporting Bugs
You are allowed to report bugs only in this thread.
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)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
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):
ART Runtime:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Hi pawitp,
Works great and stable.. but i use pa gapps with enable ART.
Speed and Performance for this early Build is awesome.
Thanks that you work for our A700
Gesendet von meinem GT-I9505 mit Tapatalk 2
Hi all
I am really eager to upgrade my A700 to kitkat... Since acer won't provide upgrades, i am considering unofficial ROMs.
Can you guys comment on the downsides of this Rom?
Any functionality not working?
Many thanks
Installation aborted error status 7)
back to 10.2 adb push
s1r1 said:
Installation aborted error status 7)
back to 10.2 adb push
Click to expand...
Click to collapse
Try updating your recovery to the latest version.
Installed it over 10.2 stable version without a glitch (6.0.4.4 recovery). Seems to work fine, performance seems to be a little under 10.2 but it's early build. Thank you very much pawitp !
cwm 6.0.4.4 works fine thanks.
kit kat for a700
Hi pawitp
Thank you very much for this Rom ! I did a full wipe before flashing coming from Evil Alex Purgatory. Rom is fast and smooth but when i delete a widget on homescreen there is no "delete" button on the upper edge so i've got to keep the widget picked and "scan" the upper edge until it turns to red. Waiting for update or reflash ? But not a big thing for me.
G mac_o
mac_o said:
Hi pawitp
Thank you very much for this Rom ! I did a full wipe before flashing coming from Evil Alex Purgatory. Rom is fast and smooth but when i delete a widget on homescreen there is no "delete" button on the upper edge so i've got to keep the widget picked and "scan" the upper edge until it turns to red. Waiting for update or reflash ? But not a big thing for me.
G mac_o
Click to expand...
Click to collapse
It's currently a bug if you disable "show search bar" in launcher.
Cm11 works great on my a700 with pa-gapps and Art.
Gesendet von meinem A700 mit Tapatalk 4
Hi,
Loving it !
This is my first unofficial rom on a700 and I must recognize your fantastic work. It works great and is a major improvement compared to stock.
On top of jumping to a far more enjoyable version of Android, it brings an end to sluggish behavior AND to the below average responsiveness of the touch screen. It is like a new tab really. So THANK YOU.
One question though. I wiped everything, flashed the rom and the Gapps. At startup my memory available was only about 10Gigs...odd for a 32Gigs tab no?
The attached screenshot is where I am now. Feels like some space is missing.
What do you think?
benjieb said:
Hi,
Loving it !
This is my first unofficial rom on a700 and I must recognize your fantastic work. It works great and is a major improvement compared to stock.
On top of jumping to a far more enjoyable version of Android, it brings an end to sluggish behavior AND to the below average responsiveness of the touch screen. It is like a new tab really. So THANK YOU.
One question though. I wiped everything, flashed the rom and the Gapps. At startup my memory available was only about 10Gigs...odd for a 32Gigs tab no?
The attached screenshot is where I am now. Feels like some space is missing.
What do you think?
Click to expand...
Click to collapse
Either it's a miscalculation or some space is used where Android doesn't recognize (e.g. CWM backups).
If you run the following command from adb shell or terminal emulator, you'd be able to find out where all your storage went.
Code:
su
busybox du -d 2 -h /data
To check the actual free space, run
Code:
df /data
nice
continuous fc's of gapps and bootloop
i came from pawitps cm10.2 and installed cm11 plus the gapps given in the first post of this thread. i did a dirty upgrade (no full wipe) and everything worked well. then i decided to change from dalvik to art. the tablet rebooted and converted all the installed apps. since then i have continuous fc's of gapps which renders the tablet unuseable as the error messages pops up that fast and frequently that i have no chance to get access to the apps in the background. i then forced a shutdown by pressing the power button for several seconds and tried to restart the tablet. no success it hangs now showing the new cm-logo with the turning arrow around it.
a reflash of the rom did not help (as expected as the bad config telling it to use art instead of dalvik is still there). at the moment i am downloading an updated package of gapps from 12.12.2013 to flash it and see if that helps.
my next step would be downgrade to cm10.2 to get it back running.
any advice about how to change from art back to dalvik without the need of flashing an older rom is very appreciated. by the way, am i the only one who has tried out the new art vm? anyone having success to use it?
greetings
peter
peter_altherr said:
i came from pawitps cm10.2 and installed cm11 plus the gapps given in the first post of this thread. i did a dirty upgrade (no full wipe) and everything worked well. then i decided to change from dalvik to art. the tablet rebooted and converted all the installed apps. since then i have continuous fc's of gapps which renders the tablet unuseable as the error messages pops up that fast and frequently that i have no chance to get access to the apps in the background. i then forced a shutdown by pressing the power button for several seconds and tried to restart the tablet. no success it hangs now showing the new cm-logo with the turning arrow around it.
a reflash of the rom did not help (as expected as the bad config telling it to use art instead of dalvik is still there). at the moment i am downloading an updated package of gapps from 12.12.2013 to flash it and see if that helps.
my next step would be downgrade to cm10.2 to get it back running.
any advice about how to change from art back to dalvik without the need of flashing an older rom is very appreciated. by the way, am i the only one who has tried out the new art vm? anyone having success to use it?
greetings
peter
Click to expand...
Click to collapse
If you look at the linked page, you'd see that one of the gapps package is marked as not ART compatible
Boot into recovery and hope that you have adb shell access, then run
Code:
mount /data
rm /data/property/persist.sys.dalvik.vm.lib
Otherwise, you'd need to do a data wipe/factory reset.
peter_altherr said:
i came from pawitps cm10.2 and installed cm11 plus the gapps given in the first post of this thread. i did a dirty upgrade (no full wipe) and everything worked well. then i decided to change from dalvik to art. the tablet rebooted and converted all the installed apps. since then i have continuous fc's of gapps which renders the tablet unuseable as the error messages pops up that fast and frequently that i have no chance to get access to the apps in the background. i then forced a shutdown by pressing the power button for several seconds and tried to restart the tablet. no success it hangs now showing the new cm-logo with the turning arrow around it.
a reflash of the rom did not help (as expected as the bad config telling it to use art instead of dalvik is still there). at the moment i am downloading an updated package of gapps from 12.12.2013 to flash it and see if that helps.
my next step would be downgrade to cm10.2 to get it back running.
any advice about how to change from art back to dalvik without the need of flashing an older rom is very appreciated. by the way, am i the only one who has tried out the new art vm? anyone having success to use it?
greetings
peter
Click to expand...
Click to collapse
Hi, im using pa-gapps and they work perfectly with art. I had art on the a700 for a short time enabled but since xmbc doesnt work with art yet i had to go back :/ I believe on the top of the website where you can download the gapps suggest in first post is written that they dont support art yet. Dont know why pagapps work well with art and the official cm gapps dont. I recommend a full wipe, reflash cm11 and install pa-gapps.
http://forum.xda-developers.com/showthread.php?t=2397942
thank you pawitp for your excelent work on porting cm11 to our A700 and also for the hint regarding the gapps problem. i just did not notice that they are not art compatible. thanks also to BonzenPaule for the hint with pa-gapps. i have flashed this one: pa_gapps-stock-4.4.2-20131212-signed.zip and at the moment the tablet is rebuilding the apps-cache. so i will see if the boot process completes. i will report as soon as it finishes.
greetings
peter
pawitp said:
Either it's a miscalculation or some space is used where Android doesn't recognize (e.g. CWM backups).
If you run the following command from adb shell or terminal emulator, you'd be able to find out where all your storage went.
Code:
su
busybox du -d 2 -h /data
To check the actual free space, run
Code:
df /data
Click to expand...
Click to collapse
Hey, very helpful. I now see that I have huge amount of data in data/media... Very odd thing is that it contains every thing i had in "sdcard" in my previous stock setup... BUT it does not show in my current "sdcard". Despite wiping everything it seem to still be there. Have I missd something in the process?
benjieb said:
Hey, very helpful. I now see that I have huge amount of data in data/media... Very odd thing is that it contains every thing i had in "sdcard" in my previous stock setup... BUT it does not show in my current "sdcard". Despite wiping everything it seem to still be there. Have I missd something in the process?
Click to expand...
Click to collapse
CWM is designed not to wipe the "sdcard" when wiping data. However due to multiple users support, recent versions of Android do not recognize the content. You should use move the files into /data/media/0.
Sent from my Nexus 4 using xda app-developers app
the very simple way to upgrade lasted CMW is download ROM MANAGER from ggplay
thanks @scoobyjenkins
I see there's this new CM11 going, and thanks to @Hashcode who solved most of the complex problems already, here's my first stab at CM11 on our Nook HDs that installs into internal memory (EMMC).
The install is a lot similar to how it was done in CM10.2 days, but you will need a new recovery image (and a new sdcard image for those doing initial install):
So, For Nook HD+: Initial ovation sdcard image (cwm) | ovation recovery image (CWM)
For Nook HD: hummingbird Initial sdcard image | hummingbird recovery image (CWM)
I did some light testing and things seems to be working for whatever light loads I came up with, but still there are probably tons of problems that I have not yet noticed. Please write in the comments about what's broken and I'll try to fix it. Once it's good enough, I'll try to get official nightlies going for CM11 as well, I guess.
Latest CM11 EMMC images are now available as CM11 nightlies at:
For Nook HD+ get ovation builds
For Nook HD get hummingbird builds
There also might be experimental builds available referenced below in the history section.
(Also for completeness, For Nook HD+ sdcard image cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
For new Installs:
Download the initial sdcard image
ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
Instert the card into your nook and reboot
Flash the recovery image
Flash cm11 image
Flash whatever other extra things you need like gapps
remove the sdcard
reboot the nook
For upgrades from CM10.x (the only tested are 10.2 and 10.1). If you have any problems after upgrade - you'll need to do factory reset to clear /data:
Download recovery zip and CM11 install and place it on the nook
Reboot into recovery you already have installed
Flash the recovery zip you just downloaded
reboot into recovery again (This is important! Failure to do this will botch your upgrade and you'll need to wipe /data) so that the new recovery is started.
Install CM11, install other stuff you need like gapps
reboot
enjoy
Note: After upgrade you will need to reenter all of your wifi passwords.
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (usually only needed on official CM builds, as otherwise you can use Quick Settings panel): USBHostSwitcher.apk
Known problems:
- attempting to reformat external sdcard from android crashes volume manager - seems to be upstream problem of some sort. The sdcard is left in some strange state, so don't do it. (if you did, reformat the sdcard on your PC, all data will be lost either way)
Changelog:
2014/11/297 - Bring sdcard build to current source version:
* cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip
2014/08/17 - Bring sdcard build to current source version:
* cm-11-20140817-UNOFFICIAL-ovation-sdcard.zip
2014/01/18 - Fixed 1080p movie playback on Nook HD+:
* cm-11-20140118-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140118-UNOFFICIAL-ovation-sdcard.zip
2014/01/17 - Fixed headset mic issue
* cm-11-20140117-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140117-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140117-UNOFFICIAL-ovation-sdcard.zip
2014/01/15 - Switched to TI wpa supplicant, should fix a bunch of wifi-related issues
* cm-11-20140115-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140115-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140115-UNOFFICIAL-ovation-sdcard.zip
2014/01/09 - Fixed inability to write to sdcards.
* cm-11-20140110-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140110-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140110-UNOFFICIAL-ovation-sdcard.zip
2014/01/08 - Misc updates: autodetect sdcard format, not just vfat. fuzzy touch patch courtesy of D Marble, bt-pan services that reportedly fix bt tethering for some people.
* cm-11-20140109-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140109-UNOFFICIAL-hummingbird-emmc.zip
2014/01/06 - Initial release
* cm-11-20140106-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140106-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip
The screen kept flickering like a tube light few times.
Thank you! Welcome back
Sent from my BN NookHD+ using xda app-developers app
Welcome back, you've been missed greatly. I kept telling everyone not to panic, you would be back.
Sent from my BN NookHD+ using XDA Premium HD app
Thanks dude. I was hoping you'd start building it. Downloading now!
Working well so far. Thanks for making it and glad to have you back.
for those who need gapps you could see below (Be sure to choose 4.4.2 gapps.)
Link for PA gapps : http://forum.xda-developers.com/showthread.php?t=2397942 <MINI MODULAR PACKAGE 121 MB>download link http://goo.im/devs/paranoidandroid/roms/gapps-mini/pa_gapps-modular-mini-4.4.2-20131230-signed.zip
My personal favorite is BaNK's gapps : http://forum.xda-developers.com/showthread.php?t=2012857 <core gapps only, 17MB>download link http://www.androidfilehost.com/?fid=23269279319195954
Thanks for starting the work again -- I can't wait for official nightlies. And welcome back.
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Nice to see this, I've used Bokbokan's eMMC build off his blog with TRIM support by default (MAG2GA ver06 10/2012), and I've used yours with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
It would be interesting to know if it presents visible differences from CM 10.2 regarding responsiveness, especially with ART enabled. It's the last fort to be conquered with our nooks (trim+art). Sadly my nook is not back yet so any reports would be welcome.
Awesome
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
jjjooonnn said:
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
Click to expand...
Click to collapse
It should be updatable via the settings once it's an official built. Right now, all of the builds are unofficial ones, so they have to be fully downloaded and flashed.
verygreen is the official device maintainer for CM though, so once he "approves" of the build, it will be built nightly by the CM servers, and then it will be fully integrated into their update mechanism (or CyanDelta if you use that). Just like the 10.2 builds.
TeutonJon78 said:
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Click to expand...
Click to collapse
It's on the todo list, but cwm was easier to make at first (as in, next to zero effort)
jjjooonnn said:
Does this build come with TRIM enabled?
Click to expand...
Click to collapse
Yes, this has TRIM-enabled kernel, though I have not decided if I should do it for the official releases.
Have there been any more bricks with the trim-fixed kernels in the past couple of months?
Will this be updatable via CM updates in settings?
Click to expand...
Click to collapse
I guess yes, once there are official nightlies again. But I want to make sure it's at least of adequate quality before enabling that.
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Good job!
I can't speak for anyone but didn't see anything from a quick search in the post: TRIM FAQ. I can attest that mine works and I believe it should be one of the bad eMMC (MAG2GA ver06 not ver05).
I did test TRIM (vdc fstrim dotrim) no issues, and found the CM11 under updates (after I updated to CM11) so I can attest to that much!
Thanks for the reply
Darrian said:
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Click to expand...
Click to collapse
I would say they are about same smooth. Succulent's build has some nice framework and more option in performance settings. But just from system ui or user experience they are almost the same. Not could I tell the difference in app opening or transition.
Stock launcher Does lag when press the app drawer butter from home screen. But I use Nova launcher to solve the problem.
No find significant performance inprovememt over cm10.2 yet. Maybe Kitkat just does more job in UX polishing rather then performance.
Hopefully we could find some Performance MOD to use in KitKat.
It may very well be due to the fact that I upgraded from CM 10.2 and did not do a clean install, but for me Succulent's build was extremely laggy, many apps froze frequently, and when too many apps (more than like 3) were open it would reboot itself. I have none of those problems with this build, it's super smooth and fast and I haven't had any apps become laggy or crash or reboot my tablet. And this is upgrading from CM 10.2>Succulent's KK>Verygreen's KK; I still haven't done a factory reset and don't plan to unless it becomes necessary later. I use Nova as well. I'm not saying Succulent's build is bad, I thought it was bearable enough to use and was planning on using it long term, updating with each new build until it got to where I thought it should be, but then I installed this build and the difference is staggering. If I reflashed Succulent's build and wiped my data partition I might have a better experience, but now that I have this I don't see any need to.
this is great, glad to see you're back =)
my nook is currently being borrowed, i was wondering if anyone could quickly benchmark it?
thanks
Thank you Verygreen for this new build.
I will try it today.
I have 2 questions about CM11 and Nook HD+ hardware:
- did the HD+ have a bluetooth low energy (BT 4.0) chips?
- did the HD+ have a Low-power audio playback (kitkat new feature) capable chips?
If yes, is it included in this new CM11 build?
Thanks
Edit:
I found that Nook HD+ has wl1271l chip and uses wl12xx driver. That chip is BT 4.0 and BLE. See here http://www.rfm.com/products/data/wls1271l.pdf
But this thread show that BLE isn't activated in CM.
verygreen said:
久しぶりでした
(Also for completeness, For Nook HD+ sdcard image cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
Click to expand...
Click to collapse
Thanks verygreen. Great to see your are back in action.
The SDCARD image link is downloading emmc image. Here is the correct like if any one is looking.
cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip
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!
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: