Related
Hi Guys,
Can somebody point out what are the compatiable Custom ROM for p1010...
I am looking for best custom ROMS ..
Cheers!!!!!
Well, just the CleamROM,
Motafoca said that will port cyanogenmod 9, but this will take a time.
samcortez said:
Well, just the CleamROM,
Motafoca said that will port cyanogenmod 9, but this will take a time.
Click to expand...
Click to collapse
This is correct. CleanROM is the only "non-stock" ROM available for the 1010 and technically is not a "Custom" ROM. It is based upon a "Stock" Gingerbread firmware with some "bloat" removed and some theme's added. Also, Scott from Scottroms (the developer of CleanRom) I believe has sold his Galaxy Tab and will not be providing future updates.
Motafoca is indeed working on a CyanogenMod (CM) build for the P1010 but to my knowledge he is the ONLY developer doing so. Let's all wish him luck and support him in his journey because once he is successful it will open the door to other developers.
FYI, I have created an in-depth thread specifically for the GT-P1010 that can be viewed HERE.
I will be updating that thread and adding the details above to it. My hope is that we can all discuss our "forgotten" P1010's in that thread so as to be able to find all the information more easily.
I'm one of the testers of motafoca. And well, actually, we are trying to ort cyanogenmod 7.2, but the zip doesnt works, p1010 is a little complicate. And motafoca is working on 4 devices at same time. Soo its hard. I think that in march we finish with cyanogenmod 7.2 (note: the biggest problem is do a flashable rom of cyanogenmod, after that, is just pick the drivers of gingerbread from the source)
Thanks Guys for that information...
Hi everyone! You guys probably don't know me (Shawn5162) because I haven't been active in the Moto G 2014 forums (except for my restore tool for windows) but I am very active in other device forums such as the Galaxy S5, Note 10.1 2014 Edition, LG G3, etc. In those forums I am defiantly a recognized dev, mostly for porting or compiling ROMs . But the reason I landed in this forum is because I recently I got a new device...the Moto G 2014 and feel it is a great device. But to my shock there were NO great ROMs for this device (by no means am a hatting on the 1 or 2 ROMs here). And that's where I come into play. I am a dev who has a lot of experience with AOSP and compiling and thus want to bring forth a great AOSP ROM for this device. Now I there will be no problem building it as I have experience and if do run into any issue I can refer to the Moto G 2013 devs (since both devices share almost identical specs). Also the AOSP ROM will always be on the latest version of Android (I promise i'll try my best). After all, the good thing about AOSP ROMs is you can have great levels of customization. Now there is a slim chance of failure in the project (like 1% only because everything in life has a chance of failing) but if everything goes well you guys will have a great dev supporting a great ROM. Finally, thanks for your cooperation and I will keep you guys posted all the way.
Sincerely,
Shawn5162
Also if you guys want this project to happen...please comment in the XDA comment section below.
Download Links (I am leaving download links below for other devs who want to give it a shot...also I wanted to share my sources)
Device Tree:
Device Kernel:http://d-h.st/HgD
Device Vendor:
AOSP ROM:
Project Status
12/7/2014
- Got a laptop to start developing on
- Successfully installed Ubuntu 14.04.1 LTS
- Initialized a building environment for AOSP
- Setup a Dev-Host account
- Synced Android 5.0.1_r1 repositories
- Forked the device kernel from Motorola's git
12/8/2014
- Merged source code with CM 12.0 repos
- Added /Source/kernel/motorola/titan repos/
- Imported "falcon" device tree
- Began modifying "falcon" device tree for XT1064...
12/9/2014
- Downloaded all the CM 12 packages
- Contacted @k2wl for a collaboration (He said OK! )
- Modified device kernel for XT1064 (added more functionality/patches)..I can confirm kernel tree is working
12/10/2014
- Contacting CyanogenMod Inc. in regard of OFFICIAL SUPPORT for this device
- Continued modifying source
12/11/2014
- Compiled an OTA .zip of CM 12 [doesn't boot]
No comment..
this is what I was waiting for
MrIngenieur said:
No comment..
Click to expand...
Click to collapse
Why is there something wrong
Thanx dev!....if u need a tester ..m here
Wow this would be Great! Hopefully it will grow and give us a cool AOSP ROM.
Thanks a ton!
That would be great, thanks
I really would appreciate some more development in here.Thx for that announcement!
Finally Devs Coming.
Best of luck Shawn. :thumbup:
If you make it, it would be Giant leap for Moto G
Awesome man..... I Really appreciate what u r doing for this community....
Coming from a nexus phone which broke and buying this device for the price, would be nice to see more roms.
Bring it. I love AOSP. And if you did it there would def be some donations coming your way.
N.K.V. said:
Finally Devs Coming.
Best of luck Shawn. :thumbup:
If you make it, it would be Giant leap for Moto G
Click to expand...
Click to collapse
I agree
The more, the merrier! Nothing wrong with having thriving development Hopefully once one of these kind of ROMs gets brought to the Moto G 2014, the rest will follow.
radiotecha1234 said:
Bring it. I love AOSP. And if you did it there would def be some donations coming your way.
Click to expand...
Click to collapse
Thanks!
Awesome
I'm in!
Sent from my A0001 using XDA Free mobile app
That's a good news ..... Good luck man , if you need a tester just PM me , i will test the ROM thoroughly
This seems great!
Sent from my XT1069 using XDA Free mobile app
Hi Everybody
after some weeks Trying developing ROM's and Kernels i almost Give up... the kernel developing to MTK SoC is too much different compared to qualcomm SoC's (To me at least...) after compile more than 10 kernels to Run at my phone i only get Bluetooth and Radio FM not working with random reboots annoying frequently... but a real modifications to get this phone more smooth usage fail every time...(if you only compile the original source kernel it will run exactly like original kernel...)
I'm too n0#b alone to get everything running at developing process(kernel or ROM dev.).. at qualcomm phones(Xperia Acro S and Xperia L), i get more things running correctly with much more help from others Developers... but not released anything because it will be more from the same as others releases...
so if anyone here have more knowledge about that developing process things i have the Kernel Source and ROM platform to our phone...
---
i already try make CM12.1 run too.. but don't boot =#.. and if get work soon will be too much unstable to release, like my kernels =#
i will try port CM12.1 from @fire855 using that tutorial
the other possibility is try make compile the CM12.1 using our sources with modification from this ROM
but i will need help to make it compile right =#
so.. i will like have a discussion about that process with you guys... if anyone have some experience to help our phone have more custom's things to don't be locked with Original stuff/performance only.. if anyone have a useful guide, video or tutorial to compile anything to MTK SoC's it will be great too :highfive:
I appreciate your effort! I don't know much about MTK personally, but there is a thread on 4pda about porting CM 12.1 to MTK processors.
http://4pda.ru/forum/index.php?showtopic=671898
Sent from my VIVO AIR using Tapatalk
Ilxaot said:
I appreciate your effort! I don't know much about MTK personally, but there is a thread on 4pda about porting CM 12.1 to MTK processors.
http://4pda.ru/forum/index.php?showtopic=671898
Sent from my VIVO AIR using Tapatalk
Click to expand...
Click to collapse
already started try port CM12.1 ... but will not work too much things... almost every sensor will not work because that cross-firmwareOS port (CM Modules Drivers have a different compilation process =#) what i can do is try upgrade our source kernel using other MT6592 Sources to can compile the CM12 to our device... but again i will need find Module Updates drivers(blob) from other phones sources... =#
and my status with that right know is fixing a lot of errors while i compiling the kernel... i don't reach the inHouse ROM Compilation to than can get more Errors on logs to fix to release a simple Almost "stable" rom to how want test if it works properly to everyone... but don't push me to get that finished.. i work everyday and when i have time i try my best to develop that :highfive:
and release a unstable ROM/kernel is a wrong because maybe can brick someone phone because my errors (ramdisk modifications, and partition table map when installing the rom)... or we can wait BLU release the Lollipop with Hope because on twitter( @ UKkazam) tell me about no lollipop updates to this phone =#
i Tweeted to [@ KazamUK] asking they about lollipop updates and receive two replays... One say about newer updates to fix bugs on OS but not about lollipop and other saying "unfortunately, not upgrades to newer Android versions will be released"... otherwise [@ BLU_Products] Replay this "Please stay tuned on our social media for future updates, thanks!"... so... we have a faith about BLU brings Lollipop to our device? i don't have sure but with lucky it will happens :highfive:
...
and the porting CM12.1 ROM don't worked with me... bootloop =# and CatLog is extremely confuse =#
Kernel source link not working
I have an opportunity to make a PORT CM12 for BLU VIVO AIR in two days. A neighbor of mine bought a VIVO AIR and I will do whatever is necessary to get the ROM on the device.
I helped the BLU VIVO IV the users to have CM12. But as the device was not mine, so I could not fix some bugs. In the same epoch I talked to a BVA User and helped the kernel issue. He had given me feedback in relation to not have phone signal and not be able to replace the IMEI. But as I had no time, and the phone in my hands, the CM12 ROM stood with him.
Currently, it is quite possible that after CM12 MT6592 to be 95% stable in most of these devices Socs, the VIVO AIR may also have.
Once I have the device in hands, I'll let you guys know if CM12 can be available for all users VIVO AIR.
But if anyone know a actually already exist a ROM CM12 for VIVO AIR and clones.... Let me know...??
That would be awesome and I'm sure as me a lot of users are going to be happy about it
Sent from my REVIVED VIVO AIR using XDA mobile app
Hey folks,
I know most people have already given up on this phone because it didn't sell well and doesn't have much support. But like the rest of us still browsing this forum, I still have my M9 and still believe it can be improved. I am currently working on a project to build a clean AOSP rom (without any kinky modifications, just a nice stock rom built directly from the AOSP sources.)
I've never undergone such a project, and I've been reading a lot about the steps necessary to realize this goal. I've been following Sony's excellent AOSP building guide so far. I have the android sources downloaded, all I'm missing are the proprietary files (from the device itself, most likely) and the ability to set up the proper device trees/manifests. I was planning to use the Cyanogenmod device tree because a lot of work has gone into it and, given that my M9 is currently running one of the CM13 nightlies, is pretty stable and works with new device firmwares. I know there is already a guide on the Cyanogenmod wiki for building CM for the M9, but I am not building CM at all, I want to build a 100% stock AOSP rom.
Can anybody help me proceed from here? I've downloaded the https://github.com/CyanogenMod/android_device_htc_hima-common tree and put it into device/htc/himaul but I'm not sure where to go from here. The extract-files.sh script does not work (because there is no CM helper script). Does anyone have any experience with this sort of thing?
Thank you very much in advance. I hope this will help everyone as I know many people have been looking for a non-CM AOSP rom for this phone (some do not agree with CM design philosophies). I definitely plan to share this rom and write a guide to help other projects when this is figured out.
I look forward to hearing back,
vivremetrique
Hi, I have no idea on doing roms, but you could help be your tester ...
whatever you need, talk me
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
It would be good to make a ROM Nougat if possible
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Frug01 said:
[/COLOR]It would be good to make a ROM Nougat if possible
Click to expand...
Click to collapse
Yes, the sources I will be building from will be Nougat sources (7.1 experimental sources). Thank you for offering to test once this is done.
throcker said:
AOSP 100% and cyanogenmod device tree are totally different
I don't know what does it take to have a full aosp working rom, but I'm sure that CM code has nothing to do with it.
anyway, with the right work it shouldn't be so hard since m9 shares hardware with nexus 6p...
Click to expand...
Click to collapse
I mean the operating system will be 100% AOSP, but obviously since this is not a Nexus/Pixel device the device tree will not be included in AOSP... The device tree/proprietary files have nothing to do with the actual user experience, they are simply needed for support of the hardware/stock kernel if desired/camera or wireless firmware. I don't see the sense is rewriting these from scratch given the time and effort already put into them by CM devs/those in the Cyanogenmod threads in this forum.
It would be great if some of you could help gather helpers for this project. It seems that properly setting up the device and getting ready to build the rom are all that is missing, so I'm hoping this goes relatively quickly.
So I believe I've made some progress. I downloaded the htc vendor files, the htc msm8994 kernel files, the hima-common tree, and the himaul tree. There is still something missing, because running the "lunch" command warns that it cannot locate the config makefile.
I found references to cm in cm.mk in device/htc/himaul/cm.mk but I don't know what to replace them with and I don't want to download the whole CM source tree as well.
Can anyone shed some light on this issue?
I can't help you, but that is a very good idea! Hope you can solve this issue.
Nice project, I would love to see AOSP Nougat on our M9! I'm not a dev who could help you with the building process, but maybe the dev of the CM14 port for M8 could give you an advice. Good luck!
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Any telegram group of One M9???
Enviado desde mi HTC_M9u mediante Tapatalk
Adromir said:
I think you are underestimating the efford and skills it needs. Even with official Kernel Source released it took some really effort to make for example the camera work. If you don't know hot to setup a device tree for an existing rom, then I feel the skills required exceeding the ones you have. I don't want to offend you, but maybe it's better to take a step back an learn how to add this to an AOSP Marshmallow rom, instead of thinking about porting it to Nougat. If it would be that easy, wouldn't a ready to use Nougat Version of any other popular Rom for the m9 be out already?
Click to expand...
Click to collapse
That effort would.not be wasted. Once the solution to the camera problem is solved, it's solved for all versions, not just Marshmallow. We can reuse the kernel source and firmware blobs in N. I reckon that we don't have a rom because nobody is working on it.
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Adromir said:
If it would be that easy, why isnt there an official (or even inofficial) cm 14 for m9 out, as it already got an official cm 13? If everything you needed would be to just switch everything else to cm 14 and reuse the mm kernel source and blobs?
Click to expand...
Click to collapse
Because there is almost zero demand for one. People in the CM13 thread are actively discouraged from even mentioning CM14. How can we develop the ROM if we don't have anybody working on it?
Given CM's automated device tree preparation system, I doubt it would take more than a simple source tree update to Nougat to start compiling a 7.x ROM (whether it works perfectly or not, it would be a start).
Well then I would say, a way to start might be to try compile a booting cm 14 for the m9. Last time I looked there has been at least a device tree prepared for cm 14. I guess that would be the easiest way to test, if you might be succesfull with it
Any news @vivremetrique ? Or did you drop the project?
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Trainwr3ck said:
While it is possible to build cm14.1 for the M9, I was unable to make it see the sim card after days of trying. something in libril or possibly the firmware I have makes it not work.
Click to expand...
Click to collapse
If it is the same Problem I had with a CM13 based rom, then the build.prop is missing some Values to detect network. I took them from a working one and put them in the BoardConfig by hand
can't help, but my hopes are so high for this one!
..
Reserved.....
Hello... 'been using this phone for over a year now here is a clean build.prop from 6055B variant!
Also i'd like to help somehow, but I don't know how... I have zero Android dev experience (not really... last phone I ever modded was OT-918D *eons* ago, so it might as well be zero) but i'd be happy to test-drive anything as long as UI & RILd works.
I'll chime-in on Telegram too :good:
PizzaG said:
This will be the release thread for LineageOS 14.1
***LineageOS 14.1 Test Build for the 6055K is now live on Telegram with Download Link. Bluetooth and Camera aren't working yet***
If you want it to install on other variants, you will need to modify the installer script inside the zip. I'm not going to take the time to modify every Test Build to support every model. I'm running it on 6055U. If you do want to run it on another variant of 6055 and it's not installing, contact me on Telegram and I'll run you through how to modify the installer script to install on your device.
If you have anything to offer or just want to chat, you can find us here: https://t.me/Idol4Homies
Please don't report bugs here, we'd much rather you report any issues on our Telegram Group where the Dev will be able to see. I''m helping where I can and modifying little things but LimitedPython is doing the bulk of the Developing for this phone, please show your support and stop by the group to chat and say thanks.
5-13-2019- LOS 14.1 is currently booting to ADB but not posting yet. Sorting out some GPU issues and hopefully it'll be fully booting sometime this week.
5-14-2019- LOS 14.1 booting to OS. LTE Data and phone service works. Audio and most everything else is still broken currently but being worked on. If anybody has a clue what they are doing or how to help move this along to a public release, please join us on Telegram. I have a test image for people who can lend a hand but I'm not releasing anything publicly yet.
5-17-2019- LOS 14.1 working great so far. The only things not working at this point are Camera and BlueTooth, which hopefully will both be working very soon. I'll release a test build in the next day or so, so others can test. I'll be releasing TWRP and LOS 14.1 for the 6055U and 6055K variants. If you have another model you want supported from the 6055 line, PM me.
5-19-2019- This will work on every 6055 Model guys. That means 6055K, 6055B, 6055U, 6055R and 6055P will all work with this and future roms. No need to worry about "Bricking", as I have released Alcatel Stock Flashing software which will bring most, if not all the Alcatel Qualcomm devices back from the dead.
5-20-2019- Bluetooth fixed and working
Click to expand...
Click to collapse
I tried to go to your Telegram link for the LOS 14.1 6055U download, but it won't work. Idk why... Could you post a link to it here or something? Thanks in advance!
**scratch that I found it on the donate page**
Hello everyone.
I possess an Alcatel Idol 4 6055K, I would be very much interested in installing Lineage OS on this smartphone but I can't find any other source on the web on how to do it except for this thread.
I understand it should be possible with a release you're posting on Telegram, but if I click on the link it seems I can't acceed to the group.
Do you have any advice on how to try this OS on this marvellous phone?
So, no chance to ever see Lineage released for Alcatel Idol 4?
museovivo said:
So, no chance to ever see Lineage released for Alcatel Idol 4?
Click to expand...
Click to collapse
Yes, 14.1 has been out for a while now and 15.1 works too, I was told that a few days ago by the Dev. Come vist us on Telegram: https://t.me/Android_General_Chat
The Dev is in there and should be able to provide you download links for Los 14.1 or 15.1
We also still need donations as the Dev has lost his Idol 4 and needs a new one to continue making Idol 4 Fully Treble