Yes exactlyI'm confused. You let it for 24 hours without doing anything and when you checked it after it was full, but when you restarted it, it was 52%?
Yes exactlyI'm confused. You let it for 24 hours without doing anything and when you checked it after it was full, but when you restarted it, it was 52%?
Well, mainly because it doesn't make a difference, and it isn't so hard, tbh. All one needs to do is to read a couple of lines to know which to use.Why isn't some dev trying to make a official TWRP build so there isn't this confusion everywhere what recovery to use. And with official I mean one build that can be submitted to the official TWRP repo.
Well he raised a r8 question... Lots of rooting method..lots of twrp thread...it just create confusion for newbies.. Make a thread dat could make way for newbies to decide themselves which method to use..which twrp to use...etc..Well, mainly because it doesn't make a difference, and it isn't so hard, tbh. All one needs to do is to read a couple of lines to know which to use.
Well me and @h2o64 we are using ONE assert like stock, so TRWP will work the same for stock zips and custom ROMs, no need to people change stuff around.Well, mainly because it doesn't make a difference, and it isn't so hard, tbh. All one needs to do is to read a couple of lines to know which to use.
Yeah, I was going to do that next build after looking at you guys using ONE as assert.Well me and @h2o64 we are using ONE assert like stock, so TRWP will work the same for stock zips and custom ROMs, no need to people change stuff around.
https://github.com/h2o64/android_device_oneplus_onyx/commit/3ce1cd48782b9d72f383fabf2acc78b137fe4364
This ROM also uses fstab.onyx instead of fstab.qcom like stock and other recent snap devices.
This kind of customization just bring headaches for users and development standards, the rule should be stay close to stock naming and stuff because there's no reason to not be so.
CyanogenMod 12.1 for OnePlus X (E1003)
Ehm, cm13 was booted before cm12.1 fyi.Need help porting cm13? Im here!
Successfully booted cm13 on op2
Were pretty much in the same condition now.
Audio/ril/camera/etc not working![]()
Ik that opx!=op2Ehm, cm13 was booted before cm12.1 fyi.
Op2 != opx
it works on E1001. Use the recovery provided to flash.Is this ROM only for E1003? Will it not work on chinese model E1001 ?
So camera works but it doesn't capture? Also, you need to check if prima module is being built into your kernel.it works on E1001. Use the recovery provided to flash.
---------- Post added at 12:21 PM ---------- Previous post was at 12:05 PM ----------
I compiled for another project Mokee Opensource using your device tree, kernel and vendor files, but having the same issue as Resurrection Remix build, eg wifi problem, camera capturing problem.
Do you know the reason why cm works, but other projects don't work?
Yes, the camera shows the live images, but fails to capture anything. ( on the mokee rom I built and Resurrection Remix posted in the forum)So camera works but it doesn't capture? Also, you need to check if prima module is being built into your kernel.
If you can't take images, then you're missing an encoding library. Find which lib is called and fix it.Yes, the camera shows the live images, but fails to capture anything. ( on the mokee rom I built and Resurrection Remix posted in the forum)
Would you give me some hints how to check whether the Qualcomm Atheros Prima WLAN module is being built sucessfully?
I used your kernel source without modification and saw prima module related code in the kernel folder. Does it mean the module is included?
Thank you so much.
I just made a mixture of your cm kernel and my ramdisk and it turned out WiFi worked. So the WiFi problem must be related to the kernel, though I don't know how to fix it.If you can't take images, then you're missing an encoding library. Find which lib is called and fix it.