Related
This isn't another one of those 'can somebody port Sense' threads.
Please note that this thread is for developer-oriented discussion. If you don't have anything to say to help development, please refrain from posting here.
Also note that ideas are welcome. Just check if the idea you're about to post has already been posted by somebody else.
Right now, it's just multiple people working on this. No team, just individuals.
As of the last edit of this post, there has been little to no progress:
I'm constantly working on builds. The current, and the only goal I'll be striving towards as of now is using a T-Mo HTC One X ROM in combination with RaymanFX's CM10.1 RC2 build.
XDA RC @abcdjdj has reported that he has fixed a lot of errors in his build, and is now stuck at the bootanimation. If you can help him in any way, here is what's wrong with his build. He's using FXP's CM9 as a base and a 4.0 HTC One X with Sense 4 ROM as a port.
The OP will constantly be updated with any progress anyone makes.
We're currently using this XDA thread to help us port the ROM.
--------------------------------
Here's everything I have to share on my build:
PORT: HTC One X, T-Mobile Edition| Android 4.2.2
BASE: Sony Xperia S, nozomi | Android 4.2.2
------------------------
ITesters needed. If you can work through adb commands and can provide me with logcats, please leave a post about it in the thread.
And finally, a note to anyone that may be cursing me for working so very slow (because I admit, this is very slow):
Please understand that all this isn't easy for me. I have painfully slow internet, making each download at least one hour, and thus a pain. My time on this project is limited every day, so progress is slow.
Reserved.
someone755 said:
Okay, so this is the work that has already been done and some of the mysteries that puzzle me right now:
I've edited the CM9 kernel's ramdisk, like stated in the tutorial I'm using (see post 1). As of now, the kernel itself is broken and even if the ROM was complete, not even the booting would work. (Well, booting works as far as showing the boot logo (the green FXP one) goes. But the LED notification light for entering recovery doesn't light. Bootloop over and over...)
Many of the lib files intended to be copied from one lib folder to the other are missing on our Nozomis... My question is, what are the consequences...?
My main issue here is that the zip won't flash. The recovery (no matter which I choose) just returns an 'ERROR' and refuses to flash the file...
Another question would be how to repack an .elf kernel into a boot.img. Because now, I'm trying with letting the CM9 kernel in the zip (since it is an .img) and then flash the modified .elf kernel that I repacked with Flashtool. Inefficient, but at least there's a way.
So currently, the priority list would be:
1.Get zip to flash
2.Fix kernel
...Not necessarily in that order. We could fix the kernel first, but there isn't much gain to it if the ROM zip can't even be flashed to test if it truly works...
Click to expand...
Click to collapse
Bro, it may be possible to get Sense on our devices. Even I have been working on getting Sense booted on our device. My status:-
PORTED FROM - HTC ONE X
BASE - FXP 215 CM9
STATUS - Gets past kernel and even loads bootanimation. Fixed many errors in the logcat. Gets stuck at bootanimation and even displays a message saying that System is not responding, would you like to close it.
I couldn't manage to fix any more errors in the logcat so I gave up but you have rekindled my spirit to get Sense booting on out device. I will upload my rom soon along with the logcat.
Cheers,
abcdjdj
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
someone755 said:
Wow, you actually got the thing to boot?
The only question is how did you manage that based off of a tegra CPU? Would be very interested in seeing that...
On a not-so-very related note, your port was of ICS and Sense 4 , correct?
Am I the only one around here that favors old software?
Click to expand...
Click to collapse
Not fully booting but I think close to booting. I followed the guide mentioned by you in the OP and one by one eliminated all errors that I could eliminate. I had been working on Sense for around a month during my school holidays but now I am not getting any free time. And yes it is Sense 4 (Android 4.0.4).
Sent from my LT26i using xda app-developers app
But isn't the Tegra3 completely different than our FUJI board?
Especially the graphics, those must be out of control on your ROM...
If I were you, I'd at least take the AT&T version of the HOX.
Oh yeah, I forgot to ask: is it the same if I try and port from a MSM8260 board (the same as the Xperia) and the later S4 Qualcomm versions (used in the Xperia T, AT&T One X etc.)? Because porting from a CDMA phone (HTC Rezound) seems to make the work harder...
Thankfully, my summer holidays have just begun, so I have plenty of free time (that's also the reason I started my project).
P.S.
Yeah, maybe that's exactly what I should do. Ditch the CDMA phone and start with the Snapdragon S4 One X!
I would prefer Sense 3.x, but oh well, at least Sense4 is also Sense
http://www.xda-developers.com/android/sense-4-ported-to-sony-xperia-devices/
I just found this. It's not even that old...
Anyways, I've been thinking if the devs of this would be able to help us.
This development stuff gets boring pretty quick when you do it for the 10th time
@samuel2706, could you give these guys a little hand?
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
someone755 said:
But he's a HTC Dev... Wouldn't we need something more like a nexus or better yet a Xperia developer?
Click to expand...
Click to collapse
Yes,, maybe, but he also could give a little help. Can't he?
Sent From my LT26i using Tapatalk 4
Contact the guy who did this http://forum.xda-developers.com/showthread.php?t=2184706
Well, I thought I'd make this thread so that devs could help each other to actually work together and create a working Sense ROM. So naturally, all help is welcome from anyone.
Anyways, I'm on my way to finishing yet another try, this time with the AT&T One X. Fingers crossed that it at least makes it to the bootanimation.
EDIT: I see that the easiest way to get Gapps is with including the default /data folder from the original HTC ROM (with vending, youtube etc.). But I have to add that to the updater-script. So, I want to ask, is /dev/block/mmcblk0p14 the data partition on the Nozomi?
What's happening?
samuel2706 said:
What's happening?
Click to expand...
Click to collapse
Hi,
I am porting [or trying to port] Sense 4 from HTC One X to Xperia S. I used FXP 214 CM9 as a base. I followed this guide - http://forum.xda-developers.com/showthread.php?t=2245786
Then I fixed as many errors as I could by checking the logcat and got it till the Bootanimation. But now I need help to get it to boot. So, I have attached the logcat from my latest build.
Thanks for your help,
abcdjdj
Maybe copying a few more files could help. Maybe act like your xperia is a HTC device? http://forum.xda-developers.com/showthread.php?t=1222746
Could be worth a try and play with this copying a bit...
Seems to be failing at dalvik; very strange, it doesn't show any major errors on first glance however I'll take a longer look at when I can, however I can link you to this thread that may help you in the meantime Porting
What about this one? http://forum.xda-developers.com/showthread.php?t=2276871
Nice and automated, but the question is, will it work?
I'm trying it with the HOX, just need to wait for it to copy to the phone...
All this seems like a big race -- who will get it working first? Hyped!
Kinda makes me wish I still had my xperia S I could have given this a real good go at; but instead I have a galaxy s4, so it's going to be mostly logcats and such I can help with, I don't like blind building things; made that mistake before.
A blind build is better than no build. Unless it makes bricks...
Thanks a lot for helping out.
Though I'll never understand how a pro HTC dev can go to Sony and then Samsung. ;P
I just hope THIS time my kernel will boot... Cause if it doesn't ... [censored]...
EDIT: Okay, [censored] is happening... Why can't I make this zip flash? I've done it a million times, but all I get is ERROR... ;-;
unfotunatly, i'm not a dev. but i really like the idea. specially if considering porting htc one sense version to our nozomi. i think it would fit like a glove
Hi.
First of all, thanks for all you great people for working and developing for these phones.
Today, for the first time, I flashed my phone. Having android on Wave 2 feels great!
I installed CarbonRom but I'm not entirely satisfied with it and wanted to try to install some other ROM (like ZenDroKat, I heard good things about that one) and run into a problem. I noticed that my PC doesn't see the phone at all! There is no reaction, not sound when connecting the phone. I tried the front and the back usb-ports, and on our family laptop. The multiloader doesn't find the port either.
Although it did react in recovery mode (TWRP) and installed drivers for "Android Composite ADB Interface", whatever that is.
Or could I install a new ROM without trying to fix this?
Once i had a problem detecting my phone , i was so frustrated : what worked with me , maybe this sound silly but :
Does your phone charge with the USB cable :
if yes in mini USB port there is a tongue inside , trying raising it a little with a sharp metal
if no , maybe your cable is the problem .
between that and this , probable you can install Omni rom , by copying the rom to sdcard if you have external card reader , since you have already TWRP installed.
Thanks.
I did figure it out. Well, I didn't fix it on CarbonRom but I managed to install another ROM. The USB worked in Download Mode, so I just re-installed Bada and then installed ZenDroKat ROM. For now it seems to work fine.
Now, is there a way to delete your own threads?
I have Windows 8 on my computer, when I update my windows with connected phone it shows Acer updates in Microsoft update menu. I update all, and after my computer didn't recognize my phone. Then I delete Acer drivers and it recognize again
Sent from my GT-I9000 using XDA Free mobile app
DkayBlack said:
Thanks.
I did figure it out. Well, I didn't fix it on CarbonRom but I managed to install another ROM. The USB worked in Download Mode, so I just re-installed Bada and then installed ZenDroKat ROM. For now it seems to work fine.
Now, is there a way to delete your own threads?
Click to expand...
Click to collapse
i think Omni is better ,and stable ,try it
ice_ice said:
i think Omni is better ,and stable ,try it
Click to expand...
Click to collapse
Yeah, I'm having issues with ZenDroKat. Namely, it often refuses it go out of sleep mode, I missed phone call due to that.
I'm going to try Omni then, thanks for advice. There are so many roms, it is hard to determine which one is better at a first glance.
DkayBlack said:
Yeah, I'm having issues with ZenDroKat. Namely, it often refuses it go out of sleep mode, I missed phone call due to that.
I'm going to try Omni then, thanks for advice. There are so many roms, it is hard to determine which one is better at a first glance.
Click to expand...
Click to collapse
Short development history: by Rebellos
The project has been started by Oleg in March 2011 - development progress has been made rapidly by him, however, he had been using JTAG Riff Box to make Wave oneNAND memory organisation the same like in Samsung Galaxy S (SGS) I9000 - phone with very similiar hardware to Wave. The problem is it's very expensive and advanced stuff. In the meantime mijoma found security hole in Wave's Bootloader3 (BL3) FOTA loading code and made PoC-exploit for that. That allowed me to create, with help of srg.mstr, mijoma and b.kubica, simple Badadroid bootloader, loading kernel zImage from moviNAND flash memory - this is where port has been made bootable on literally any Wave phone. However, oneNAND layout still remains untouched and by default kernel is configured to use SGS oneNAND partitions. So nbates66 and anghelyi put all their efforts into making this method of booting operatible. It succeed after few days and ShadowAS1 had released unofficial tutorial explaining how to bring up pre-alpha Android into S8500 device. The problem was that only 1 bootloader version was supported this time, mijoma came up with idea of making our FOTA bootloader capable of supporting alot of bootloaders - he created "BL Univ Boot FOTA". Oleg became very busy with his real life stuff so kernel development practically stopped. Currently I'm the most active kernel developer, altough I'm not so experienced as Oleg is and I'm learning from scratch so it goes very, very slow.
December 2011 - KB_Jetdroid contacted me and we started to work on Jet&Wave modem driver.
April 2012 - mikegapinski has joined the project to get things together and make first really working ROM.
9 April 2012 - Mike got ICS platform booting.
Mike has stopped maintaining platform so I took it over.
Oleg has finally got S8530 in his hands and made SCLCD driver for it. Praise him!
Both S8500 and S8530 versions are semi operatible. The most complicated, annyoing, and needed driver is Modemctl+RIL.
March 2013 - World's first working non-AT commands based RIL for non-Android phone has been released. Most of the implementation was done by KB_Jetdroid, me and Volk204, basing on opensource Replicant's RIL for Samsung Galaxy S.
April 2013 I finally fixed S8530 display driver.
September 2013 - we've got working microphone recording, and shortly after Tigrouzen found a proper patch fixing voice communication during calls.
22 September 2013 - we released first version capable of multicalls.
~~October 2013 - GPRS connections are working
Currently most of the core work is done.
We are working hard with Volk204 on RIL interface, doing small progress day by day.
en very brief : there was one team , that did all the work since the start ,"the Badadroid team" , Badaroid developed by Rebellos and Volk204 was a base for Omnirom ported by volk204 which he is the main developer now , and all those rom you see is basically noob roms , they copy the work of Volk204 , they are actually no developers in the first place, if Volk204 doesn't fix the bugs in his roms , their roms has them . i would recommend
Nand - use Omni rom http://forum.xda-developers.com/showthread.php?t=2800014
u wanna keep bada - Badadroid 4.4 http://forum.xda-developers.com/showthread.php?t=2609560
Hero355 is also a good one but he has own bugs and he isn't around much this days , work on it stopped http://forum.xda-developers.com/samsung-tizen/bada-android/rom-carbonrom-s8500-s8530-t2840174
read this thread http://forum.xda-developers.com/showthread.php?t=1459391
Thanks, that's quite interesting.
It's amazing that you people are still developing for these phones. They are so outdated that I wouldn't have guessed that anyone bothered with them.
ice_ice said:
u wanna keep bada - Badadroid 4.4 http://forum.xda-developers.com/showthread.php?t=2609560
Click to expand...
Click to collapse
Why would anyone want to keep bada? Isn't the main reason to install android-based ROM to get rid of that awful system? :laugh:
DkayBlack said:
Thanks, that's quite interesting.
It's amazing that you people are still developing for these phones. They are so outdated that I wouldn't have guessed that anyone bothered with them.
Why would anyone want to keep bada? Isn't the main reason to install android-based ROM to get rid of that awful system? :laugh:
Click to expand...
Click to collapse
THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DOESN’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.
KNOWN BUGS (what doesn't work):
- Modem in 2G mode work incorrect(Network registration don't work with some SIM cards, permanent full signal straight, problem is with audio in calls)
With 3G all is OK, Use this: Settings -> More.. in "wireless&network" category -> Mobile Network -> Preferred Network type -> 3G only
- Conference Calls
- Some problems with audio codec settings, but generally it should
For me : Call diverting , not working
GPS not fully working
Roms is amazing , fast , but not so fast when installing Gapps ,(i did install them , but i disable all of it)
Battery life
don't get me wrong Omni is my daily rom , but this could be a problem if talk to much on phone , battery drop out fast , with average use it won't last 10 hours
Good day XDA!! This is my first ever post or thread on XDA, for about 5 years I have been a spectator to this site, and it has been an essential source for all things us android foondies want and need. But for the past month I have hit a blank when it comes to my new tab3 ve 7.0 sm-t116nq (goyave3g).
It started when I wanted to root it, little to no support for this model was available (at least through the search function) I managed to root through Kingo root on a pc. But now my dilemma is finding/porting rooms for this model. I have no problem with all my Mediatek androids, but I'm in the dark when it comes to samsung. I don't even know where to begin, for other popular Samsung's it's not a problem, obviously because they're popular.
SO, I need some help. I hate this abomination they call touchwiz, I want a vanilla aosp rom for this model, or even better CM or PAC-MAN rom!! I am prepaid to put a lot of time and effort into this. I have extremely limited experience, most of my past successes was actually the success of other xda members (you guys are awesome BTW.) Any info would be apriciated.
So let's revive this tablet and let's start a revolution for budget tablets.
Dudzzz576 said:
Good day XDA!! This is my first ever post or thread on XDA, for about 5 years I have been a spectator to this site, and it has been an essential source for all things us android foondies want and need. But for the past month I have hit a blank when it comes to my new tab3 ve 7.0 sm-t116nq (goyave3g).
It started when I wanted to root it, little to no support for this model was available (at least through the search function) I managed to root through Kingo root on a pc. But now my dilemma is finding/porting rooms for this model. I have no problem with all my Mediatek androids, but I'm in the dark when it comes to samsung. I don't even know where to begin, for other popular Samsung's it's not a problem, obviously because they're popular.
SO, I need some help. I hate this abomination they call touchwiz, I want a vanilla aosp rom for this model, or even better CM or PAC-MAN rom!! I am prepaid to put a lot of time and effort into this. I have extremely limited experience, most of my past successes was actually the success of other xda members (you guys are awesome BTW.) Any info would be apriciated.
So let's revive this tablet and let's start a revolution for budget tablets.
Click to expand...
Click to collapse
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Thunderoar said:
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Click to expand...
Click to collapse
Oh, such a good news, but tell me, will your cm support sm-t113 too bro?
x3m_zion said:
Oh, such a good news, but tell me, will your cm support sm-t113 too bro?
Click to expand...
Click to collapse
dont know, still testing
Thunderoar said:
good news,i'm currently developing cm for this tab it might take a while depending on the device itself
Click to expand...
Click to collapse
How is it going? Any news for us?
danny02 said:
How is it going? Any news for us?
Click to expand...
Click to collapse
i decided to suspend the project because of school though
Estamos presos no Android 4.4.4 =/
Maldito SM-T116BU
But is not there anyone interested in developing a rom with Lollipop for the SM t116? Hardware the device has, a Galaxy J1 mini has almost the same processed and less than 1gb of ram and it runs the Lollipop well
mmacedoc7 said:
But is not there anyone interested in developing a rom with Lollipop for the SM t116? Hardware the device has, a Galaxy J1 mini has almost the same processed and less than 1gb of ram and it runs the Lollipop well
Click to expand...
Click to collapse
hi! you can read here https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-tab-3-lite-sm-t116-goyave-t3537793
pit file
Can anyone help me find pit file for galaxy sm-t116NU??????
OMG, Im also stuck here with SM-T116BU which was officially upgraded to Tab E (somehow) how it happened, i don't know since this was my son's Tab 3v originally.
lately. i have rooted tru inception (nice job for the rooting guys) then tried TWRP 3.1.1.0 but couldnt boot, down ver to TWRP 2.8.7.0 bcos the others are either not TAR for odin or files are missing to boot TWRP recovery.
so far, i have tried CM-13 but failed miserably, perhaps those files are corrupted as well
I enjoyed loading with my "Note3 with touchwiz" DO NOT TRY THIS UNLESS YOU KNOW HOW TO RECOVER, so i tried using the same ROM N9005_TouchWizMM_V4_16-04-2016. installation smoothly with TWRP into TAB E but could NOT make it BOOT.
I guess some files are missing while downloading those as well or those files have been corrupted thru the years.
N9005_TouchWizMM_V4_16-04-2016 not difficult to find but NEED an expert to cook a SM-116 version since this is best "complete" ROM (need kernel) in my Note3 now
I'll keep trying ROM N9005_TouchWizMM_V4_16-04-2016 into THIS TAB E and mixed with SM_116 kernels n I KNOW I MIGHT BRICK THIS SM-116 Tab E, what the HACK so let it be, NO VENTURE NO GAIN hahahaaa
deranche said:
OMG, Im also stuck here with SM-T116BU which was officially upgraded to Tab E (somehow) how it happened, i don't know since this was my son's Tab 3v originally.
lately. i have rooted tru inception (nice job for the rooting guys) then tried TWRP 3.1.1.0 but couldnt boot, down ver to TWRP 2.8.7.0 bcos the others are either not TAR for odin or files are missing to boot TWRP recovery.
so far, i have tried CM-13 but failed miserably, perhaps those files are corrupted as well
I enjoyed loading with my "Note3 with touchwiz" DO NOT TRY THIS UNLESS YOU KNOW HOW TO RECOVER, so i tried using the same ROM N9005_TouchWizMM_V4_16-04-2016. installation smoothly with TWRP into TAB E but could NOT make it BOOT.
I guess some files are missing while downloading those as well or those files have been corrupted thru the years.
N9005_TouchWizMM_V4_16-04-2016 not difficult to find but NEED an expert to cook a SM-116 version since this is best "complete" ROM (need kernel) in my Note3 now
I'll keep trying ROM N9005_TouchWizMM_V4_16-04-2016 into THIS TAB E and mixed with SM_116 kernels n I KNOW I MIGHT BRICK THIS SM-116 Tab E, what the HACK so let it be, NO VENTURE NO GAIN hahahaaa
Click to expand...
Click to collapse
What exactly are you trying to do?
Well. The TouchWiz works perfectly on my note3 so I'll try to cook a TouchWiz for Sm-t116 from the note3 platform. If u have ready ROM, do send them. Tks in advance !
Ps. Out of town next few days ??
deranche said:
Well. The TouchWiz works perfectly on my note3 so I'll try to cook a TouchWiz for Sm-t116 from the note3 platform. If u have ready ROM, do send them. Tks in advance !
Ps. Out of town next few days
Click to expand...
Click to collapse
Guys please give the firmware rom for TVRP on the TAB-3 Lite SM-T116 ! Cause when I for some reason flashed TVPP I realized that there are no custom firmwares for this device , But I need 100% working FI-WI, and cyanogen mod does not fit, cause Wi-Fi doesn't work there!
Hi,
So, cm-13 is very unlikely on our device, but i'll take a look anyway (a slow look as my time is very limited).
Here you'll find my "work" and "help requests".
First, for sure i didn't "worked" on a lot of device, but it's the first one i have with a dedicated partition to the kernel dts.
Code:
/dev/block/platform/hi_mci.0/by-name/dts /dts emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/boot /boot emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/recovery /recovery emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/misc /misc emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem /modem emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/modem_dsp /modem_dsp emmc defaults recoveryonly
+/dev/block/platform/hi_mci.0/by-name/sensorhub /sensorhub emmc defaults recoveryonly
- I wonder if the dts, which is kernel dependent, could be the major problem to get a custom rom version (kk, jb, mm), or even a stock huawei rom, to work from any base rom. I'll try to make some experiment soon.
- I did sync cm-13, and "of course" have cwm recovery working. But whatever i'm trying i can't get screen output on twrp 3.0. Does someone have a clue on this?
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Cpasjuste said:
@codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
You're looking at the wrong account.
https://github.com/honor6-dev
Start recovery and have a look at /tmp/recovery.log.
Hint:
https://github.com/honor6-dev/andro...common/blob/cm-12.1/BoardConfigCommon.mk#L150
https://github.com/CyanogenMod/andr...mmit/7273770a9fedff12ca80135356c52fee06c8aba0
Cpasjuste said:
- @gabry3795 , do you still have the device ? I would be happy to get your hangout/google nickname if you have any to sometime talk about this device. @codeworkx is of course also welcome for any advice. By the way your cm12.0 github repo (codeworkx) doesn't seem's to be up to date, even if i understand that's it's in a non-working state.
Click to expand...
Click to collapse
Yes, I still have this device! I'll write you via pm my nickname.
good luck you guys
i have really nothing to offer ..
but please make this happen ..
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Cpasjuste said:
Unfortunately I really have no time to play with it this days, I'll try to take a look soon.
Envoyé de mon HUAWEI MT7-L09 en utilisant Tapatalk
Click to expand...
Click to collapse
pls we wait for a long time:good:
It would be great to se cm no this device. Good luck and hope you make it. I would help if knew anything about programming but unfortanatly i dont
Cm we want... thank you for your interest!! ?
Kzyw said:
Cm we want... thank you for your interest!!
Click to expand...
Click to collapse
+1
why is there not one custom rom for this device?
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Motawa88 said:
why is there not one custom rom for this device?
Click to expand...
Click to collapse
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Scruffykid said:
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
i too have wondered about this. im sure its possible but it might be far to difficult an endeavor because if it weren't, someone would have attempted it by now. i really miss my nexus 5 with all its custom roms. i suggest that all mate 7 owners get in contact with huawei and demand they comply with the android user agreement. they are technically supposed to give up sources. we could fight, but not unless we unite.
Yes we can! Yes we can! Yes we can!
Scruffykid said:
As I understand there are some crucial files / source codes that Huawei is refusing to release to the public. This alone sounds super dodgy, because isn't Android supposed to be open source? Or can companies "own" a custom version of Android and do this sort of thing?
These files are crucial for creating custom kernels and ROMs, as they have to do with (once again, this is how I interpreted it) how the device handles the CPU and GPU.
Basically, while it is possible to install other ROMs on the device, they'll have to be based on EMUI and its kernels, because it is the only thing that contains these files necessary to make the device run, which makes the entire exercise pointless because EMUI is s*** no matter what form it takes.
I wonder if it wouldn't be possible to simply "extract" this necessary code from the stock kernels / ROMs and implement it in a custom one? I do not know even the slightest thing about programming, so I could just be sounding like an idiot.
Click to expand...
Click to collapse
You're right, extracting stock binary files is an essential part of roms porting but some important files can't be inherited because they are strictly hardware-related, therefore you have to compile the original android source and then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
gabry3795 said:
...then "patch" that files for the specific GPU/CPU (starting from android 5 lollipop) with other files given by the vendor of the phone.
Click to expand...
Click to collapse
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Scruffykid said:
But isn't that the entire problem, the "other files" that have to be supplied by the vendor? Huawei is refusing to release them, and therefore making it impossible to develop custom ROM's.
Or are you saying that it is possible, but there just isn't enough interest in the phone for anyone with the necessary skills to actually go through the trouble?
Click to expand...
Click to collapse
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
gabry3795 said:
I'm saying that Huawei must provide that 'patches' (as Qualcomm did, for example) otherwise is impossibile to build a working ROM, this is the problem. We cannot do anything without them.
Click to expand...
Click to collapse
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
droidbot1337 said:
this is why we should all come together so as to put pressure on huawei to release these files. i have been trying for months now but its getting very tiresome. im going to start a twitter account that will hopefully get their attention. i think the problem is that the general public dont know much/anything about custom roms. there should be a custom rom psa for all android users that point out the benefits of custom roms.
Click to expand...
Click to collapse
I agree. If you get that account running let us know here so that we can support it.
Cheers! :good:
---------- Post added at 12:03 PM ---------- Previous post was at 11:32 AM ----------
droidbot1337 said:
because huawei refuses to share their kernel source. suffice it to say, im done with huawei. its a good thing that there are many new phones being released soon. from now on its snapdragon or nothing!
Click to expand...
Click to collapse
Agreed.
Unfortunately I live in a place where just picking up a new phone is not as easy as 123, But I think I'll try and get my hands on a different phone this weekend. Huawei pisses me off.
No source release by Huawei.
No Kirin SOC support would be a huge problem to get it working I think.
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Pd. There a bootable cm13 rom that i'm using to write this :v
I'm sorry if i had a bad engish, i'm a mexican :v
armando121504 said:
I've searching for karthick111's cm11 folder, then i saw a folder called "cm14.1" with a zip called "cm14.1-20161220UNNOFICIAL-nevisp" and i downloaded and flashed it but it bootloops :'v
Does anybody know if it's usable or a wip?
Click to expand...
Click to collapse
Yeah... I have just flashed it, but it has been in a bootloop for 20+ minutes already. Needless to say, this is probably a test/WIP CM14.1 build that @karthick mostwanted is testing for the Galaxy Fame to see if it will work at all. From what I am aware of, later CM ROMs (CM13, 14, and 14.1) will not work as well as they should on this device as it is low-end and doesn't have the RAM or processing power that is required, however, CM13 is fairly usable from what I have tried, but I still find the CM11 (KitKat 4.4.4) ROMs to be the best. Then again, it is always good to keep and eye on and test the latest builds that the developers release, as I have seen some older devices get ROMs which shouldn't work on them because of their hardware, but do, because the developer is able to configure it to make it work.
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
karthick mostwanted said:
I'm disappointed
I don't know why everyone being stalkers
The work is not even done yet and u guys are posting it here without my permissions
Yes in next build I will try to brick the device badly if this persists again
If the work is done I will share it for sure
Don't irritate developers by doing this way
Click to expand...
Click to collapse
Fair enough, but I assumed that since it was publicly available to view and download, then it should be okay to publicly discuss about the development surrounding the ROM/s, but I guess not.
Thank you for the time and effort you put into these builds and the continuation of custom ROM development for this device.