Introducing CyanogenMod for the Asus MeMO Pad HD7
I have been working on CM 10.1 for ME173X for a couple months now, it took me a while as I had never heard of MTK before I got this device. I have come to a good start point for anybody that wants to build for MTK devices.
Anybody should be able to use this source to start building for there own device, so please do not ask if this can be ported, you can build it yourself.
RULES OF THIS THREAD:
1. Do NOT ask for an ETA!
2. Do NOT ask if this can be ported to another device!!!
3. Do NOT PM me with questions about this, if you are trying to develop for another device then comments are welcome.
4. Please use the thanks button instead of posting a thanks reply
Let's keep this as clean as we can to help devs get going and contributing to the development.
This is an alpha build, so expect nothing to work.
Links will be up soon, please be patient.
If you would like to help in the development, you can initialize the repo with this command to get started. For now these are simple changes that should get you to a point that it will boot. The only thing required is for you to set up your device files. This also includes my latest CWM based recovery so it should work for small recovery partitions.
Code:
repo init -u git://github.com/BSydz-MTK/android.git -b cm-10.1
My sources can be found here: http://github.com/BSydz-MTK
Kernel Source can be found here.
Credits: xplodwild, chrmhoffmann, bgcngm
XDA:DevDB Information
CM 10.1 Asus MeMO Pad HD7 Alpha, a ROM for the Android General
Contributors
BSydz
ROM OS Version: 4.2.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-03-21
Last Updated 2014-03-21
General Installation info
INSTALLATION:
Flash in a custom recovery:
1. Copy zip to sdcard
2. Boot to recovery
3. Make backup
4. Install zip from sdcard
5. Select custom ROM zip
6. Accept install
7. Reboot
8. Enjoy!
Sideload after build:
In same terminal as the build
Code:
adb reboot recovery
In recovery:
Make backup in recovery if needed
Choose Install from sideload
Code:
adb sideload out/target/product/ME173X/cm-10.1-20140322-UNOFFICIAL-ME173X.zip
You will have to change the date according to the date of build.
Change logs and other details
This will be for change logs and details about issues and fixes
General instructions for building
Build Instructions:
1. Build Environment:
You will have to have your Android build environment set up, here is a guide, you do not have to "download the source" at the end.
http://source.android.com/source/initializing.html
2. Create an Android directory on your computer:
This can be named anything you like. I use /CM-10.1-MTK.
3. Open directory in terminal
4. Initialize the repository:
Code:
repo init -u git://github.com/BSydz-MTK/android.git -b cm-10.1
repo sync
After everything is downloaded/synced:
This downloads prebuilt files for CM
Code:
./vendor/cm/get-prebuilts
5. Connect your device to the computer and make sure adb is working
6. Pull files from device: Note: Some files may not have permission so you may have to pull them from the device manually using root explorer or similar.
Code:
cd device/asus/ME173X
./extract-files.sh
cd ../../../
7. Build:
Code:
. build/envsetup.sh && brunch cm_ME173X-eng -j4
Optional Build:
Copy BSydz_ME173X_build.sh to the root of the Android directory, i.e. the dir you created and are using for your build.
This will give you information through out the build, like what step it is at and how long the build took.
Code:
./BSydz_ME173X_build.sh
Most Common Errors:
make: *** No rule to make target
discription:
This simply means that the file that it is being told to build is not where you said it would be.
Solution:
Make sure the file is where it is supposed to be.
First off, this is stellar. I'm pretty sure you just managed to achieve the impossible. You'll go down in history as the man who got Cyanogenmod on a MTK device! Congrats!
Sent from my Galaxy Nexus using xda app-developers app
jrk190 said:
First off, this is stellar. I'm pretty sure you just managed to achieve the impossible. You'll go down in history as the man who got Cyanogenmod on a MTK device! Congrats!
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Thanks, but I am not the only one. Lots of credit goes to xplodwild, chrmhoffmann, and bgcngm. I am just setting it up so that it is accessible to anybody that wants to help. They have made more progress than me as far as getting things working, I just know from experience that if you put the code in front of peoples face, they will be more likely to contribute something to the project. Since we don't have that base to start from, I figured I would put it together and let everybody at it.
Congrats !!!! Would try a build this night !!
Thanks for your work b !!!!
Gesendet von meinem Ascend G510 mit Tapatalk
edit:
short feedback:
The build process runs very clean !!! and ends with no errors. " cm-10.1-20140323-UNOFFICIAL-ME173X.zip "
i think your work is an very good base man
...i had only 15 minutes to playin around with, because i musst work
For the very first cm Alpha on MTK it works very good....
THX again,
sorry did read this now...
Remember this is just a basic boot, nothing works. There is no sound, wifi, bluetooth, and there is still an issue with the mounts and permissions. So the sdcards don't work. I have updated my github and you should be able to build a bootable ROM from it. I will post a link for the flashable ROM after I get a few things taken care of.
Thank you. you get all the goodies. Have no guess. about the beta release.?
Hi BSydz
Nice work!
Download Link?
Gesendet von meinem ME173X mit Tapatalk
awesome news! looking forward to this weeks!!
Sent from my ME173X using xda app-developers app
can someone do some benchmarks?
great work btw!
BSydz
You will that we build the Rom self. But i have only DSL 2000 and its not good for downloading over 10GB! DSL 2000 is 220 KB/s . Slow! Can you give me a download link?
Please.
Sorry for my very very bad english!
Gesendet von meinem HUAWEI G510-0100 mit Tapatalk
spanitzer said:
BSydz
You will that we build the Rom self. But i have only DSL 2000 and its not good for downloading over 10GB! DSL 2000 is 220 KB/s . Slow! Can you give me a download link?
Please.
Sorry for my very very bad english!
Gesendet von meinem HUAWEI G510-0100 mit Tapatalk
Click to expand...
Click to collapse
I will post a ROM soon, just trying to work a few bugs out before I do.
Sent from my WX435 using Tapatalk 2
Ah okay.
Thanks!
Gesendet von meinem ME173X mit Tapatalk
ROM link in download section.
Here is a mirror if you have any issues.
http://www.mediafire.com/download/a3fu2ui4fqkhpbl/cm-10.1-20140325-UNOFFICIAL-ME173X.zip
Thanks!
You are the best!
Gesendet von meinem ME173X mit Tapatalk
Has a way of opening wifi...
Thanks also
The Rom is very very very smooth!
The Wiko Stairway has a MT6589 and CM10.2-11. But Wifi works in Wiko. Can we use some drivers from Wiko?
Gesendet von meinem Ascend G510 mit Tapatalk
spanitzer said:
The Rom is very very very smooth!
The Wiko Stairway has a MT6589 and CM10.2-11. But Wifi works in Wiko. Can we use some drivers from Wiko?
Gesendet von meinem Ascend G510 mit Tapatalk
Click to expand...
Click to collapse
I am working on it. I am going to build cm11 and omni to see if it will work for our device. I am currently modifying CWM 6.0.4.7 to fit on our recovery partition to be able to install them. Once I figure out what needs to be done I can back port it and go from there.
Also our device is mt8125, so there may be slight differences.
Remember I am only one man, and building takes a while between changes. And this is my only tablet so I don't wanna just leave it in dev mode.
Plus I lost all of my backups cause my sdcard just died trying to remove it from my broken SD slot. That will be the last time I use a drywall screw to try to take out my sdcard ... lol.
Please be patient, this is uncharted territory, and this is my first MTK device.
Sent from my ME173X using Tapatalk 2
BSydz said:
I am working on it. I am going to build cm11 and omni to see if it will work for our device. I am currently modifying CWM 6.0.4.7 to fit on our recovery partition to be able to install them. Once I figure out what needs to be done I can back port it and go from there.
Also our device is mt8125, so there may be slight differences.
Remember I am only one man, and building takes a while between changes. And this is my only tablet so I don't wanna just leave it in dev mode.
Plus I lost all of my backups cause my sdcard just died trying to remove it from my broken SD slot. That will be the last time I use a drywall screw to try to take out my sdcard ... lol.
Please be patient, this is uncharted territory, and this is my first MTK device.
Sent from my ME173X using Tapatalk 2
Click to expand...
Click to collapse
I believe that in the Wiki CM thread, that they mentioned that stock kernel only works on CM10.2, not CM11, so try CM10.2/Omni4.3. There's also this: https://gerrit.omnirom.org/#/q/topic:mt6589,n,z on gerrit, perhaps you can try that wifi fix, by renaming it?
Related
This thread will be kept for troubleshooting issues with CM build by @KINGbabasula
Please report any bugs found in this thread and keep the Original thread clean.
Link to the thread will be posted here when build will be published
Do not ask for ETA.
Rom will be ready when it's ready !!!
ptothej said:
Hi all
I'm working on CM buil for our beloved i9105P a skullface has stopped the development for our device.
I've started to work on one with a big help from Skullface and a tons of tutorials found.
The thing is when it comes to compiling the build o got an error
No rule to make a target `/home/przemo/Source/out/target/product/i9105P/kernel', wymaganego przez `/home/przemo/Source/out/target/product/i9105P/boot.img'. Stop.
Folder structure is set up as follows
kernel is in folder /home/przemo/Source/kernel/samsung/i9105P
and device files from github are in the folder home/przemo/Source/kernel/samsung/i9105P.
What i'm doing wrong ??
Any help appreciated
Click to expand...
Click to collapse
Try putting the kernel zImage in /home/przemo/Source/out/target/product/i9105P/kernel... and renaming it to "kernel"
panda00 said:
Try putting the kernel zImage in /home/przemo/Source/out/target/product/i9105P/kernel... and renaming it to "kernel"
Click to expand...
Click to collapse
But the out folder is being created when compiling CM build
ptothej said:
But the out folder is being created when compiling CM build
Click to expand...
Click to collapse
Oh sorry, I meant /home/przemo/Source/kernel/samsung/i9105P/kernel - put the zImage inside and rename it to "kernel".
Copied the wrong line
EDIT: Oops wait a second!
Will work on it tomorrow, to much computer screen for today
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2
Ok so kernel issue is done, was a typo in boardconfig file LOL.
Now ther issues
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libvpx_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_mpeg2ts_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_httplive_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libstagefright_id3_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libFLAC_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libopensles_helper_intermediates/import_includes
Import includes file: /home/przemo/Source/out/target/product/i9105P/obj/STATIC_LIBRARIES/libOpenSLESUT_intermediates/import_includes
Export includes file: frameworks/ex/variablespeed/jni/Android.mk -- /home/przemo/Source/out/target/product/i9105P/obj/SHARED_LIBRARIES/libvariablespeed_intermediates/export_includes
Notice file: frameworks/av/media/libstagefright/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright.so.txt
Notice file: frameworks/av/media/libstagefright/colorconversion/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_color_conversion.a.txt
Notice file: frameworks/av/media/libstagefright/codecs/mp3dec/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_mp3dec.a.txt
Notice file: frameworks/av/media/libstagefright/codecs/aacenc/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_aacenc.a.txt
Notice file: frameworks/av/media/libstagefright/matroska/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_matroska.a.txt
Notice file: frameworks/av/media/libstagefright/timedtext/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_timedtext.a.txt
Notice file: external/libvpx/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libvpx.a.txt
Notice file: frameworks/av/media/libstagefright/mpeg2ts/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_mpeg2ts.a.txt
Notice file: frameworks/av/media/libstagefright/httplive/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_httplive.a.txt
Notice file: frameworks/av/media/libstagefright/id3/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_id3.a.txt
Notice file: external/flac/libFLAC/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libFLAC.a.txt
Notice file: frameworks/av/drm/libdrmframework/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libdrmframework.so.txt
Notice file: frameworks/av/drm/common/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libdrmframeworkcommon.a.txt
Notice file: frameworks/av/media/libstagefright/omx/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_omx.so.txt
make: *** Brak reguł do zrobienia obiektu `vendor/samsung/i9105P/proprietary/lib/libvorbisidec.so', wymaganego przez `/home/przemo/Source/out/target/product/i9105P/system/lib/libvorbisidec.so'. Stop.
make: *** Oczekiwanie na niezakończone zadania....
Notice file: frameworks/av/media/libstagefright/yuv/NOTICE -- /home/przemo/Source/out/target/product/i9105P/obj/NOTICE_FILES/src//system/lib/libstagefright_yuv.so.txt
Any Ideas ?
Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer
ptothej said:
Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer
Click to expand...
Click to collapse
I m going to try cm10.1 soon
Bt I think I will wait for ur build.. good luck .
ptothej said:
Please ignore previous post got it sorted, had to copy lib and etc folders to vendor folder.
Still few issue to resolve, but getting closer
Click to expand...
Click to collapse
BTW question. Is it with OC Or what ?
warface123 said:
BTW question. Is it with OC Or what ?
Click to expand...
Click to collapse
It's Stock CM so to speak
warface123 said:
BTW question. Is it with OC Or what ?
Click to expand...
Click to collapse
He's basically got to go with stock CM kernel with no changes to the source as to achieve official CM status somewhere along the road.
Sent from my GT-I9105P
panda00 said:
He's basically got to go with stock CM kernel with no changes to the source as to achieve official CM status somewhere along the road.
Sent from my GT-I9105P
Click to expand...
Click to collapse
As there is no custom kernel at the moment, neither do i have time or knowledge to compile custom kernel.
I've decided to compile GM build based on Skullface project.
As Panda00 said it's a long road ahead.
Sorry to interrupt but I try to follow CM build and have some questions:
- Basically we use(d) http://wiki.cyanogenmod.org/w/Doc:_porting_intro as guideline?
- Device configuration is already done -> skullface's github? Is this one for I9105P or also for I9105?
- Can the stock samsung kernel be used with CM or has it to be kernel source from Samsung Open Source?
- As for kernel source I saw different things till now: skullface imported GT-I9105_SWA but for GT-I9105P we need GT-I9105P_JB?
- There are also GT-I9105_CIS and GT-I9105_MEA available at Samsung Open Source. Are those regional stuff or what's the meaning of CIS and MEA? Does it matter which to choose?
- Next step would be trying to build CM (if Samsung stock kernel can be used it would be easier to build CM instead of using kernel source I assume)?
s2+user said:
Sorry to interrupt but I try to follow CM build and have some questions:
- Basically we use(d) http://wiki.cyanogenmod.org/w/Doc:_porting_intro as guideline?
- Device configuration is already done -> skullface's github? Is this one for I9105P or also for I9105?
- Can the stock samsung kernel be used with CM or has it to be kernel source from Samsung Open Source?
- As for kernel source I saw different things till now: skullface imported GT-I9105_SWA but for GT-I9105P we need GT-I9105P_JB?
- There are also GT-I9105_CIS and GT-I9105_MEA available at Samsung Open Source. Are those regional stuff or what's the meaning of CIS and MEA? Does it matter which to choose?
- Next step would be trying to build CM (if Samsung stock kernel can be used it would be easier to build CM instead of using kernel source I assume)?
Click to expand...
Click to collapse
You have a lot of questions. LOL.
Skullface's work is based on I9105P source , but he just misnamed it.
The stock boot.img cannot be used, you have to modify it (just a little bit) to work with CM. If you're using Skullface's work then that was done for you already.
I know that MEA is Middle East and Africa.. so yes they're regions.
Sent from my GT-I9105P
Kernel seems to have been built sucessfully :victory: but I didn't include pawitp's changes yet
Now I'm waiting for the rest to finish :fingers-crossed:
Build has finished but no zip file inside out directory
Update: forget my problem, found out what was missing :victory:
s2+user said:
Build has finished but no zip file inside out directory
Update: forget my problem, found out what was missing :victory:
Click to expand...
Click to collapse
Well done, now i can stop working on mine CM, no point having 2 same builds.
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2
ptothej said:
Well done, now i can stop working on mine CM, no point having 2 same builds.
Wysyłane z mojego GT-I9105P za pomocą Tapatalk 2
Click to expand...
Click to collapse
Well you 2 could always collaborate; work together.
Sent from my GT-I9105P
panda00 said:
Well you 2 could always collaborate; work together.
Sent from my GT-I9105P
Click to expand...
Click to collapse
Could do
Well after all we need developers for everything else cause I'm no developer
I only wanted to try building CM and there is so much stuff that I want to know about the whole process of porting and building. But after all it's a little beginning :highfive:
I will be making daily builds of AOSP from the master branch. This is pure AOSP, no extra features. The only thing changed is the build.prop so the Play Store will work. Go to https://android-review.googlesource.com/#/q/status:merged,n,z for a changelog.
Downloads
ROM
GAPPS
FIX
DON'T FORGET TO INSTALL FIX OR ROM WON'T BOOT!
You'll notice I made a custom gapps package. The only difference between my gapps and the ones on goo.im is mine comes with all gapps that come with Nexus devices. If you want to save space then flash the one from goo.im.
Every time I go back to homescreen I get an red border , could you tell me if that was designed that way or what?
@cmason37
Maybe he has made eng build instead of userdebug
Gesendet von meinem Nexus 7 mit Tapatalk 4
Kevinjoa said:
@cmason37
Maybe he has made eng build instead of userdebug
Gesendet von meinem Nexus 7 mit Tapatalk 4
Click to expand...
Click to collapse
That is correct it says eng in the build my bad
Hello People,
How can we use Kernel to port a rom?
Do we need to wait for any Custom ROM for our Mobile? or Can we directly download CM 12 ROM and replacing some files from CM12 to MI4i Kernal?
Please, show me some light.
Best Regards,
More like download cm 12 and replace some files
Sent from my Mi 4i using Tapatalk
rocky_09 said:
Hello People,
How can we use Kernel to port a rom?
Do we need to wait for any Custom ROM for our Mobile? or Can we directly download CM 12 ROM and replacing some files from CM12 to MI4i Kernal?
Please, show me some light.
Best Regards,
Click to expand...
Click to collapse
I think you mean the kernel source. We need this to build a kernel for our mi4i. Especially for a custom from like cm12. But its not as easy as downloading a rom. A complete devices stock have to be created for the device to get everything work. So far as I know cm doesn't support any xiaomi device official. For cm we need the suitably vendor files to build the rom. Some we can pick from similar devices like yureka for example.
I think the devs here will do a good job. In 2 weeks after my exams I have time to try a port if in this time not other devs release a rom
Gesendet von meinem Mi 4i mit Tapatalk
smoki3 said:
I think you mean the kernel source. We need this to build a kernel for our mi4i. Especially for a custom from like cm12. But its not as easy as downloading a rom. A complete devices stock have to be created for the device to get everything work. So far as I know cm doesn't support any xiaomi device official. For cm we need the suitably vendor files to build the rom. Some we can pick from similar devices like yureka for example.
I think the devs here will do a good job. In 2 weeks after my exams I have time to try a port if in this time not other devs release a rom
Gesendet von meinem Mi 4i mit Tapatalk
Click to expand...
Click to collapse
Thank you very much for the detailed explanation.
I am new to this stuff. If you don't mind can you please expalin.
1. So, When we have Kernel, How we can use the files of the Kernel to port other devices.?
2. Suppose, If we take AOSP Rom from Google and Developers Rom from MIUI and can I simply replace the files?
UNOFFICIAL CyanogenMod 13.0 for HTC One M9
just thought i'd share
im sure cyanogenmod will have nightlys soon
NOT WORKING
dt2w
gsm only for right now
DOWNLOADS
click me
I use open gapps arm64 nano
all source from
cm git
cm gerrit
kernel
cm kernelXDA:DevDB Information
CM-13.0 UNOFFICIAL BUILDS android 6.0, ROM for the AT&T HTC One (M9)
Contributors
rc420head
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-12-04
Last Updated 2015-12-03
Woot!!! Awesome work!! You guys rock....
Oh man...this is awesome! Thanks!
Thank you so much. you the man!
Is anything being worked on for the other carriers? Mainly concerned about the Himawhl (Sprint).
Wow, I didnt expect cm13 this early. Great work, hope the sprint himawhl coming soon.
Himawhl in development? Great job devs nonetheless.
Bluetooth working fine with my gwatch r ? will test later with my car stereo
Getting this though..
I am having problems with external sd card. any file manager except stock can't find it (I have my titanium backup folder on ext sd, and also TiBu app can't find it)
may be some new behavior I don't know. gallery can't access to sd as well.
besides that this rom is so smooth and fast, I think I will stick with it. really expecting much from sense 6.0
everything working fine
Not asking for an ETA, but should we wait for candy six or flash this in the mean while?
rc420head said:
UNOFFICIAL CyanogenMod 13.0 for HTC One M9
just thought i'd share
im sure cyanogenmod will have nightlys soon
NOT WORKING
dt2w
gsm only for right now
DOWNLOADS
click me
Created 2015-12-04
Last Updated 2015-12-03
Click to expand...
Click to collapse
Thanks for this .. I think we need gapps for marshmallow also, you can get it here >> gapps for arm64 >> http://opengapps.org/
throcker said:
I am having problems with external sd card. any file manager except stock can't find it (I have my titanium backup folder on ext sd, and also TiBu app can't find it)
may be some new behavior I don't know. gallery can't access to sd as well.
besides that this rom is so smooth and fast, I think I will stick with it. really expecting much from sense 6.0
everything working fine
Click to expand...
Click to collapse
I think its because google changed the mount point for the external SD. Its at /mnt/media_RW/(some hex number).
My guess is root apps need to be updated.
For my backups I just copied the folder over to the internal storage then I could restore my data. I just let google reinstall all the apps as its a major version change rather than reinstall the old app.
omg!!! cant wait to finish work now,, will be flashing this bad boy later
Jhonys said:
Not asking for an ETA, but should we wait for candy six or flash this in the mean while?
Click to expand...
Click to collapse
Uploading CandySiX now, ill post it in candy5 thread
Sent from my LG-H811 using Xparent Red Tapatalk 2
Ill try it today and will let you know :d thanks so much!
n3m35155 said:
I think its because google changed the mount point for the external SD. Its at /mnt/media_RW/(some hex number).
My guess is root apps need to be updated.
For my backups I just copied the folder over to the internal storage then I could restore my data. I just let google reinstall all the apps as its a major version change rather than reinstall the old app.
Click to expand...
Click to collapse
will take a look later. meanwhile I reverted to sense because battery seemed to drain too fast and my g watch had problems on keep connected
SD Card also not mounting, infact it says its corrupt.. And the AOSP Keyboard keeps crashing so I couldnt connect to wifi or sign-in to my Google Account during Setup, not a deal breaker but just FYI.
Is it possible to use smocha kernel with cm13?
Gesendet von meinem HTC One M9 mit Tapatalk
Rogi1997 said:
Is it possible to use smocha kernel with cm13?
Gesendet von meinem HTC One M9 mit Tapatalk
Click to expand...
Click to collapse
It is not but he's working on it as far as I know
Sent from my LG-H811 using Xparent Red Tapatalk 2
Someone who wants to test my ROM? This ROM Is quite unlike other Note 3 ROM's. Is based on CyanogenMod.
Kernel in this ROM is the latest sources from Samsung with tweaks.
I am not responsible for bricked devices.
Don't work:
- Need to work more with SELinux.. Have some deniers
- You tell me
What is special about my ROM?
- Newer kernel source
- Lag free experience, because I have focused on GPU-source and PowerHall without overclocking. The key is efficiency
Mod edit: Links removed
Will test this out!
Edit: So far so good, but as mentioned below, battery drain tremendously. Though, it's still WIP so no complaints & thanks for your efforts.
Test and report,good to see different nougat projects
Sent from my SM-N9005 powered by QS-N9005-LP
really smooth rom
cellular data works fine and the rom is really smooth, battery drains real quick and app permissions popup glitches.
recent apps panel look really huge and needs alot of resizing
@christer12 awesome mate. ? Gonna give it a try
What are the bugs?
---------- Post added at 08:03 AM ---------- Previous post was at 08:00 AM ----------
How about battery life?
Nightstreetz said:
cellular data works fine and the rom is really smooth, battery drains real quick and app permissions popup glitches.
recent apps panel look really huge and needs alot of resizing
Click to expand...
Click to collapse
Recent panel is okay. This is what it looks on Android Nougat...:silly:
hey guys what kind of gappss did you use? i used the 7.0 open gapps stock one, but i can't get past the first few steps (select language, wifi and so on) as the play services keep crashing on me. I assume the gapps i use aren't fully compatible.
yka1988 said:
hey guys what kind of gappss did you use? i used the 7.0 open gapps stock one, but i can't get past the first few steps (select language, wifi and so on) as the play services keep crashing on me. I assume the gapps i use aren't fully compatible.
Click to expand...
Click to collapse
you must flash the rom along with gapps at the same time. If you first flash the rom and boot and then flash gapps you will face Google Play service fc's.
so
1. Flash rom
2. Don't boot and flash Android 7.0 gapps (Any)
3. flash supersu.zip if needed
poof done no force close
NImesh Basu said:
you must flash the rom along with gapps at the same time. If you first flash the rom and boot and then flash gapps you will face Google Play service fc's.
so
1. Flash rom
2. Don't boot and flash Android 7.0 gapps (Any)
3. flash supersu.zip if needed
poof done no force close
Click to expand...
Click to collapse
Hi, Thx for your feedback! Thats how i have done it (or how I always do it with AOSP Roms)
That's why I was wondering if I picked some incompatible Gapps by mistake.
May I ask you which one you picked? (Stock, full, mini, ore something else than open Gapps?)
Gesendet von meinem SM-N930F mit Tapatalk
yka1988 said:
Hi, Thx for your feedback! Thats how i have done it (or how I always do it with AOSP Roms)
That's why I was wondering if I picked some incompatible Gapps by mistake.
May I ask you which one you picked? (Stock, full, mini, ore something else than open Gapps?)
Gesendet von meinem SM-N930F mit Tapatalk
Click to expand...
Click to collapse
open gapps nano
I used opengapps arm 7.0 pick and everything worked as expected.
Sent from my SM-N9005 using XDA Free mobile app
supergen007 said:
I used opengapps arm 7.0 pick and everything worked as expected.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Thx, for me all worked except for "Stock" for whatever reasons..went ahead and used "full" instead
Gesendet von meinem SM-N9005 mit Tapatalk
ROM is working excellent no FC's or error or anything. Only bug I have is the battery icon can't change, doesn't show percent and may or may not be showing the wrong amount left in the status bar.
Sent from my SM-N9005 using Tapatalk
jamboss said:
ROM is working excellent no FC's or error or anything. Only bug I have is the battery icon can't change, doesn't show percent and may or may not be showing the wrong amount left in the status bar.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
You can't change the battery Icon within the status bar settings that's correct, however you can make the percentage appear within the stock battery icon. Go to settings / status bar / status bar icons". There, i have a setting for showing the percentage at the bottom of the screen, once I pass all the slider options for the icons I want to enable.
Gesendet von meinem SM-N9005 mit Tapatalk
yka1988 said:
Hi, Thx for your feedback! Thats how i have done it (or how I always do it with AOSP Roms)
That's why I was wondering if I picked some incompatible Gapps by mistake.
May I ask you which one you picked? (Stock, full, mini, ore something else than open Gapps?)
Gesendet von meinem SM-N930F mit Tapatalk
Click to expand...
Click to collapse
I think Android Pay is the cause of that trouble.
I'm so exited about CM14 on my note 3. One day i will try it. Have to wait now :/
Two questions.
1. Are there only two devs working on CM14 for note 3?
2. trader418 has one CM14 rom, but not that much time to work on it.
Can't you two collaborate on one rom, or at least a stable base that you can then work on separately if you which?
I'm asking this for as a user and not a developer this make sense.
Two cooks can be a good thing. :good:
Thanks for this rom m8.
Tesla said:
I'm so exited about CM14 on my note 3. One day i will try it. Have to wait now :/
Two questions.
1. Are there only two devs working on CM14 for note 3?
2. trader418 has one CM14 rom, but not that much time to work on it.
Can't you two collaborate on one rom, or at least a stable base that you can then work on separately if you which?
I'm asking this for as a user and not a developer this make sense.
Two cooks can be a good thing. :good:
Thanks for this rom m8.
Click to expand...
Click to collapse
This ROM is stable as hell and everything I have tried so far is working. Battery icon reads the correct info and the percent is showing in the icon. ROM is perfect.
Sent from my SM-N9005 using Tapatalk
Great rom mate. Hopefully you'll be able to fix permission pop up glitch and video camera bug.
Rom is so smotth and stable, no random reboot or force close either...
flashed and everything works perfect..christer you do great work..well done from me
by the way is there any way to change dpi on this rom?