At pershoots request, here is the official nightly discussion thread. I will be updating this with information that I find and users posts that are helpful. REMEMBER: THIS IS A WORK IN PROGRESS SO ALWAYS READ THE THREE POST FOR UPDATED INFORMATION
CyanogenMod 10.1 is a free, community built distribution of Android 4.2 (Jelly Bean) which greatly extends the capabilities of your tablet.
New CM Wiki page! http://wiki.cyanogenmod.org/index.php?title=Main_Page
New CM Documention! http://wiki.cyanogenmod.org/index.php?title=Documentation
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Usual CM disclaimers:
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.
*/
Known Issues (copied from droidbasement):
-A random flicker (it’s faint and fast) can be observed occasionally/infrequently. If this becomes a nuisance to you, you can try to alleviate this by selecting ‘Disable HW overlays’ in Developer Settings. This does not survive a reboot (must be selected on every boot) and impacts swiping motion (it slows it down) in Trebuchet (the Launcher).
-P4*: A 720P recording, when played back, will have artifacts in the upper section of the image. Also when launching the recorded video for the first time, you will encounter a bit of a delay before it launches.
-P4*:If you use the standard GAPPS (from goo), the keyboard will close if typed on for 2 or 3 letters quickly in succession, if you use Google Search, Messaging and/or Gtalk (there could be more). This is a GAPPS library issue. Install a third party keyboard (Swiftkey 3 works ok) and switch to it. This does not affect Browser, System, etc (stock KB works fine there). The GAPPS from wingray don’t appear to exhibit this behavior from brief feedback (make sure your system is cleaned out using the latest recovery (format system), prior to installing the rom and gapps if you had the set from goo installed prior (it has also been reported that data needed to be wiped as well to rid of the residuals)): http://forum.xda-developers.com/showpost.php?p=35825009&postcount=3553
-Wallpaper will be down aligned on the lockscreen.
Things that need work from the community:
Samsung Keyboard Layout
Tell me more
CWM:
Make sure you have the latest (CWM 6.0.3.0)
Download from pershoot website, select your Tab version below:
P7510 (Wifi Only)
http://droidbasement.com/galaxy/roms/cm10.1/p4wifi/
P7500 (3G+Wifi)
http://droidbasement.com/galaxy/roms/cm10.1/p4/
SCH-I905 (Verizon)
http://droidbasement.com/galaxy/rom...//droidbasement.com/galaxy/roms/cm10.1/p4tmo/
Download recovery.tar.md5 and flash with ODIN or Mobile ODIN
Links for ODIN 1.85 : MediaFire
Links for Mobile ODIN by Chainfire Play Store and XDA
Bootloaders: Make sure you update your bootloaders to ICS. People who flashed an ICS custom ROM coming from HoneyComb (3.1) do not have the correct bootloaders.
Download Bootloaders from pershoot site: http://droidbasement.com/galaxy/roms/cm10.1/
Locate your variant and flash with ODIN. *NOTE: MOBILE ODIN DOES NOT FLASH BOOTLOADERS. ONLY ODIN WILL
Bootloader Flashing Instructions: (see image attached to post if unclear)
1) Open ODIN, all settings should be at default, if you change anything, hit reset or make it the same as image attached.
2) Select PDA slot and select the bootloader.tar file.
3) Flash
4) If unclear about the instructions, please ask!
Modems:
Download the recommended modem for your device at droidbasement:
http://droidbasement.com/galaxy/roms/cm10.1/
Install instructions are in post #3
P4 Variants Downloads: (Please see READ ME in post #2 to avoid and confusions or headaches)
P7510 (Wifi Only)
http://get.cm/?device=p4wifi&type=nightly
Changelog: http://mobile.10.1.cmxlog.com/?device=p4wifi
P7500 (3G+Wifi) (You must be on the ICS modem for best results.)
http://get.cm/?device=p4&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4
SCH-I905 (Verizon) (You must be on stock ICS (and it’s modem) before flashing to this build, for LTE functionality)
http://get.cm/?device=p4vzw&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4vzw
SGH-T859 (T-Mobile)
http://get.cm/?device=p4tmo&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4tmo
gapps: (update 01/29/2013)
P75xx gapps: gapps-jb-20130129-P75xx.zip http://www.mediafire.com/?44xhky6dyx4wlw2 Credit to dreamcwli from his thread on Xoom My Android ROM 4.2.1 for original package (Please thank him for the gapps)
Known Issues if using Goo Inside gapps or other gapp packages:
-Hot word detection for Google Now (caused the Google Now crash when starting)
-Gesture typing (causes random crashes when enabled)
-Photosphere (crashing when selecting camera or after aligning shot)
These features are removed in P75xx gapps.
Removed any Google Apps (e.g. Play Music, Sound Search, Calendar, Gmail) that can be downloaded in Play Store: https://play.google.com/store/search?q=Google+Inc.&c=apps
Credits:
pershoot for his hard work
Cyanogen for his amazing ROM
CyanogenMOD Team for their awesome work
Follow CyanogenMOD Team:
Google+
Twitter
PSA from CyanogenMOD about non-NEON future support: https://plus.google.com/u/0/117962666888533781522/posts/8wcuSVkr7zR
READ ME:
#If using 4.2.2 and want to roll back to 4.2.1 (last build is Feb 13th), you will need to do a full wipe to move backwards or you will bootloop. (update 02/19/13)
#PSA from CyanogenMod team: https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq (update 02/19/13)
ADB Whitelist
As of the Android 4.2.2 update, when you connect your phone to a computer, you are presented with your computer's RSA key fingerprint to open the adb connection. You also have the ability to permanently trust the computer, so you don't have to repeat this step upon every re-connect.
In order for this to work, you must be on the latest SDK which will grant you an updated 'adb' binary.
We will not be introducing any functionality to sidestep this default security, so if you don't update, you will lose the ability to access the device using adb.
# CM 10.1 is based on Android 4.2.1. Any and all proprietary applications that you have installed outside of CM should be updated to their 4.2.1 counterparts. Do not use the 4.1 versions of proprietary applications, else you will experience difficulties.
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal.
# You do not need to wipe when updating to 10.1 if coming from an earlier CM version. However, as we mentioned in the weekend's PSA, users updating (instead of wiping) will experience a conflict in the application data for the Clock app. You are advised to clear this apps data on first boot of 10.1.
# Another item to note is that the support for the 10.0 feature that allowed for an expanded number of targets on the pattern lockscreen is not in 10.1. If you use this lockscreen, disable it before updating from 10.0.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0. Credit to post from CyanogenMOD team (G+ https://plus.google.com/+CyanogenMod/posts/9X561GFMxL5)
Coming from Samsung ICS ROM (custom or not) requires a FULL WIPE (Wipe Data, Cache, and Dalvik Cache) If you do not WIPE you will get a bootloop.
From droidbasement:
GT-P7500 (p4), GT-P7510 (p4wifi), SCH-I905 (p4vzw) and SGH-T859 (p4tmo)
-For P4VZW: You must be on stock ICS (and it’s modem) before flashing to this build, for LTE functionality
-For P4WIFI UK: You must be on the US ICS bootloader (odin .tar.md5 inside the .zip in the folder), otherwise you may incur a rolling screen
-For P4: You must be on the UK ICS bootloader (odin .tar.md5 from AUS inside the folder), otherwise you may incur a rolling screen.
-For P4*: You must be on the ICS modem for best results.
BEFORE REPORTING ANY BUGS, PLEASE DO A FULL WIPE AND FLASH AGAIN TO VERIFY THE BUG! ALSO, NOTHING WILL GET FIXED WITHOUT A LOGCAT (we cannot debug xda posts, need a logcat)
Getting a logcat:
1) Make sure ADB is installed (http://developer.android.com/sdk/index.html)
2) Open Command Prompt
3) adb logcat -d > logcat.txt
4) Locate the logcat and upload to xda
Install Instructions: IMPORTANT TO SEE READ ME IN POST #2 It will save you a lot of headaches when upgrading or updating your Tablet.
1) Install the latest CWM (see 1st post for more info)
2) Install ICS bootloaders (1st post) *People who flashed an ICS custom ROM coming from HoneyComb (3.1) do not have the correct bootloaders.
3) Boot into CWM and flash CM10.1 (Please see READ ME in post #2 for more information)
4) Flash gapps-jb-20130120-P75xx.zip (see 1st post for download)
5) Reboot
pershoot has stated before: "best to wipe as some experience lag with multi user." and "if you get any latency/ bizarro behavior, wipe"
F.A.Q
Want Adobe Flash on your Jellybean Tab? (update 05/21/13) New version is (11.1.115.58)
Check out the latest download here: http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html Scroll to Flash Player for Android 4.0 archives and download most current (11.1.115.58). *Note: Flash is not supported in Jelly Bean, no support given in this thread as well.
Need Developer options and Performance tabs?
Go to settings>About tablet and start tapping Build number until it says your a Dev.
I am getting sudden reboots or freezes?
Not all tablets are created equal, if you are experiencing sudden reboots after Overclocking, reset your options back to default.
I am still rebooting or freezing?
Do a full wipe and DO NOT install anything. If the tablet is not rebooting or freezing, install your apps one at a time to isolate the cause. If you are using Titanium Backup, DO NOT RESTORE DATA FOR SYSTEM APPS.
I get Force Closes (FC) when I launch ____ app?
Try clearing data for the application by going Settings>Apps and locate the app and select Clear Data.
How can I increase Launcher performance?
Enable wallpaper hack (Settings> Launcher>Homescreen) and select Wallpaper quick render to boost home UI response (when using a static wallpaper).
Once I am on CM10.1, do I need to continue getting my updates at get.cm?
No, you can update future nightly builds by going to Settings>About tablet>CyanogenMod updates. Once there, change Update types to "New Versions (incl. Nightlies)" *NOTE: Pay attention to the file name, you might occasionally see CM 9 or 10 in the list, DO NOT FLASH!
Can I enable Voice Calling on my tablet?
At this time, the framework has the hook enabled to allow for users to work on the feature. IT IS 100% UNSUPPORTED at this time because it requires you to flash modems which is a deviation from the recommended setup.
I flashed ___ from another___ thread, now ___ this stopped working?
Wipe data and flash CM 10.1 from get.cm, does this issue still happen? If so, post logcat... if not, seek support from the thread you flashed the file from.
I HATE the new layout with the navigation keys in the middle, can I move it?
At this time, the nav keys in the middle is the design. Who knows, CM Team might change this in future builds.
OH NO! Where did my previous CWM backup go?
4.2. changed the file structure on how internal storage is viewed. Data on the internal/fake sdcard will go to 0/ (i.e. /sdcard/0/; /data/media/0/) (both are the same thing).
Since the internal storage is emulated, it is setup now (using file explorer like ES) /mnt/shell/emulated then you will see /0/; /legacy/; /obb/; and /clockworkmod/. Copy clockwordmod folder to your PC and if you need to, flash back to old ROM with old CWM and then move the backup back to /sdcard and then restore.
Using the latest recovery, to find /sdcard while in recovery, you will need to adb to /data/media/. *Note: Make sure to have a copy on your PC, I ran out of space before restoring since it is all in the /data.
Hey! Did you see the easter eggs!!
So not only is there an easter egg when you press the Android version and long press on the jellybean, but if you hit CyanogenMod version, CM planted one too. But did you know that by doing the easter egg and long pressing on the jellybean, you unlock another one! Go to Daydreams under Display in settings and you will see BeanFlinger!
My sound is really low or really high when I am using headphones!
If you are having really low or high volumes while listening with headphones, I recommend Voodoo Sound from Supercurio in the Play Store (Link). This allows you to take control of your volume and change it to your preferences.
I see cm-10.1-xxxxxxxxx-UNOFFICIAL-p4xxxx.zip on Droidbasement, what's the difference between droidbasement builds and nightlies?
The UNOFFICIAL builds on droidbasement are experimental builds compiled by pershoot for testing. It is recommended to flash the nightly builds unless specifically asked to test an unofficial build.
Awesome man and thanks...
Sent from my GT-P7500 using Tapatalk 2
Crazy question, where is dev options located? can't seem to find it anywhere.
Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
kiladubz said:
Crazy question, where is dev options located? can't seem to find it anywhere.
Click to expand...
Click to collapse
Go to About in settings and hit the Build Number until it says your a Dev now
eddai said:
Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
I am going to need more information about Voice calling since I have the Wifi only model. If someone else can chime in about multi user would be great, I haven't tested multi user yet.
nakedninja42 said:
Go to About in settings and hit the Build Number until it says your a Dev now
Click to expand...
Click to collapse
oh, rock on dude, thanks!
eddai said:
Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Not sure about voice calling... but as far as user account limits, I don't believe there are any beyond the physical limitations of the internal storage.
Sent from my Nexus 10 using Tapatalk HD
kbluhm said:
as far as user account limits,
Click to expand...
Click to collapse
i've capped it at +3.
https://github.com/CyanogenMod/andr...mmit/b6458e0209ecee044dfb338f9dae98c29efdfcc6
How can I check which bootloader I am currently on?
Dreameagl said:
How can I check which bootloader I am currently on?
Click to expand...
Click to collapse
You can't if you are not sure, then you should flash the one on droidbasement (see OP).
pershoot said:
i've capped it at +3.
https://github.com/CyanogenMod/andr...mmit/b6458e0209ecee044dfb338f9dae98c29efdfcc6
Click to expand...
Click to collapse
Any Solution for creating more? ı need more than 5+. Dont ask why
ı am running unofficial Build of Cm 10.1 (D2dyno's build) and, outgoing voice calls working perfectly, but no incoming calls tablet doesnt rings.
Any idea for your work?
Thanks for Reply.
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
eddai said:
Any Solution for creating more? ı need more than 5+. Dont ask why
ı am running unofficial Build of Cm 10.1 (D2dyno's build) and, outgoing voice calls working perfectly, but no incoming calls tablet doesnt rings.
Any idea for your work?
Click to expand...
Click to collapse
sorry, i'm not increasing it more at this current time.
that unofficial rom is my device/vendor/kernel specific work + all of the cyanogenmod team's framework/system/build/misc work (from quick scan of the op's thread).
voice calls you are on your own with (the hook is enabled in the framework overlay so people can do what they will with it). you need to flash a separate modem for it. there's a thread around here where discussions were being held for it and people were attempting to fix some stuff regarding it.
Great thread. BTW I don't have KW issue on wingray's gaaps.
me_guitarist said:
Great thread. BTW I don't have KW issue on wingray's gaaps.
Click to expand...
Click to collapse
+1; everything is working great on P4vzw. Thanks to the OP for putting this thread together and to Pershoot for keeping the 10.1 alive and well.
Thanks ninja for creating this thread. The other one has grown too big. Cheers!
Sent from my GT-P7510 using xda app-developers app
Nice work
Wow. Great job Pershoot and team!
Running absolutely wonderful on the Google I/O P7510.
Been following your builds on droidbasement for the last 6 months. Glad to see it in the nightlies now.
Thanks for keeping this device alive.
Why is Google now often not working
Running the nightly with wingray gapps. It runs pretty good .
There were crashing issues with Google Now a while ago as well for CM10. What I'd so special about that app that it crashes way more easily than other apps?
Related
°°°
Attention: This ROM is discontinued!
It still works great as a daily driver and got a large userbase, but as CM10.1 has been abandoned there won't come any new updates anymore!
After working really hard on it for more than 2 month(!) I proudly present my first CM10.1 T-Build :fingers-crossed:
I put lots and lots of effort into it to create a great, smooth and bugfree rom experience for you guys.
I tried to fix all huge bugs on CM10.1 like bluetooth fast forwarding and the wifi hotspot.
Additionally I took the time to create a non-neon gapps package, as the official 4.2 one does only support neon.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you appreciate all the effort that has gone into this ROM then consider a donation.
While it's neither expected nor required it is highly appreciated!
> Paypal Donate link <
Each donator will get a huge thank you and a private dance show
Preview (you can't wait for the leafs getting down now, can you!):
(and as I've been asked a couple times in the past: yes, you can send me an amazon gift card code via PM as wel!)
CM Known Bugs & Fixes:
This list shows what has been done so far.
As you can guess by the sheer amount of the fixed bugs there has been put lots and lots of time into this ROM.
And don't forget about all the awesome work pengus77 has put into the kernel - without him we would still suffer from bsods and huge battery drain.
Do NOT post or ask about stuff on the known bugs list!
The bug is listed here - I don't need to get reminded that it's there.
If there's progress or an ETA or anything we will post about it - if not there's not.
I really mean it! Do not ask, it's just annoying. It might only lead to us abandoning the work on the bug.
Oh check the "plans for the next build" section below as well.
But of course you're very welcome to post a decent fixing idea or development related note in'te the CM10.1 development discussion.
Hall of shame of people who ignored my warnings and still posted about already known bugs.
If someone continuously breaks this threads rules you'll land on my ignore list.
tonyp (damn!)
CM10.1 specific bugs:
Bluetooth is accellerating on many headsets fixed (by replacing the bdroid bt stack with bluez)
Wifi hotspot isn't working fixed (by forwardporting the CM10 internal hotspot handling to CM10.1)
SDCard write speed is subpar. not fixed
bugs affecting all CM10+ based ROMs (unordered list):
unable to reject calls on SU660 basebands fixed
low brightness after unlocking fixed
automatic time on SU660 and v30x basebands is broken fixed
wifi & 3g drain fixed (Kowalski Kernel)
notification lights aren't working fixed
zram is selected at 18% but isn't enabled fixed
init..rc contains some parameters interfering with the kernel configs fixed
bootanimation gets displayed "too long" fixed
CM10.1 Performance CPU settings aren't compatible with our Tegra CPU fixed
you can't bind the searchkey to actions like opening the recent app drawer fixed
FM radio isn't working fixed (see here)
In-Call muting fixed
Call forwarding fixed
autobrightness isn't working properly semi-fixed (kk120+ - kernel instead of ROM controlled, so you can't control it in the ROM, but via a sysfs)
Stock camera has some drawbacks (especially panorama & hdr) semi-fixed (by his or this ported LG Stock camera)
HDMI isn't usable not fixed
no signal after airplane mode bug (double press data or reboot to gain it back) not fixed
Changes and cherrypicks to the CM10.1 codebase:
Major Changes:
The codebase is CM10.1.0 RC4
fixed all the bugs above
incuded tiny non-neon gapps
Development settings enabled by default
Advanced reboot enabled by default
tonyp memory management added and enabled by default
(you can turn it off at Settings - Performance - Memory management)
purgeable assets enabled by default
enabled Pie Controls
Vibrations lowered (no, you can't change it back easily)
removed the autobrightness configuration options
(it's kernel controlled, you can't change it in the ROM!)
removed Videoeditor (and some LWPs)
added the awesome epic Kowalski kernel as prebuilt
(including KowalskiManager, alsa mixer and tx power stuff)
added a ****ing epic easteregg
Cherrypicks:
added more options to rebind the hardwarekey
added more options to the lockscreen longpress buttons
(including screen off! save the power power button some presses!)
option to pull down the Quick Settings panel when there are no new notifications
added a notification drawer brightness slider
option to disable the CRT animation
Center Clock option
Text-only batterystyle
Quickmemo framework support
Option to disable the lockscreen Camera widget
Custom carrier text
Recents RAM bar
much much more - read the changelogs linked at the end of the next post
Plans for future builds:
Bugs fixes:
-
Other:
GCC 4.7 experiments
CREDITS:
arcee and the CM team for all the work they did.
pengus77 for his awesome work at the kernel and new bootloader.
niko (Andrei E.) for his work on including the bluez stack into android.
marsgod for fixing the callbug on the old bootloader.
wkpark for the cracked ICS bootloader, the ramhack idea, and all is valid input.
goo.im, AndroidFileHost and vadonka for providing me great hosting services.
I got a bug - can I report it?:
If you want me to take the time to help and fix your bugs I expect you to take the time and do this properly!
Quick check: Did you do a full wipe before installing build 01? If not you need to do that first!
Check the known bugs section. If it's listed or mentioned there, drop it (and wait patiently if it'll get fixed eventually).
Use the search function and try to find if others have been posted about it.
You're only at the app and can't properly search within a thread?
Then wait until you're at home and report the bug from there!
Check the last 3 pages if the bug has been mentioned there.
You still with me? All of this takes too much of your precious time?
Then use another ROM!
Still nothing? Then report the bug in this thread.
Always attach logs to your bugreport!! Bug reports without logs will get ignored completely.
Study this for more details: [Reference] How to get useful logs
People who fail in doing this properly will get into the hall of shame.
Downloads:
ROM:
By downloading and/or using this ROM you agree to the guidlines of this thread:
Read and understand the entire OP!
Yes, it takes a couple minutes - but what's that compared to the 2+ month I put into the ROM??
Don't be a douchebag!
Follow the rules!
If you agree click the button and download the ROM :fingers-crossed:
Download: http://tonyp.basketbuild.com
Make sure to download the correct version for your bootloader!
Mirror: http://goo.im/devs/tonyp
Gapps:
This ROM already has tiny gapps included! That's a minimum gapps package (<20mb)
I put a lot of effort into integrating the required apps and libs and tested it carefully.
I choose this approach because of the many problems that the standard package causes to our non-neon Tegra2 phone.
Included are only the most basic (g)apps like Playstore, Talk (with working videochat), Calendar sync provicer etc.
If you want to remove the included gapps flash this package after flashing the ROM:
CM10.1-gapps-remover-tonyp.zip
For those of you who want the "full" gapps package including Google Now, TTS, Faceunlock, voice search etc. I worked on a full non-neon gapps package.
Get it from this thread: Non-neon Gapps (Android 4.2) dev-discussion thread
Do NOT flash any other gapps package - they aren't compatible with our phone!
If you accidently did that then format /system and reflash the ROM.
This is necessary to prevent bugs like like the keyboard closing while typing.
Addons:
You can download my officially supported addons from the addons folder:
http://goo.im/devs/tonyp/CM10.1-T-Builds/addons
This ROM has native support for Quickmemo.
For more details read this post.
I've build patches for OpenPdroid and PDroid2.0.
For more details read this post.
Kernel:
kowalski kernel thread
This ROM comes with the awesome kowalski kernel by pengus77.
For new versions (which come regularly) check out his thread!
Various:
TWRP recovery for both bootloaders
my modded adb drivers
Instructions:
Updating to a newer T-Build::
No wipes or system-format needed!
Choose the correct ROM for your bootloader
Flash the ROM
Flash the latest kowalski kernel
Tiny Gapps are included, so there's no need to flash gapps if those are enough for you.
If you want the full gapps package use the non-neon one I provide here.
If you want to remove gapps flash this package after flashing the ROM: CM10.1-gapps-remover-tonyp.zip
Reboot
Coming from another ROM:
If you're on the newbl either use pengus CWM 6.0.2.5 or my TWRP!
Other recoveries won't work.
oldbl users can use any CWM >5 or TWRP version.
Do a full wipe!
Just do the wipe, you will be thankful afterwards when everything does run better.
Format /system
Choose the correct ROM for your bootloader
Flash the ROM
Flash the latest kowalski kernel
Tiny Gapps are included, so there's no need to flash gapps if those are enough for you.
If you want the full gapps package use the non-neon one I provide here.
If you want to remove gapps flash this package after flashing the ROM: CM10.1-gapps-remover-tonyp.zip
Reboot
Don't restore system apps (like Settings) or system data (like Wifi data) with TitaniumBackup!
My personal recommended configuration:
Go to Settings - Performance - Processor and change the "Maximum CPU frequency" to 1200 (or even 1500) and "Set on Boot"
Open the KowalskiManager
enable the 3 power saving options at the top
lower TX Power to 11
Change the SD readaheads to 512
enable dynamic fsync
This ROM comes pre-configured with the following memory management changes:
zRAM enabled with 18%
tonyp memory management enabled
purgeable assets enabled
Changelog:
T-Build 01
T-Build 02
T-Build 03
T-Build 04
T-Build 05
Let me leave with a couple more notes:
This ROMs focus is stability! It's intention is to be a daily driver without the need to constantly flash new updates - that's why I kept you guys waiting that long and didn't release my daily testbuilds (more like 3 builds a day actually) which haven't been perfectly stable, yet.
That's why I took CM10.1 M3 as a base and don't merge in nightly features - everything in this ROM should be well tested and fully working.
I only picked memoryleak fix that's been discovered after M3.
I won't cherrypick each and every feature that's in some other ROM!
If there's a real useful addition that I personally like I will do it, but the fancy stuff has to go into other ROMs.
You guys know me - I am mostly patient and don't mind slight offtopic posts.
For completely offtopic posts you can use the CM 10.1 discussion thread.
... but I hate people who are lazy and don't do their own research. I spent countless hours on this ROM, I think I can expect you to spent a little time before asking questions.
I am not a vendor who's obligated to release a ROM for the phone - I am doing this in my free time for you and me.
So please - don't behave like a total noob. Or [email protected] and I will have a busy fishlapping time
F.A.Q. - Frequently Asked Questions:
How can I swap the mounting points for internal SD card and external SD card?
If you're on the new bootloader, flash this script via Recovery (thanks, @C0D3N1N3R!). For those on the old bootloader, you need this one instead (thanks, @SWTR!).
Which gapps package should I use with this ROM?
Seriously? You haven't been paying attention, have you? Go read the posts above this one!
Which PDroid version should I use?
It's a matter of personal preference, actually. Try both and see which one fits your needs the best. Keep in mind that if you're switching between Openpdroid and PDroid 2.0 (or viceversa) you need to uninstall the app and re-flash the ROM first, or else this kitten will die and it'll be in your conscience forever! I'm serious!!
Just flashed this ROM via recovery and can't get past the boot logo, what's wrong?
Chances are that you're using the wrong Recovery. Try pengus' CMW v6.0.2.5 and flash the ROM again. If the problem persists, check that the ROM zip file isn't corrupted (see each build's md5 hash on tonyp's goo.im CM10.1 folder). If none of that helps, then you better get Tony some logs
How can I know which bootloader my device is using?
An easy way to indentify this is by seeing the bootloader logo that appears when you turn on your device: white -> old bootloader, pink -> new bootloader.
How can I set a custom DPI on this ROM?
You can either use the Google Play DPI Fix Tool, or Tony's personal recommendation: Xposed in combination with Xposed App Settings (link down, use this one or this one instead for now) (see reference by @rugglez).
Viber doesn't work on this ROM, I can't even make a call. What can I do?
According to what we have read, recent versions of Viber won't work on CM 10+ for our device. Apparently, the developers of the app were been notified about the issue and they might look into it soon. Worry not, my friend, since not everything is lost. According to @engine24, Viber version 2.3.6.338 seems to be working alright. Make sure you uninstall your current version of Viber first before installing this one, though!
Battery drain is a bit too high, what's happening?
If you just flashed this ROM, please do one or two full battery charge cycles and see if it helps. Also, check on BetterBatteryStats for rogue apps keeping your device awake (and this is definitely worth a read!).
My screen goes bright before unlocking / after locking?
It's a known issue when using autobrightness. There's no fix for this at the moment.
My GPS takes ages to get a lock, how can I fix it?
Try the latest version available of the Google Specific No-SSL AGPS patch by @crypted. Unpack the gps.conf file and copy it into /system/etc/ using a root file explorer (set permissions to rw-r--r--). Optionally, you can add ro.ril.def.agps.mode = 1 to build.prop (find it in /system folder) but only if you're still having problems after applying the patch.
And, in case you're wondering, the answer is no: this patch won't be integrated into the ROM, so don't ask ... or will it?
Edit: that damn Tony added it to T-Build 3, so this is no longer necessary (unless he decides to drop it hehe)
Hardware Search key is not working!
Go to Settings > System > Hardware keys and make sure that Enable custom actions is checked. Also, change Search key action to In-app Search.
Spoiler post
Well the title says it all
Spoiler nr1. here is a screenshot of battery life with this rom and KK121...
Yeah im already curious...........tout de meilleur frère :laugh:
Waiting for upload to finish....merci
rmrajm1 said:
Yeah im already curious...........tout de meilleur frère :laugh:
Waiting for upload to finish....merci
Click to expand...
Click to collapse
Already finished, tony has great upload speed hehe
Loving the structure and text of the thread, though, same with the pictures
Sent from my LG-P990 using xda premium
Can:t w8!! Good job guys!!
Sent from my LG-P990 using xda premium
Oleeeeee
Gesendet von meinem LG-P990 mit Tapatalk 2
Thanks alot , well done .. will be testing it in moments
Congrats for the release tonyp. I've been with your test builds since I found them so I'm waiting eagerly to try this final build.
Thanks for the great work!
great job done.....I am thrilled to try a CM ROM....will report a feedback....
I am sure it will rock
CONGRATS and THANKS for the hard work.
Congrats downloading it
Sent from my LG-P990 using xda premium
This sounds great. Thank you for the sacrifices you've made a big investment in this old phone that can still be done to compete with the newer devices.:thumbup::beer:
Sent from my LG-P990 using Tapatalk 2
tonyp congratulations.
Thanks for your hard work
Sent from my LG-P990 using xda app-developers app
Yeah... downloading... :victory:
I found the easter egg.. :laugh::good:
Subscribed and ready for fishslapping... xD
Downloading and flashing too.
Thank you tonyp!
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 <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 UNOFFICIAL builds? A version of CyanogenMod not compiled by CyanogenMod's build servers and may contain code not yet committed to the repository. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Downloads
Latest build:
http://www.mediafire.com/?mzjrx8sxmigzl
Google Apps:
PA Team: http://forum.xda-developers.com/showthread.php?t=2397942
CM Team: http://d-h.st/users/dhacker29?fld_id=27426
Installation
- First time flashing CM11 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM7/CM9?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from CM10/CM10.1?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally restore /data from Nandroid Backup (the update will wipe your /data)
Optionally install the Google Addon
- Upgrading from CM10.2?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from another build of CM11?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Note: The partition layout of CM11 is the same as CM10.2.
Known Issues
Please do not report bugs if it is already listen in the list of known issues
Display issues in Browser & other embedded webviews (Google Chrome works fine)
No access to TV-Out menu
Layout issues in lockscreen
Can only mount 1 sdcard on PC
Menu soft-buttons appearing where they shouldn't
Some CyanogenMod features a missing - please do not file bug reports for those.
Color calibration & vibration intensity does not get saved
Users of CM9/CM10/CM10.1 may have to upgrade to CM10.2 first if they face set_metadata_recursive error during install
Reporting Bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
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. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone 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:
FAQ
Why is there no transparent status bar/lockscreen widget/"OK Google"?
Those features have been disabled by Google for low RAM device in order to save RAM. You can try enabling it by removing "ro.config.low_ram=true" from /system/build.prop, however, it is not an officially supported setup.
Changelog
20131116
Initial release
Credits:
Nelson - Team Passion - Join Us on FB for Android related and friendly discussions!
FaultException, Pawitp and CyanogenMod Team
All users and developers contributing to development
Enjoy!
-- Reserved --
-- * Reserved *--
Good Job.
excelent...
Downloading, will post about ROM features later.
Now, i can menage to port ROM's with more features, because of you.
You are best
Nice thanks 4 this.. will try asap.
Sent from my SAMSUNG-SGH-T959 using xda app-developers app
after some using of ROM
ROM is totaly OK.
I know it was hard work, and thank you.
BAD THINGS:
1. Its little buggy, slow, with some '' better '' kernel, it should fly.
2. Hmm, icons, are stocks like in 4.3.1 Android, except camera, settings and and voice search.
3. Menu icons, are in 6x4, it look very ugly for me.
4. Camera is buggy. - NO 720p record -
5. Status bar pulling down is buggy to.
GOOD THINGs:
1. New dialer, very good.
2. After log into play store, you got new Gallery from Google, editing pictures very exposed and good.
3. New keyboard +
4. Other 4.4 goodies.
SCREENSHOOT:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Galaxy3HELL said:
ROM is totaly OK.
I know it was hard work, and thank you.
BAD THINGS:
1. Its little buggy, slow, with some '' better '' kernel, it should fly.
2. Hmm, icons, are stocks like in 4.3.1 Android, except camera, settings and and voice search.
3. Menu icons, are in 6x4, it look very ugly for me.
4. Camera is buggy. - NO 720p record -
5. Status bar pulling down is buggy to.
GOOD THINGs:
1. New dialer, very good.
2. After log into play store, you got new Gallery from Google, editing pictures very exposed and good.
3. New keyboard +
4. Other 4.4 goodies.
Click to expand...
Click to collapse
Thanks for the review.
I can look into fresh start of kernel later on.
Remember, CM has just started work over KK sources... merging of features is still in progress and this may take some time.
According to me, it is more fluid than JB which will let me keep this as daily driver.
neobuddy89 said:
Thanks for the review.
I can look into fresh start of kernel later on.
Remember, CM has just started work over KK sources... merging of features is still in progress and this may take some time.
According to me, it is more fluid than JB which will let me keep this as daily driver.
Click to expand...
Click to collapse
yeah, you are probably wright.
I,m sure that kernel will solve lots of problem.
Take look at mackay kernel on i9000 forum, he also have 4.4 KitKat ROM.
Fluid, it is, but Vanir 4.3.1 is at the moment most fluid rom on this forum.
Don't get me wrong, great ROM, love you.
Bye!
Galaxy3HELL said:
yeah, you are probably wright.
I,m sure that kernel will solve lots of problem.
Take look at mackay kernel on i9000 forum, he also have 4.4 KitKat ROM.
Fluid, it is, but Vanir 4.3.1 is at the moment most fluid rom on this forum.
Don't get me wrong, great ROM, love you.
Bye!
Click to expand...
Click to collapse
I can compile Mackay, if required.
neobuddy89 said:
I can compile Mackay, if required.
Click to expand...
Click to collapse
That would be great
Can you do that?
Awesome ROM Neo! I'm trying it right now and its really AWESOME! Enabled ART asap; apps open quick and are generally fluid. (Hangouts stutters when scrolling though) Scrolling over to Google Now stutters slightly, but thats to be expected with the first release. This is really good! Stable enough to be daily driver for me :good:
mackay has to be compiled from inside rom source.
cannondaleV2000 said:
mackay has to be compiled from inside rom source.
Click to expand...
Click to collapse
I can change that.
Downloading mackay kernel as zip file since I can't fork it as I already have forked one from CM.
I forgot to add FaultException to Credit list... adding..
neobuddy89 said:
I can change that.
Downloading mackay kernel as zip file since I can't fork it as I already have forked one from CM.
Click to expand...
Click to collapse
cool i thought about doing that but never had time to really look at it. would you mind sharing the parts needed for standalone build after you get it working? i want to build the kernel for my cappy.(hardbricked my vibrant) but i dont want to sync all the source since i dont maintane roms
cannondaleV2000 said:
cool i thought about doing that but never had time to really look at it. would you mind sharing the parts needed for standalone build after you get it working? i want to build the kernel for my cappy.(hardbricked my vibrant) but i dont want to sync all the source since i dont maintane roms
Click to expand...
Click to collapse
I will share on github if ready.
However, you may need to take care of its ramdisk which I believe should be same.....
Great start, appreciate your work.
got error status 7 coming from vanir. even tried flashing right after but still failed. tried rebooting recovery while while still in same session then was greeted by a message saying i lost root and gave me an option to flash su so i did, after doing so my phone rebooted on its own then finally some progress as i seen the cm splash screen then went into recovery which happen to be a new one. proceeded to flash tom again wiping everything minus sd flashed rom, install finally went through.
this is just about the fastest this phone has been since cm7, really...
stock cam fcs, at least with PA gapps
and for some reason, I cant get the ok google to work with this phone..tried updating search and everything
daily driver worthy, however
laylovj said:
this is just about the fastest this phone has been since cm7, really...
stock cam fcs, at least with PA gapps
and for some reason, I cant get the ok google to work with this phone..tried updating search and everything
daily driver worthy, however
Click to expand...
Click to collapse
Stock Cam working fine here with CM gapps. 720p definitely working.
To enable ok google, lockscreen widgets, and transparency in the status bar, you have to delete ro.config.low_ram=true from the build.prop. Neo mentioned this in the OP under FAQ. OK Google and the rest work perfectly fine after deleting it. :good:
Hobbesfed said:
Stock Cam working fine here with CM gapps. 720p definitely working.
To enable ok google, lockscreen widgets, and transparency in the status bar, you have to delete ro.config.low_ram=true from the build.prop. Neo mentioned this in the OP under FAQ. OK Google and the rest work perfectly fine after deleting it. :good:
Click to expand...
Click to collapse
never was a reader..still am not
anyway, reflashed again and PA gapps stock cam seems to work now..weird.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Great Devs have been working hard for our little device. Hats off to them.
This thread aims to reduce flooding of queries not related to development in dev threads
so as not to hamper their work.
And hopefully not to flood other devices' forums as well.
Let's discuss here, provide logcats if necessary and report bugs to help the developers.
CyanogenMod 11.0 is a free, community built, aftermarket firmware distribution of Android 4.4.4 KK(),
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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
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.
From CM11 Dev thread.
Current issues (06/10/2014)
OMX codecs (for accelerated audio/video - may never be solved)
SIM unlock doesn't work (you must remove your SIM lock in another device/ROM)
Video recorder
First-time installation:
Read first posts of DEV Thread:
1.http://forum.xda-developers.com/showthread.php?t=2766229
ClockworkMod v6 is mandatory to install CM11.
Download the latest full OTA build for cooperve from:
RC9: http://download.androidarmv6.org/_builds/cooperve/stable/
Nightlies: http://download.androidarmv6.org/_builds/cooperve/
Quote of dev: psyke83
"IMPORTANT!!! mandatory recovery
update required for cm11 builds later
than 23/07/2014
IMPORTANT!!!
As of 23/07/2014, all CM11 builds for the
bcm21553 series will be switched over to
the MTD flash drivers. In order for these
packages to work correctly, you must first
flash an MTD-compatible recovery (CWM
v6.0.5.2 or later only).
Don't flash the updated recovery until a)
you've backed up your data, b) the CM11
23/07/2014 build (or later) is available,
and c) you're ready to switch to the MTD
build.
How to update to MTD build:
Download an MTD-compatible recovery
(linked below) and a full CM11 OTA build
dated 23/07/2014 (or later).
Perform a full backup using the old
recovery (mandatory!)
Flash the updated recovery, and reboot
into the new recovery.
In the new MTD recovery, perform a data-
wipe, and manually format /system (this
step is critical in order for your partitions
to be properly converted to the mtd/
yaffs2 format - don't ignore it!)
Flash the CM11 package.
Once you've data-wiped and flashed the
initial MTD build, future CM11 updates
can be installed normally (delta or full
packages, as you desire).
Notes:
Older ROMs will no longer be compatible
with the MTD recovery and yaffs2-
formatted partitions. If you wish to use a
stock/modded Gingerbread ROM, CM7 or
CM9, you should wait until MTD versions
of these ROMs become available.
If you want to go back to a non-MTD
ROM, you must flash an entire stock ROM
(CSC+MODEM+PDA) via Odin, or else
your partitions will be stuck in MTD
format."
###_________________
MTD-COMPATIBLE RECOVERY @Post #308 by lesikvip
###_________________
Some Screens:
Full Screenshots: http://forum.xda-developers.com/showthread.php?p=54014189
Gapps link: http://madteam.co/forum/index.php?topic=6285.0
How to update (via OTA):
Please consult the cm-ota instructions on Jenkins.
Summary of major work done:
Forked broadcomCM devices into androidarmv6 repository (forked from ics branches).
Initial changes needed for cm-11.0 have been committed to cooperve, tassve, totoro and bcm21553-common device trees.
All of Broadcom's code has been adapted for the cm-11.0 branch.
After some reverse engineering of the vendor binaries, "adbd" and "init" built from source now work correctly.
ADB will now set the proper USB mode, can give a root shell, and no longer has a hardcoded dependency on /system/bin/sh,
which should help a great deal with debugging. We also no longer need to use the init prebuilt binary - the source-built version
is now compatible.
Implemented common kernel source for totoro, cooperve and tassve.
Implemented hybrid boot/recovery/charge ramdisk.
Fixed WiFi, Bluetooth, Bluetooth tether & mac addresses.
Fixed graphical performance regression on CM11 branch.
Fixed basic audio (speaker, microphone, software encoders/decoders)
Fixed GPS.
Fixed Gallery, wallpaper chooser, live wallpapers, RenderScript, and possible EGL crashes in other apps
Added workaround for SystemUI corruption
Fixed graphical corruption/stability issues (caused by buggy GL_EXT_discard_framebuffer extension)
Fixed RIL, telephony and audio routing to speakers, headset, earpiece, microphone and microphone mute.
* = this code is work in progress, meaning that it won't be available in OTA builds.
IMPORTANT NOTICES from the dev:
psyke83 said:
OK, I managed to fix routing and volume control while in-call. I've merged the changes and started OTA builds for the three devices, so that you can have a build with working telephony. Enjoy!
To see the build status (to know when they will be available from the updater):
totoro: http://jenkins.androidarmv6.org/job/cm-ota/390
tassve: http://jenkins.androidarmv6.org/job/cm-ota/391
cooperve: http://jenkins.androidarmv6.org/job/cm-ota/392
If telephony doesn't work in the tassve or cooperve builds, try updating to the latest baseband. If that still doesn't work, please send me a radio log:
Code:
adb shell logcat -b radio >radio.log
Click to expand...
Click to collapse
psyke83 said:
Folks,
If you're using Link2SD, Mounts2SD, or want a functional app2sd method, keep reading.
These applications are (IMHO) a little too intrusive to be used on my ROM. The main reason is that the apps install their respective mount scripts in a non-optimal location (/system), which can cause problems when you perform ROM upgrades. Link2SD is particularly egregious, because it overwrites a core system file with its script (/system/bin/debuggerd, which is needed by a system service), and this breaks delta updates.
In the past (for CM7), I always favoured S2E on my devices due to it being a much cleaner app2sd implementation, but it had some problems with corruption due to some (IMHO) unnecessary filesystem tweaks. Additionally, S2E doesn't yet support KitKat/CM11. With these issues in mind, I decided to release a fork of the application (called simple2ext_mod), which is focused on maximizing stability and providing support for CM11 ROMs.
I would strongly suggest that you give this app a try. If you're already using Mount2SD or Link2SD, you'll probably have some problems (as they will leave their mount scripts behind). So, it might be a good idea to do a data-wipe beforehand.
Here's the release thread: http://forum.xda-developers.com/android/apps-games/app-simple2extmod-cyanogenmod-11-t2840295
Click to expand...
Click to collapse
Im pretty sure everybody will use the cm7 and cm9 discussion thread for cm11 too.
Someone tried to install some gapps. Official gapps for cm (small version) can't install. Status 7 (with cwm 6).Banks gapps install ok but always fc's
Enviado desde mi GT-I9300 mediante Tapatalk
Hi, does CM11 required EXT4 file sistem and (or) CM7? I tried to install this on stock rom it's says E:Can't mount /data. Thanks!
Sent from my GT-S5830i using Tapatalk 2
yusrilramadhan said:
Hi, does CM11 required EXT4 file sistem and (or) CM7? I tried to install this on stock rom it's says E:Can't mount /data. Thanks!
Sent from my GT-S5830i using Tapatalk 2
Click to expand...
Click to collapse
You need EXT4 flash it on CM 7.
I have no problem with the stock firmware ask. Also there was an error Error mount / system, but I ignored her and flashed CM11 successfully!)
luilly said:
Someone tried to install some gapps
Click to expand...
Click to collapse
I tried, but all in vain. Flashing by cwm, installs successfully, the phone appears at startup window "Updating Applications", but when the system is running ... no gapps Separately, through the APK file, installs gallery, play store, sync and something else. Play market behaves erratically, often crash.
smbe.
lesikvip said:
I have no problem with the stock firmware ask. Also there was an error Error mount / system, but I ignored her and flashed CM11 successfully!)
I tried, but all in vain. Flashing by cwm, installs successfully, the phone appears at startup window "Updating Applications", but when the system is running ... no gapps Separately, through the APK file, installs gallery, play store, sync and something else. Play market behaves erratically, often crash.
smbe.
Click to expand...
Click to collapse
Wait, did you insert the SIM Card too? Cause it's only show blackscreen when using SIM Card
Sent from my GT-S5830i using Tapatalk 2
Just wanted to thank the developers for great the work.
I have closed my thread for discussion for cm7/cm9/cm10 so this is the new thread for future.
So best of luck to OP for good maintainence of discussion thread.
cooperve/cm-11-20140707-NIGHTLY-cooperve.zip
does this fix the sim card issue for cooperve?
yusrilramadhan said:
Wait, did you insert the SIM Card too? Cause it's only show blackscreen when using SIM Card
Sent from my GT-S5830i using Tapatalk 2
Click to expand...
Click to collapse
No, when you run the sim black screen ..
But the problem with crash on startup with sim solved! Firmware modem part S5360_XXMK1, through Odin.
Addressing 4pda. ru/forum /index.php? showtopic= 585296&view =findpost&p =32722332
Links can not place restrictions on the forum (10 posts)
lesikvip said:
I have no problem with the stock firmware ask. Also there was an error Error mount / system, but I ignored her and flashed CM11 successfully!)
I tried, but all in vain. Flashing by cwm, installs successfully, the phone appears at startup window "Updating Applications", but when the system is running ... no gapps Separately, through the APK file, installs gallery, play store, sync and something else. Play market behaves erratically, often crash.
smbe.
Click to expand...
Click to collapse
Thanks. We Have to Wait for a nightly which could install gapps. Thanka for this hard word guys.
Enviado desde mi GT-I9300 mediante Tapatalk
Screenshots CM11 [GT-S5830i]
Updating...
Can i put these on first post?
Thanks
patrol31 said:
Can i put these on first post?
Thanks
Click to expand...
Click to collapse
Yes, you can! @patrol31
luilly said:
Thanks. We Have to Wait for a nightly which could install gapps. Thanka for this hard word guys.
Enviado desde mi GT-I9300 mediante Tapatalk
Click to expand...
Click to collapse
Ggaps up from the usual 5830, here is the link 4pda.ru/forum/index.php?showtopic=531172&view=findpost&p=28339926. I advise you to remove setupwizard.apk, to avoid mistakes when you first start.
Cm 11 is a bit slow but in airplane mode it is fast
in notification bar it shows no internet connection and emergency calls ( blinking)
I think that is why the phone is slow
lesikvip said:
Ggaps up from the usual 5830, here is the link 4pda. ru / forum / index.php? showtopic = 531172 & view = findpost & p = 28339926. I advise you to remove setupwizard.apk, to avoid mistakes when you first start.
Original 4pda. ru/forum/index.php? showtopic=585296& view=findpost&p=32708265
Click to expand...
Click to collapse
Thanks but Error 404 in anyone link inside. Please, can you upload the gapps?
Gapps link now provided on the first post.
luilly said:
Thanks but Error 404 in anyone link inside. Please, can you upload the gapps?
Click to expand...
Click to collapse
Posted a link to a personal, if you have the opportunity to lay out in the subject as an alternative. Because I have been to most gapps problem.
Sailfish OS for Nexus 4
The porting effort is now continued by community: http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is Jolla's port of Sailfish OS for the Nexus 4 (check full address in post #3)
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about Sailfish OS please head over to sailfishos.org.
This is not an Android ROM, this is a different base of an operating system called Linux, running the GNU C library (glibc).
It only uses parts of Android for hardware enabling (drivers).
Special Thanks to the Nexus 4 porters, carepack who took over as community's release engineer, MultiROM author Tassadar, Jolla sailors especially MSameer for camera experiments, early porters Stskeeps, lbt, thp, alterego, faenil, LEDs spiiroin, sensors lpotter, USB phdeswer, the HADK team, the Mer Project, the Nemo Project and all the fine people over at #sailfishos-porters
Release Notes:
This release is based on Sailfish OS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of beta quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/android/nexus/images#instructions
b. Download links can be found here: https://developers.google.com/android/nexus/images#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4-demo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Bug reports, if internet search refuses to help:
First search XDA for keywords. Things like libsailfishapp have already been worked out by this amazing community
Software-related bugs (Sailfish OS): first search http://together.jolla.com . Tag your questions with "community-build"
Hardware-related problems: at the Nemo Project Bugzilla under Hybris-ing component
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Known issues:
OTA Updates do not work
The camera does not fully work
Android app support is not available (unlike in Jolla phone): please ask about the status for open-source Dalvik runtime framework on #sailfishos-porters on irc.freenode.net and also check this XDA Thread
All remaining: In Bugzilla
Check changelog in #2 post.
Last Updated 2014-12-11
Changelog:
Read Sailfish OS release notes:
https://together.jolla.com/question...in-upgrade-to-software-version-11038-uitukka/
https://together.jolla.com/question/50175/release-notes-software-version-10819-tahkalampi/
Release notes/Known issues in EA4:
* EXPERIMENTAL: Jolla Camera
** Viewfinder stream freezes after ~20secs so be quick to take a photo
** Video recording is not available
* EXPERIMENTAL: orientation sensor works (no PS or ALS)
** was stable during tests, but we'd ask community to attempt making HADK hybris-11.0 port of mako instead, for hopes of better sensors integration
* LED notifications work
* Devicelock including Allow untrusted software
* MultiROM support (min. v28) New to MultiROM? Read here.
** you must have Android 4.2 and cm10.1 as your primary ROM
** Instructions: http://forum.xda-developers.com/nexus-4/orig-development/mod-multirom-v24-t2472295
** two alternatives for hackers:
*** 1. you can still have Android 4.4 -based secondary ROMs, provided you inject required firmwares (check MultiROM threads)
*** 2. you can have Android 4.4 as primary, flash (physically into phone's partition) modem image from 4.2 (0.84 tested OK), and still see things working in SF and CM (tested). It is not yet supported to inject radio.img for SailfishOS only (via MultiROM menu button)
* MultiROM's awesome side-effect fix - ability to power-off the device (thanks to isolated primary ROM)
* Once USB cable plugged, it gets assigned a DHCP address by an internal phone's DHCP server
* Available USB modes: Developer Mode, Charging; untested: Tethering, Mass Storage, PC Connection
Release notes/Known issues in EA3:
* EXPERIMENTAL: Jolla Store is now available, you'll need to register with your Jolla Account
** NOTE: Booting Nexus 4 with SIM first, and then removing SIM (or vice versa) may cause Jolla Store to see it as two different devices and cause potential breakage. Please stick to either SIM available or not when running Sailfish OS on Nexus 4.
** There may be a bug with oFono RIL support that makes it not report IMEI value causing this and will be sorted out in a later update.
** DISCLAIMER: Using Jolla Store with Jolla Account might break applications on your other devices, use it at your own risk!
** Android support is not available from the Store, even if you can see Android apps listed (those will be removed eventually from store view)
** This functionality means that image comes with only minimal set of pre-installed apps. Use Store to download the ones you need.
* The backlight is dark during first launch, but can be fix by switching the currently-not-working ambient light sensor off (uncheck Settings->System->Display->Adjust automatically)
* When display is blanked, power management sets WLAN to the lowest speed state
** Can be noticed in a SSH-over-WLAN session
** Chat notifications may arrive with a slight delay
Fixes after EA2:
* Watermark removed
* Phone-call audio volume can now be changed with the help of volume buttons
* Improved responsiveness when waking phone up with the power button
* Settings->System->Developer Mode or About Product do not freeze anymore
* Reverted to the original (non-Silica) Fingerterm
Fixes after EA1:
* Phone-calls with audio work
* Timers and alarms (with device powered on) work
* HTML5 video+audio works in Browser (tested splash on http://jolla.com )
* Update is based on Sailfish OS version 1.0.5.16
Release notes/Known issues in EA2:
* If not auto-detected from SIM, set-up mobile internet data settings via Settings->System->Mobile network->(long tap on the first toggle-item under "Mobile data" section)->(enter settings given by your operator)
Nexus4-specific known issues reported by the adopters:
* Chinese text input not working
* Localhost name is shown as Jolla
* Switching between the online and offline status in the status information setting takes very long and often doesn’t switch properly
* Google contacts which are put together with different information, are now split up into several contacts in Sailfish
* The battery display seems to be a bit buggy because it loses about 15% from one second to another
* The calendar overview when filled with events seems to be a bit laggy
* The email push is not working correctly, I do not receive any emails until I push the refresh button
* Splitting words in the German translation: e.g. in the open apps on the home screen it says: "Kurzzeitmesse" and in the next line the missing "r"
* NOTE: all other Sailfish OS issues have already been reported on TJC - http://together.jolla.com - and many of them were fixed in this 1.0.5.16 release
Release notes/Known Issues in EA1:
* There has been no throughout testing of telephony related functionality (roaming, airplane mode, etc) and any use of this functionality is at your own risk
* ALS and PS Sensors, Reset device, Bluetooth, USB MTP, Bluetooth, WLAN hotspot, Camera video recording, and video playback is not supported
* The image SW is not currently upgradeable, nor is any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, or word prediction for virtual keyboard preinstalled
* This image does not include any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, Microsoft Exchange support, or word prediction for virtual keyboard preinstalled
* It is not possible to double-tap to wake up the device
* FPS drop while scrolling in homescreen due to non-batching when rendering of application icon grid
* Icons/graphics appear unproportionally small in browser toolbar, time select widget, and Settings favourite icons
For even more curious ones: there has been a huge community porting effort to numerous devices, news and photos can be found here: http://forum.xda-developers.com/showpost.php?p=54302138&postcount=2
Jolla's relnotes:
Dear early adopter of Sailfish OS for Android devices. This is important - read this whole mail through and follow all steps exactly as written.
IMPORTANT: If you choose to publish this mail through blogs, news sites, forums, or others, quote it as-is and in complete form ONLY, or people's devices may be at risk.
We're happy to publish the fourth Early Adopter Release of Sailfish OS (1.0.8.19) for Nexus 4 (mako) to you.
We have also released the EA2 version of the Sailfish OS Hardware Adaptation Development Kit (HADK), as per earlier email.
This installation image is for early adopters only, meaning we know that some things are not functional or perhaps even broken -- please see the release notes below. We are excited to get all of you properly included in the early stages of the project. Do note that this Sailfish OS image is strictly for personal and non-commercial usage only.
We've prepared a 'demo' version of the image which contains the kind of preinstalled 'marketing' content and the core apps used for demonstrations - this helps you quickly get a feel for all the interactions that are avalable on a device that has been used for a while but isn't really what you want for personal use. You can however cleanly remove the demo content.
We want to build a community around Sailfish OS for Android devices that is based on mutual trust and respect for what we are all doing. Hence -- we ask that whenever you do screenshots, videos, forum or blog posts (and we're happy if you do!) or the like, you emphasise that this is work-in-progress and not a productised release. It is important for Jolla that correct expectations are set for those who might be users of the final product -- and that they understand what they see is not a released product. If you do demo videos, take advantage of our new 'demo content' image (check availability for your device) that has pre-set contacts/imagery/messages/etc to show full functionality of Sailfish OS.
WARNING: Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hearing loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck.
NOTE: You will lose your on-device data (including /sdcard), so make a proper backup and make sure to copy that backup to your PC.*
NOTE: Make sure to read all the release notes below. Please DO NOT contact Jolla Care nor Developer Care for any issues encountered with this Early Adopters build, instead use the following communication channels:
We will all meet in #sailfishos-porters (note, new location) on irc.freenode.net and please use us (thp, alterego, Stskeeps, lbt, sledges) to work together, report any bugs, graphical glitches or missing functionality that you find, which are not included in the release notes above. You can also find the hardware adaptation source code at http://github.com/mer-hybris .
You are also welcome to participate in threads at http://forum.xda-developers.com/nexus-4/general about Nexus 4 and Sailfish OS as well as for more general Sailfish OS topics at http://forum.xda-developers.com/jolla-sailfish/general
First
Is the SailfishOS 1.0.8.19 is the newest one?
thlinh130295 said:
First
Is the SailfishOS 1.0.8.19 is the newest one?
Click to expand...
Click to collapse
Yes it is, update9 is out in September
Im on the way to flash stock 4.2.2 and downloading cm + EA4, will report again
---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------
one more question, do it need to use MultiRom? i use TWRP/CWM instead, it's ok?
thlinh130295 said:
Im on the way to flash stock 4.2.2 and downloading cm + EA4, will report again
---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------
one more question, do it need to use MultiRom? i use TWRP/CWM instead, it's ok?
Click to expand...
Click to collapse
multirom enables you to have multiple ROMs and select them at boot
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
x.0ni.x said:
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
Click to expand...
Click to collapse
what kernel you're using? You have to flash the modem of android 4.2.2 ak 0.84 or google factory 4.2.2 image.
flashable zip of modem:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
google factory image:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
and a lttle help from first post:
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
MultiROM ≥v28 ability is in the image. New to MultiROM? Read here. Check for more DIY alternatives how to layout your MultiROM in #2 post below.
Click to expand...
Click to collapse
x.0ni.x said:
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
Click to expand...
Click to collapse
Yes, 4.2.2 radio IMG needs flashing. But have no fear, we tested: primary CM11 still fully works with that, including 3G, so I don't even know what are the so-important radio.img differences there
carepack said:
what kernel you're using? You have to flash the modem of android 4.2.2 ak 0.84 or google factory 4.2.2 image.
flashable zip of modem:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
google factory image:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
and a lttle help from first post:
Click to expand...
Click to collapse
Awesome!! Thank you!! Found the radio in zip form. Fixing to flash in a few minutes!! I'll get bk to you shortly to let u know if this works! It's coming along tho. At least the camera is working and suck on this OS. Can't wait to see what the next update entails!!
x.0ni.x said:
Awesome!! Thank you!! Found the radio in zip form. Fixing to flash in a few minutes!! I'll get bk to you shortly to let u know if this works! It's coming along tho. At least the camera is working and suck on this OS. Can't wait to see what the next update entails!!
Click to expand...
Click to collapse
Read first post
sledges said:
Yes, 4.2.2 radio IMG needs flashing. But have no fear, we tested: primary CM11 still fully works with that, including 3G, so I don't even know what are the so-important radio.img differences there
Click to expand...
Click to collapse
Flashed radio image zip fill over sailfish os still no wifi connection grrrr so frustrating. I want this to work but lost now
---------- Post added at 11:36 PM ---------- Previous post was at 11:35 PM ----------
carepack said:
Read first post
Click to expand...
Click to collapse
Read it over and over tyvm
x.0ni.x said:
Flashed radio image zip fill over sailfish os still no wifi connection grrrr so frustrating. I want this to work but lost now
Click to expand...
Click to collapse
Which radio.img did you flash? Try another one, too. If you tried 0.84, then try 0.54 instead, or vice-versa. We did not test any others (and newer than 0.84 won't work)
sledges said:
Which radio.img did you flash? Try another one, too. If you tried 0.84, then try 0.54 instead, or vice-versa. We did not test any others (and newer than 0.84 won't work)
Click to expand...
Click to collapse
Tried .83. I'll download the other 2 now. Thanks again.
x.0ni.x said:
Tried .83. I'll download the other 2 now. Thanks again.
Click to expand...
Click to collapse
If you're still unlucky, could you give more info as to how exactly does the WLAN not work?
Do you enable it via Settings->WLAN (click on glowing bulb switch), then use pulley menu to "Connect to Internet" ?
sledges said:
If you're still unlucky, could you give more info as to how exactly does the WLAN not work?
Do you enable it via Settings->WLAN (click on glowing bulb switch), then use pulley menu to "Connect to Internet" ?
Click to expand...
Click to collapse
Flashed 0.54,0.83, & 0.84. Same thing for all 3. And yes that's how I'm TRYING to enable it. But it just says on that screen where u pull it down to "connect to the Internet" "unable to connect to internet. Please restart your phone". I even reflashed the ROM with all 3 radios and still nothing. I as well hit the lil "lightbulb"wifi switch in the row of like Bluetooth, mobile connection, etc. It comes on but I go to the WLAN connection to get wifi going nothing still. Same message.
I flashed 0.84 radio and Wi-Fi don't work too.
Kubino said:
I flashed 0.84 radio and Wi-Fi don't work too.
Click to expand...
Click to collapse
which kernel you're on?
try this one:
http://d-h.st/users/hellsgod/?fld_id=28949#files
If you have as first rom an cm rom then take the file with cm in the name
If you're on aosp android use the one without it. In my constellation it works quite right.
So the steps I've done:
1. I had an android AOSP rom as primary.
2. I've downloaded the kernel without cm in the name. Correct kernel is needed with kexec patch. Is included in the files
3. downloaded sfosEA4 and cm10.1 and radio 0.84
4. In android I've downloaded multirom manager from play store.
so this were my requirements. now the todo:
1. went into recovery and flash the kernel
2. went back into android / multirom manager and do the installation process
3. after some time you'll be back in android and installation is finished
4. reboot into recovery. flash modem 0.84
5. go back to android and look if everything is working
6. then back to recovery again Go -> Advanced -> add rom -> sailfish
7. then you can select 2 zips. first one is cm10.1 and second is sailfish
8. install
9. after that you'll be able to boot sailfish too. everything should be fine.
carepack said:
which kernel you're on?
try this one:
http://d-h.st/users/hellsgod/?fld_id=28949#files
If you have as first rom an cm rom then take the file with cm in the name
If you're on aosp android use the one without it. In my constellation it works quite right.
So the steps I've done:
1. I had an android AOSP rom as primary.
2. I've downloaded the kernel without cm in the name. Correct kernel is needed with kexec patch. Is included in the files
3. downloaded sfosEA4 and cm10.1 and radio 0.84
4. In android I've downloaded multirom manager from play store.
so this were my requirements. now the todo:
1. went into recovery and flash the kernel
2. went back into android / multirom manager and do the installation process
3. after some time you'll be back in android and installation is finished
4. reboot into recovery. flash modem 0.84
5. go back to android and look if everything is working
6. then back to recovery again Go -> Advanced -> add rom -> sailfish
7. then you can select 2 zips. first one is cm10.1 and second is sailfish
8. install
9. after that you'll be able to boot sailfish too. everything should be fine.
Click to expand...
Click to collapse
I have Paranoid Android 4.5 beta 2 as my primary ROM with the kernel you have as well. Also have Miui V5 installed with hellscore B47 as the kernel. I knew this in advanced as I figured Jolle was going to possibly release an update because multiROM had made it possible to finally flash it. Did all the steps provided above to my own knowledge. I think I'll delete the sailfish and start fresh. Hopefully that will work. If not may just be a bug that will be solved I'm sure. As these builds are only EXPERIMENTAL not even Alpha yet. Major bugs are to be expected. So no worries. I just really like the design of this OS outside of android.
EDIT. Are you saying to flash the radio over my primary ROM (PA 4.5 BETA 2 or the sailfish OS)? I flashed over the radio over the sailfish OS not primary. Just to be completely clear here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This ROM is Abandoned as Cyanogen pulled the plug on CyanogenMod
As soon as Lineage OS build farm is setup, it'll return as Lineage OS. A new topic will be started. In the mean time, building from source is an option.
This project is the official continuation of the http://forum.xda-developers.com/tab-s2/development/rom-cyanogenmod-13-0-tab-s2-9-7-t3397682]unofficial build.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
I used @RaymanFX's T815 image to base my cm 13.0 build on.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will be voided !
*
* 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.
*
About the ROM
Current state of ROM : testing
Everything except what's reported below is working. Nothing 'fixed' yet, first build.
What is Fixed
What is not working
Important
Fingerprint scanner not working
Minor
Limited wifi 5GHz support (channels above 100 give issues)
Compass is 180 degrees mis-aligned
About says 'Phone' instead of 'Tablet' (haven't found any other issues, other then text)
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 13.0 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Samsung Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
**********
17-07-2016 - Corrected last noop usage to bfq in /init.samsung.rc
**********
11-07-2016 - Recompile UNOFFICIAL BETA build with latest CM patches.
**********
05-07-2016 - Enabled multi user in UNOFFICIAL BETA build.
**********
29-06-2016 - 1st Nightly build
- Changelog limited to changes in gts210wifi sources, updates in gts2-common and other general parts are included via nightly system.
**********
Downloads
All CM 13.0 Nightly releases can be found here: http://get.cm/?device=gts210wifi
All UNOFFICIAL BETA versions van be found here: https://www.androidfilehost.com/?w=files&flid=68015
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/CyanogenMod/android_device_samsung_gts210wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 13.0 for Samsung Galaxy Tab S2 9.7 T810, ROM for the Samsung Galaxy Tab S2
Contributors
T_I,CTXz, Sub77, Moonbutt74, RaymanFX, Hennymcc
Source Code: https://github.com/Galaxy-Tab-S2
ROM OS Version: 6.0.x Lollipop
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-06-13
Last Updated 2016-06-27
XDA:DevDB Information
CyanogenMod 13.0 for Tab S2 9.7 wifi, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, RaymanFX, CTXz
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-06-29
Last Updated 2017-01-08
Great to see the journey resulting in an official nightly. Well done.
Sent from my A0001 using Tapatalk
Fritzy62 said:
Great to see the journey resulting in an official nightly. Well done.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks, I'm totally happy. Looks nice, even with my dark theme...
Sent from my T810 running cm-13.0
This awesome love your work just one thing when I try to format my SD card as internal it just gets corrupted why is this
Delta wolf said:
This awesome love your work just one thing when I try to format my SD card as internal it just gets corrupted why is this
Click to expand...
Click to collapse
Can't think of a reason why it should do that. (and why you should do that, with 32 Gb internal)
I'm currently out of large enough SD's so I could transfer internal to external.
Does a format as regular card work?
Can you get a logcat (start before format, stop after it failed) of the format as internal and when regular fails, one of that action as well?
Congratulations, all your hard work is paying off. Great stuff sir. Love your ROM. ?
Sent from my SM-T810 using XDA-Developers mobile app
Not sure how to get logcat but formatting as portable works while formating as internal it all goes through says Sd card is working I hit done and it says corrupted EDIT***: some other people were having this issue on different devices it appears it was an issue with cm 13 that got patched in a different nightly likely the same issue here
---------- Post added at 03:13 PM ---------- Previous post was at 02:27 PM ----------
So formating as internal still goes corrupt but when entering twrp to erase the Sd twrp says it can't mount adoptable storage unit
Thanks for your hard work.
As I am still on the "unofficial" build, do I need to clean flash the official nightly ?
Edit:
Did a clean flash, to on the safe side. Unfortunately though I still cannot get the quicksettings to. I don't even the option in my menu.
Incase embedding doesn't work: https://www.youtube.com/watch?v=tp6c60Andgk
OK so I have a floating logcat did the format and stopped it how do I send it over can't find option to save the log EDIT**** I FOUND HOW TO SAVE but won't let me upload I can send an email with it if that is OK? And only reason I'm doing it is because I have a bunch of big apps and a lot of music I had 2gb free before I erased everything and flashed cm also if I may request a close all button for closing out application
Thank you for the CM port! I am testing this on my tab and like others say, Netflix does not work (cannot find the liboecryptXXX to remove or change filename) and sd card is always corrupt no matter which option you choose (64GB SD card). Let me know if there is anything I need to send to help.
akiradavis said:
Thank you for the CM port! I am testing this on my tab and like others say, Netflix does not work (cannot find the liboecryptXXX to remove or change filename) and sd card is always corrupt no matter which option you choose (64GB SD card). Let me know if there is anything I need to send to help.
Click to expand...
Click to collapse
Netflix seems to be working for me I downloaded the tablet version from Google play store I did get a Google play services error but just closed app and opened again and everything worked fine was watching an episode of walking dead
EDIT: just tried again and now all it says is loading I prefer to use kodi so not a big deal to me
Delta wolf said:
Netflix seems to be working for me I downloaded the tablet version from Google play store I did get a Google play services error but just closed app and opened again and everything worked fine was watching an episode of walking dead
Click to expand...
Click to collapse
Where can I find the tablet version of Netflix? I only see the one app in the Play Store.
EDIT: Also - I am on version 13.0-20160629-NIGHTLY-gts210wifi - Maybe this nightly broke Netflix?
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
Delta wolf said:
Netflix seems to be working for me I downloaded the tablet version from Google play store I did get a Google play services error but just closed app and opened again and everything worked fine was watching an episode of walking dead
EDIT: just tried again and now all it says is loading I prefer to use kodi so not a big deal to me
Click to expand...
Click to collapse
Ahh, just saw this. Yeah, it appears its down. But at least ChromeCast works!
Wow. Official for the T810. Nice job! Should hopefully be somewhat soon before the 710 gets it aswell. I'm thinking of getting a 713 to learn this on. Good stuff!
Nice work! This may just get me off my year-long break from flashing.
Sent from my SM-G935T using Tapatalk
Thanks TI for all the hard work in getting this ROM running on our S2's, it's running really nice and smooth for me and I thank you and those who helped for putting forth all the effort in making it happen, it's much better than TW IMO. :good:
Idk if it's OK to post a request in this thread but can someone in the community please create a custom under/overclock/under volt kernel for this ROM? I was spoiled using the ROM and custom kernel that Engine95 made for Lollipop TW and it seemed to take my S2 to the next level especially with battery savings, adjusting the BIG processor down to 500mhz really had a noticeable impact. Idk what settings he used for the undervolting but he set the oc parameters for the little processor up to 1.6ghz and the BIG from 500 to 2.2ghz on the interactive governor and my S2 was running great. I can only imagine what this ROM would do with a similar custom kernel but I know the performance would make our S2's jump to the next level. Thanks again :good:
Is it also possible to add multi user support
pilspeda said:
Thanks for your hard work.
As I am still on the "unofficial" build, do I need to clean flash the official nightly ?
Edit:
Did a clean flash, to on the safe side. Unfortunately though I still cannot get the quicksettings to. I don't even the option in my menu.
Incase embedding doesn't work: https://www.youtube.com/watch?v=tp6c60Andgk
Click to expand...
Click to collapse
Embedded didn't work (here). Thanks for the video, learning more about android every day. I have the option set to right and when I turn it off nothing changes, so I can confirm, it doesn't work. Will have to check on the phone what it should do though and then look into it.
Delta wolf said:
OK so I have a floating logcat did the format and stopped it how do I send it over can't find option to save the log EDIT**** I FOUND HOW TO SAVE but won't let me upload I can send an email with it if that is OK? And only reason I'm doing it is because I have a bunch of big apps and a lot of music I had 2gb free before I erased everything and flashed cm also if I may request a close all button for closing out application
Click to expand...
Click to collapse
Emailing would be fine. There is a site to share logs online, but I've forgotten which one that is. (will look into that as well)
akiradavis said:
Thank you for the CM port! I am testing this on my tab and like others say, Netflix does not work (cannot find the liboecryptXXX to remove or change filename) and sd card is always corrupt no matter which option you choose (64GB SD card). Let me know if there is anything I need to send to help.
Click to expand...
Click to collapse
I'm using 32 and didn't need to format. Will test.
Nandr0idC0nsumer said:
Wow. Official for the T810. Nice job! Should hopefully be somewhat soon before the 710 gets it aswell. I'm thinking of getting a 713 to learn this on. Good stuff!
Click to expand...
Click to collapse
The T713 is snapdragin, not exynos, different base. I don't know if you can use the common we have, I guess not, as that one depends on the exynos libs.
Towle said:
Nice work! This may just get me off my year-long break from flashing.
Click to expand...
Click to collapse
A whole year without flashing? I select my devices on the option to flash... (when no image available, I'll build )
Welcome back to the light.
At the moment the rom is on phone mode. For multiuser etc. you have to set android to tablet mode.