Related
Hallo i watch all this roms... They are all 4.2.2. In the sort time adroid L its out... And i have the big question when we have one real update ??? I have this phone 9 months until now i live in eu
gkm8123 said:
Hallo i watch all this roms... They are all 4.2.2. In the sort time adroid L its out... And i have the big question when we have one real update ??? I have this phone 9 months until now i live in eu
Click to expand...
Click to collapse
100% agree but unfortunately duo to mate 2 is out they have no plan to update mate1 to 4.3 or 4.4:crying:
i really think ham is good phablet and deserve better support from manufacturer.
mazi_v said:
100% agree but unfortunately duo to mate 2 is out they have no plan to update mate1 to 4.3 or 4.4:crying:
i really think ham is good phablet and deserve better support from manufacturer.
Click to expand...
Click to collapse
This kind of support let me turn away from Huawei. A pitty. But i want decent support. A phone schould get 2 year regular updates. Thats wat a customer deserves
Well you'll have to dive deeply into it to do the job of building a custom Android ROM. I just downloaded the kernel sources from the official JB (4.1) release, but I'm not sure how far I can get with that. Some experienced devs here posted that they would need Huawei's sources for KitKat to build a KitKat ROM, but I also have an Ascend P1 and I'm running a custom KitKat CyanogenMod build from the forums here although Huawei only released ICS (4.0) Kernel sources. I will have a try with a custom cross compiling toolchain of mine that I use for my Radxa Rock, but it's quite generic. I'll let you know how far I could get if at all.
Cheers!
The kernel build was successful, but I've simply used Google's latest toolchain (arm-linux-androideabi-4.6-android-4.4.4_r1). I'm now syncing the most recent Android repo, that will take some time. I will try to set everything up to start compiling tomorrow morning or something...
Just in case you want to build the kernel yourself as well: There is an indentation issue in one of Huawei's Makefiles for the touchscreen, you'll see an error message about it if you run the first make according to the README_kernel.txt. You can just add tabs and your file should look like this:
[drivers/huawei/device/touchscreen_Mate/Makefile]
Code:
[COLOR="DarkOrange"]#
# Makefile for the touchscreen drivers.
#
# Each configuration option enables a list of files.
obj-y += synaptics_i2c_rmi.o
obj-y += rmi_dev_6.o
obj-y += rmi_f54_6.o
obj-y += rmi_fw_update_6.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean[/COLOR]
CyReVolt said:
The kernel build was successful, but I've simply used Google's latest toolchain (arm-linux-androideabi-4.6-android-4.4.4_r1). I'm now syncing the most recent Android repo, that will take some time. I will try to set everything up to start compiling tomorrow morning or something...
Just in case you want to build the kernel yourself as well: There is an indentation issue in one of Huawei's Makefiles for the touchscreen, you'll see an error message about it if you run the first make according to the README_kernel.txt. You can just add tabs and your file should look like this:
[drivers/huawei/device/touchscreen_Mate/Makefile]
Code:
[COLOR="DarkOrange"]#
# Makefile for the touchscreen drivers.
#
# Each configuration option enables a list of files.
obj-y += synaptics_i2c_rmi.o
obj-y += rmi_dev_6.o
obj-y += rmi_f54_6.o
obj-y += rmi_fw_update_6.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean[/COLOR]
Click to expand...
Click to collapse
A kitkat kernel that would make you in my opinion almost immortal for Mate users
henk_j said:
A kitkat kernel that would make you in my opinion almost immortal for Mate users
Click to expand...
Click to collapse
We'll see, I'm still learning about the stuff, but the chances look quite fair. I've set up the rest of the environment and the build is running now. But I guess it will take some more hours. I usually need about 3.5 hours to build chrome, firefox or libreoffice. AOSP should be similar. I'll see how far it got today evening/night. But for now it looks good, I'm running with -j4 as recommended. ^^
CyReVolt said:
We'll see, I'm still learning about the stuff, but the chances look quite fair. I've set up the rest of the environment and the build is running now. But I guess it will take some more hours. I usually need about 3.5 hours to build chrome, firefox or libreoffice. AOSP should be similar. I'll see how far it got today evening/night. But for now it looks good, I'm running with -j4 as recommended. ^^
Click to expand...
Click to collapse
if you have more cores processor why dont increase the thread value so that build process will complete more quickly
svvv said:
if you have more cores processor why dont increase the thread value so that build process will complete more quickly
Click to expand...
Click to collapse
I have 2 cores, so 4 is quite fine. The next option would have been 16.
Take your time! we need more developers
Any news ?
Really appreciate the works here.
so many had forgotten Mate 1 and P6 since 2 & 7 came out...
For me the first editions are always the best although the the 2nd might have little differences or improvements (but always have flaws or bugs more than the 1st editions)..
so very much grateful and thanks for devs that spent their time looking at mate 1 and p6...
Will donate if theres any need for it..count on me for that..
[email protected]
gkm8123 said:
Any news ?
Click to expand...
Click to collapse
Come on, I'm writing every couple of hours...
Well, the news is: v8 failed in some point. I've just resynced the AOSP repo to start over. ^^ I'll let you know how it went today evening. I also have a job, you know.
CyReVolt said:
Come on, I'm writing every couple of hours...
Well, the news is: v8 failed in some point. I've just resynced the AOSP repo to start over. ^^ I'll let you know how it went today evening. I also have a job, you know.
Click to expand...
Click to collapse
Ok no problem, thank so much for your help
Well, the newer patches didn't resolve the issue so I decided to try the normal user build (I tried a full debug build first). For now it looks very promising. I'm not sure if I can figure out how to to fix the issue I had, so if this one fails at the same point (although as far as I understood it was one of the debug parts so it shouldn't), it might get a little harder. We'll see ^^
thank you mate.. i mean CyReVolt.
i hope ur doing ok with ur job also,, and really hope u give us a good news..
cumanisengdoang said:
thank you mate.. i mean CyReVolt.
i hope ur doing ok with ur job also,, and really hope u give us a good news..
Click to expand...
Click to collapse
Sure, np... actually, it failed again due to the same problem, and I quickly figured out the cause (I already had suspected that): I'm on a strongly hardened Linux system, and the
Code:
mksnapshot
tool was killed due to NX protection (see http://wiki.gentoo.org/wiki/Hardened/PaX_Quickstart#Understanding_PaX). So if you're running a PaX protected kernel or similar you might run into the same issue. Duh... -.-
It's up and running again, so let's wait for a result!
While waiting you can try the Android kernel I have attached. Don't ask me how to do that. I have no clue. This is just for fun. And for you!
Considering work: It was actually quite funny today because I had to work on a Mac and OSX feels just horrible to me. My boss asked me to take a glance at Xcode and especially the new beta and Swift. I'm so glad to be back at my Linux machine now.
CyReVolt said:
Well you'll have to dive deeply into it to do the job of building a custom Android ROM. I just downloaded the kernel sources from the official JB (4.1) release, but I'm not sure how far I can get with that. Some experienced devs here posted that they would need Huawei's sources for KitKat to build a KitKat ROM, but I also have an Ascend P1 and I'm running a custom KitKat CyanogenMod build from the forums here although Huawei only released ICS (4.0) Kernel sources. I will have a try with a custom cross compiling toolchain of mine that I use for my Radxa Rock, but it's quite generic. I'll let you know how far I could get if at all.
Cheers!
Click to expand...
Click to collapse
The main problem is not the kernel. We can build a kitkat rom with the 3.0.8 kernel , but we have no source for display part , audio part. We have to use the prebuilt hwcomposer , grallloc etc. . These prebuilt libs are compatible only with the android version of the stock rom they are coming from and with the kernel they are patched for.
With sources of display driver we can patch the kernel and the driver to work on KK . Like I did JB on ZTE V11,V71,V55 tablet with 2.6.35 kernel , but that device was QC based device with available display driver sources. (http://forum.xda-developers.com/showthread.php?t=1629630)
I have compiled a 4.3 rom for mate , but I am stuck at display. There are changed routines in framework which are not working with 4.2's display drivers . One solution can be to get these sources , or to change the framework to work with the 4.2' display driver.
The Mate is my first non QC chipset based device , but also the last too. This is my fourth device from Huawei and until now I was satisfied , they simply do not care Mate customers. The release of the KK for Mate is just a few hours job , but they wont do it.
joe.stone said:
The main problem is not the kernel. We can build a kitkat rom with the 3.0.8 kernel , but we have no source for display part , audio part. We have to use the prebuilt hwcomposer , grallloc etc. . These prebuilt libs are compatible only with the android version of the stock rom they are coming from and with the kernel they are patched for.
With sources of display driver we can patch the kernel and the driver to work on KK . Like I did JB on ZTE V11,V71,V55 tablet with 2.6.35 kernel , but that device was QC based device with available display driver sources. (http://forum.xda-developers.com/showthread.php?t=1629630)
I have compiled a 4.3 rom for mate , but I am stuck at display. There are changed routines in framework which are not working with 4.2's display drivers . One solution can be to get these sources , or to change the framework to work with the 4.2' display driver.
The Mate is my first non QC chipset based device , but also the last too. This is my fourth device from Huawei and until now I was satisfied , they simply do not care Mate customers. The release of the KK for Mate is just a few hours job , but they wont do it.
Click to expand...
Click to collapse
Thats why we have to get some sense into their heads thats trough they're Wallet. The only way tot make them do this strangely by hurting them where it counts.
Alright, I'm getting the point now... so I did some research.
The GPU is a Vivante GC4000, so might this help https://github.com/laanwj/etna_viv ?
I wouldn't mind the sound at first. I would love to work on this somehow.
Can you point out which files I should look at? I know a bit about the ARM/Thumb ISA, so I'd try to reverse engineer a little to either adjust the pre-built drivers or the framework using them. =) I don't give up very quickly, you know! Finally, I'd just contact Huawei and talk straight to them. Thanks in advance for all your efforts.
Cheers
CyReVolt
I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app
I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.
Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app
How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?
hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0
I'm ready to do that work only if i knew how to...
Sent from my One V
hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.
http://downloads.sourceforge.net/pr...xz?r=&ts=1439784880&use_mirror=skylineservers
SHA1: 463f818fc8b57525981a46e31ea5ee63f2987742
MD5: 88d8db5d4c9637daeb339eb79878c93a
Mirror: https://mega.nz/#!j4s1WYLK!DpK2bMfznrt_ih3-UtE6xvUgFSAujw9LBu4qgSCSzkU
Thanks to @neilownz for notifying us in the system image thread! Let the rom development begin!
Oh and xposed framework also works for the idol 3 as of yesterday.
Click on mirrors. I already finished downloading it in case it disappears.
Yay. Let the development begin
Yes, thx alcatel !
thanks for noticing
damn you've been faster than me
Only source code for 4.7 ? Just decompressing it and seeing only idol347.... ?
Is source code for 5.5 also included ?
frankee207 said:
Only source code for 4.7 ? Just decompressing it and seeing only idol347.... ?
Is source code for 5.5 also included ?
Click to expand...
Click to collapse
Yes it is. Plus 1.8 GB external tools.
Game of Roms.
Roms are coming...
My favourite season of game of ROMs xD
hellow everyone,
sorry if is it the wrong place...our chip is the same as the one plus one? we can hack same system camera app and libs?
yazzabo said:
hellow everyone,
sorry if is it the wrong place...our chip is the same as the one plus one? we can hack same system camera app and libs?
Click to expand...
Click to collapse
No, the 6045 has a 64bit Snapdragon 615. The OnePlus One has a 32-bit Snapdragon 801.
someone could compile a kernel?
cpu -snap615-msm8939
board msm8916
32bits-arm.......64 bits -Aarch64 for gcc? or armv8?
arm64-defconfig
gcc version for compiling?
Woohoo cyanogenmod (or another ROM) here i come!!!
Successful compilation
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
petrov.0 said:
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
Click to expand...
Click to collapse
Does the source released allow for cross development ie if someone does put together a rom they can generate it for both the 6039 and the 6045 series? I'm waiting for the day someone generates a kernel with some of the newer governors like intellidemand or interactiveX...perhaps would solve any of the remaining lag and heat issues. I honestly thought they would have made factory rom downloads available first before source but certainly won't complain.
petrov.0 said:
I can confirm that there are no problems with the compilation of the kernel from the source (for my device of course, which probably most of you already know is 6039y). But that's all for now. There is much more work to be done.
Click to expand...
Click to collapse
Why I can not compile the kernel from arm64 none idol3 or idol347 defconfigs works, all the same mistake of the image with different gcc 4.8.2,4.9.3,4.9 .... you may need to install a tool in ubuntu 32bits to compile kernel 64bit?
on the contrary if you compile perfectly from arm (idol347) but not 64bit?
rarely anything but to extract the zip is idol347_fsr_20150717 while away the zip is OT_6039X_6045X_20150717.tar.xz but not impossible since idol347 is snap is 401 ... idol3 6045x 615
another rare idol347 has defconfig in arm and arm64 ... while idol3 only arm64
franq36 said:
Why I can not compile the kernel from arm64 none idol3 or idol347 defconfigs works, all the same mistake of the image with different gcc 4.8.2,4.9.3,4.9 .... you may need to install a tool in ubuntu 32bits to compile kernel 64bit?
Click to expand...
Click to collapse
I use the prebuilts from the Cyanogen repo. Also the recommended architecture of the host machine for compilation of Android is x86_64 from long time.
@franq36 ... In case that you are curious. This is the list with the installed gcc packages on the host machine.
Code:
gcc install
gcc-4.7 install
gcc-4.7-base:amd64 install
gcc-4.7-multilib install
gcc-4.8 install
gcc-4.8-base:amd64 install
gcc-4.8-multilib install
gcc-4.9-base:amd64 install
gcc-multilib install
franq36 said:
on the contrary if you compile perfectly from arm (idol347) but not 64bit?
Click to expand...
Click to collapse
Here are two logs from my virtual machine. The first build is for 32 bit architecture while the second is for 64 bit. The TARGET_KERNEL_ARCH in both cases however is arm. arm64 cannot be compiled successfully, as returns the following error:
Code:
make[2]: *** No rule to make target `zImage'. Stop.
make[1]: *** [sub-make] Error 2
franq36 said:
rarely anything but to extract the zip is idol347_fsr_20150717 while away the zip is OT_6039X_6045X_20150717.tar.xz but not impossible since idol347 is snap is 401 ... idol3 6045x 615
Click to expand...
Click to collapse
I don't understand what you mean here. The idol347 however is with Snapdragon 410 not 401.
franq36 said:
another rare idol347 has defconfig in arm and arm64 ... while idol3 only arm64
Click to expand...
Click to collapse
This is strange indeed.
---------- Post added at 19:52 ---------- Previous post was at 19:10 ----------
famewolf said:
Does the source released allow for cross development ie if someone does put together a rom they can generate it for both the 6039 and the 6045 series?
Click to expand...
Click to collapse
I'm not sure about this. The devices are different, the boards are different, the kernel configuration and respectively the kernel is different, the display resolution of the devices is different. These are too much differences I think.
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
keyra74 said:
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
Click to expand...
Click to collapse
i think you can contact the guy named mario tomas serrafero hes the one that writes the main page articles
keyra74 said:
How do we get someone from xda staff to post this in portal news so people will see they can now use the sources?
Click to expand...
Click to collapse
for now it is early, still are not completely operational ... I think for 6045
and I managed to fix compilation errors through installed ubuntu 14.04.3 64 bits and all the tools ...
idol3_defconfig is only arm64 and gives -mgeneral-regs-only error.
I could cheat and load it from arm but having to fix several compilation errors and dependencies bad in defconfig.
I am having many compilation errors which explains that the GCC is not quite right. NDK official gcc 4.9. arm-linux-androideabi have to look any more current or Linaro to check
I think there is a gcc 4.9.3
I'm half compilation with many problems ... I hope it's not the fault of sources and it is time lost
has any one started on porting CM12/12.1 ? you could count on me for testing
Is there a way that someone can make a Lollipop ROM for SM-T210R? Preferably CM 12.1 or a stock ROM. I have seen multiple people on these forums ask when this will happen. I've seen the Galaxy Tab 2 AND the ORIGINAL Galaxy Tab get Lollipop before Tab 3. The Tab 4 already got it...
Thanks, and I hope that we will see a day where everyone will have the latest version of Android on their devices...
TrendingTech said:
Is there a way that someone can make a Lollipop ROM for SM-T210R? Preferably CM 12.1 or a stock ROM. I have seen multiple people on these forums ask when this will happen. I've seen the Galaxy Tab 2 AND the ORIGINAL Galaxy Tab get Lollipop before Tab 3. The Tab 4 already got it...
Thanks, and I hope that we will see a day where everyone will have the latest version of Android on their devices...
Click to expand...
Click to collapse
Tab 3 has closed source I wouldnt expect any CM in the future
Sent from my white GT-I9305
why?
Minto107 said:
Tab 3 has closed source I wouldnt expect any CM in the future
Sent from my white GT-I9305
Click to expand...
Click to collapse
How come, I don't understand, there are serveral other ROM's for KITKAT, why would it be impossible to build a Lollipop ROM? I have NO idea how to build a rom, otherwise I would give it a try.
What makes it so difficult?
We don't have drivers to build any custom ROM rather than Samsung based one. We probably can have MIUI based on Sammy but if you want custom ROMs you've chosen a wrong tablet. Tab 2 7 would do a job correctly
Sent from my white GT-I9305
Minto107 said:
We don't have drivers to build any custom ROM rather than Samsung based one. We probably can have MIUI based on Sammy but if you want custom ROMs you've chosen a wrong tablet. Tab 2 7 would do a job correctly
Sent from my white GT-I9305
Click to expand...
Click to collapse
isn't there a Galaxy Tab 3 Lite lollipop ROM that we can port over to SM-T210R?
TrendingTech said:
isn't there a Galaxy Tab 3 Lite lollipop ROM that we can port over to SM-T210R?
Click to expand...
Click to collapse
None of TAB 3 family devices got 5.x so there's nothing to port. Tab 3 7,8,10 won't be updated to 5.x
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
Tab 3 8.0 has unofficial cm-12.1
Tab 3 8.0 has unofficial cm-12.1 and tab 3 10.1 also got it,
Grynot said:
Tab 3 8.0 has unofficial cm-12.1 and tab 3 10.1 also got it,
Click to expand...
Click to collapse
Omg but 8.0 uses Exynos 10.1 uses Intel and 7 uses ****ty Marvel CPU! You don't have source so no CM for you
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
So, im just stuck with effin 4.2? Since i originally rooted over a year ago, i have then tried to go back to stock to update, but ii can never get an ota update.....im just frustrated with all this. Trying to teach myself and getting stuck, SUCKS!!! I KNOW I DONT USE it to its fullest potential.....ANY help would rock....oh and would help my brain hurt LESS!! Thanks! !
rheecollinskelley said:
So, im just stuck with effin 4.2? Since i originally rooted over a year ago, i have then tried to go back to stock to update, but ii can never get an ota update.....im just frustrated with all this. Trying to teach myself and getting stuck, SUCKS!!! I KNOW I DONT USE it to its fullest potential.....ANY help would rock....oh and would help my brain hurt LESS!! Thanks! !
Click to expand...
Click to collapse
You know that Tab 3 8.0 is only 4.2.2 supported, not even close to KitKat, although you can find yourselves SM-T21x Kit Kat roms. Lollipop will not be supported by any chance, even for custom roms man!
It really depends on the amount of work you are willing to do.
Some parts are binary blob only *at this time*, but may change in the future.
For example, the Vivante GPU driver has some patches under review for the mainline Linux kernel and a open source driver in progress (look up etnaviv).
If you *really* want the Tab 3 7.0" to have Lollipop, you have to be willing to do some work. Maybe try to get some of the drivers that are used in the device into the mainline kernel. Maybe get basic functionality working.
In any case, it really is up to the community at this point, and we are part of the community.
vorpalblade77 said:
It really depends on the amount of work you are willing to do.
Some parts are binary blob only *at this time*, but may change in the future.
For example, the Vivante GPU driver has some patches under review for the mainline Linux kernel and a open source driver in progress (look up etnaviv).
If you *really* want the Tab 3 7.0" to have Lollipop, you have to be willing to do some work. Maybe try to get some of the drivers that are used in the device into the mainline kernel. Maybe get basic functionality working.
In any case, it really is up to the community at this point, and we are part of the community.
Click to expand...
Click to collapse
Yeah but XDA is full of noobs that only asks when, why it takes so long time... Bringing Lollipop to TAB 3 7inch is very hard work... This tablet wasn't a beast, since release date it was low end tablet with such tragic performance. For such noobs who just want and doesn't want to help I've got an advice. Get Nexus 7 2013... 6.0 on board, noob friendly
Wysłane z mojego Lenovo TAB S8-50L przy użyciu Tapatalka
As I know so far, Marvell didn't release source codes for Galaxy Tab 3, so it's impossible to build CM12 for this device.
DroidTwe4kz said:
As I know so far, Marvell didn't release source codes for Galaxy Tab 3, so it's impossible to build CM12 for this device.
Click to expand...
Click to collapse
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
vorpalblade77 said:
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
Click to expand...
Click to collapse
@gr8nole built unofficial CM11 from his own source. He wrote device specific tree I think.
vorpalblade77 said:
I *thought* everything that was necessary to build a working ROM was in Samsung's source dumps. Maybe not all the information required, but all the source code.
For that matter, I was under the impression that the unofficial Cyanogenmod port was working (Cyanogenmod 11) with an unofficial kernel.
Am I wrong?
If I am, then that might be why I have yet to successfully build a booting recovery, but other people have.
Click to expand...
Click to collapse
The only sources that Samsung provides is kernel sources. That is not nearly enough to build a completely working rom.
DroidTwe4kz said:
@gr8nole built unofficial CM11 from his own source. He wrote device specific tree I think.
Click to expand...
Click to collapse
Yes, I did build from my own device tree, but there were other devs that contributed a lot of the early work on that tree. I'm not going to try to mention all the names because I don't want to leave anyone out. But, suffice it to say, it wasn't just me. :good:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
gr8nole said:
The only sources that Samsung provides is kernel sources. That is not nearly enough to build a completely working rom.
Yes, I did build from my own device tree, but there were other devs that contributed a lot of the early work on that tree. I'm not going to try to mention all the names because I don't want to leave anyone out. But, suffice it to say, it wasn't just me. :good:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
Click to expand...
Click to collapse
You already did more than enough for our device and I'm thankful for that. Someone will continue to build CM based on your source.
gr8nole said:
To wrap up this post, the reason I gave up on CM for that device is because the Marvel hardware was too difficult (for me) to get working properly. Things like Wifi and hardware acceleration never worked well (or at all) and I don't have the ability to get them working any better. With essentially no other Marvel based devices to use as a guide, it was beyond my capabilities.
Click to expand...
Click to collapse
For hardware acceleration, did you ever look at the etnaviv project? I know that they are working on getting patches upstreamed for the GPU on the SM-T210 (Vivante GC 1000)?
For that matter, the Marvell SD8787 wifi chip has firmware mainlined (as of 2011, updated in 2015) and has driver support in "drivers/net/wireless/mwifiex/sdio.h" as of commit 4a7f5db1 (take a look at CONFIG_MWIFIEX). I don't know if its worth attempting to backport or not (some issues may have been fixed). Maybe look at the linux-firmware tree?
I'm pretty certain that at one point Marvell was looking at getting a device tree for the PXA986/PXA988 into the mainline kernel, but I don't think they succeeded.
Parts on the SM-T210R that I haven't found in the mainline kernel is the touchscreen. I haven't looked at everything else yet, and I'm not *absolutely* certain that the touchscreen isn't in the mainline kernel either (I might be looking at a config option and assuming the wrong thing from Samsung's sources).
EDIT1: I've been trying to build cyanogenmod on systems that aren't officially supported by AOSP, which is why I may have never been able to build it myself and *actually* contribute and check to see if etnaviv works, and if the mainline driver works better. Anyway, thanks for your work gr8nole (and everyone else's).
EDIT2: For SD8787 bluetooth support, look at CONFIG_BT_MRVL/CONFIG_BT_MRVL_SDIO
vorpalblade77 said:
For hardware acceleration, did you ever look at the etnaviv project? I know that they are working on getting patches upstreamed for the GPU on the SM-T210 (Vivante GC 1000)?
For that matter, the Marvell SD8787 wifi chip has firmware mainlined (as of 2011, updated in 2015) and has driver support in "drivers/net/wireless/mwifiex/sdio.h" as of commit 4a7f5db1 (take a look at CONFIG_MWIFIEX). I don't know if its worth attempting to backport or not (some issues may have been fixed). Maybe look at the linux-firmware tree?
I'm pretty certain that at one point Marvell was looking at getting a device tree for the PXA986/PXA988 into the mainline kernel, but I don't think they succeeded.
Parts on the SM-T210R that I haven't found in the mainline kernel is the touchscreen. I haven't looked at everything else yet, and I'm not *absolutely* certain that the touchscreen isn't in the mainline kernel either (I might be looking at a config option and assuming the wrong thing from Samsung's sources).
EDIT1: I've been trying to build cyanogenmod on systems that aren't officially supported by AOSP, which is why I may have never been able to build it myself and *actually* contribute and check to see if etnaviv works, and if the mainline driver works better. Anyway, thanks for your work gr8nole (and everyone else's).
EDIT2: For SD8787 bluetooth support, look at CONFIG_BT_MRVL/CONFIG_BT_MRVL_SDIO
Click to expand...
Click to collapse
I haven't looked at any of this in a long time, and have no real desire to at this point.
gr8nole said:
I haven't looked at any of this in a long time, and have no real desire to at this point.
Click to expand...
Click to collapse
Fair enough. I'll probably look into once I know I have my build environment set up correctly. E.g., I can build a recovery and have it work correctly.
Hi, I'm working on porting LineageOS to the J327P (j3popltespr), I have the kernel ready but the problem that I've encountered is the vendor tree. There seems to be no vendor tree available for the j3popltespr. I found a vendor tree for the 2016 J3 (github.com/djeman/android_device_samsung_j3xnlte - link to GitHub for the j3xnlte) which is a similar model in regards to being the predecessor of this device but otherwise have different CPUs (j3xnlte/J320 having an Exynos 3475 or Spreadtrum SC9830 CPU and j3poplte/J327P having a Qualcomm MSM8937 CPU) I don't know if I could use that vendor tree or if I'd have to manually get components from my own phone. There seems to be a phone named the BQ Aquaris U which has the same CPU and is officially supported by Lineage which might be a good place to start. Any help would be appreciated, thank you!
HUAWEI HONOR 7C also uses MSM8937 CPU.
AgentICS said:
Hi, I'm working on porting LineageOS to the J327P (j3popltespr), I have the kernel ready but the problem that I've encountered is the vendor tree. There seems to be no vendor tree available for the j3popltespr. I found a vendor tree for the 2016 J3 (github.com/djeman/android_device_samsung_j3xnlte - link to GitHub for the j3xnlte) which is a similar model in regards to being the predecessor of this device but otherwise have different CPUs (j3xnlte/J320 having an Exynos 3475 or Spreadtrum SC9830 CPU and j3poplte/J327P having a Qualcomm MSM8937 CPU) I don't know if I could use that vendor tree or if I'd have to manually get components from my own phone. There seems to be a phone named the BQ Aquaris U which has the same CPU and is officially supported by Lineage which might be a good place to start. Any help would be appreciated, thank you!
Click to expand...
Click to collapse
Hey did you ever have any luck? Or need me to mess around with mine or her anything for you?
EirikrHinnRauthi said:
Hey did you ever have any luck? Or need me to mess around with mine or her anything for you?
Click to expand...
Click to collapse
User sands207 was leading dev work on this device until a big fiasco caused him to cease development. I contacted him a few years ago after I messed up the baseband on my j327p and couldn't figure out how to make wifi work anymore. He graciously helped me out. Perhaps he still has some files that may be of use to restart new dev work.
funkybluemonkey3 said:
User sands207 was leading dev work on this device until a big fiasco caused him to cease development. I contacted him a few years ago after I messed up the baseband on my j327p and couldn't figure out how to make wifi work anymore. He graciously helped me out. Perhaps he still has some files that may be of use to restart new dev work.
Click to expand...
Click to collapse
Oh no! Do you know what kind of fiasco? Is it OK you think for me to @ him in here to check in?
EirikrHinnRauthi said:
Oh no! Do you know what kind of fiasco? Is it OK you think for me to @ him in here to check in?
Click to expand...
Click to collapse
It's a long read but this was my starting point for the j327p. https://forum.xda-developers.com/t/...-mobile-sprint-sprint-xas-and-virgin.3637741/ I believe it was him and another dev SonderTech that were the gurus for this device. I forget whom I actually messaged. If you read through all the links and pages it looks like they got it as far as 6.1.0 with quite a performance boost. I think what was preventing it further was something do with the kernel or device tree for the next version never being released for j327p.