CyanogenMod 12.1 is a free, community built distribution of Android 5.1.1 (LolliPop) which greatly extends the capabilities of your phone.
This is the UNOFFICIAL Weekly Build of CM12.1 for the AT&T HTC One XL based on current Nightlies w/ HEAVILY MODIFIED PARTITION SCHEME.
**SWITCHING TO THESE BUILDS WILL REQUIRE A FULL DEVICE WIPE. BACKUP EVERYTHING**
Our /userdata partiton is to small for LP and art opts for apps and fill up quickly. These builds provide a long term solution to this by re-arranging which partitions are used to house which files systems. Here's how it's done:
by-name/fat {~12GB US, ~23GB EU models}(previously our internal_sdcard storage) -> is now used for /data, which will include a /data/media style sdcard like what is used on newer android devices
by-name/userdata {~2.5GB} (previously our /data partition) -> is now used to house /system. This now larger /system dir is big enough to allow for full dex-preopt which will speed up first boot but results in larger zip files
by-name/system {~1.5 GB} previously used for /system is no longer used.
To hear about the latest updates and changes to CyanogenMod as a whole, please follow +CyanogenMod on Google+!
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.
*/
Installation Instructions (These are all required)
FOLLOW THESE STEPS CLOSELY
IF COMING FROM CM-12.1 OFFICIAL BUILDS
SKIP TO STEP 3
THE MODIFIED RECOVERY LISTED BELOW SUPPORTS BOTH LAYOUTS
wiping "by-name/system" as EXT4 or FAT will enable TWRP to swtich back and forth
from EVITA <-> EVITAX
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
BACKUP EVEYTHING YOU WANT TO KEEP TO A PC/OTG DRIVE WE WILL BE WIPING EVERYTHING
Flash this custom TWRP recovery that supports EvitaX scheme.
Reboot to recovery, From the "WIPE" menu choose "ADVANCED WIPE", then manually change /system to "FAT" format.
Reboot to recovery again to allow TWRP to setup the modified partition layout. From the "WIPE" menu choose FORMAT DATA, then manually wipe from the advanced wipe menu: /system, /cache, /dalvik
Reboot to recovery again to allow TWRP to setup it's storage and configs on the newly formatted /data partition
Download latest build from theflamingskull.com/evita.html .
Locate 5.1 Gapps via a quick Google search.( I prefer opengapps.org )
Use "adb push", "adb sideload", or MTP to trasfer ROM/GAPPS to device
Install ROM and gapps.
Enjoy Quick boot up and usable space for apps.
TO REVERT TO STOCK LAYOUT:
The modified recovery mounts the old "by-name/system" partition as sdcard1 for easy revert.
reboot to recovery
In recovery, wipe /system using the "Advanced wipe" menu. Select "Sdcard1" and use the "Change File System" option to convert /Sdcard1 to EXT4.
reboot to recovery, the standard fstab will load.
Wipe all partitions as instructed above and proceed to flash desired ROM/gapps.
FOR OTHER DEVS:
To build with this new layout you will need
http://review.cyanogenmod.org/#/c/124797/1
If anybody really want's to build recovery on thier own the modded
tree can be found here:
https://github.com/jrior001/twrp-htc-evita/tree/twrp-dm
List all Questions and Off-Topic discussions here
Huge thanks:
h8rift,intervigil, deck, mdmower, invisiblek, flyhalf205 - Great team to work with for the HTC MSM8960 device family.
XDA:DevDB Information
CM12.1 EvitaX Unofficial, ROM for the AT&T HTC One X
Contributors
jrior001
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: hboot 2.14 or higher
Based On: CM
Version Information
Status: Stable
Created 2015-12-17
Last Updated 2016-01-03
Reserved
Revised Partition Layout
You Sir gave my Evita a third life!
Thanks again.
Going to test it out, will report back, using f2fs on data and cache before switching twrp versions and it seems to have kept the partition scheme of that after wiping, hopefully no problems from that
Update: So it installed well, no errors i've seen, installs apks very nice and quick, no freezes of any kind, overall very solid rom
this looks awesome!!!
Sir Is there any way to use /system partition as sd card or for swap.
Toqeer said:
Sir Is there any way to use /system partition as sd card or for swap.
Click to expand...
Click to collapse
Both of those "could" be done in theory.
Its only ~1.2 GB, I didn't really even consider mounting it as sdcard because its so small.
For swap, the zram feature we already added a while back is considerably faster than swap on a ext4 partiton so I wouldn't advise doing this.
Sent from my ASUS_Z00A using Tapatalk
So installed flawlessly without any error after running couple of hours it seems heavy battery draining even 11% within 15 minutes however all other things works like a charm, will be report back after a day. One question sir can I flash torched kernel?
@jrior001 - First of all, awesome work. Evita is one of the best devices around and I've been owning it since 2013. Its so unfortunate that Evita didnt get a partition update like Jewel got. This is simply awesome.
2 questions:
What needs to be done if we decide to switch back to a sense rom?
The 1.2 GB that is free is lost/wasted? Can that be added to the 12GB? Reason i ask is, my Evita has only 16GB, which already is pretty less considering how easy it has become to find 64GB devices.
jrior001 said:
Its only ~1.2 GB, I didn't really even consider mounting it as sdcard because its so small.
Click to expand...
Click to collapse
Haha, only 1.2GB With 16GB in the hood, 1.2GB is like 16%
Can we utilize that 1.2GB space as well? Can it be added to /data so that its added space could be used as well.
:good:
Sam3087 said:
@jrior001 - First of all, awesome work. Evita is one of the best devices around and I've been owning it since 2013. Its so unfortunate that Evita didnt get a partition update like Jewel got. This is simply awesome.
2 questions:
What needs to be done if we decide to switch back to a sense rom?
The 1.2 GB that is free is lost/wasted? Can that be added to the 12GB? Reason i ask is, my Evita has only 16GB, which already is pretty less considering how easy it has become to find 64GB devices.
Haha, only 1.2GB With 16GB in the hood, 1.2GB is like 16%
Can we utilize that 1.2GB space as well? Can it be added to /data so that its added space could be used as well.
:good:
Click to expand...
Click to collapse
1. Flash your old regular twrp back and wipe everything! Reformat sdcard to fat32/vfat and reflash normal build ROM.
2. If anything it would have to be mounted as a separate "internal sdcard" similar to how the old sdcard was mounted. Its possible but its messy and confusing. I was trying to keep this as clean and simple as possible.
There was also some talk of moving cache to that partition but honestly were not gaining enough to any of it all that exciting
2.
Sent from my ASUS_Z00A using Tapatalk
is the TWRP 2.8.7.0 EvitaX version a modified recovery from the original? i already have the regular 2.8.7.0 version installed but wondering if it would accept the 12.1 EvitaX rom?
droydr said:
is the TWRP 2.8.7.0 EvitaX version a modified recovery from the original? i already have the regular 2.8.7.0 version installed but wondering if it would accept the 12.1 EvitaX rom?
Click to expand...
Click to collapse
If you want to use this modified ROM, then the modified EvitaX recovery is required. It is matched to the new partition layout. This is not optional.
Sent from my ASUS_Z00A using Tapatalk
Hi jrior,
First of all, everything is working great! Thank you so much for your efforts!
I've two questions, though.
1. The ROM says that there is an upgrade and suggests what looks like a regular CM12.1 download. If I let it upgrade, it will bootloop, right?
2. What if I want to install another ROM using the same configuration? Would I have to rebuild the entire ROM or would it be enough to replace storage_list.xml, fstab and init.target.rc? I see that there is also a mk file there which implies that something must be built. What if I skip this step?
Thanks!
thelonewolf_pav said:
Hi jrior,
First of all, everything is working great! Thank you so much for your efforts!
I've two questions, though.
1. The ROM says that there is an upgrade and suggests what looks like a regular CM12.1 download. If I let it upgrade, it will bootloop, right?
2. What if I want to install another ROM using the same configuration? Would I have to rebuild the entire ROM or would it be enough to replace storage_list.xml, fstab and init.target.rc? I see that there is also a mk file there which implies that something must be built. What if I skip this step?
Thanks!
Click to expand...
Click to collapse
1. Yes this is a problem I can't work around, luckily my recovery won't let you flash that build.
2. Yes that ROM would need to be rebuilt. The storage.XML gets imbedded in frameworks.jar and can't just be copied ROM to ROM
Sent from my ASUS_Z00A using Tapatalk
jrior001 said:
1. Yes this is a problem I can't work around, luckily my recovery won't let you flash that build.
2. Yes that ROM would need to be rebuilt. The storage.XML gets imbedded in frameworks.jar and can't just be copied ROM to ROM
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Cool, thanks man!
So, there is actually one feature (so far) that I'm missing in the PAC ROM, namely: ambient display. That is, the display would come on whenever I pass my hand over the phone. This was actually very useful for me, and battery penalty was minimal. I remember trying to cook this into some other ROM, and managed to get the options showing in the settings menu, but the thing never actually worked for me. Would you know how to add this feature?
Otherwise, it's a great ROM, everything is super smooth, zero glitches so far.
Hey jrior001 man,
Can I waste a couple of minutes more of your time?
So, I'm trying to get your ROM to have ambient display. I installed xposed and added a module that enables it in settings (effectively, it does the same thing as recompiling SystemUI and framework-res and changing flags like doze_display_state_supported and config_dozeAfterScreenOff. I guess you know what I'm talking about. I looked at the original java code, and all it seems to do is enter the daydream state with some special mode enabled.
So, everything seems to be working great, but instead of getting the dimmed black-and-white display, I get nothing, the display stays blank. Doze is working though, because the moment I touch the screen, it comes up in full color just as it should. So, it does wake up and enter daydream, but just doesn't show anything.
Now, looking at logcats at that time, here's what I see:
Code:
E/qdoverlay( 160): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Operation not permitted
E/qdoverlay( 160): static bool overlay::eek:verlay::displayCommit(const int&, uint32_t): commit failed
E/qdhwcomposer( 160): hwc_set_primary: display commit fail for 0 dpy!
E/qdoverlay( 160): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 160): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 160): == Bad OVInfo is: mdp_overlay z=0 fg=1 alpha=255 mask=-1 flags=0x40000 id=-1
E/qdoverlay( 160): src msmfb_img w=736 h=1280 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-1
E/qdoverlay( 160): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 160): Ctrl commit failed set overlay
E/qdhwcomposer( 160): configureLowRes: commit failed for low res panel
E/qdoverlay( 160): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 160): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 160): == Bad OVInfo is: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x20000 id=-1
E/qdoverlay( 160): src msmfb_img w=736 h=1280 format=13 MDP_RGBA_8888
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-1
E/qdoverlay( 160): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 160): Ctrl commit failed set overlay
E/qdhwcomposer( 160): configure: configMdp failed for dpy 0
E/qdhwcomposer( 160): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Operation not permitted
E/qdhwcomposer( 160): hwc_sync: acq_fen_fd_cnt=1 flags=0 fd=15 dpy=0 numHwLayers=3
This repeats many times until the phone goes back to sleep or until I touch the screen and wake it up.
Strangely enough, regular daydreams do work, and clock, for example, displays fine on a dimmed black-and-white screen.
Any ideas where to look?
Thanks in advance!
thelonewolf_pav said:
Hey jrior001 man,
Can I waste a couple of minutes more of your time?
So, I'm trying to get your ROM to have ambient display. I installed xposed and added a module that enables it in settings (effectively, it does the same thing as recompiling SystemUI and framework-res and changing flags like doze_display_state_supported and config_dozeAfterScreenOff. I guess you know what I'm talking about. I looked at the original java code, and all it seems to do is enter the daydream state with some special mode enabled.
So, everything seems to be working great, but instead of getting the dimmed black-and-white display, I get nothing, the display stays blank. Doze is working though, because the moment I touch the screen, it comes up in full color just as it should. So, it does wake up and enter daydream, but just doesn't show anything.
Now, looking at logcats at that time, here's what I see:
Code:
E/qdoverlay( 160): Failed to call ioctl MSMFB_DISPLAY_COMMIT err=Operation not permitted
E/qdoverlay( 160): static bool overlay::eek:verlay::displayCommit(const int&, uint32_t): commit failed
E/qdhwcomposer( 160): hwc_set_primary: display commit fail for 0 dpy!
E/qdoverlay( 160): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 160): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 160): == Bad OVInfo is: mdp_overlay z=0 fg=1 alpha=255 mask=-1 flags=0x40000 id=-1
E/qdoverlay( 160): src msmfb_img w=736 h=1280 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-1
E/qdoverlay( 160): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 160): Ctrl commit failed set overlay
E/qdhwcomposer( 160): configureLowRes: commit failed for low res panel
E/qdoverlay( 160): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 160): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 160): == Bad OVInfo is: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x20000 id=-1
E/qdoverlay( 160): src msmfb_img w=736 h=1280 format=13 MDP_RGBA_8888
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 160): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-1
E/qdoverlay( 160): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 160): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 160): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 160): Ctrl commit failed set overlay
E/qdhwcomposer( 160): configure: configMdp failed for dpy 0
E/qdhwcomposer( 160): hwc_sync: ioctl MSMFB_BUFFER_SYNC failed, err=Operation not permitted
E/qdhwcomposer( 160): hwc_sync: acq_fen_fd_cnt=1 flags=0 fd=15 dpy=0 numHwLayers=3
This repeats many times until the phone goes back to sleep or until I touch the screen and wake it up.
Strangely enough, regular daydreams do work, and clock, for example, displays fine on a dimmed black-and-white screen.
Any ideas where to look?
Thanks in advance!
Click to expand...
Click to collapse
We need like 3 patches for it to work... I'll try to grab them and get another 12.1 evitaX build up tom maybe.
Sent from my ASUS_Z00A using Tapatalk
jrior001 said:
We need like 3 patches for it to work... I'll try to grab them and get another 12.1 evitaX build up tom maybe.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
cool! thanks!
thelonewolf_pav said:
cool! thanks!
Click to expand...
Click to collapse
Build is up w/ambient included. May never see that on official builds though, my patches already got rejected.
Sent from my ASUS_Z00A using Tapatalk
jrior001 said:
Build is up w/ambient included. May never see that on official builds though, my patches already got rejected.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
you just made my day! thanks!
Related
First I must thank @ aorth, and @ garyd9. Without these guys, this would not be here. Please smash their thanks button when you see them.Thank you guys so much. Much if not all of this is gard9's mod's just ported to our device. In fact until I make any relevant edits this thread will remain tagged [PORT].
Beta 4 up. Stock Clocks and voltages built a version with voltage tables intact, but lowering even one of them by the min(25mV) and applying in SetCpu causes panic.
Beta testers needed. You know the drill. Backup and feedback is always appreciated.
Im almost positive all 6200 kernel partitions are on mmcblk0p5, you can double check with 'get pit' & heimdall. Mobile Odin says it supports P6200 and works fine. I honestly can not say for sure, but Im 99% confident this is the case. Those with any rare models, please be Warned!Flashing a kernel to the incorrect partition is asking to be bricked.--please put both custom and stock on sdcard in case you cannot boot.--
The 2 .zips that have zImage at the end, are to be extracted and flashed with Mobile Odin(recommend Pro to wipe), or heimdall.
Keep in mind if you use Mobile Odin and it doesnt boot, you will be stuck. Good idea to have stock loaded for heimdall, or stock .zip wit CWM Recovery.
The other 2 that start with GT-P6200 can be flashed in recovery. <WARNING>: SOME People have had to wipe /data ; factory reset to get past stuck boot logo.</WARNING> I have updated the install script, so cache and dalvik should be totally cleared.
Either way my custom binary count hasnt changed any.
Features
custom bootanimation support: place appropriate botoanimation.zip in: /system/media/ with permission rw-r--r--. The ICS one garyd made us works lovely. Im using the xda TV one. link coming soon:
Busybox in /sbin.
Support for init.d scripts. (Personal warning about Supercharger scripts: Nitro lag nullifier is OK, but I dont recommend using the I/O tweaks, put me in a boot loop everytime. Be Warned. Also his 3G tweaks made my 3G speeds worse.)
Removed a lot of debug stuff.
unsecure kernel (adb shell gives root)
reboot bootloader and reboot download support
(quick boot in market is a great app)
Enjoy!!
reserved
Beta 4 up: 3/20
Removed OC/UV, stock clocks and voltages. tried a build with Gary's table sysfs in there, UV even one frequency by 25mV and pressing apply in SetCpu caused seizure. At least were stable now. Im not too concerned about battery life. There are other tweaks we can apply.
github: still updating..
https://github.com/crotoloandroid
Established on LA2 (SER). Far so good, thanks.
Putting it through its paces right now
Thanks
SetCPU set to 200 min, 1400 max
OnDemand governor. No other changes.
Nenamark1: 55.6 fps (no previous record)
Nenamark2: 41.1 fps (47.7 fps pre-oc)... very erratic performance
Stability Test, HQ CPU&GPU, 6 minute test: CPU passes, 7. GPU passes, 55. No failures
GL Benchmark v2.1 (All Tests): Passed, however can't upload to GLBenchmark.com as their captcha service is ****ed
Only one issue I've come across so far, and this is the same issue RichardTrip was having when he compiled some custom kernels for me earlier this year. Random wakelocks bring the tab out of sleep and turn the screen on.
These are caused by the usb scanner looking for external USB devices...
Code:
D/UsbService( 3447): setUsbObserverNotification :: titleId = 0, messageId = 0, icon = 17302785, visible = false, dismissable = false
D/usbhost ( 3447): new device /dev/bus/usb/001/004
D/usbhost ( 3447): usb_device_open /dev/bus/usb/001/004
D/usbhost ( 3447): usb_device_new /dev/bus/usb/001/004 fd: 298
D/usbhost ( 3447): usb_device_new read returned 259 errno 4
D/UsbService( 3447): usbDeviceAdded : device :: /dev/bus/usb/001/004 [1519h:0020h] [02h,00h,00h] (CDC Control)
D/UsbService( 3447): isBlackListed :: deviceName = /dev/bus/usb/001/004
D/UsbService( 3447): isBlackListed :: mHostBlacklist[i] = /dev/bus/usb/001/002
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz2 subClass=0
E/UsbService( 3447): continue...
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/NotificationService( 3447): cancelNotification - pkg:android, id:17302785
D/TabletStatusBar( 3529): setVisibility(View.VISIBLE
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
D/dalvikvm( 6436): GC_CONCURRENT freed 358K, 11% free 6800K/7559K, paused 2ms+1ms
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/KeyguardViewMediator( 3447): setHidden false
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [02h,02h,01h] (CDC Control)
E/UsbService( 3447): isBlackListed :: clazz = 2, subClass = 2, protocol = 1
E/UsbService( 3447): isBlackListed :: clazz2 subClass=2
D/UsbService( 3447): usbDeviceAdded : interface :: /dev/bus/usb/001/004 [1519h:0020h] [0ah,00h,00h] (CDC Data)
E/UsbService( 3447): isBlackListed :: clazz = 10, subClass = 0, protocol = 0
E/UsbService( 3447): isBlackListed :: clazz10 subClass=0
D/UsbService( 3447): turnOnLcd ::
D/PowerManagerService( 3447): reactivateScreenLocksLocked mProxIgnoredBecauseScreenTurnedOff=true
I/PowerManagerService( 3447): Ulight 0->3|0
I/PowerManagerService( 3447): setTargetLocked mask=2 curValue=0.0 target=95 targetValue=95 delta=6.3333335 nominalCurrentValue=0
I/PowerManagerService( 3447): scheduling light animator
I/power ( 3447): *** set_screen_state 1
D/KeyguardViewMediator( 3447): onScreenTurnedOn, seq = 3
D/KeyguardViewMediator( 3447): notifyScreenOnLocked
D/KeyguardViewMediator( 3447): handleNotifyScreenOn
D/LockScreen( 3447): updateLayout: status=Normal
D/PowerManagerService( 3447): enableLightSensorLocked enable=true mAutoBrightessEnabled=false
D/PowerManagerService( 3447): jumpToTargetLocked targetValue=95: 2
I/PowerManagerService( 3447): Light Animator Finished curIntValue=95
I/OrientationDebug( 3447): [WindowOrientationListener] in enable(), now call SensorManager.registerListener()
D/SensorManager( 3447): registerListener :: handle = 4 name= MPL accel delay= 60000 Listener= [email protected]0c5dc38
D/MPLSensor( 3447): handle : 4 en: 1
D/MPLSensor( 3447): enabled_sensors: 16 dmp_started: 0
D/MPLSensor( 3447): MLSetMPUSensors: 70
I/MPL-ml ( 3447): Actual ODR: 25 Hz
D/MPLSensor( 3447): set_power_states > MLDmpStart()
I/ ( 3447): mpu3050_resume: Resuming to 0070
D/MPLSensor( 3447): setDelay : handle=4, delay=200000000
I/ ( 3447): mpu3050_suspend: suspending sensors to 0000
I/ ( 3447): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 3447): Actual ODR: 25 Hz
I/ ( 3447): mpu3050_resume: Resuming to 0070
D/MPLSensor( 3447): setDelay : handle=4, delay=60000000
I/ ( 3447): mpu3050_suspend: suspending sensors to 0000
I/ ( 3447): mpu3050_suspend: Will resume next to 0070
I/MPL-ml ( 3447): Actual ODR: 25 Hz
I/ ( 3447): mpu3050_resume: Resuming to 0070
V/WindowManager( 3447): Setting event dispatching to true
D/KeyguardViewMediator( 3447): setHidden false
D/WifiStateMachine( 3447): ConnectedState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65659 when=-1ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65659 when=-1ms }
E/wpa_supplicant( 3807): initalize the scan timer ( 7 )
D/WifiService( 3447): ACTION_SCREEN_ON
I/ScreenReceiver : ( 4156): android.intent.action.SCREEN_ON
D/ProximityScreenOff( 4156): ScreenReceiver : action = android.intent.action.SCREEN_ON State: IDLEPhoneOn = false
D/WifiStateMachine( 3447): ConnectedState{ what=65618 when=-5ms arg1=1 }
D/SensorManager( 4156): registerListener :: handle = 8 name= GP2A Proximity sensor delay= 10000 Listener= [email protected]
I/ProximityScreenOff( 4156): SensorMonitor onStart::Registered
D/WifiStateMachine( 3447): ConnectedState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65591 when=-12ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65591 when=-13ms }
D/WifiStateMachine( 3447): ConnectedState{ what=65608 when=-13ms arg1=1 }
D/WifiStateMachine( 3447): ConnectedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): SupplicantStartedState{ what=65549 when=-13ms }
D/WifiStateMachine( 3447): DefaultState{ what=65549 when=-14ms }
D/WifiStateMachine( 3447): ConnectedState{ what=65613 when=-14ms }
D/WifiStateMachine( 3447): ConnectModeState{ what=65613 when=-14ms }
D/WifiStateMachine( 3447): DriverStartedState{ what=65613 when=-14ms }
D/JuicePlotter.CollectService( 4252): battery:48, plugged:0, screen:95, wifi:true(0kb/s), apn:false(0kb/s), bluetooth:false,cpu:2
W/googleanalytics( 4331): Store full. Not storing last event.
D/SurfaceFlinger( 3267): Screen about to return, flinger = 0xa920
chrisrotolo said:
1st I must thank @ aorth, and @ garyd. Without these guys, this would not be here. Please smash their thanks button when you see them.Thank you guys so much. Much if not all of this is gard9's mod's just ported to our device.
Beta testers needed. 100% working and stable for me. UWAXME - Malyasia Tab
Im almost positive all 6200 kernel partition is on mmcblk0p5, you can double check with get pit & heimdall. Mobile Odin says it supports P-6200 and works fine. I honestly can not say for sure, but Im 99% confident this is the case. Those with any rare models, please be Warned!--please put both custom and stock on sdcard in case you cannot boot.--
the 2 .zips that have zImage at the end, are to be extracted and flashed with Mobile Odin(recommend Pro to wipe), or heimdall.
Keep in mind if you use Mobile Odin and it doesnt boot, you will be stuck. Good idea to have stock loaded in heimdall, or stock .zip wit CWM Recovery.
the other 2 that start with GT-P6200 can be flashed in recovery.
Either way my custom binary count hasnt changed.
As Im short on time at the moment I will make this brief and update this thread shortly.
contains:
custom bootanimation support place usual in: /system/media/bootanimation.zip with permission rw-r--r--. the ICS one garyd made us works lovely.
OC to 1.4 (NO UV yet, but likely in final release.)
unsecure kernel (adb shell gives root)
and init.d scripts tested with Supercharger. (Personal warning about Supercharger scripts: Nitro lag nullifier is OK, but I dont recommend using the I/O tweaks, put me in a boot loop everytime. Also his 3G tweaks made my actually worse.)
to come: UV, reboot download support, (botologos maybe?), what else? let me know I'll see what I can do. This is my first kernel, Im learning as I go.
This should have been released a week ago, but I was stuck on a permissions issue, that was so easy to fix.
Enjoy!!
Click to expand...
Click to collapse
it great and mega fast i am so pleased we have you on out team bro you are mega awesome....donation on its way.
i installed the cwm version and it wad stuck in boot loop but i wiped data and it worked...thanks got for app extracter haha :-D but well worth it.
thanks man keep up the good work
regards jmar8124 G-tab plus kl3 Malaysia
You had to factory reset? Ill double check my scripts to wipe cache and dalvik
chrisrotolo said:
You had to factory reset? Ill double check my scripts to wipe cache and dalvik
Click to expand...
Click to collapse
ye but it could have been something to do with old tegers haha stupid lum of crap haha its got to be the worst app iv ever purchased. thanos man you kernel is great il try installing it agen with out kernel beeing loaded
Updated my original post above ^^^
double_ofour said:
Pare how can i convert CDL to o2? step-by-step please
Click to expand...
Click to collapse
Thanks chris, will test this. Excited to see some dev going on with international version of 7+. Some suggestions:
Please name your kernel! Make it sound cool as it really is
Add cifs.ko support in the future?
Also just a question, would oc'ng to 1.4 ghz be dangerous without any overvolting. Thanks!
Sent from my GT-P6200 using XDA
download and flash awayyyy.... doing stress test now...
edit...
installation no problem... setting up setcpu now... and doing stress test for max 1400
thanks for the help testing guys. This 1.4 is "hidden" in stock cpufreq commented out as "development only". Should be fine unless you run graphics intense apps with min & man set to 1.4 and performance governor for long periods of time.
I'll add warning about some having to wipe /data with CWM.
I'll look into cifs.ko, should be doable.
I've been getting a lot of dropped signal, may be totally unrelated, I just move to a new building, and also just got word we should be getting AT&T LTE in Hartford CT in a few weeks, so could be network thing.
be back as soon as I can guys. Feedback helps.
u guys getting any deep sleep on cpu spy? im not getting any deep sleep
Edit: a reboot helped got deep sleep back. Reasonable batt life at 1.4ghz
being using it for 2 hours with nova2... current batt from 100% to 60% but full 2 hours on nova... quite ok... runnning setcpu 1400 with ondemand governor... havent face any problem yet...
Flashed the custom kernel with recovery ...everything works just fine.
First boot was a bit long as expected.
I used nofrills cpu control, the default interactive governor was a bit laggy, changed to conservative. No deep sleep problem at all.
Thank you.
Sent from my GT-P6200 using XDA
For anyone interested in cifs.ko or tun.ko, check out this thread...
http://forum.xda-developers.com/showthread.php?t=1400255
Anyone else having wakelocks? / random wake ups? I havent had any.
Welp, likely not going to be able to implement @garyd9's UV, keep getting this mesaage :
arch/arm/mach-s5pv310/built-in.o: In function `s5pv310_set_cpufreq_armvolt':
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:735: undefined reference to `exp_UV_mV'
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:735: undefined reference to `exp_UV_mV'
arch/arm/mach-s5pv310/built-in.o: In function `s5pv310_cpufreq_init':
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:2121: undefined reference to `exp_UV_freq'
/home/chris/Desktop/samsung-kernel-p6200/arch/arm/mach-s5pv310/cpufreq.c:2121: undefined reference to `exp_UV_mV'
make: *** [.tmp_vmlinux1] Error 1
at end of kernel build. The one we have I think should be fine. I will add support for reboot bootloader (& download), and probably release final version tomorrow.
I dont want to make this a long in depth thing anyways (its already been a few weeks for me), becuase hopefully Ice Cream is near.
And my home cpu is in dire need of an upgrade (AMD dual core 4GB) building takes nearly an hour on VM, I will likely be getting a new one shortly.
UPDATE: so I think I am getting wake locks/ USB issue. I think Ive had it wake itself 3 times in a row, and Ive had it lose signal when I press power button to wake device, it signal bars are 0;all grey, and/or says no signal, and occasionally at the same time will says usb device removed.
ive compared my config to garyd9's, at least the one I think he used. didnt see anything I think might cause it, although we do have a bit more hardware in ours. I though I recall something in the kernel menuconfig about wakelocks.
I guess its to be expected, hacking my first kernel. Guess I will just have to run some DMESG's
VENT APPEND: I am finding github push/pull/commit/add/etc to be a steamy pile of crap. I will search for alternatives.
yup got random wake locks... but i haven't face any usb/no signal issue. at least not yet
btw info about governors is quite nice here...
http://forum.xda-developers.com/showthread.php?t=1369817
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
chrisrotolo said:
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
Click to expand...
Click to collapse
chris,
using cpu spy and betterbatterystats app from xda, i was able to trace my wakelocks to mediascanner. so i just killed mediascanner and i got deep sleep back. im not sure though if i had this problem even before i flashed your custom kernel because i never used cpu spy and betterbatterystats on the stock kernel. maybe this helps? i don't get signal drops
chris... i'm currently testing some of the script for init.d on this thread...
http://forum.xda-developers.com/showthread.php?t=1353903
chrisrotolo said:
I found the archive article on wakelocks in galaxy nexus forums. Power management configs are same as garyd9's I believe, maybe because of our always on data connection. Have to look in /proc/wakelocks
Click to expand...
Click to collapse
im always on wifi, barely use my data plan. but i do have wakelocks draining the battery. i also noticed once that my screen didn't time out, screen was on all the time when i left my tablet, so battery drained quite quickly. i think someone has reported this also. i'll do more observation.
Camera works few days when i do a clean install of original rom. Or sometimes witrh custom rom. But after few days or hours camera starts closing. With original rom/ruu it doesn't say anything but custom rom says "can't connect to camera" and camera closes. Factory reset with original rom works sometimes but not allways. I have tried wiping cahce etc, fix permissions, other camera apps, clean install, w/ and w/o sd-card. Allways the same. Camera stops working.
Here is logcat:
http://pastebin.com/KrAT91wm
I made new logcat. Trying to make it shorter. http://pastebin.com/HkFwwMu0 This is with Viper ROM.
Is this the problem? How to solve it?
PHP:
W/mm-camera( 160): whichCamera no 2nd camera
I/mm-camera( 160): set sensor selection :0
D/mm-camera( 160): mm_camera_init, open FD: -1
E/mm-camera( 160): mm_camera_init: controlFd is invalid No such file or directory FD: -1
E/QualcommCameraHardwareZSL( 160): startCamera: mm_camera_init failed:
E/QualcommCameraHardwareZSL( 160): createInstance: startCamera failed!
E/CameraService( 160): Could not open camera 0: -1
I/CameraService( 160): Destroying camera 0
All of a sudden, on Stock + Root TF700T, WiFi won't turn on. I highly doubt that this is related to my WiFi router ... the WiFi won't even enable on the tablet, and I can't even see a MAC address in About Tablet section.
I also did some digging and have some additional detail, but I cannot find a solution.
logcat:
Code:
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such file or directory)'
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2767): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2767): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2767): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2767): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 3ms+3ms, total 57ms
D/AsusBrightnessManager( 489): br transform : 35 -> 13
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
D/DockManagerService( 489): mLastAcOnline:false mAcOnline:false
D/LowBatteryService( 1487): onReceive:Intent { act=android.intent.action.BATTERY_CHANGED flg=0x60000010 (has extras) }
D/LowBatteryService( 1487): mAcOnline = false, mDeviceBatteryLevel = 96, mDockBatteryLevel = 0, mDockBatteryStatus = 0
D/LowBatteryService( 1487): Battery level is higher than threshold, no need to apply
D/LowBatteryService( 1487): Battery level is good, no need to apply low battery config.
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 489): Supplicant not running, cannot connect
E/WifiHW ( 122): Failed to open wlan fw path param (No such file or directory)
E/SoftapController( 122): Softap fwReload - failed: -1
E/WifiStateMachine( 489): Failed to reload STA firmware java.lang.IllegalStateException: command '46 softap fwreload wlan0 STA' failed with '400 46 Softap operation failed (No such file or directory)'
E/WifiStateMachine( 489): Failed 6 times to start supplicant, unload driver
W/CommandListener( 122): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener( 122): Setting iface cfg
E/WifiStateMachine( 489): Unable to change interface settings: java.lang.IllegalStateException: command '48 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 48 Failed to set address (No such device)'
E/WifiHW ( 489): wpa_ctrl_open fail, retry again
I/wpa_supplicant( 2792): Successfully initialized wpa_supplicant
E/wpa_supplicant( 2792): nl80211: Could not add multicast membership for scan events: -2 (No such file or directory)
E/wpa_supplicant( 2792): Failed to initialize driver 'nl80211'
E/wpa_supplicant( 2792): wlan0: Unsupported driver 'nl80211'
D/dalvikvm( 1258): GC_CONCURRENT freed 427K, 14% free 3700K/4272K, paused 2ms+1ms, total 22ms
W/NvCpuClient( 489): Failed to bind to service
D/AsusBrightnessManager( 489): br transform : 35 -> 13
E/WifiHW ( 489): Supplicant not running, cannot connect
W/NvCpuClient( 489): Failed to bind to service
Also, output from netcfg:
Code:
[email protected]:/ # netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
dummy0 DOWN 0.0.0.0/0 0x00000082 76:ad:93:6b:c9:b7
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
ip6tnl0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
And here is output of my wpa_supplicant.conf:
Code:
[email protected]:/ # cat /etc/wifi/wpa_supplicant.conf
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
And I searched the entire filesystem for "nl80211" and found nothing.
Does anyone have suggestions on where to go next? Did my driver somehow get deleted, or am I just not looking for the right thing?
Thanks.
I will use this question in the future as an example of how to ask for support properly. Unfortunately I don't have a solution for you, but you could check the files in your /data/misc/wifi, maybe you can find something unusual. Your MAC address should come from some file on the FAT filesystem on /dev/block/mmcblk0p5 - I'd recommend making an image of it as a backup and then analyze the image.
_that said:
I will use this question in the future as an example of how to ask for support properly.
Click to expand...
Click to collapse
I provide Enterprise-level support to software devs working in the Cloud and particularly on CentOS/RHEL Linux servers. This is why I know how to ask for help properly.
Well, since I can't find much, and there aren't any definitive answers here, my next thoughts are:
1) Something is seriously jacked up on the filesystem, possibly corrupted driver, possibly something worse. Hopefully, this is the case, because a software problem is possible to fix.
2) The WiFi radio is permanently damaged, or "burnt out".
In the hopes that it's something more like software, I'm going to reimage. I just need to decide what ROM to use. Not having network connectivity will make the prep for this a bit more challenging, but I can work through it using a MicroSD card.
If it's #2, well then I suppose I will have wasted my time reimaging and will be on the market for a new tablet ... and I need to get on that right away because I need to travel soon. Any suggestions are welcome ... I'd like a 9" or 10" tablet and it must have an HDMI out (micro preferred) and be able to handle 1080p video.
Thanks.
[SOLVED]
I am having a heckuva time even doing what I described above.
-I had never unlocked the bootloader before, so when I tried the ASUS unlock util v8, it gave error "INSTALL_FAILED_SHARED_USER_INCOMPATIBLE"
-I tried the ASUS unlock tool v7, and was finally able to install it but when I run and select Unlock I get an error that there is no network connection (FFS that's what I'm trying to resolve!)
-I can't get into recovery, I just get the Android guy with "ERROR!" when I enter fastboot and select "RCK".
My only option is to go back to Stock. So, I tried this:
http://forum.xda-developers.com/showthread.php?t=1833212
The steps in that post result in the same Android guy with the "ERROR!" screen ... not a very helpful error msg.
So, I tried this, and used the stock firmware from ASUS. (NOTE: I downloaded "ASUS Transformer Pad TF700T Firmware: V10.6.1.14.10 Only for US SKU (Android 4.2.1)" directly from ASUS after I read their notes on where to check for which one you need ([Settings]-->[About tablet]-->Build number).):
http://www.transformerforums.com/fo...e-firmware-tf700-tf701-tf300-tf101-tf201.html
From that post ^^ I did Method B: Flash from MicroSD. I extracted the .zip I downloaded from ASUS, and renamed the new zip EP201_768_SDUPDATE.zip per the GUIDE linked above.
I put in my MicroSD, went back into fastboot, and selected "RCK". It was at this point that I began typing the above. Total time to get to this point was about 90 minutes!
-----
FINALLY, for the first time, I saw a progress bar under the Android guy, and he had gears turning in his belly.
*INSERT SIGH OF RELIEF HERE*
As I was typing out all the above, progress bars were moving, and a few reboots happened. I expected that I would be fully back on Stock ROM, and that my data would have been wiped. I never ran a data wipe, I just assumed the ASUS installer would do that by default.
Well, it didn't wipe data. But, what it did do: restore all my device drivers!! After about 10 minutes, and 2-3 reboots, Android loaded with my existing desktop and settings, and the WiFi connected right away!!
So, this fixed it. I documented the above so anyone (even me, months from now) having a similar problem might be able to use these steps.
WOO HOO!
lost root
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
CaptainRewind said:
I should add that I lost root now. I think at this point, after all I've been through with this, I'm just going to press on and install CyanogenMod which is what I was planning to do anyway.
Click to expand...
Click to collapse
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
sbdags said:
Just flash this to get root
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Click to expand...
Click to collapse
Yep, I had to do that anyway because I wanted to do a full Titanium Backup first. Still, I'm moving to CM now.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Download Links
CyanogenMod: download.crpalmer.org
Google apps addon:
Download: http://d-h.st/users/dhacker29/?fld_id=27426 (use latest lpmr1 gapps)
XDA:DevDB Information
CyanogenMod 12.1 for MondrianLTE (Unofficial), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
ROM OS Version: 5.1.x Lollipop
Version Information
Status: No Longer Updated
Created 2015-04-18
Last Updated 2016-02-13
Reserved
Works fine
ROM works fine, made a dirty flash from CM12.
No problems at all.
http://review.cyanogenmod.org/#/c/95004/2
hopefully merged soon (already in cm12 since late march..just noticed recently in cm12 builds in mms.apk...should have known by looking at the history for the cm12 version)
EDIt
One thing though
Email exchange (hotmail etc) app has a repeated error popup during sync..this is from 4/17 build and also today's 4/18...was not the case till 4/16..noticed the apk file size has changed (not sure what..but it starts giving error popups during sync...pretty irritating as have to somehow get it to stop the sync to stop the popup...using the cm12.1 email apk 5.82mb from 4/16 or earlier fixes the issue)
cm12 not having such issues,.at least from 4.16 to 4/18 no email.apk file size changes..no sync issues
Edit attached mixer file to address earpiece echo for other caller not speakerphone echo for other caller.. change zip in extension to xml.. not a zip file..put in system etc folder permissions 644
Does miracast work with this build? I know CM started enabling the feature, but it didn't work when I last tried it with my SM-T315. Thank you for your answer.
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
TWRP 2.8.5.0 here. Any later version will work as well.
Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP
vrl13 said:
Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP
Click to expand...
Click to collapse
Thanks!
There's a donate link in my profile but I prefer not to clutter up useful information with extra donate links...
My PayPal is [email protected].
Beer uploaded: 7UG08116JF1461945
Thanks again!
Sent from my SM-T325 using Tapatalk
Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app
mackenzie121 said:
Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Hello,
I'm having no issue with both 2.4 and 5ghz wifi in my home.
Sounds like a router problem though.. can your other devices pick your wifi without a hitch?
Maybe it would help using a fixed IP, in case you are using DHCP now.
Regards.
Sent from my SM-T325 using Tapatalk
RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
I used TWRP 2.8.6.0. I already flashed several nightlies on this tablet, no issues.
---------- Post added at 10:41 PM ---------- Previous post was at 10:26 PM ----------
Is the changelog the same of the nightlies for "MONDRIANWIFI"? Thanks
Is it support cifs ?
Device encryption doesn't work. Build 20150507
Log:
Code:
D/Cryptfs ( 247): unmounting /data succeeded
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 247): Loading keymaster app failed
E/Cryptfs ( 247): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 247): Failed to init keymaster
F/libc ( 247): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 316 (vold)
F/libc ( 247): Unable to open connection to debuggerd: Connection refused
W/vold ( 316): type=1400 audit(0.0:190): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:190): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:190): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:190): item=0 name="/vendor/firmware/keymaster/keymaster.mdt"
W/auditd ( 314): type=1320 audit(0.0:190):
W/vold ( 316): type=1400 audit(0.0:191): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:191): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:191): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:191): item=0 name="/firmware/image/keymaste.mdt"
W/auditd ( 314): type=1320 audit(0.0:191):
W/vold ( 316): type=1701 audit(0.0:192): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=u:r:vold:s0 reason="memory violation" sig=11
I/Vold ( 8391): Vold 2.1 (the revenge) firing up
D/Vold ( 8391): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 8391): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 8391): Check if PFE is activated on Boot
E/Cryptfs ( 8391): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 8391): Error getting crypt footer and key
I see, that file /vendor/firmware/keymaster/keymaster.mdt exists:
# ls -la /system/vendor/firmware/keymaster/keymaster.mdt
lrw-r--r-- root root 2015-05-07 07:04 keymaster.mdt -> /firmware/image/keymaste.mdt
# ls -la /firmware/image/keymaste.mdt <
-r--r----- system drmrpc 12892 2014-11-13 05:32 keymaste.mdt
Any ideas how to fix it? Thanks.
crpalmer said:
CyanogenMod
Click to expand...
Click to collapse
f2fs support?
I am waiting for 10 minutes, hanging on the logo
Alexey71 said:
f2fs support?
I am waiting for 10 minutes, hanging on the logo
Click to expand...
Click to collapse
Try again with today's build and let me know.
crpalmer said:
Try again with today's build and let me know.
Click to expand...
Click to collapse
For me :
cm-12.1-20150523-UNOFFICIAL-mondrianlte.zip work fine but
cm-12.1-20150527-UNOFFICIAL-mondrianlte.zip and cm-12.1-20150528-UNOFFICIAL-mondrianlte.zip don't work : hanging on the logo
27-28 build not work (ext4-f2fs)
26 build work ext4
Builds 0527 and 0528 does not boot; instead, causes shutdown of the tab.
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
Code:
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/DEBUG ( 1389): tid 15467 does not exist in pid 15467. ignoring debug request
I/ServiceManager( 1385): service 'media.audio_flinger' died
I/ServiceManager( 1385): service 'media.player' died
I/ServiceManager( 1385): service 'media.camera' died
I/ServiceManager( 1385): service 'media.audio_policy' died
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
I/mediaserver(15513): ServiceManager: 0x2a00b448
I/AudioFlinger(15513): Using default 3000 mSec as standby time.
E/MediaPlayerFactory(15513): calling dlopen on FACTORY_LIB
E/MediaPlayerFactory(15513): calling dlsym on pFactoryLib for FACTORY_CREATE_FN
E/MediaPlayerFactory(15513): registering DASH Player factory...
I/CameraService(15513): CameraService started (pid=15513)
I/CameraService(15513): Loaded "BCM21553 Camera HAL" camera module
D/BcmCamera(15513): HAL_get_number_of_cameras: numCameras:1
I/AudioPolicyManagerBase(15513): loadAudioPolicyConfig() loaded /system/etc/audio_policy.conf
I/AudioFlinger(15513): loadHwModule() Loaded primary audio interface from Samsung BCM21553 audio HW HAL (audio) handle 1
I/AudioFlinger(15513): HAL output buffer size 1024 frames, normal mix buffer size 1024 frames
I/AudioMixer(15513): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project
I/AudioFlinger(15513): Using module 1 has the primary audio interface
D/AudioPolicyManagerBase(15513): setOutputDevice() changing device from (2) to (2) force (1) delayMs (0) on Output (2)
I/AudioFlinger(15513): AudioFlinger's thread 0x40f53008 ready to run
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
D/audio_hw_primary(15513): call=n, earpiece=n hp=n speaker=y sco=n a2dp=n out_device=2
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
I/audio_a2dp_hw(15513): adev_open: adev_open in A2dp_hw module
I/AudioFlinger(15513): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 3
I/AudioFlinger(15513): loadHwModule() Loaded usb audio interface from USB audio HW HAL (audio) handle 4
W/AudioFlinger(15513): Thread AudioOut_2 cannot connect to the power manager service
E/AudioFlinger(15513): no wake lock to update!
I/r_submix(15513): adev_open(name=audio_hw_if)
I/r_submix(15513): adev_init_check()
I/AudioFlinger(15513): loadHwModule() Loaded r_submix audio interface from Wifi Display audio HAL (audio) handle 5
I/AudioPolicyService(15513): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/AndroidRuntime(15512):
D/AndroidRuntime(15512): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
D/AndroidRuntime(15512): CheckJNI is OFF
D/dalvikvm(15512): Unable to stat classpath element '/system/framework/core.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm(15512): DexOpt: --- BEGIN 'conscrypt.jar' (bootstrap=1) ---
E/dalvikvm(15640): Fatal error: java/lang/Object
E/dalvikvm(15640): VM aborting
F/libc (15640): Fatal signal 6 (SIGABRT) at 0x00003d18 (code=-6), thread 15640 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
I/DEBUG ( 1389): Revision: '0'
I/DEBUG ( 1389): pid: 15640, tid: 15640, name: dexopt >>> /system/bin/dexopt <<<
[A bunch of seemingly random (at least for such a noob like me) numbers]
W/dalvikvm(15512): DexOpt: --- END 'conscrypt.jar' --- status=0x0006, process failed
E/dalvikvm(15512): Unable to extract+optimize DEX from '/system/framework/conscrypt.jar'
D/dalvikvm(15512): Unable to process classpath element '/system/framework/conscrypt.jar'
D/dalvikvm(15512): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm(15512): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/gps_ril_BRCM( 1390): ril thread received 0 events
D/gps_ril_BRCM( 1390): ril_state_thread, fd < 0, calling timeout_action_add
D/dalvikvm(15512): DexOpt: --- BEGIN 'okhttp.jar' (bootstrap=1) ---
E/dalvikvm(15692): Fatal error: java/lang/Object
E/dalvikvm(15692): VM aborting
F/libc (15692): Fatal signal 6 (SIGABRT) at 0x00003d4c (code=-6), thread 15692 (dexopt)
I/DEBUG ( 1389): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1389): Build fingerprint: 'Samsung/cm_totoro/totoro:5.1.1/KTU84Q/20150211:userdebug/release-keys'
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
knuxfanwin8 said:
I'm making a CM12.1 ROM port. Every time after compilation, I'm just stuck on the boot screen. My logcat logs always look like this:
And so on, and so on, until it fails to load everything and starts all over again.
And yes, if you look at the logs, I am porting a ROM to an obsolete device and no, I don't really care that it's "not gonna work". I just want to fix that dex problem.
What I tried so far:
- cleaning up the rom (did nothing)
- changing up a few libraries that had something to do with "dex" (did nothing, but I might have missed something)
- re-unpacked the frameworks (did nothing)
- re-downloaded the rom then re-unpacked the frameworks (also did nothing)
- downloaded another rom and re-unpacked the frameworks (did nothing, what a waste of bandwidth)
- cleared Dalvik cache (did not do anything, I do that every build alongside with a factory wipe in CWM)
- changed the kernel TWICE (did nothing except for making logcat work (it wasn't working for a few builds))
Anyone got any ideas?
Click to expand...
Click to collapse
Yeah. You need to Deodex both ROM BASE and PORT BEFORE you build. That is the reason you keep getting dex errors. Use ASSAYYED Kitchen or @superR's Kitchen or similar to accomplish this ?