Related
Gents,
I need your help about "kernel", as I know when installing Android I need the folder named Android and the data.img.
But the kernel what is that?
Thanks for reading and more for helping.
The kernel is the core of the Android OS. Windows too runs on a kernel. Every build already includes one, and usually the most up-to-date or stable version, so you shouldn't have to worry about it, unless you want to update your kernel some time in the future.
I've been running Android for several months now and I've not updated the kernel once.
Still there is somthing to say
First I want to thank you for giving me some of your time.
The answer is clear, but why there is update always (now is 8.6)?
and what the kernel is including, is it the same of Android folder?
I hope I will find some more time.
Check out here for a bunch of explanations of terms that are commonly used around here
http://forum.xda-developers.com/showthread.php?t=852660&highlight=glossary
The reason that the kernels are updated alot is that the people who build the kernels find flaws in them through testing them, and through the feedback they recieve here on XDA.
Then they work to try and find ways to fix those flaws. Sometimes in fixing one flaw, a new one emerges. Generally it is a good idea to use the latest version of whatever kernel came with the build.
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Yup, i confirm, doesn't work on lg g3. Pitty.
joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
Sorry for my delay. I started a re-coding "marathon" on the weekend and it stretched for a week.
I intend to support the LG G3 as well as I possibly can, on any ROM. I have almost bought a G3 for testing a few times, but haven't gone through with it yet.
The CM12 kernel does not at present include the needed Qualcomm V4L FM radio "IRIS" driver.
I will try to submit the tiny 2 line config file change needed for that and see if they respond.
Someone built an FM friendly kernel and it worked, but there are/were still some audio issues. We can work around this with the new analog mode being added to Spirit2, and this should be properly resolved at some point.
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
joergherzinger said:
Oh, thats great to hear.
For the Cyanogen part: They actually have a section in their bugtracker for FM Radio [1]. Once you have done that could you post the links to the pull request and the bug entry here. I will follow it and update my phone as soon as the fix is built. If there is anything I can do to help you please let me know.
[1] https://jira.cyanogenmod.org/secure...=+"FM+Radio"+ORDER+BY+priority+DESC&mode=hide
Click to expand...
Click to collapse
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
WOW great news!!
Thank's very much :victory:
mikereidis said:
OK.
Last night I submitted the same patch for Xperia Z1 and it seems well received. First time I ever built a CM ROM and it took a few days to get everything downloaded and built and figure out how to submit CM patches etc.
My response time to posts and emails has increased, and my responses are more brief, because I have decided to spend more time doing what needs to be done and less time talking about it.
Click to expand...
Click to collapse
Great! I'm trying CM12 in my G3 and, despite some typical nightly bugs, it's working quite well. I only really miss FM radio! :fingers-crossed:
Any progress ?
ariek44 said:
Any progress ?
Click to expand...
Click to collapse
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
will not start
mikereidis said:
Is the needed FM driver in the CM12 kernel for LG G3 now ?
And is the remaining problem that the sound sounds horrible ?
See my posts 9001 and 9002 for info on the new March 6 beta release. 9002 has link to the free version to try: http://forum.xda-developers.com/showthread.php?t=1059296&page=901
Click to expand...
Click to collapse
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Phenax said:
New beta app says no tuner in current cm12 nightly. Tried flashing a different kernel - resin - but same result.
Click to expand...
Click to collapse
If you have the T-Mobile variant, I do not think FM can ever work for you.
As with the LG G2, only the Sprint and International variants have the FM antenna pin connected as needed to the headset jack for the antenna.
Other variants are purposely and permanently "broken" by shorting the pin to ground.
There was rumor here and there that other variants might work, but I think that was based on Spirit not showing a specific error at one point.
So, AFAICT, only the International D855 and Sprint's model.
joergherzinger said:
Hi, I've read that support for LG G3 is in the works but is or will there be support for the G3 running CM12?
I've just tested this, even bought the version from Play store and for me it doesn't work. Is there a Kernel requirement for FM radio which CM12 may not have? I could supply any log data you request.
Thanks and great work so far.
Click to expand...
Click to collapse
I have built a CM12 based kernel that I think should work.
I do not have a G3 so I can not test it.
I can not make any guarantees that it will boot and won't harm anything.
This is a boot.img file. Anyone flashing it should understand how to flash such a file so I won't explain.
I will submit the patches to CM once someone can verify.
md5sum ~/mikes_boot_fm_12-20150307-UNOFFICIAL-d855.img
d8080528d3f37448e57a6da84162d4df
Thanks !
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Edit: I just noticed that wake up by double tap does not work. I assume that just because you used a different kernel config to the stock cm one...
Click to expand...
Click to collapse
Great !
I did not touch the kernel config at all. I used this one, stock as of this morning, AFAICT: https://github.com/CyanogenMod/andr...0/arch/arm/configs/cyanogenmod_d855_defconfig
The config has this, unchanged:
Code:
CONFIG_RADIO_IRIS=y
CONFIG_RADIO_IRIS_TRANSPORT=y
All I did to patch/fix was this:
Code:
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris-transport.c kernel/lge/g3/drivers/media/radio/radio-iris-transport.c
cp kernel/motorola/msm8226/drivers/media/radio/radio-iris.c kernel/lge/g3/drivers/media/radio/radio-iris.c
This copied the Qualcomm fix from the MotoG kernel source that allows radio-iris-transport to work built into the kernel, instead of only as a module.
joergherzinger said:
Genius, it works. Sound quality seems fine to me. Just send me the link to the patch you will send in and I can confirm the cm guys, that it is working if you want.
Click to expand...
Click to collapse
Patch is here: http://review.cyanogenmod.org/#/c/90794/
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
joergherzinger said:
I played around with it a bit more. FM worked like a charm, but several other things didn't work at all. Most importantly Settings crashed for me when I tried to open display settings. I assume that is because my CM is a little more than a week old while your build is just a few days old. I reverted by to my old boot.img but I will test the first nightly with your patch in it.
Click to expand...
Click to collapse
Maybe.
I've seen Settings crash on a few devices/ROMs.
Common AOSP Lollipop ROMs still have lots of problems.
They ALL have a nasty memory leak that gets bigger every time Spirit sends an RDS update to notification shade/remotes/lockscreen. I have to reboot my test phones every day or so to avoid unpredictable restarts when Android system_server fills its' internal table maxed at 51,200.
Stock Lollipop ROMs don't have this problem, so IMO must be some common bug in CM12 I think. (I could/should verify if Nexus/pure AOSP shares this.)
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
joergherzinger said:
Well, it doesn't look too good. They seem to want this as a loadable module, which you explicitly stated different in your commit message. Any ideas an what to do next?
Click to expand...
Click to collapse
Yes, I think so, it's just taking me a long time to do it.
The patches I provided WORK. The complaint was that IF they re-configure the kernel to use modules, then the kernel will not build and he did not like that.
Many kernels have removed modules now and it is rare to go back to modules, so I find this a bit strange, but I am not the one maintaining kernels.
The patches were not really "developed" by me. I just grabbed the very similar files from the MotoG CM12 kernel thinking they would not complain; it was just aligning the code between CM12 kernels.
My plan since the patches were rejected is to use the files from (I think) a Sony CM12 kernel that I think should work with or without modules.
But I have had a LOT of trouble getting d855 kernels and ROMs to build since my initial changes that worked AND it can take hours to build a new ROM and I still have not figured out how to build just the kernel, which is much faster.
This is the problem I had last night and the night before and I am not a ROM dev so it takes time for me to figure out what is wrong or how to fix (maybe a "make clean" or similar"):
creating userdata.img...
Running: mkf2fsuserimg.sh /tmp/tmpqdNGFw 12297699328
in mkf2fsuserimg.sh PATH=/home/m/android/system/out/host/linux-x86/bin:/usr/lib/jvm/java-1.7.0-openjdk-amd64/bin:/home/m/android/system/out/host/linux-x86/bin:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin:/home/m/android/system/prebuilts/gcc/linux-x86/:/home/m/android/system/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin:/home/m/android/system/development/scripts:/home/m/android/system/prebuilts/devtools/tools:/home/m/android/system/prebuilts/android-emulator/linux-x86_64:/home/m/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/lib/jvm/jdk1.8.0_25/bin:/home/m/b:/home/m/b/android-studio//bin/:/home/m/b/android-sdk//platform-tools/:/home/m/b/android-sdk//tools/:/home/m/b/android-sdk//build-tools/21.1.2/:/home/m/b/android-ndk-r10//build/tools/:/home/m/b/android-ndk-r10//
make_f2fs -l 12297699328 /tmp/tmpqdNGFw
/home/m/android/system/out/host/linux-x86/bin/mkf2fsuserimg.sh: line 31: 23180 Segmentation fault $MAKE_F2FS_CMD
Traceback (most recent call last):
File "./build/tools/releasetools/add_img_to_target_files", line 261, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/add_img_to_target_files", line 255, in main
AddImagesToTargetFiles(args[0])
File "./build/tools/releasetools/add_img_to_target_files", line 241, in AddImagesToTargetFiles
AddUserdata(output_zip)
File "./build/tools/releasetools/add_img_to_target_files", line 156, in AddUserdata
assert succ, "build userdata.img image failed"
AssertionError: build userdata.img image failed
make: *** [/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip] Error 1
make: *** Deleting file `/home/m/android/system/out/target/product/d855/obj/PACKAGING/target_files_intermediates/cm_d855-target_files-079aa1bcfa.zip'
Click to expand...
Click to collapse
With troubles like these, and ROM builds taking hours and my lack of a G3 to test, this is moving slowly.
Add the fact that I am exhausted from the last few months of MORE major changes to Spirit2, some time spent with my family and looking into Android Auto and things move even more slowly.
...And the build guide for G3 seems to have disappeared too: http://wiki.cyanogenmod.org/w/Build_Guides#vendor=%22LG%22;
...And... any chance you know the OFFICIAL CM12 way of switching between module and non-module kernels ? I know the defconfig "CONFIG_MODULES=y" thing, but I'm not sure if other changes are needed. I can do a "make menuconfig" but I'm not sure if I should write .config to the defconfig. "make config" gives a million options; I tried that and produced a kernel that probably won't even boot on a G3.
Perhaps I should post in a G3 forum section asking for help.
I posted on that patch now: http://review.cyanogenmod.org/#/c/90794/
Hi, I don't understand half you are talking about
I'm just an user who wants CM12 and FmRadio.
That being said, I can read this changelog in 777 kernel thread (http://forum.xda-developers.com/lg-g3/development/kernel-777-kernel-t3003115). Did anyone try this "radio" builds?
02/08/15
- R6
- Fix Powersuspend
- CM kernel updates
- Synaptic touch firmware update
- Separate d855 builds with fm radio module
Click to expand...
Click to collapse
(EDIT: Tried by myself. Radio works with 777 kernel. However, audio quality is quite bad.)
Second, I would like to test any beta kernels, spirit app, or whatever in my G3 D855, in order to help making it work. Please tell me how can I do it.
Thank you very much!
hi guys, I see there are still no threads for FirefoxOS that has been just released by FXP for our device too (z3c) so I'm creating one
this thread just to discuss about it!
INFO: http://fxpblog.co/2015/09/26/firefox-os-releases-by-fxp.html
DOWNLOADS: http://fxpblog.co/firefox/nightly/
INSTALLATION:
- You must have a UNLOCKED BL
- Extract all system images from the ARIES zip you downloaded
- Connect phone to PC in fastboot mode and then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot reboot
downloading the zip for aries right now! will see how it goes
in the meantime, I have already some questions I would like to reply myself after testing the new OS or if somebody already knows the answers, please let me know!
1. rootable? DON'T THINK SO
2. recovery can be installed or to go back to stock will have to flash FTF via flashtool? SEEMS NO RECOVERY AT ALL?!
3. camera present/working? if so, without fish eye bug? CAMERA NOT WORKING AT ALL
4. gapps are needed? in firefox OS there is no Play Store right? NO GAPS, THERE IS MOZILLA MARKETPLACE WITH FEW STUFF STILL OF COURSE
Please contribute guys in answering all the above questions!
THANKS
All credits to Mozilla and FXP ( @freexperia ) teams of course!
few screenshots:
https://www.dropbox.com/s/2ut81qaqjgu3fqo/2015-10-01-11-14-23.png?dl=0
https://www.dropbox.com/s/vvrx7153ql6xjzf/2015-10-01-11-14-33.png?dl=0
few impressions so far:
the bad:
- no camera
- no dt2w
- no extsd support (where I have all my stuff!)
the good:
- seems very nice and promising
- app ops
- nice animations
will keep updating!
Really interested to try this once it's fully functional. Thanks for the heads up!
moly82 said:
- I'm pretty sure you must have a UNLOCKED BL
Click to expand...
Click to collapse
Unlocked bootloader for sure, since you must flash boot.img
Our device is ARIES, if someone doesn't know yet
Testing today...
me too just unlocked the BL!
EDIT: just booted inside FirefoxOS for my first time
things I noticed so far:
see OP
First impressions:
-only English language.. mmmhhh.. and the keyboard is only in english
-you can import your contacts also from gmail... ok.. that's good
-there's a tutorial at the beginning that explains how it works :victory:
-camera just doesn't work (the camera is in use by another app) !!??!!
-some popular apps ready to install... ok, fine!
-to take screenshots you have to press home+power... but I can't get it :crying:
-settings menu is like a hybrid between android and ios
-all the gestures work properly and are different from android, but they're friendly :good:
-the phone is getting very hot now
-arrrgghhh.... force close... the phone rebooted automatically :crying:
yes for sure not ready for daily driver, but seems very nice
for screenshots I just used android normal gesture (power + vol down)
no recovery right? will have to flash FTF to go back to stock?
phone is not hot at all here so far
Problem with camera is in HAL. Logcat... logcat.
In AOSP builds there is no camera, this is the cause.
Seems problem has been solved. Waiting for new build from fxp team then
https://t.co/XGZ6c75N0X
it seems very very basic and not ready for daily use but well better than nothing..! let's see
xperia z3c fxos
right now the bug for the camera on the lollipop build is being worked on, as far as i can find in our bug reports the kk build camera should be working or it would be under QA-blocker. Also for some of the problems you are having such as only english when building make sure to put PRODUCTION=1 it will make it so it flashes all of the languages, that just has to do with not setting the right build variables.
Fxos-QA contributor rep
Sorry i would give you links but i am a new user on this site so i cant...
jamie_fxos said:
right now the bug for the camera on the lollipop build is being worked on, as far as i can find in our bug reports the kk build camera should be working or it would be under QA-blocker. Also for some of the problems you are having such as only english when building make sure to put PRODUCTION=1 it will make it so it flashes all of the languages, that just has to do with not setting the right build variables.
Fxos-QA contributor rep
Sorry i would give you links but i am a new user on this site so i cant...
Click to expand...
Click to collapse
not sure to understand correctly, you mean there is a firefoxos version based on kk for z3c with working camera? where?
because it seems I can find only the lp build in fxp site... thanks! :silly:
moly82 said:
not sure to understand correctly, you mean there is a firefoxos version based on kk for z3c with working camera? where?
because it seems I can find only the lp build in fxp site... thanks! :silly:
Click to expand...
Click to collapse
i just double checked with of the devs, The aires device, you can build the kk version which does have a working camera, you just have to compile it yourself. The lp build currently available on task cluster does not have the working camera, in all honesty the lp kernal version is not fully complete yet, right now the camera is one of those parts that are not fully complete. if you want to take a look the bug number is 1163557 you have to go to bugzilla.mozilla.org it might help explain the situation. right now lp is experimental.
firefox os QA
mozilla rep
Jamie Charlton
thanks mate, will do! and thanks also for the info, it is nice someone from firefoxos project directly is looking around here and share info with us!
unfortunately i'm not skilled enough for building myself, so can just wait for fxp team to build them for us.
afaik devs are working on updated/fixed camera blobs for lp as we speak, so we could have a decent camera available for aosp soon, in that case hope it will land in firefox os too
really looking forward for a usable build of firefoxos for our device, it seems a very nice project... i like firefox, i like opensource, i don't like google at all recently... so hope to find in fxos soon a great alternative! :good: :fingers-crossed:
moly82 said:
thanks mate, will do! and thanks also for the info, it is nice someone from firefoxos project directly is looking around here and share info with us!
unfortunately i'm not skilled enough for building myself, so can just wait for fxp team to build them for us.
afaik devs are working on updated/fixed camera blobs for lp as we speak, so we could have a decent camera available for aosp soon, in that case hope it will land in firefox os too
ht
really looking forward for a usable build of firefoxos for our device, it seems a very nice project... i like firefox, i like opensource, i don't like google at all recently... so hope to find in fxos soon a great alternative! :good: :fingers-crossed:
Click to expand...
Click to collapse
come end of next week i might be able to get you a kk build, i cant say for 100% due to moz is giving me mine next week. If it comes with a KK kernal on it i can see if I can make you one, i dont think it is under nda for the blobs for kk, im not sure 100% though. i just know for the flame device im not allowed to give out builds that have not gone through approval from t2mobile as distributable.
moly82 said:
1. rootable? DON'T THINK SO
Click to expand...
Click to collapse
Yes. rootable.
jamie_fxos said:
come end of next week i might be able to get you a kk build, i cant say for 100% due to moz is giving me mine next week. If it comes with a KK kernal on it i can see if I can make you one, i dont think it is under nda for the blobs for kk, im not sure 100% though. i just know for the flame device im not allowed to give out builds that have not gone through approval from t2mobile as distributable.
Click to expand...
Click to collapse
thanks mate you rock!
will see so, btw no need to hurry for me, as I am taking my z3c to assitance today or tomorrow (broken magnetic port :crying: ) and dunno when I'll see it again... :silly:
moly82 said:
thanks mate you rock!
will see so, btw no need to hurry for me, as I am taking my z3c to assitance today or tomorrow (broken magnetic port :crying: ) and dunno when I'll see it again... :silly:
Click to expand...
Click to collapse
By the time you get it back i hope that i will already have a working build for you.
Also people, if the base image you are using is gotten from mozilla its a 99% chance its rooted, they are left unlocked for testing and development reasons, the only time they are locked usually is when you are getting them from the phone manufacturer also know as a production build, which we do not make.
Mozilla rep
Firefox OS QA
Jamie Charlton
Okay i have looked into it, the only way i can make you a base image is if it is blib free so you would have to get the blobs from Sony. The blobs are currently under nda so there is no way i can share them without getting in trouble. The only way it seems you could get the kk build with a working camera is if you flash back to android and then get the blobs from the device and then from there you would have to add them to the blob free base image.
The project got already discontinued by Mozilla because the not given chance to get close to Android, iOS or WIP
Maybe with a hardboot kernel it could be saved as a stable, second OS with Multirom...
In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
ROMs:
HOW-TO Root and Install Stock ROM: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 7.0) - 4+64 Variant
- 20171028: https://mega.nz/#!4Lo2TJyJ!-m8rhxTJ3VCFjQnLfauIC2dGMfnPwGtcs7o32J4Et-k
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
- 20171022: https://mega.nz/#!t6onDL5D!JI3mdIyqG2A_pXtZ-vKzCAwj-QFBAFPCRIiM6TbbDZY
- 20170830: https://mega.nz/#!kLYjVTpY!l8_hoKlS7d0_RLV71xUBwL1w0lR11PN4IVPC1u26EEM
- 20170615: https://mega.nz/#!ZeQTARAQ!Z8q1hUWtMn6SXFtL-PfTFbwvQz6G9i46WosEXlU2ay0
Stock (Android 7.0) - 6+64 Variant
- 20171028: https://mega.nz/#!0bxyDQbb!FOnbe5cYZr7Q7DWQKgSx4IQ7Keiy7fD5aZ55ZOe9zDc
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
- 20171022: https://mega.nz/#!FOQHRIhB!nTA2F2SVAs4ncESTAJRyvHBIMBw5QU8Ot1Vl7lQL418
- 20170810: https://mega.nz/#!IP5xwabB!D2i1ac-utl6A8A-q77cvwE0iQmJBrjz1-c6imAZ5Xhg
- 20170621: https://mega.nz/#!AfIz3SLb!41TxksnjlcgN51t1MggQdoVRlVPiajcebaO6BEEpeug
Flash Tool
- SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP 3.1.1 by @jemmini (20170810 based): https://mega.nz/#F!FVsH2JLR!bKDbF3Wz3Jsyk8_A4R_m4g
Root:
Rooting Methods (if you are on Stock ROM)
- Pre-rooted boot.img for 4/64 variant: https://forum.xda-developers.com/showpost.php?p=74358280&postcount=335
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
How u do it man... So many development for so many devices... Share some knowledge dude.
sagargjasani264 said:
How u do it man... So many development for so many devices... Share some knowledge dude.
Click to expand...
Click to collapse
For Mediatek Devices it is pretty easy because if you manage to build a ROM for a device that has its software made by the same company who did the same software for another device (i hope this sentence is clear), then you can build a ROM for both devices with just some minor changes.
Alberto96 said:
For Mediatek Devices it is pretty easy because if you manage to build a ROM for a device that has its software made by the same company who did the same software for another device (i hope this sentence is clear), then you can build a ROM for both devices with just some minor changes.
Click to expand...
Click to collapse
Yep.. Got that line clearly... But what to do when u don't have source codes for your perticuler device or similar device with same company and software ? U can't build.... Am i right?
If its possible pls pm me.. I dont wanna add more off topic comments in ur thread..
sagargjasani264 said:
Yep.. Got that line clearly... But what to do when u don't have source codes for your perticuler device or similar device with same company and software ? U can't build.... Am i right?
If its possible pls pm me.. I dont wanna add more off topic comments in ur thread..
Click to expand...
Click to collapse
I'll just reply here for the last time, it is OT, but still useful for development
When there is no kernel source code, i use the prebuilt kernel image (included with the Stock ROM), while everything else gets compiled (excluding proprietary files required to handle the hardware).
Alberto96 said:
I'll just reply here for the last time, it is OT, but still useful for development
When there is no kernel source code, i use the prebuilt kernel image (included with the Stock ROM), while everything else gets compiled (excluding proprietary files required to handle the hardware).
Click to expand...
Click to collapse
I don't know i got last part correctly or not but i will google now for that.. Anyways thanks for information man.. Keep it up ur work.. And keep sharing knowledge..
... the rom - download (mega) is it working with the 4gb version too? great job so far...
i have tried that rom, it does not work for 4gb version, doogee logo stuck on the screen
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
i bought phone from banggood came with offical outdated software, so i will never get update.the only rom with update is 20170621. the rom that we have here 6gb version,hope someone will provide rom 20170621 for 4gb version.
many thanks
I'm also wondering about ROMs for the 4gb version of the phone? Have they updated that to the same level as the 6gb ROM? I thought the specs were identical apart from the extra 2gb of memory??
Can you do a rom for 4gb Version?
pheemc said:
Can you do a rom for 4gb Version?
Click to expand...
Click to collapse
"Can you do" doesn't exist yet.
It is only the Stock ROM provided by DOOGEE directly, not something I made. You have to ask DOOGEE if you want other variants, then provide me the link.
Ah okay, i thought this was the pure stock Android Rom without Doogee "bloat".... Do you think there will be a lineage Version in future?
pheemc said:
Ah okay, i thought this was the pure stock Android Rom without Doogee "bloat".... Do you think there will be a lineage Version in future?
Click to expand...
Click to collapse
It's too early to discuss about source-built ROMs, this is a pretty new platform.
hi guys,i cannot find any source that i can obtain doogee mix 4gb varient rom(build 20170621),i already asked admin doogee mix forum ,but no response.any idea where we can get that rom? thanks
the rom does not work . the flash tool say the scatter is invalid
libuda04 said:
the rom does not work . the flash tool say the scatter is invalid
Click to expand...
Click to collapse
It does, I have flashed it on my own MIX.
How did you flash it with SP Flash Tools?
When i connect and try it says BROM ERROR: STATUS_BROM_CMD_SEND_DA_FAIL(0xC0060003)
What does it mean.
I installed drivers for MT67xx and latest SP Flash Tool
I have my phone turned off and when i connect (after clicking download in SP Flash Tool) it says the error.
Hi guys, i'm pretty novice about all of this and i dont speak english a lot, i have a problem with my new DOOGEE MIX (6gb i think), i tried to uninstall the "DOOGEE OS" many times but i failed all time. There is a cat/gameboy on my screen and i cant remove them, maybe i can find an issue here. Thank a lot in advance and have a good day !
hi, do following:
home screen, press on the screen a few seconds,you will see launcher settings, then turn off search bar and know on home screen
hans2001 said:
hi, do following:
home screen, press on the screen a few seconds,you will see launcher settings, then turn off search bar and know on home screen
Click to expand...
Click to collapse
Oh yeah it worked ! I have almost intalled something for "root" my phone. Thank a lot dude !:laugh:
Do you know how to remove the last background on the left too ? The one with all the newspapers ? I'am actually searching on the new launcher settings but i cant find it, thank .
I don't know if anyone knows about or tested the Carbon ROM build on July, 2017 which I found. Here's the link-
https://get.carbonrom.org/device-mocha.html
Please enlighten me if this is a fake website and fake custom ROM for Mipad(mocha).
it's legit and official site there.
Carbon Rom is Real ..... Not Fake!!!!!!!
I'm using it for past one week . working great
jeswinkumar said:
I'm using it for past one week . working great
Click to expand...
Click to collapse
Can u review the ROM in details?
Like Installation process, Android version, Pros and Cons,Stability, battery life,Performance and smooth operations, etc..
rocky869 said:
Can u review the ROM in details?
Like Installation process, Android version, Pros and Cons,Stability, battery life,Performance and smooth operations, etc..
Click to expand...
Click to collapse
I wouldn't use it yet. It was a test build, there are some broken stuff in it. Official build (built by servers) need some extra work, because the device tree/vendor needs to work without changes to the source code itself. This is not possible with our current trees (highwaystar's work), and so there are some issues with that build. Primarily, the camera is broken, because SELinux is enforcing. I've fixed it my personal builds, but now there are some issues with webview crashing. This is why I refrained from making a thread here. Once it's 100% stable, I will make a thread here.
Feel free to use it but don't complain when you realize some things are broken.
drakonizer said:
I wouldn't use it yet. It was a test build, there are some broken stuff in it. Official build (built by servers) need some extra work, because the device tree/vendor needs to work without changes to the source code itself. This is not possible with our current trees (highwaystar's work), and so there are some issues with that build. Primarily, the camera is broken, because SELinux is enforcing. I've fixed it my personal builds, but now there are some issues with webview crashing. This is why I refrained from making a thread here. Once it's 100% stable, I will make a thread here.
Feel free to use it but don't complain when you realize some things are broken.
Click to expand...
Click to collapse
Thanks for the feedback. I am using BDITA ROM latest version for over 6 months, although on KitKat but its the safest and most stable ROM I found for our MIPAD. Battery life,performance and ROM stability are 3 important things I look for in any ROM and BDITA serves me well.
I will wait more until I find a ROM which can replace BDITA