Related
Xperia Play Users,
I am currently working on bringing CM10 to the Play, and I'm looking for input from anybody else who has ideas.
The Rules:
Post something constructive, no "Good Luck" "reserved" etc. this thread is for working through problems when building CM10
That said.
Update: I'll be posting errors here, so it'll be easy to keep track of.
First error I hit (& fixed? (compiler hasn't failed yet on this one)) deals with hardware/qcom/display/libcopybit where copybit_c2d.cpp fails to compile with a couple of errors related to "KGSL_USER_MEM_TYPE_ION" is not declared. (iirc)
I fixed this (I think) by replacing CM10's qcom/display with caf's qcom/display
Second error: (Erroring out right now)
In-line kernel building. I'm getting a (possible) GCC compiler false error where it says
Code:
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: In function 'wl_iw_set_pmksa':
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5335:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c:5338:5: error: array subscript is above array bounds [-Werror=array-bounds]
/home/paxchristos/Android_Source/cm10/kernel/semc/msm7x30/drivers/net/wireless/bcm4329/wl_iw.c: At top level:
cc1: error: unrecognized command line option "-Wno-unitialised" [-Werror]
Possible fix: for now turn off in-line kernel building until either error is solved.
Error 3 -- Removed in-line kernel building, but forgot to set device/semc/zeusc/prebuilt/kernel to copy to out/target/product/zeusc/kernel ... whoops
Error 4 -- The way things are sent to logcat has been changed from ICS
Code:
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_string:device/semc/msm7x30-common/liblights/lights.c:87: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function write_int:device/semc/msm7x30-common/liblights/lights.c:66: error: undefined reference to 'LOGE'
/home/paxchristos/Android_Source/cm10/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/zeusc/obj/SHARED_LIBRARIES/lights.semc_intermediates/lights.o: in function set_light_backlight:device/semc/msm7x30-common/liblights/lights.c:131: error: undefined reference to 'LOGV'
Fixed by copying over liblights/ from jellybean version of msm7x30-common/
Error 5 -- Same error happens with msm7x30-common/libsensors/
Fixed the same way as error 4
Error 6 -- Last error I'm gonna talk about tonight:
I did (apparently) a half baked revert to using a prebuilt kernel & it just bit me in the butt. I'll fix it tomorrow & keep updating this.
Fixed it by using half of FXP's custombootimg.mk where it calls (PRODUCT_OUT)/kernel instead of (TARGET_PREBUILT_KERNEL)
Anybody else up for learning with me & briniging JB to the Play?
Pax
UPDATE: Pre-alpha release are available here: http://www.mediafire.com/?6ggud46a7c6cq
Latest kernel is here: http://forum.xda-developers.com/showpost.php?p=29498363&postcount=233
Remember, this is an alpha, a lot of stuff does not work. Please logcat any errors you find, otherwise (unless it's something like baseband unknown) I WILL IGNORE THEM
What Works:
CDMA Data
Calls
SMS
AUDIO!!
HW Video
GPS
What Doesn't Work:
Haven't tested to much, you guys tell me
I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app
sasukekun67 said:
I came across this by googling, hope that helps :
http://forum.xda-developers.com/showthread.php?t=1104142&page=4
Cheers, I'm willing to learn if you don't mind teaching a newbie in dev
Sent from my Play using xda app-developers app
Click to expand...
Click to collapse
Thank you, I think for JB CM wants to use -O2 when compiling so I'm not gonna touch that one (for now)
A Good place to start would be with Keiran's building ICS tutorial with some changes.
First off, I'm using Ubuntu 10.04 LTS, but Ubuntu 12.04 LTS *should* work (no guarantees)
To download the vendor tree (vendor/semc)
use this instead of what Keiran has (koush cleaned out a lot of the vendor trees out of his git, and mine is outdated)
Code:
git clone https://github.com/kali-/proprietary_vendor_semc.git -b ics semc
also, I'm using the ICS device tree (same as keiran) instead of JB because the JB tree's are not 100% functional right now.
Pretty much if you follow that (& I suggest instead of doing make -j# bacon do mka bacon) & run into any errors, i'll help with whatever suggestions I might have (or anybody else)
Note: If somebody needs help trying to build AOKP, I'll help, but I'm not as familiar with the source as I am with CM
Pax
Also, before I forget, here a how-to sync caf's (code aurora forums) repo (similar to cm/AOSP/etc)
https://www.codeaurora.org/xwiki/bin/QAEP/
The branch I synced was jb.
Pax
Sent from my R800x using Tapatalk 2
First build is complete, I'm need to make a nanadroid & flash a new kernel (I'm on keics/CNA right now so it'll be a little bit before I post results )
Pax
hi,
it won't boot on sony ericsson hdpi devices without msm.... changes (look at mini pro thread you will find a lot of usefull information about it)
you need to enable triple buffer in the kernel
Thanks Nickholtus, i'll look into it.
Status 6 error in the update-script (really? off the cm-10 building ?!?!) so i'm working on that now...
if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel
nickholtus said:
if you can fix the framebuffer error in the kernel we have a fully booting rom
kamarush made a build for me (from cm10 sources) with play device tree (his own)
only that error is preventing a boot
edit: can you upload your current kernel?
i know a ugly fix to get it at least booting, but i am on holiday now and i only have a windows pc with slow internet and no kernel
Click to expand...
Click to collapse
I'll probably base it off either FXP or Mjolnir's kernel (sorry Lupus)
[sritke]Do you have a link with a how-to add in triple buffer? [/strike] CAF!! - https://www.codeaurora.org/gitweb/q...it;h=50c3bc621e2cf0c3587b1827d931738d148c33d8
UPDATE: Nickholtus, it's not this easy, is it?!?! https://www.codeaurora.org/gitweb/q...;hpb=1125e58c5744e1ad833e30e5d2a74eb6dca1ca20
Also, if anybody wants to try to fix the update-script, i've attached it
no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
edit:
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix
nickholtus said:
no i don't know, we think it is in msm_fb.c in the kernel source
see this post for more info: http://forum.xda-developers.com/showpost.php?p=29062634&postcount=177
---------- Post added at 09:03 PM ---------- Previous post was at 08:58 PM ----------
i don't think so, but i can't try it.
kamarush couldn't find it (how to enable triple buffer) but if that's it it is an easy fix
Click to expand...
Click to collapse
Here's the best diff (all 3) i've found for the commit
https://www.codeaurora.org/gitweb/q...ff;h=acffb1675f468a85f528e01707f3fa98f45b77f8
i am going ask kamarush and see what he thinks
he thinks it can probaply fix it
While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.
Sythedragon said:
While I'm no help for this, for the script stuff, can't you enlist the help of the supercharger guy? He seems to be pretty adept with script lark.
Obviously, that's coming from an outsider.
Click to expand...
Click to collapse
hahaha, different type of scripts, but thanks for the idea
Pax
Also: Made the changes in the kernel I have on hand, fxp's from cm9/10 source. I've added in the correct stuff to cyanogen_zeus_defconfig & mach-msm/board-semc_zeus.c as soon as I'm done downloading Doom's ndk, i'll try & build it & see if it works
Pax
kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster
nickholtus said:
kamarush is making the kernel for me, with triple buffer enabled
edit: haha you was faster
Click to expand...
Click to collapse
I was, then I got arrowed in the knee
Or i would be, but then my git clone downloads at ~200 kb/s
Nickholtus,
Here's a test kernel, the changes are in the zImage, the ramdisk is FXP's from well, it's a source build off code from yesterday.
thanks
going to try it now
still the same error
edit: i need to get adb working
doesn't find the device
Lemme look into it, i'll test it out shortly (trying to get my build of cm10 to install )
Pax
Edit: Nickholtus, could you post a link to your build, mine just doesn't want to work
Pax
Edit 2: I think it's because i'm coming from CNA to CM10, i'm gonna build cm9 then retry with that
Pax
i can't upload my build, the upload speed here is 15kbps atm
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull
mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.
I'm looking forward to seeing this forum get some custom ROMs too...
Looks like progress is getting on with it now
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app
hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.
Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2
Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:
It's been requested that I create a new thread for this so as not to clog up @milaq's thread.
As some of you may have seen in flintman's Evervolv and milaq's CM threads, there has been a lot of work on the 3.4 kernel for tenderloin. Its a pretty awesome feat to have this running on our good ol tenderloin. =)
The gratitude for this kernel and build needs to be given to almost anyone but me. (Flemmard, flintman, jcsullins, Dorregaray and everyone that came before me on this device (dalingrin, green, and other's I'm sure that I'm missing)). I've had my tenderloin for quite awhile but never really done much with it until recently.
Anyway, without further ado, I present to you nightlies of CM-11.0 for tenderloin with a 3.4 kernel and -caf based HALs. Basically what this means is we'll be running the latest code from codeaurora on our msm8660 tenderloin.
THERE WILL BE BUGS! This thing is not perfect. It is still in active development.
CURRENT BUGZ (in no particular order):
- Bluetooth steals battery, but DOES work (jcsullins) - also sixaxis app doesn't work =(
- Camera is a bit derpy still, major wip, it takes pictures though (Dorregaray)
- Other stuff? Probably, yea
Destructions: PLEASE READ
1. This is a /data/media rom (relevant). What that means is you should be partitioned with a very small 'media' partition and a very large 'data' partition. The benefit of this is that your /sdcard and /data partitions share the big chunk of your usable space, just like any newer phone does these days. Use TPToolbox to achieve the new partition scheme: http://forum.xda-developers.com/showthread.php?t=2756314
2. You'll need a recovery that has both /data/media support and selinux support. Any of the following will work. Flashable via recovery.
-PhilZ Clockworkmod 6.0.4.7 (non-touch)(will backup and restore in both cwm and twrp format)
-Milaq's ClockworkMod 6.0.5.4
-Flintman's TWRP
3. Now you're ready to flash the rom. Downloads here: http://www.invisiblek.org/roms/cm-11.0/tenderloin/
4. Gapps here: http://wiki.cyanogenmod.org/w/Google_Apps
I'd recommend wiping data when coming to this rom or going to a different one (going between milaq's and this should be fine).
These are automatically built on my personal server at home and then uploaded. There may or may not be issues during the build times so don't always expect a fresh build every day. You can follow the automated twitter account here which will spit out a tweet once the build is finished uploading.
Sources:
-Kernel
-Device Tree
-CM Sources (the rest of what's needed)
There are a couple more changes and a couple other repos that are required to build this. Add this stuff to your .repo/local_manifests/roomservice.xml in order to build this yourself (after syncing the cm source of course)
http://pastebin.com/jKAMWM8T
You'll also need to cherry pick this commit from jcsullins: http://review.cyanogenmod.org/#/c/54380
Feel free to fork and fix!
Again -
Thanks to everyone that has contributed to making this rom.
Flemmard, flintman, jcsullins, dalingrin, green, milaq, the entire CM team and I'm sure many others.
Good new year present.
Looking forward to when Bluetooth is working. That and the black boxes were the only thing keeping me off KitKat.
Sent from my TouchPad using XDA Premium 4 mobile app
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
k4ever said:
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
vinukondamahesh said:
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
Click to expand...
Click to collapse
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
k4ever said:
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
No clue. I heard of apps disappearing from the Google Home Launcher, but not getting completely removed or preventing apps from being installed. Is that the launcher you're using? Only remedy I heard from that (Milaq's CM11 thread, somewhere around page 40) was to just readd them from the app drawer.
Best advice is to wait for todays build to get uploaded and see what happens.
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
allstar319 said:
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
Click to expand...
Click to collapse
thank you its working nw
milaq actually has a flashable zip in his thread. that is the easiest. i was on 4.3 went into that recovery, made a backup then flashed the new cwm, rebooted recovery did a full wipe and flashed the rom and gapps and i am up and running. who would have ever thought we would have kitkat on a touchpad. not to mention a 3.x kernel. unreal, thanks for everyones work. Happy New Year
jerryatherton said:
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
Click to expand...
Click to collapse
Oops, I had the wrong image there. Link updated with the cwm =P
EDIT: Also added a flashable zip for it, had trouble downloading milaq's so I made my own =/
Anyone else getting a Core Process failure message when booting to the 01012014 Build?
I went back to the 12312013 build and all appears to be back to normal.
To be clear, I went straight to this build from a fresh CM9 image without booting into Android - ever. Got a second-hand device back from a relative, and pushed it to CM11, so it may have been a result of my own process.
I'll reflash 01012014 and see if the error persists.
--McBean
Really looking forwards to a stable version of this to try. Thanks for the effort.
BillzillaAus said:
Really looking forwards to a stable version of this to try. Thanks for the effort.
Click to expand...
Click to collapse
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
k4ever said:
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
allstar319 said:
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
Click to expand...
Click to collapse
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Click to expand...
Click to collapse
Also, the old kernel was preventing us from having "official" CM builds.
Getting SoD's once I turn the screen off. Tried the old way to fix that by raising the min clock, but that didn't seem to help. Any ideas?
k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
The 3.4 kernel, minimally, resolves an issues with the other CM11 builds where the core/stock apps were experiencing "black boxes" which prevented users from reading mail, using the browser to navigate and some other issues. Right off the bat, the new kernel resolves that issue.
--McBean
Here is the kernel source for:
General Mobile Discovery Elite
Gionee Elife E7
These two devices using the same kernel source. You should use the defconfig from your own device to compile and use it with shared source.
Source link: http://www.burakgon.com/kernel-sources-for-general-mobile-discovery-elite-and-gionee-elife-e7-is-here/
Have fun while modifying!
XDA:DevDB Information
Gionee Elife E7 - General Mobile Discovery Elite Kernel Sources, a Kernel for the GiONEE Elife E7
Contributors
burakgon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2014-04-01
Created 2014-04-01
Last Updated 2014-04-05
Thanks a lot burakgon. I knew you were the real deal! Can you please post your ROM as well which is used in discovery mobile? And your flash tools which you promised to release as well?
[OFF TOPIC]
@burakgon Sir i Need General Mobile Discovery Kernel Source... You Made ATOM ROM Having ATOM Kernel For General Mobile Discovery Which Means You Have its Kernel Sources... i Tried Kernel Sources Released By FLY For its Fly-IQ4410 But Those Sources Are Not Complete Lots Of Drivers Are Missing And There is No Hope From Other Rebranded Devices... its An Humble Request Sir
Sorry To Disturb You Here...
Thank You very very much
let my exams complete
i will port cm
if you can provide device tree it will be awesome
yasirmujtaba said:
if you can provide device tree it will be awesome
Click to expand...
Click to collapse
I will try
Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.
icoolguy1995 said:
Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2706689
burakgon said:
I will try
Click to expand...
Click to collapse
hey burakgon did you got correct sources from gionee
i heard you were talking to gionee support for problems with kernel sources
pls reply
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..
GTARaja said:
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..
Click to expand...
Click to collapse
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.
Ravikirancg said:
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.
Click to expand...
Click to collapse
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time
Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.
GTARaja said:
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time
Click to expand...
Click to collapse
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
dhirajranger said:
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.
Click to expand...
Click to collapse
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..
Ravikirancg said:
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..
Click to expand...
Click to collapse
Missing dt.img??
Sent from my ST25i using Tapatalk
AnoopKumar said:
Missing dt.img??
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..
They use some dtb.img.......
Have a look at dtb.img method
Sent from my Discovery Elite using XDA Premium 4 mobile app
This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
Ravikirancg said:
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..
Click to expand...
Click to collapse
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk
AnoopKumar said:
This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
yes I did that.. and as you mentioned, I get a white screen.. actually, my kernel itself didnt compile.. but I had some dts files and built a dt.img out of it.. if you built a stock kernel, mind sharinng your dt.img?
This is a build of Cyanogenmod 12.1 for the Tab S 8.4 LTE (SM-T705). This build is based on the last copy I had of Eousphoros' device tree source prior to them being deleted. All credit therefore goes to Eousphoros for the original port. I have only fixed a couple of build errors against the latest 12.1 source.
Please note that although I've checked that the basics are working there will probably be a few bugs. I don't think the device tree I had saved was the latest from the last of Eousphoros' builds so there may even be regressions from his last build. On the plus side the build should incorporate the security fixes in CM 12.1 since then.
I have limited spare time and I'm fairly new to building Android, so in all likelihood I won't be able to fix any issues you have quickly. I'll post a new build from time to time if people are interested, but don't expect daily / weekly builds.
**** Update 06/09/15 - I've made a new build which hopefully fixes the microphone during calls. Link is updated below.
**** Update 31/08/15 - It is my experience that the mobile data is a lot more stable if you have a KitKat radio installed and don't install the Lollipop libs. This is also backed up from comments in the thread I therefore recommend that if you plan on running this Rom you flash a KitKat radio. I use version T705XXU1ANF. I've put a link to this below (use the 'CP' slot in Odin).
Installation
Flash the zip file in recovery (I used TWRP)
Flash Google apps
If your coming from a stock Lollipop rom, rather than Kitkat, then you need to flash the lollipop-radio.zip. (this will give you the correct libs for the Lollipop baseband to get data working.) **** See note above. It is more stable to flash the KitKat modem.
Downloads
cm-12.1-20150904-UNOFFICIAL-klimtlte.zip https://www.dropbox.com/s/1ozly8yyupud727/cm-12.1-20150904-UNOFFICIAL-klimtlte.zip?dl=0
lollipop-radio.zip https://www.dropbox.com/s/9ag8lyrjk6twlre/lollipop-radio.zip?dl=0
modem.bin https://www.dropbox.com/s/fjhyr2tkgzzz10b/modem.bin?dl=0
These are also mirrored at the link below (Thanks to bu44er)
https://drive.google.com/open?id=0Bw9GrMgIwzUKTmdoTGNwdHZzV1k
Old Versions
cm-12.1-20150822-UNOFFICIAL-klimtlte.zip https://www.dropbox.com/s/0zs9xv7tqtoyyhu/cm-12.1-20150822-UNOFFICIAL-klimtlte.zip?dl=0
Source
Device Tree https://github.com/mtdoughty/android_device_samsung_klimtlte
Kernel https://github.com/mtdoughty/android_kernel_samsung_klimtwifi
Vendor Blobs https://github.com/mtdoughty/android_vendor_samsung_klimtlte
I have just downloaded the files and I am flashing immediately. I'm hoping data works because if it does I'm buying you a beer (please tell me you drink beer)?
---------- Post added at 11:42 PM ---------- Previous post was at 10:45 PM ----------
Works flawlessly here, data works and not had one issue. I owe you a beer.
Sent from my SM-T705 using Tapatalk
bu44er said:
I have just downloaded the files and I am flashing immediately. I'm hoping data works because if it does I'm buying you a beer (please tell me you drink beer)?
---------- Post added at 11:42 PM ---------- Previous post was at 10:45 PM ----------
Works flawlessly here, data works and not had one issue. I owe you a beer.
Sent from my SM-T705 using Tapatalk
Click to expand...
Click to collapse
Also call feature work?
mtdoughty said:
This is a build of Cyanogenmod 12.1 for the Tab S 8.4 LTE (SM-T705). This build is based on the last copy I had of Eousphoros' device tree source prior to them being deleted. All credit therefore goes to Eousphoros for the original port. I have only fixed a couple of build errors against the latest 12.1 source.
Please note that although I've checked that the basics are working there will probably be a few bugs. I don't think the device tree I had saved was the latest from the last of Eousphoros' builds so there may even be regressions from his last build. On the plus side the build should incorporate the security fixes in CM 12.1 since then.
I have limited spare time and I'm fairly new to building Android, so in all likelihood I won't be able to fix any issues you have quickly. I'll post a new build from time to time if people are interested, but don't expect daily / weekly builds.
Installation
Flash the zip file in recovery (I used TWRP)
Flash Google apps
If your coming from a stock Lollipop rom, rather than Kitkat, then you need to flash the lollipop-radio.zip. (this will give you the correct libs for the Lollipop baseband to get data working.)
Downloads
cm-12.1-20150822-UNOFFICIAL-klimtlte.zip https://www.dropbox.com/s/0zs9xv7tqtoyyhu/cm-12.1-20150822-UNOFFICIAL-klimtlte.zip?dl=0
lollipop-radio.zip https://www.dropbox.com/s/9ag8lyrjk6twlre/lollipop-radio.zip?dl=0
Source
Device Tree https://github.com/mtdoughty/android_device_samsung_klimtlte
Kernel https://github.com/mtdoughty/android_kernel_samsung_klimtwifi
Vendor Blobs https://github.com/mtdoughty/android_vendor_samsung_klimtlte
Click to expand...
Click to collapse
thanx a ton buddy downloading
will report bugs if found any
cant make phone calls unless using a earphones
and i even cant end or receive calls... waiting for fix
yep
pincakez said:
cant make phone calls unless using a earphones
and i even cant end or receive calls... waiting for fix
Click to expand...
Click to collapse
you're right mate, this is a known issue for eusphorous cm12 build and this is based on that rom so no doubt it also got that bug. Didn't yet tried the rom so that i can also give a feedback. downloading.
can you mirror it mate? too slow for me
I'm uploading the installation file and the lib files to my Google Drive. I'll share a link as soon as they have uploaded.
Sent from my SM-T705 using Tapatalk
thank you!
bu44er said:
I'm uploading the installation file and the lib files to my Google Drive. I'll share a link as soon as they have uploaded.
Sent from my SM-T705 using Tapatalk
Click to expand...
Click to collapse
nice mate
https://drive.google.com/folder/d/0Bw9GrMgIwzUKTmdoTGNwdHZzV1k/edit
---------- Post added at 06:23 PM ---------- Previous post was at 06:23 PM ----------
That's the radio file, I just need to upload the flashable CyanogenMod
Thanks for your effort dude.
Hope that this project will help you to improve your skills and more developer can join this project to help you.
how the battery life? gaming temps?
My battery life was really good, been watching HD video all day
---------- Post added at 06:11 AM ---------- Previous post was at 05:54 AM ----------
Here is a link for anyone who would like the files. I've uploaded the installation files, radio files and the Google Apps Package I like using.
My Google Drive Folder
https://drive.google.com/open?id=0Bw9GrMgIwzUKTmdoTGNwdHZzV1k
@bu44er
many thanks for your great job !!!! you are the one and only, make offer to load a new CM 12.1 for my 705 !!! must flash it !!! thanks
Thanks should go to @mtdoughty as he's got everything work and has obviously worked hard doing so. I don't mind providing a permanent mirror for anyone who needs it.
Sent from my SM-T705 using Tapatalk
Thnx @mtdoughty, much appreciated, testing right now.
Hmm, for me, youtube is not working, video wont start to play. Do I need to flash libs or install additinal video players?
Update: oh, youtube works with chrome, but not with the default browser for me ... strange.
@muff99
perhaps it may be that YouTube indeed his own player with brings, but in CM 12.1 the link missing for stock player samsung? I was already with earlier versions. the same can happen if I use the stock player on my ironrom uninstall, because I prefer to work with the MX Player. is just a thought, not a fact.
all things work great
call dial nd ending can b achieved by another external dialer app
bug mic not working unless ur r on speaker phone or headset
Is data working?
Data is working for me but I can barely use the phone for calls as the sound is very bad and drop the call frequently. I've tried with earphones, BT headset and the tab itself with the same bad audio.
Anyone with the same symptoms?