Related
[Q&A] [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam
Q&A for [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4] [GEEB] Unofficial CM-11.0 - Linaro 4.8, LEDs for E971/3, HDR cam. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Just registerd to say thank you for 5.0 android!
Only yours build is working awesome! NFC, camera, battery life is exelect! I'm very glad. One problem is that i can't put some widgets on desktop... it crashes and reappearing without my widget.
Why you didn't update your thread, and what is differences in your build(for exmpl. the 2th of December and the 9-th)?
nikudim said:
Just registerd to say thank you for 5.0 android!
Only yours build is working awesome! NFC, camera, battery life is exelect! I'm very glad. One problem is that i can't put some widgets on desktop... it crashes and reappearing without my widget.
Why you didn't update your thread, and what is differences in your build(for exmpl. the 2th of December and the 9-th)?
Click to expand...
Click to collapse
I haven't gotten to the point with cm-12.0 where I'm comfortable "advertising" it yet. Once I get it building with linaro, and get init.d scripts and some other goodies working I'll do a new thread. As it stands, it's very much the same as brothaedhung's with some extra kernel kangs and some device tree tweaks.
As far as widgets go, I'm not sure as I haven't seen that issue. Could you describe the issue with some more detail, and get a logcat if possible?
Thanks for the kind words though
ronasimi said:
I haven't gotten to the point with cm-12.0 where I'm comfortable "advertising" it yet. Once I get it building with linaro, and get init.d scripts and some other goodies working I'll do a new thread. As it stands, it's very much the same as brothaedhung's with some extra kernel kangs and some device tree tweaks.
As far as widgets go, I'm not sure as I haven't seen that issue. Could you describe the issue with some more detail, and get a logcat if possible?
Thanks for the kind words though
Click to expand...
Click to collapse
Oh, you won't believe I just disable "Don't keep activities" and it works now!!!:laugh:
The problem was when i tried to put Clock for expl. the launcher crashes and appearing again without my widget. Now, i've put my widgets and turn on "Don't keep activities". Perfect! I could not spot any problems, yet!!! Good luck with developing, and thanks again!
ronasimi said:
02/03/2015 - Sorry guys, I've been slacking off on updating this post. All current builds are using my KK kernel brought up for LP, with stock frequencies instead of low_cpuclocks. I'll be posting a new build later this morning. As far as I know, this is the only CM build still using mako sources
Click to expand...
Click to collapse
Noticed this over here after looking in the Canadian section (which has most certainly be dead for a while). Great to see you're still active on this. Just want to make sure before trying this that there's nothing else required to move from KK to LP (assuming not since its on a KK kernel still). Any particular recovery recommended and/or version? I'm on a Bell E973 using PAC 4.4.4-RC2, TWRP 2.6.3.1.
Edit: Decided to update recovery to 2.8.4 from brothaedhung after doing some lurking around. Flashed 02/03 and full stock PA gapps. Everything butter so far. Cheers!
@ronasimi : Latest build is working fine, in call screen is also normal, just sensors not working some times,,
thanks..
Click to expand...
Click to collapse
I have the same issue in your latest CM12. Proximity and brightness don`t work at all. I use jb e970 modem. Don`t flash hybrid radio because I`m in Russia. Also there isn`t any frequence low than 300 Mhz...
And I try your build of CM11: 20141111. There are a lot of bugs:
1. In profiles doesn`t work ring mode "normal". It doesn`t swith to it after another modes (vibrate and mute).
2. Don`t work "Double tap to sleep"
3. In perfomance dont`t work setting minimal and maximum frequency - after rebooting they are turned to default.
I have e970 will it work with this rom?
dro3 said:
I have e970 will it work with this rom?
Click to expand...
Click to collapse
It works. You should give a try to the CM12.1 version. :good::good::good:
ryupunk said:
It works. You should give a try to the CM12.1 version. :good::good::good:
Click to expand...
Click to collapse
I have tried it but my phone gets signal lost many times
"ap watchdog bark detected"
Help!
Since i flashed 12.1 rom, this message with green screen appears frequently!
5.1.1 CM12.1 Unofficial, Watchdog Kenel Panics (green screens)
long post, so if you want the meat of the story scroll down!
hi guys, i'm an avid user of the e970 and i found this marvelous forum to be one of the most useful resources ever. freegee, lgnpst for when i bricked my phone, cm11, cm12, solid geeb kernel, validus, and now cm12.1 unofficial; it's all there. i'm certainly enjoying the experience that this device paired with this community has to offer.
first i'd like to thank the developers, and i'm seriously appreciating the active development on 12.1. i just finished using validus and while it was a much more solid experience than the short-lived cm12, android 5.0 was still killing me in terms of battery life. 5.1 certainly fixed that up though.
i want to second a few observations that are being made, which are the green-screen happenings. i want to mention something in particular though:
when i first flashed 12.1 unofficial i didn't have the recommended gapps at the time, so i flashed the minimal gapps for 5.0 (just to get wheels rolling per se). sure enough, it was a crazy experience. com.google.<insert service name here> was crashing repeatedly, often causing loss of functionality or green-screens. in a day i'd get anywhere between 4 and 7 green-screens (this was for three days, i'm talking about the 4/21 release). i re-wiped and formatted /system and re-installed 4/21 cm12.1, along with the recommended gapps this time.
NOW i'm having far fewer crashes, far fewer slow-downs and stutters; overall a much more lean experience. i also want to especially thank the developer for one thing: THANK YOU, for giving me back HSPA+ speeds on my att jb radio. validus and cm12 for some reason wouldn't give me HSPA speeds, just slow HSPA speeds that would take forever to peak at 200, 250 K/s (averaging around 70 to 140 K/s). now i can enjoy speeds up to 900 K/s (i'll run a speed test when a more stable release comes out)
so, is it gapps or a kernel issue? newer gapps reduced a lot of problems (though that's a given). also i'd like to point out another error: wi-fi. the mac address keeps changing upon reboot, namely the last three hex values. the first three are always 00:11:22. this wouldn't bother a lot of everyday users, but my workplaces utilizes mac filtering (only way around it is to use the battery-intensive 3g option instead, and i have terrible 3g reception at work where i sit; OUTSIDE my office, i get great reception, but it's bloody hot here x.x)
in any event, if someone could help me out or give me some advice that'd be great.
to summarize:
5.0 gapps + cm12.1 = lots of watchdog events
5.1 gapps + cm12.1 = a lot LESS watchdog events, still happening though
wi-fi mac address gets randomly generated at reboot
phone doesn't get detected by the computer on usb unless you leave it plugged in and do a soft reboot (advanced reboot option; common in most cm12.x instances with default kernels; solid geeb was better, and cm11 was flawless pretty much)
using built-in kernel
att jb radio
clockworksmod touch recovery, the last one (6.0.1.8 i think? it's the last one on their website)
4 gig micro sd card is in the slot, if that makes a difference
one more note: i'm having far fewer crashes on this new install maybe because there are only google related apps (other than whatsapp which i installed right away). future planned apps to be installed:
adobe acrobat
battlenet authenticator
es file explorer
facebook messenger
titanium backup
mx player
aedict japanese dictionary
busybox
greenify
orpheus music player
qr code reader
skype
supersu
terminal emulator
any increase in instability henceforth i'll let you know. also for anyone NOT having greenscreens on the e970, do you have whatsapp? if NO, interesting. if YES, still interesting, but please what version? mine's not the latest (yet)
blitz9826
so this is new:
after reaching 100% battery level on charge, the phone used to cool down. ever since switching to this rom, the battery DOESN'T cool down, it stays warm/hot. i know for a fact it's not a charger issue since i'm charging it with the same usb port as i have been in hte past (and every other phone for that matter on the same port)
any ideas?
blitz9826
sensors
Sensors isnt working. 28.04 build.
Will you fix it?
Icons are blurry?
Hey. Loving this ROM so far. Only problem is that the icons are blurry (not HD as usual). I wiped the cache and delvik cache but it's the same problem. Anyone know how to fix this? Thanks.
ronasimi, i am waiting, that you will read this. Please try to fix sensors in your unofficial 12.1 builds. I really want use your rom, but sensors is not working.
I have e970 with mako z30f bootloader, and latest twrp.
Auto rotation
The auto rotation is not working. Only staying in portrait. Can anyone help?
Mobile Data to Wifi Switching
@ronasimi
first of all thanks for the Great rom im using from almost a month with no issues at all.
Just a little question about wifi. Wifi did not connect automatically when my phone is locked. I've to wake it then WiFi connects immediately.
same is when im using mobile data and saved WiFi is in range. but phone will connect it,until i wake the device.
please help me out on this.
[SOLVED] Problems rooting 12.1 E971
Edit: For anyone else facing this issue, flashing the beta version of SuperSU from a custom recovery works.
On a previous 12.0 build I was able to get root just fine, but after clean flashing the latest 12.1 build no method seems to work. I've tried flashing the latest SuperSU update zip from TWRP, using adb to push su and busybox, and using the built in root in developer options.
Flashing the zip and using adb result in SuperSU saying there is no binary installed, and with the root in developer options it never pops up something asking for permission.
Has anyone gotten root on the latest 12.1? Thanks in advance.
Cm 12.1 Bluetooth Issue on E971
Thanks for the great rom. Works great except one minor. Bluetooth connection on and off consistently.
I have cm-12.1-20150521-UNOFFICIAL-geeb.zip rom installed.
Thanks!
Thank you for your hard work on the ROM.
On an E971 with a clean flash, as others above have reported, the sensors/auto rotation are not working.
Another request would be to add repo specifics on your description of the ROM at the start of the thread. You link to your github account where the repos are stored but there are many of them, some with similar names. I am interested in reproducing your build process and possibly contributing some changes, but I am not sure which specific device, vendor and kernel repos you are using to generate the build. Would love to get rotation sorted out and keep development going on this solid 5.1 option for a still capable device.
Still kind of suprised that CM isn't doing 12.1 builds for E973/E971 but it seems they have dropped a large number of phones with the move to 5.0/5.1 and angered a lot of people.
Thanks!
*** This project is now abandoned in favor of the LineageOS variant ***
This is a port of Cyanogenmod 14.1 for the Samsung Galaxy Tab A 7.0 (2016) LTE SM-T285. Cyanogenmod needs no introduction, it is one of the most popular aftermarket ROM distributions around.
5.1.1 is the best that you can get from samsung right now and it is not known if they plan to do any upgrades. I have absolutely no idea why samsung chose to stay with the outdated 5.1.1 mid 2016 when we already got 7.1 coming out. This custom rom is probably the best you can get if you want an upgrade from Lollipop. Performance on the latest build is also better, you be the judge.
As this is the first CM-14.1 release, I don't recommend you use this as a daily driver, but it should be good enough for some. Make sure you read the pending issues below and decide if this is acceptable to you before you flash this rom. This rom probably won't get much use out of some people until bluetooth is fixed.
Based off on Cyanogenmod 14.1 sources which is based on Nougat 7.1.
Device Tree:
=========
https://github.com/jedld/device_samsung_gtexslte.git
https://github.com/jedld/vendor_samsung_gtexslte.git
https://github.com/jedld/kernel_samsung_gtexslte.git
Update Dec 3, 2016
===============
Fixed GPS, Wifi Hotspot, Graphics issues, Calls, Camera,sdcard is now marked as adoptable.
Works:
- Wifi/SMS
- Audio
- Graphics with glitches (minor screen tearing, blank screen showing up on overlays)
- GPS
- Wifi Hotspot
- Incoming/Outgoing Calls
- MTP
Does not work:
- Bluetooth
- Camera
- LTE (Due to APN issues)
- Battery Meter not updating
Bugs/Known Issues
* Problems recording video
Other Notes:
- selinux permissive
Most of the issues are fixable, I just need more time and encouragement
SM-T280 Users: Unfortunately this rom would probably not work on it since the SM-T285 and SM-T280 have different kernels and slightly different hardware. I don't have access to this device so it would be hard for me to port it over. However I believe there are a lot of similiarities in the device tree that can be shared. If a dev with the SM-T280 is interested I can probably help.
Download
========
Remember flashing an unofficial ROM on your samsung device will probably void your warranty, Samsung representatives will probably not be able to help you as they are still stuck at 5.1.1 land as of now and have no idea how to handle a SM-T285 that is running 7.1.
As always flash this at your own risk. Make sure you have a copy of the stock ROM so that you have something to fall back to, which is highly the case when using an experimental rom.
See DevDB download section.
BUILD12032016
Note that this rom is pure stock and does not come with the Play Store or any Gapps, I suggest you download a micro gapps package separately and install it via recovery.
There have been reports that recent versions of open gapps don't work properly, it is advised to use older versions instead (e.g. open_gapps-arm-6.0-nano-20161109.zip)
Installation Instructions
==================
Perform a backup of all of your important files. This ROM is experimental and I will not be responsible for your loss of data.
Download the zip file and extract the tar.
Use Odin/Heimdall to flash the tar file to your device. If you are coming from stock oranother rom make sure you wipe first using TWRP. Coming from a previous version of OMNIRom for SM-T285 may not require a wipe, however please perform a wipe if you encounter problems.
Root and customization
===================
This ROM is a purely based on source and is not rooted out of the box. However you can easily root it by using TWRP to install the latest version of SuperSU.
If you want to customize this ROM and repackage it you may use this guide as a reference.
XDA:DevDB Information
CM-14.1 Samsung Galaxy Tab A 7.0 LTE (SM-T285), ROM for the Samsung Galaxy Tab A series
Contributors
jedld
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Abandoned
Created 2016-12-03
Last Updated 2017-01-31
Nice job!!!
Great job! The ROM is impressively fluid, and I particularly love the way it renders fine text, which I appreciate because I prefer DPIs of 140 to 160. Unfortunately, just like in the early iterations of OmniROM 6.0, the tablet will not connect to the internet over cellular networks no matter how much I tinker with APNs. It's a great build, nevertheless, and I look forward to future releases.
Thank you !! Will give it a try.
posting here too (as did on omni - realized this is the cm 14.1 board)...
"briefly tried the cm14.1....much better very fast response-on the omni the pull down was an issue (would also ask me to format the sd card)
noticed here too the signal tends to drop in and out (wonder if it is some power saving going on-it goes to full strength during a call)...speakerphone also does not work here but must say this is better than the omni even though data does not work"
keyboard much better here too
on both cm14.1 and the omni, the dialer tends to be have some lag when pressing the numbers (do it too fast and can get many errors)-minor thing understand this is an alpha and the omni is a beta
thanks
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
mazmorbid said:
I can't get Soft Keys to work, worked fine on the Omni ROM, only problem I have come across so far.
Click to expand...
Click to collapse
needs some xml changes that needs to be compiled into the framework for that I believe. Though there are more critical bugs I need to fix with this 7.1 rom.
I wish I could help in some way, appreciate your work.
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
khanhpt said:
thank for your awesome work, but i cant download any app from Playstore, it's downloading for a long time, i tried many way to force it works but nothing change. Have any one meet this trouble?
Click to expand...
Click to collapse
Try using an older gapps package like from october, recent versions seem to have issues.
jedld said:
Try using an older gapps package like from october, recent versions seem to have issues.
Click to expand...
Click to collapse
Thank Jedld, i has tried 27th,october version and it WORKS, thank.
I used the version as recommended in the Omni ROM, which was from the 9th of November, no problems with the app store or downloading apps either.
Any closer to another release ?
Nougat will take a while unfortunately
jedld said:
Nougat will take a while unfortunately
Click to expand...
Click to collapse
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
mac231us said:
hello jedid any hope here for data on cm14.1? Thanks
https://review.cyanogenmod.org/175308
https://review.cyanogenmod.org/175307
https://review.cyanogenmod.org/175306
http://forum.xda-developers.com/moto-g-2014/orig-development/rom-cyanogenmod-14-0-t3458931
http://forum.xda-developers.com/mot...ent/rom-cyanogenmod-14-1-moto-x-play-t3515135
Click to expand...
Click to collapse
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
jedld said:
Tough to know for sure. Hopefully some progress will happen before christmas.
Sent from my Samsung SM-T285 using XDA Labs
Click to expand...
Click to collapse
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
mac231us said:
not knowledgeable here on CM and how things are done but those links for the CM...looks like they got merged just 6 days back. Or maybe these are not relevant? just asking/wondering thanks
Click to expand...
Click to collapse
Those patches didn't help unfortunately Though I've fixed network type selection in CM-14.1 already, unfortunately data connection still won't come online due to errors related to APNs. Seeing as this was working perfectly in CM-13 this could be a CM-14 or Nougat related change, it will take a while to figure out what that is. As for bluetooth I was able to get it to turn on, however it is still unable to detect/pair to any device, this is also something that was working in CM-13.
any hope on porting this to t280?
klemen241 said:
any hope on porting this to t280?
Click to expand...
Click to collapse
I don't have the T280 so I wouldn't know. There are devs that are trying or have tried to work on it, not sure about their progress.
Discontinued
!!!!PLEASE READ THIS SECTION BEFORE PROCEEDING TO FLASH THIS ROM!!!!
This is based of @vampirefo 's LineageOS , with my tweaks as I now use the port section to test and share with others to help the original LineageOS by @vampirefo to gain fixes
What works : so far , Ril(sim cards) , Bluetooth , Wifi , Audio , Microphone , HotSpot , Rotation .
Bug: Camera (really hard to fix)
P.S- THIS IS NOT A DAILY DRIVER READY ROM , THIS IS PURELY EXPERIMENTAL AND FOR THE JOY OF IT. DONT COME TO ME IF SOMETHING WENT WRONG . FEEL FREE TO REPORT MAJOR BUGS , BY MAJOR WE ( THE R1 HD'S ROUNDTABLE TEAM ) MEAN BUG AND GLITCHES THAT HINDER A NORMAL DAY 2 DAY USAGE OF THE ROM....SMALLER BUGS WILL BE LOOKED AT LATER IF POSSIBLE.
THANKS TO THESE DEVS THIS WOULD HAVE NOT BEEN POSSIBLE:
THANKS TO :
@CyanogenMod
@oleg.svs (REALLY BIG THANKS TO HIM)
@DeckerSU (ANOTHER REALLY BIG-UPS TO HIM)
@OceanLaber over at 4PDA.ru
@niklabs
@vampirefo
@ THE R1 HD'S ROUNDTABLE TEAM
System : Nougat 7.1.1
Kernel : 3.18.19
OS : LineageOS 7.1.1
FULL WIPE/CLEAN WIPE BEFORE FLASHING ROM AND GAPPS
!!!!!! Advance Wipe : Dalvik , system , cache , data , internal
then go back to twrp main menu , go to mount and uncheck system , go back to twrp main menu again
then go to reboot and choose recovery to reboot back to recovery.
Afterwards proceed to flash rom and gapps as usual!!!!!!
**Download Link is automatically updated to recent release**
Download : https://www.androidfilehost.com/?fid=457095661767128973 <<---- Beta 4
Gapps : http://opengapps.org/
Choose Platform: Arm
Android : 7.1
Variant : Its your choice. ( You can choose Micro version to enable Google Assistant )
PLEASE DON'T TELL ME THAT THE CAMERA DOES NOT WORK , WE ALL KNOW THAT IT DOES NOT
Enjoy!!
KazuDante said:
Ive Been looking around to find new roms that i could port to the R1HD. Ive ported about 5-8 roms that work on the R1 HD but only 2 works flawlessly but the others have a camera issue ( camera not connecting ).
Now ive found a x32-bit CM14.1 for the MT6735 , that works on the device that it was built for. Of course I quickly went to attempt to port it but no luck as of now. The issue seems to be that the /system partition is not mounted correctly in regards to our boot image .
Here are the links for those who want to look at it with us ( R1 HD's Round Table )
Where i saw the post : https://vk.com/smart_rom (scroll down a little bit and you guys will see cm14.1 mt6735, they even made a 64bit now)
Where the test builds are posted and also the sources : https://github.com/olegsvs/android_device_archos_persimmon/releases (now they are testing Resuretion Remix 5.8.XX)
It just to prove that MT6735 can also be running Android 7 as well.
As a team we can make this happen and bring new life to the R1 HD.
Update : Now a Resurection Remix 5.8 is also running on the MT6735 x32. ---> https://vk.com/wall-77256552_14248
Click to expand...
Click to collapse
Can you post links for the working Roms? I have been searching for a working Roms for quite some time and I can't manage to find one, don't know how you did it!
I will re-download and fix them to re-upload but only the one that everything works including the camera.
Sent from my BLU R1 HD using Tapatalk
Here one i ported but the camera does not work : https://drive.google.com/file/d/0BzU6b7lzLmttNjVEX0VqdU9OMTg/view?usp=drivesdk
Sent from my BLU R1 HD using Tapatalk
Are there any with a working camera that you could post?
Yes there is one that everything works , i will upload it soon , my only network access is this phone and im low on credits to get more data.
Sent from my BLU R1 HD using Tapatalk
Great!! Let me know if you get 14.1 up and running. I'm a huge cm fan and would love the nougat features! Thanks in advance for your hard work.
Great!!! Uyeee!!
Finally we are getting Nougat
UPDATE
STUCK IN SETUP WIZARD
Keyboard is fc
+++Fixed+++
But is Android marshamallow rom port
Can wait to try any cm 14.1 build
For our Phone
Cheers
Keep THE good job
quick update,found another CM14.1 thats compiled for a MT6737 device with a 3.18.19 kernel , i'm going to test it out because one of the port i made was also from a MT6737 device.
khyr said:
Great!!! Uyeee!!
Finally we are getting Nougat
UPDATE
STUCK IN SETUP WIZARD
Keyboard is fc
+++Fixed+++
Bit is antes Android marshamallow rom port
Can wait to try any cm 14.1 build
For our Phone
Cheers
Keep THE good job
Click to expand...
Click to collapse
aospkeyboard.....during setup avoid anything that requires you to type anything just skip them , then once pass that go to settings->about phone to activate develloper mode , then go to developer mode to enable usb debugging , then on your computer head over to apkmirror to download google keyboard or GBoard(new name for google keyboard), once downloaded open CMD(command prompt) or terminal (for mac n linux users ) type adb install ( then drag the downloaded keyboard in this spot of this message with just 1 space apart from last typed word wich is install in our case then hit enter)........once the install is complete head back to setting then language & input and switch it to GBoard or something else if you decided to get a different keyboard.
with the new cm14.1 that i found today thats built for a 3.18.19 this time actually mount's the system partition and now im able to grab logcats and dmesg ect.... right now what im seeing are egl/mali errors......but i really think we could use that source and use our binary files to build the r1 its own cm14.1 tree
other devs check update 2 in OP.
Modifying an updater-script from a different device and ROM would not necessarily work. IIRC, The Galaxy S2 and Galaxy S Blaze 4G was able to do that, but in this instance, with different phone hardware, this would not work. Luckily, you did not get bricked from doing this. Unless you are completely building from source, with the R1 files, these dirty ports will take a hefty amount of time. I recommend building a device tree and start building with the kernels that either you have found, or have been created on this forum.
xWolf13 said:
Modifying an updater-script from a different device and ROM would not necessarily work. IIRC, The Galaxy S2 and Galaxy S Blaze 4G was able to do that, but in this instance, with different phone hardware, this would not work. Luckily, you did not get bricked from doing this. Unless you are completely building from source, with the R1 files, these dirty ports will take a hefty amount of time. I recommend building a device tree and start building with the kernels that either you have found, or have been created on this forum.
Click to expand...
Click to collapse
from my experience with porting , modding the updaterscript doesnt cause much threat since i remove any other potential threats to the device and of course i dont flash the boot.img that's for the other device....pretty much i modded the updaterscript just to that it flashes the rom to the right partitions for the device im flashing , yesterday was the first time i ported a kernel (boot.img-kernel) from another device's boot.img and it booted the R1, the only thing that did not work was the sim cards since the kernel was compiled with a different driver that was for the other device. it even added in the settings menu a fingerprint option (of course did not work) even tho the R1 does not have a fingerprint sensor. so my conclusion was that the other device is pretty much a clone of the R1 with a slight difference in some hardware , the purpose of the kernel port was to see if it will boot the r1 wich it did but more is the fact that the other device has a defconfig for a 64bit version as well wich the R1 does not and building a 64bit kernel for the r1 would allow me to port over so many more roms. I really wish the devs of this community would take interest in this because this would change the R1 alot.
KazuDante said:
from my experience with porting , modding the updaterscript doesnt cause much threat since i remove any other potential threats to the device and of course i dont flash the boot.img that's for the other device....pretty much i modded the updaterscript just to that it flashes the rom to the right partitions for the device im flashing , yesterday was the first time i ported a kernel (boot.img-kernel) from another device's boot.img and it booted the R1, the only thing that did not work was the sim cards since the kernel was compiled with a different driver that was for the other device. it even added in the settings menu a fingerprint option (of course did not work) even tho the R1 does not have a fingerprint sensor. so my conclusion was that the other device is pretty much a clone of the R1 with a slight difference in some hardware , the purpose of the kernel port was to see if it will boot the r1 wich it did but more is the fact that the other device has a defconfig for a 64bit version as well wich the R1 does not and building a 64bit kernel for the r1 would allow me to port over so many more roms. I really wish the devs of this community would take interest in this because this would change the R1 alot.
Click to expand...
Click to collapse
C,Mon Devs
F2FS?
KazuDante said:
Ive Been looking around to find new roms that i could port to the R1HD. Ive ported about 5-8 roms that work on the R1 HD but only 2 works flawlessly but the others have a camera issue ( camera not connecting ).
Now ive found a x32-bit CM14.1 for the MT6735 , that works on the device that it was built for. Of course I quickly went to attempt to port it but no luck as of now. The issue seems to be that the /system partition is not mounted correctly in regards to our boot image .
Here are the links for those who want to look at it with us ( R1 HD's Round Table )
Where i saw the post : https://vk.com/smart_rom (scroll down a little bit and you guys will see cm14.1 mt6735, they even made a 64bit now)
Where the test builds are posted and also the sources : https://github.com/olegsvs/android_device_archos_persimmon/releases (now they are testing Resuretion Remix 5.8.XX)
It just to prove that MT6735 can also be running Android 7 as well.
As a team we can make this happen and bring new life to the R1 HD.
Update : Now a Resurection Remix 5.8 is also running on the MT6735 x32. ---> https://vk.com/wall-77256552_14248
Update 2 : here is the boot image i used to get the CM14 system partition to be up and allowed me to use a few adb/shell commands ,this by any mean does not mean that CM14.1 booted properly , theres alot of issues , i could not as of now even get the boot animation to load . this is purely experimental. : https://drive.google.com/file/d/0BzU6b7lzLmttSThpX3ctbHNkcFU/view?usp=sharing
And heres the CM14 i downloaded and tested it : https://github.com/DeckerSU/android_device_smart_surf2_4g/releases/tag/0.2alpha
Also of other dev out there are going to take a crack at it the initial updaterscript wasnt correct so replace it with this updaterscript : https://drive.google.com/file/d/0BzU6b7lzLmttVVh0NUQxWjRNODg/view?usp=sharing
this is yet another step foward for R1 HD.
P.S THIS DOES NOT BOOT , DONT FLASH IT IF YOU DONT KNOW WHAT YOU ARE DOING, I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR. YOU HAVE BEEN WARNED . (4DEV ONLY NOT USERS)
Click to expand...
Click to collapse
Why not create Support for F2FS IN DATA PARTITION
This Will increase perfomance a Lot AND running cm14.1 64bits
This device Will fly!!!
khyr said:
Why not create Support for F2FS IN DATA PARTITION
This Will increase perfomance a Lot AND running cm14.1 64bits
This device Will fly!!!
Click to expand...
Click to collapse
for that we first need x64 kernel and x64 twrp....thats if R1 bootloader allows x64 kernels
KazuDante said:
for that we first need x64 kernel and x64 twrp....thats if R1 bootloader allows x64 kernels
Click to expand...
Click to collapse
What about F2FS ?
IT IS POSSIBLE TO GET IT?
khyr said:
What about F2FS ?
IT IS POSSIBLE TO GET IT?
Click to expand...
Click to collapse
Unless we can actually compile a fully working rom for the R1 , for f2fs to properly work both rom and kernel has to support it..that also includes the twrp.
As of now we still can't figure out whats missing that's stopping a compiled rom for our device (ex. cm13 from @vampirefo and @bullet25 )to boot.
Damn! What do you think about Lenovo k80m
4GB ram 64G storage
Intel Atom procesador it Is worth it Upgrade from Blu R1 this Phone Is stock in kit kat 4.4.4
http://m.gsmarena.com/lenovo_k80-7216.php
I know this Is a off topic question
But Is just $139 AND you got 64GB of storage AND 4G ram
The zenfone 2 4GB RAM it Is in the same pricetag but Is only 16GB storage
The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T​
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- Touchscreen failure (sometimes occurs, if touch works after reboot it will work till next reboot);
- Camera (both);
- Dock special keys (top row);
- GUI crashes; - occure less often
Currently, I'm only one from Unlegacy Team, who has TF device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Latest information about OREO builds can be found HERE.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Eee Pad Transformer Prime
Contributors
Clamor, Ziyan, Narkolai
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17
Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.
REPARTITION and TREBLE
TF201 users know well what is repartition. While flashing 4.2BL from HB internal storage is reformatted. This thing is exactly the same.
I worked on it for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY!
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash HB bootloader or Bootloader 4.2 attached in Downloads section.
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
MalibuKoKo said:
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
Click to expand...
Click to collapse
Actually you can't build fully working ROM from my source for now. If you would like to help in developing - PM me.
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
goosebickel said:
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
Click to expand...
Click to collapse
Based on latest 4.2 bootloader (like Hairybean). I'll provide a bootloader + new TWRP and separate TWRP as soon as I get a stable recovery build.
General Feedback
Finally got around to flashing your ROM a week ago, following your instructions, everything went fine. I installed your UA-bootloader and flashed _that16 kernel.
Running pretty smooth with Pico gapps installed, after a week, the usual happens, slow loading apps etc, but that is not the ROMs fault, the very slow memory that Asus put into it and Google is slowing it down with constant syncs etc.
Was wondering if you had added compatibility for using MicroG?
Thanks for keeping this old tablet going.
@goosebickel sorry for such a long silence. MicroG are supported as I can say (I installed them but didn't test much).
P.S. If you are still on UA rom there is an update.
Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs from O for now. I know already about all major issues.
Thank you!
Great to see some development for the Transformer Prime
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Clamor said:
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Click to expand...
Click to collapse
Are you planning to work on Pie as well once 8.1 is somewhat stable?
shinzz said:
Are you planning to work on Pie as well once 8.1 is somewhat stable?
Click to expand...
Click to collapse
I'm planing to bring up P as well. If O works, P should work as well.
Can the ROM be installed by using the latest KANG TWRP 3.2.3 or do I need to use the TWRP found in the download section?
@shinzz TWRP from download section
any update?
shinzz said:
any update?
Click to expand...
Click to collapse
Noticed the link to the ROM is 404'ed also. - NP
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Clamor said:
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Click to expand...
Click to collapse
My 201 is on KANG's - TWRP 3.2.1-0 and KatKiss, if this ROM just a simple wipe and flash with KANG's - TWRP 3.2.1-0 and the Harry Bean bootloader on my 201 or will I need a different recovery console, bootloader ext. ext? - NP
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance