Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So always do a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Android: 7.1.2
Security Patches: May 2017
Komapatient said:
Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So do always a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Click to expand...
Click to collapse
Thank you bro for sharing and keeping the device alive ?
Btw you should consider posting this in android development forum so that people know abt it
Adarsh Dubey said:
Btw you should consider posting this in android development forum so that people know abt it
Click to expand...
Click to collapse
I intentionally posted not in the development section, since I am not developing but only building.
Komapatient said:
I intentionally posted not in the development section, since I am not developing but only building.
Click to expand...
Click to collapse
Bro you shouldn't post it in original development but you can post it in Android development as you are building the rom for the device and many of the people port roms they also don't develop nor fix bugs but post it in Android development as they are building the rom for the device
sir @Komapatient , can you please share the source kernel or ROM?
Nicklas Van Dam said:
sir @Komapatient , can you please share the source kernel or ROM?
Click to expand...
Click to collapse
Hi,
I don't understand your request. I pulled the sources from LinOS Git. There is nothing done on the source.
Komapatient said:
Hi,
I don't understand your request. I pulled the sources from LinOS Git. There is nothing done on the source.
Click to expand...
Click to collapse
Ok, it's neccesary for now. Can you please to keep update on this ROM?
Komapatient said:
Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So always do a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Android: 7.1.2
Security Patches: May 2017
Click to expand...
Click to collapse
So basically you're keeping the ROM updated with latest changes from lineage OS source code , I mean bug fixes and security patches etc.
matrixex said:
So basically you're keeping the ROM updated with latest changes from lineage OS source code , I mean bug fixes and security patches etc.
Click to expand...
Click to collapse
Yes. As a courtesy to the people who cannot compile their own ROM and to give s.th. back to the community who helped me a lot of times.
Hi @Komapatient,
Glad to see you once again around here, think we last talked when you were using the Xperia V on LineageOS.
Happy to see nicki is not fully dead and that its users can benefit from newer builds.
However there's a big concern here, I pushed the Nicki official removal for two important reasons :
- Device sources are no longer updated. If there's no real issue it's fine, but might appear.
> Issues like autobrightness flashing in a weird way upon device wake/unlock is among the biggest issue fixed / wip since the changes stopped.
> Checked in my huashan sources to find common relevant things for nicki, I just pushed an overlay cleanup and fix for MMS non-Data use.
- Kernel sources are highly outdated. To put this in a easy way, we can judge the security status
> to be around December 2016 and February 2017. Therefore the security version you share here is only the ROM sources,
> though a good portion of the security patches are actually to be worked upon for each kernel.
You can find our internal CVEs vulnerabilities tracker concerning the nicki 8x27 kernel here : https://cve.lineageos.org/android_kernel_sony_msm8x27
Someone should at some point stand up and start looking at them one by one,
fixing the ones related to the kernel version by cherry-picking, testing then pushing to gerrit.
You can take my sony_msm8960t kernel as reference if you wish, only the most recent CVEs are a work in progress,
and you should therefore easily see which CVEs concern your 3.4 kernel and find the commits in my history.
I'd gladly merge commits uploaded to gerrit if they are valid and properly authored / clean.
Hope this makes the current status of Nicki a bit more clear.
Bye.
@AdrianDC
Thank you for your clarification. The kernel sources are indeed a bummer, but as my coding skills are below zero. Sadly I am not able to help here out.
Komapatient said:
@AdrianDC
Thank you for your clarification. The kernel sources are indeed a bummer, but as my coding skills are below zero. Sadly I am not able to help here out.
Click to expand...
Click to collapse
Trying to "steal" my commits from sony_msm8960t would be a good start,
you can also check the commits tags on Gerrit to see the CVE 20xx-xxxx related numbers
when the information was set as topic, helps clearing the list too.
Since the work is already done on our side, it shouldn't be a giant work to do,
and would be a good place to start with + bring back some security updates to the device.
Please try to update this rom
please try update this rom, ,
Related
I heard at devcon that a few guys are working on Sailfish ports for a few phones, including ours. So I decided to get them together with the devs here on the forum to get the port done. The place where the developers and porters of Sailfish OS are talking to each other is on freenode, so if you want to help them... just go there and join the channel #sailfishos-porters.
Warning: This is a developement project. So please only join the channel if you really want to help. Just going there to ask for ETAs or stuff like that won' t be tolerated. Also this thread should be a place for developers to collect ideas and fix bugs, not for the purpose of asking for ETAs. Please keep that in mind.
For the initial port I would like to thank @vgrade; information on how to install the port are in second post!
XDA:DevDB Information
Sailfish OS, ROM for the ONEPLUS ONE
Contributors
dansou901, vgrade
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CM 11
Version Information
Status: Alpha
Created 2015-03-20
Last Updated 2015-03-29
This is a community port of Jolla's Sailfish OS for the OnePlus One.
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about SailfishOS please head over to sailfishos.org.
This is not an Android ROM, this is a different base of an operating system called Linux, running glibc library.
It only uses parts of Android for hardware enabling (drivers).
Release Notes:
The port is considered to be of alpha quality and released as a first step to the same levels of functionality as the Nexus 5 .
Download Location
http://images.devaamo.fi/sfa/bacon/
Kernel Source at http://images.devaamo.fi/sfa/bacon/...1.1.27-alpha1-201503192017-kernel-src.tar.bz2
Make sure you have a compatible cm11 version installed http://78.47.45.43/owncloud/public.php?service=files&t=9725fbb3b3c8d9706a2bb29388b3de83
Zip install tested with TWRP and MultiROM versions later than 20 March from http://forum.xda-developers.com/oneplus-one/development/mod-multirom-v26-t2835738
HW Support status:
(Look for OnePlus 5 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Bug reports, if internet search refuses to help:
First search XDA for keywords. Things like libsailfishapp have already been worked out by this amazing community
Software-related bugs (Sailfish OS): first search http://together.jolla.com . Tag your questions with "community-build"
Hardware-related problems: at the Nemo Project Bugzilla under Hybris-ing component
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
oneplus forum thread at https://forums.oneplus.net/threads/sailfish-os-for-oneplus-one.279537/
Known issues:
OTA Updates do not work
The camera does not work
Android app support is not available (unlike in Jolla phone): please ask about the status for open-source Dalvik runtime framework on #sailfishos-porters on irc.freenode.net and also check this XDA Thread
All remaining: In Bugzilla
ROM Kernel: Linux 3.4.0
Changelog:
Alpha2 - 29 March 2015
WLAN fixed up - vgrade/yacuken
Alpha1 - 20 March 2015
Initial release
This is a new video of SailfishOS running on the oneplus one with wlan working . http://youtu.be/Vm4m_dlUYRw
Install Video at https://www.youtube.com/watch?v=iphzmCVofbk
Details of port can be found at http://piratepad.net/gVqPXuEGW4
Please join the porting efforts at IRC channel #sailfishos-porters.
Thanks to all the Jolla sailors and SailfishOS community members for all their help, especially @stskeeps for the QCOM_BSP catch.
BREAKING NEWS - SailfishOS 2.0 version WIP at https://plus.google.com/+TomaszSternaSMK/posts/DyQHm82v2b5
vgrade
Just a little status update that you see the project isn't abandoned: @vgrade is waiting for updated AOSP sources from Oneplus. Once they're live, he can cook something for us.
Is the project still alive?
CountDooku said:
Is the project still alive?
Click to expand...
Click to collapse
Ask @vgrade if it is still alive. I didn't hear anything the last weeks, but I hope that he's still working on it...
dansou901 said:
Ask @vgrade if it is still alive. I didn't hear anything the last weeks, but I hope that he's still working on it...
Click to expand...
Click to collapse
@vgrade, is the project still alive?
msri3here said:
@vgrade, is the project still alive?
Click to expand...
Click to collapse
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade
vgrade said:
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade
Click to expand...
Click to collapse
thanks for the quick reply
Take you time
vgrade said:
Hey,
I've not been able to spend much time on this since xdadev:con due to day job commitments, fingers crossed I'll get some time over the holidays to progress some more.
BR
vgrade
Click to expand...
Click to collapse
Let me know if you need any help, I'm new to porting, but I'd be willing to lend a hand and do some of the grunt work - if you need it.
I'm very interested by getting Sailfish OS on my One Plus.
I don't know how to install the build you'll provide but I suppose that you will give a litte tutorial with it.
I'm now following this thread !
Looking forward to this
@dansou901 might be of interest.
Edit: might be your work. [emoji5]
https://twitter.com/vgrade/status/573375605640695808
gsmyth said:
@dansou901 might be of interest.
Edit: might be your work. [emoji5]
https://twitter.com/vgrade/status/573375605640695808
Click to expand...
Click to collapse
Good find! I don't have twitter so I wouldn't see this... @vgrade, will you come here again when you're back from Barcelona? @KINGbabasula, is MultiROM ready to go for Sailfish OS?
Edit: It isn't my work, I'm not in Barcelona on MWC this year (but planning to go there someday...). So it's vgrades work together with the other Sailfish porters (see the IRC channel I linked in OP).
Have you guys seem this?
http://www.thejollablog.com/sailfish-os-oneplus-one/
topfreitas said:
Have you guys seem this?
http://www.thejollablog.com/sailfish-os-oneplus-one/
Click to expand...
Click to collapse
That's just a followup from vgrades tweet, so nothing new. The information that he will share the build after MWC is down in the comments...
Guys Hi
As you see great progress made during MWC week on the port. Stskeeps from Jolla identified the bug stoppng UI coming up so we are go now.
Good to see the chase up on Multirom as this makes it easier for folks to test. I think it just needs to have a build which includes the sailfish patches included so any recent upstream build should suffice. On the add room page you should see a SailfishOs radio button.
Stay tuned for more details and drop into #sailfishos-poters channel on freenode IRC and say hello.
BR
vgrade
For those wanting to build their own images I've put my porting notes at http://piratepad.net/gVqPXuEGW4 , join us at #sailfishos-porters channel on IRC .
vgrade
vgrade said:
Guys Hi
As you see great progress made during MWC week on the port. Stskeeps from Jolla identified the bug stoppng UI coming up so we are go now.
Good to see the chase up on Multirom as this makes it easier for folks to test. I think it just needs to have a build which includes the sailfish patches included so any recent upstream build should suffice. On the add room page you should see a SailfishOs radio button.
Stay tuned for more details and drop into #sailfishos-poters channel on freenode IRC and say hello.
BR
vgrade
Click to expand...
Click to collapse
vgrade said:
For those wanting to build their own images I've put my porting notes at http://piratepad.net/gVqPXuEGW4 , join us at #sailfishos-porters channel on IRC .
vgrade
Click to expand...
Click to collapse
Zip Image link now in second post in thread.
vgrade
vgrade said:
Zip Image link now in second post in thread.
vgrade
Click to expand...
Click to collapse
phone does not boot
i am using philz recovery to flash the rom can that be a problem
MasalaMan said:
phone does not boot
i am using philz recovery to flash the rom can that be a problem
Click to expand...
Click to collapse
Yes, this recovery does not have a version of tar which supports the -j option so the sailfishOs rootfs is not extracted, please use the recommended recovery
vgrade
Hi Guys, it's been so many days Kernel Sources are released, and Syhost Provided Lollipop with RIL Bug, but now the excitement is increasing day by day. When the sources weren't released, Developers were saying to wait until Kernel Sources are released , to fix major bugs. But still no response. I appreciate Developers for Providing Custom Kernels and Updated Scripts in previous Roms.
I request you to post all Lollipop Related News over here. and about Developers work on Github.
Thankyou.
well,
just a suggestion
if u just want to know the LP work progress and collect the news/info into this thread,
maybe u should change the title,
cause the title it's little 'demanding'
and for the first start, maybe u could collect the link and put in here,
also give some brief update about the progress, for example
1. Mokee 5.0.1 (link to source thread/info) - status WIP - RIL bugs
and so on...
cheers
naved97 said:
Hi Guys, it's been so many days Kernel Sources are released, and Syhost Provided Lollipop with RIL Bug, but now the excitement is increasing day by day. When the sources weren't released, Developers were saying to wait until Kernel Sources are released , to fix major bugs. But still no response. I appreciate Developers for Providing Custom Kernels and Updated Scripts in previous Roms.
I request you to post all Lollipop Related News over here. and about Developers work on Github.
Thankyou.
Click to expand...
Click to collapse
asking for ETA both explicit or implicit is a no no no... it's top rules in XDA.
if you want it really soon, use Mokee by syhost and try to fix RIL bug using kernel source code.
beside how hard is to see armani-dev commit in CM12 in github?
https://github.com/armani-dev/android_device_xiaomi_armani/commits/cm-12.0
Sorry I didn't get you.?
Hey guys,
I've just managed to make a build of Cyanogenmod with lots of help by a guy called sultanqasim (actually he did most of the work), thanks a lot bro
Probably it's very bugy. Let's call it Pre-Alpha. Anyway, the build is ready and I need guys who'd like to try it out.
I chase GDrive for the first CM build. All Beanstalk builds are uploaded to the official Beanstalk AFH.
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
NFC
Broken:
Audio through built in speakers or headphones
RIL
Camera
Mic
Various other smaller things
Some Sprint users also report that it doesn't work for them. Just try it out if you like. Every tester's report takes the project a bit closer to stable builds.
Download Cyanogenmod (GDrive)
Download Beanstalk (AndroidFilehost)
To flash it:
in TWRP, reformat the userdata partition as unencrypted ext4. Go to Wipe->Advanced Wipe, select data, click on repair or change filesystem, change file system, and choose ext4.
in TWRP, go to Wipe -> Advanced wipe, and erase system, data, dalvik, and cache
flash the file by pushing it to your sdcard or you can use adb sideload. Also you can flash GApps optionally.
reboot into the system
Looking forward to your reviews. Thanks a lot
Good luck to all of you
Remember: I'm not responsible for anything that could happen as a result of following my instructions or anything else.
XDA:DevDB Information
[Testing][ROM] Cyanogenmod 13 - Unofficial, ROM for the HTC 10
Contributors
krassermensch, sultanqasim
Source Code: https://github.com/sultanqasim
ROM OS Version: 6.0.x Marshmallow
Based On: Cyanogenmod
Version Information
Status: Testing
Created 2016-06-10
Last Updated 2016-07-13
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
Nice!
Moderator Information,
Thread re-opened to allow OP to upload file on XDA host.
Can't wait for CM13 on this phone. I know Squid2 has been a ton of work into this, from what I know, already a solid month behind the scenes.
device boots up? display?
thought this thread was closed till a download link was posted...
i don't seem to find any link or me gone blind lolll
edit:- just read that its opened for uploading the link so it seems upload is in progress
Maybe change the title with correct spelling of " Unofficial "
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
i guess we would need to wait for the upload to be finished to see if its any different or the same as the Op doesn't seem to be much of responding to any comments
@krassermensch - Can you give us a list of what is and isn't working in your experience, at least?
psych0r3bel said:
We've had a booting and partially working version of CM13 for a while now, it's posted by @squid2 somewhere in the guides and discussion thread. Which, makes me wonder, with all due respect, how this is any different from that build?Have there been any fixes to the broken things on that ROM (most of the radio, for example) that warrant this being a separate version of CM13?
Click to expand...
Click to collapse
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
krassermensch said:
Hey, squid2 is the guy I named sultanqasim in the first post of this thread as sultanqasim is his GitHub name. I managed to build Cyanogenmod with his help and his sources. He's the main developer. I'm just trying to make a more current build for those who'd like to have one. As a result my builds are based on his latest commits. I'm just the one who did minor patches which aren't as relevant as the ones squid2 performed. He's the more experienced one of us. You should treat me like a maintainer and him like the main ROM developer.
Click to expand...
Click to collapse
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
psych0r3bel said:
Hah, thanks for clearing that up - good to know. Didn't mean to attack you, just asking the questions trying to keep it all honest. So should we assume his working/not working list applies here?
Click to expand...
Click to collapse
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
I'm really glad to see this coming along! Keep up the good work. I'm not much of a tester normally but I think Im going to give it a shot later tonight and let you know what issues I can find.
krassermensch said:
Don't mind. I really want to let everyone know that the main work was made by sultanqasim as I'm not willing to steal anyone's work. I just want to provide a more current build of his work to the community. Assume some minor things have already been fixed but it's probable that you'll experience camera, nfc, radio... issues here as well... I also hope this'll be fixed soon
Click to expand...
Click to collapse
So glad to see the credits given, and insight to what testers will find.
Didn't want to see any drama, I thanks for putting the time in and squid for laying these ground work!
Sent from my HTC 10 using XDA-Developers mobile app
@krassermensch, thanks for your efforts but... If you're going to publish his work, how about updating the OP with his bug list and the title with pre-alpha. Just so users have more information, instead of the vague "it might be buggy". We know its buggy. Specifics about what works and doesn't is what people would like to know.
This still accurate?
squid2 said:
Currently working:
Display
WiFi
Bluetooth
Sensors
Audio through bluetooth
Broken:
Audio through built in speakers or headphones
RIL
Fingerprint sensor
Camera
Various other smaller things
Click to expand...
Click to collapse
Moderator Information,
Thread has been moved to general, as the OP is only hosting the work for another user.
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
matteosaeed said:
Hi, I flashed your rom with the open gapps, booted up and connected to wifi and logged in through google. I don't have any cellular connection though. I am making a nano back-up of this and going back to stock until I figure out the cellular connection. Let me know how I can help or report bugs to you.
Click to expand...
Click to collapse
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
rav101 said:
I think the RIL is not working yet which is what you need for the cellular connection. This definitely needs more work before its useable. But really good progress to date.
Click to expand...
Click to collapse
Sweet. I can test more at nights when I am at home. Doing the nanodroid now of this build.
---------- Post added at 09:17 PM ---------- Previous post was at 08:52 PM ----------
question, I am trying to go back but I am getting the failed to mount '/system' (invalid argument), any tips on how to bypass that?
This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13
Reserved
Edit 1:initial build didn't boot for me, no adb can't get log
Ok im gonna try it.
If you want, i can leave logcat for you
OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.
Ofc, it doesn't boot. And don't create threads without testing.
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.
Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought
Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar
Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.
Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha
You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.
Code:
*** Disclaimer***
No legal responsibility taken for anything.
use at own risk.
I am not a Developer . Just sharing the RR project with updates and mergers faster for users
Install with full knowledge that this might make your phone 100% unusable and will void your device warranty .
Briefing​
This is my own personal RR N build, based on 14.1. i will build the ROM ASAP once crpalmer merges any new codes .
I will upload the ROM if it Boots fine in my personal device
i am not offending anybody's build especially the Official RR thread . i just keep this thread updated daily .
please dont complain anything about the BUGS as all bugs in CM14.1 are present in my build too
Feel free to contribute, recommendations and (new) bug reports are always very welcome.
I am a newbee here if any mistakes please let me know
Click to expand...
Click to collapse
Features & Details​
FULL Substratum theme engine support with Masquerade and OMS
Compatible fully with both firmware (MM and N)
SELinux ENFORCING
Build USING Ubuntu 16.04 in Windows using VM
Click to expand...
Click to collapse
INSTRUCTIONS
Download the Rom & and ARM64 7.1 GAPPS .
Reboot to TWRP recovery .
Flash ROM and then GAPPS
Flash Custom Kernel ( Personal recomendation i am using V7.0.2-Beta Android N )
If running Nougat firmware (2.0+) you will need to flash fingerprint patch to use the home button
Click to expand...
Click to collapse
BUGS
Same as CM 14.1 ... i am not listing the bugs
ChangeLog
Add headphones backend (fixes headphones)
WIFI fix ( may be check it out yourself)
Developer settings fixed
USB tethering fixed ( working for me)
Night mode working
Bug fixes
VOIP application issue fixed when it comes for audio
Added Aptx Bluetooth Support
[*] Touch Screen Gestures added
Note :- please dont ask for BUG fixes FYI i am not a developer ... solutions and recommendations are welcome
Downloads
RR-N-v5.8.2-20170319-pme-Nightly.zip
Finally an OMS build .... No help got from any of the devs out here in XDA ... Finally managed to get the OMS in my build.
Thanks a lot to my best mate who helped me in guiding on github and gerrits ++ thanks @ mihran
GAPPS:-
Optional
substratum theme engine
XDAevDB Information
Resurrection Remix ROM N UNOFFICIAL for the HTC 10
Contributors crpalmer
Version Information
Status: Beta
Created 26.12.2016
Source Code Rom
https://github.com/vysakhraju/platform_manifest
Original Rom thread by @Eliminater
=[url]http://forum.xda-developers.com/htc-10/development/rom-resurrection-remix-m-t3440977[/URL]
Thanks alot!
Where is FP patch?
ali nz said:
Thanks alot!
Where is FP patch?
Click to expand...
Click to collapse
As i have not got the permission to use the finger print patch please use the one from CM14.1 thread by @ibrokemypie
@ibrokemypie :- Can i use your finger print patch for my ROM ?
Dec 26th Build with OMS updated in OP
OP I'm on your last build of RR unofficial from 12.22 from the other thread.
do you require or recommend a clean flash for this or can it flash dirty? thank you!
VR32 said:
OP I'm on your last build of RR unofficial from 12.22 from the other thread.
do you require or recommend a clean flash for this or can it flash dirty? thank you!
Click to expand...
Click to collapse
I did dirty flash and is wokring fine
thanks man I'll give it a go
Hi All
Need your support to add OMS support to this ROM
. I have does somebody know how to Clone / fetch the megers to my build ...
If someone know please comment so I can release the build tomorrow
ffs what is with the //word for word// copying now
one thing to build a rom using open source code, another entirely to copy an entire thread and change some words just enough to get past your teacher's plagiarism check.
ibrokemypie said:
ffs what is with the //word for word// copying now
one thing to build a rom using open source code, another entirely to copy an entire thread and change some words just enough to get past your teacher's plagiarism check.
Click to expand...
Click to collapse
As per the request and comments on RR thread i created a seperate thread for my build... To be frank yes copying was easy and i thougt of doing ..I have not spend much time in that lol.. Anyways I have not copied your build or work mate !!!
blackpanther0582 said:
As per the request and comments on RR thread i created a seperate thread for my build... To be frank yes copying was easy and i thougt of doing ..I have not spend much time in that lol.. Anyways I have not copied your build or work mate !!!
Click to expand...
Click to collapse
just to be clear, I never said nor insinuated that you copied my build, very difficult to do that anyway as being all open source, no one is copying anyone, simply building the same source code. Just frustrating to have ones words taken and repeated without permission, attribution or even a simple acknowledgement, and its suddenly something that has happened a lot in the past few days.
Really sorry mate ...yes I have not asked permission from you I apologizing for that ... I don't know how to create a thread while looking at your thread it was really a promising one just to start with .
I was at my work time though so just spend only few mjns for that ..
Sorry once again...
If you insist I will change the entire thread
thanks for building RR I'll keep an eye on this as it develops
Working like a dream for me. Really appreciate this.
(/w Nebula 7.0.2)
Tried to add full OMS support to my yesterdays build ... But I think I am missing some steps..
Without some devs support I think I might not be able to fix it
Finally an OMS included RR nightly has been uploaded... See the main thread for download Link...
Night mode / Live display works
RR-N-v5.8.0-20161228-pme-Nightly.zip
@blackpanther0582 could you compile this kernel?
https://github.com/CyanogenMod/android_kernel_htc_msm8996/commits/cm-14.1-caf
OMS(meaning substrarum) I installed from the Play Store on the 12/24 build seems to work fine. Wifi cuts out at random is that the bug everyone talks about? It just puts am X in it and says connected but no internet.
Sent from my HTC 10 using XDA-Developers mobile app
Nosferatu. said:
OMS(meaning substrarum) I installed from the Play Store on the 12/24 build seems to work fine. Wifi cuts out at random is that the bug everyone talks about? It just puts am X in it and says connected but no internet.
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Same here on both counts. Gonna install the 28th build to check it the wifi's fixed. That's literally the only bug i need fixed to be 100% daily driver. So awesome how fast CM/RR came all the sudden.
holofractal said:
@blackpanther0582 could you compile this kernel?
https://github.com/CyanogenMod/android_kernel_htc_msm8996/commits/cm-14.1-caf
Click to expand...
Click to collapse
Will sure try