CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, we will laugh at you, all, at the same time.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATIONS
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES HERE
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
Google Apps: Link 1 Link 2
TWRP Recovery: https://www.androidfilehost.com/?fid=24052804347766143
CHANGELOG
Download
GAPPS for CM-12.1
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
source
https://github.com/cyanogenmod/android_device_htc_enrc2b
https://github.com/cyanogenmod/android_kernel_htc_enrc2b
https://github.com/cyanogenmod/android_device_htc_tegra3-common
Contributors
Lloir, Thomy
Source Code: http://github.com/cyanogenmod
Working Not Working: Eventually Change log
This will be edited and updated as I make progress
Working 7/7/15:
Audio
Touch
Display
Vibrator
WIFI
Bluetooth
DATA/GSM/RIL (except for sim pin)
BATTERY
ROTATION
GPS
Not Working 7/7/14:
Device encryption
CHANGELOG
?/05/16 (well it's finally coming out) in 2017
05/05/17 -- FINAL
cgroups fixed
RIL Fixes (GSM/DATA)
3G Mtu changed, should see an increase in speed.
Security patches, fixes loads of security issues
X+ now shows up instead of the ONE (MTP) (pulled from AndyLavr git)
SElinux fix up (pulled from AndyLavr git)
CM main source update
and a load of other stuff.
------------------------------------------------------
27/11/15 ------ MD5 b9ae858d0a881ae6a24958caa067360e
Sdcard symlink is fixed? it's storage/sdcard0 (for me anyway test it for me)
Added more sepolicies for the ril :silly:
Updated main cm source
FULL WIPE
------------------------------------------------------
5/11/15
CM update which includes Security updates from Google https://groups.google.com/forum/#!topic/android-security-updates/GwZn7sixask
Reverted the changes I made to sdcard, which means /sdcard is now able to be accessed again.
------------------------------------------------------
25/10/15
More selinux denial's fixed thanks to @el-Loko logs
Let me know if the sim card issue still arises.
I've made changes to MTP and the /sdcard /storage area's
------------------------------------------------------
24/10/15
Sepolicies updated, hopfully the no sim issue will be fixed now. https://github.com/Lloir/android_device_htc_enrc2b-2/commits/cm-12.1
No more selinux denial's that I could find. All eliminated.
Source update
Kernel update's thanks to @ntemis https://github.com/Lloir/htc_kernel_oxp/commits/cm-12.1
Sim toolkit now show's and works
GPS lock is oh oh so much quicker
If google maps has a hissy fit let it die and reload it.
------------------------------------------------------
28/8/15
Updated source (Which includes the chrome fix)
------------------------------------------------------
26/8/15
Updated source
Revert my bluetooth breakage change, so BT works as it should.
------------------------------------------------------
7/8/15
http://review.cyanogenmod.org/#/c/93232/
http://review.cyanogenmod.org/#/c/105285/ + http://review.cyanogenmod.org/#/c/105284/
http://review.cyanogenmod.org/#/c/105100/ (This is a security fix hence the build today) Issue with this, currently will get sorted for a future build
Mainline cm update ^^ those changes are not merged into CM but I've picked them to go into this rom for my own personal build. I will share this build
------------------------------------------------------
7/7/2015
CM general update
CVE's patched (security) http://review.cyanogenmod.org/#/c/102586/
NFC Update
Low memory killer updated
USB OTG Enabled
Brightness should be brighter (Should)
Re-implemented the powerhal from CM-10.2 (For those of you who have been around here for ages)
Updated the keymaster file based off of the grouper (Security)
A ton of patches from the grouper kernel http://review.cyanogenmod.org/#/c/102546/
VFS/ Compaction changes http://review.cyanogenmod.org/#/c/102597/
------------------------------------------------------
20/6/2015
CM mainrom update
GPS working in permissive only mode
-----------------------------------------------------
9/4/2015
12.1 update
Chrome/Firefox work
Updated with most recent CM source
------------------------------------------------------
6/4/2015
CM-12.1
DO NOT DIRTY FLASH OVER CM-12.0 IT WILL CRASH
gps is still broken
everything below counts
NEEDS KERNEL FLASH as usual
------------------------------------------------------
6/4/2015
New Kernel, not loaded with crap. This kernel is WIP. NO SMARTMAX on it, No S2W (Let the rage begin)
Might have turned the audio up...Sounds like it, need someone to confirm
Button light stays on when it needs to now.
------------------------------------------------------
3/4/2015
Fixed No Data issue FLASH THE NEW ROM AND BOOTIMG
------------------------------------------------------
2/4/2015 or 3/4/2015 depending on where you live
1st actual working release so lets start the change log
Battery WORKING
Source updated to today's released source
SELINUX DISABLED
Rotating working
GPS broken
regretting this...check the post above this one...
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Lloir said:
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Click to expand...
Click to collapse
Sorry man cant use it daily without the battery being fixed! Other than that the camera works? at least for the most part
just installed it and i am suprised...very smooth.
still installing apps for daily use. will of cause report if theres anything to report.
what excactly does not work with cam? i can shoot pics and they look as pretty as they should.
so, happy new year to every1!
el-Loko said:
just installed it and i am suprised...very smooth.
still installing apps for daily use. will of cause report if theres anything to report.
what excactly does not work with cam? i can shoot pics and they look as pretty as they should.
so, happy new year to every1!
Click to expand...
Click to collapse
It wasn't working for me, but yeah, all of you say it works, so I'll take your word. :good:
Lloir said:
It wasn't working for me, but yeah, all of you say it works, so I'll take your word. :good:
Click to expand...
Click to collapse
I'll jump in as soon as builds with proper battery comes up.
And, thank you for being an awesome dev.
Lloir said:
sooooo I know a load of you have downloaded this? Any bugs I've not listed?
Click to expand...
Click to collapse
installing right now, can't wait to test!
i moved on to the OPO as daily driver, so i don't have to care about stability, but also i'm eager to see how the HOX+ runs Android5! Thanks for your awesome work!:good:
reaper90 said:
installing right now, can't wait to test!
i moved on to the OPO as daily driver, so i don't have to care about stability, but also i'm eager to see how the HOX+ runs Android5! Thanks for your awesome work!:good:
Click to expand...
Click to collapse
Yeah, I need to move on soon, so new devs are going to be needed for the X+ by the next major release.
Lloir said:
Yeah, I need to move on soon, so new devs are going to be needed for the X+ by the next major release.
Click to expand...
Click to collapse
This device is more than two years old now, i don't think there will be new devs coming to this device. Although i know not everyone wants to buy or can afford a new device every two years, i think this one has done it's job. while htc dropped support after only one year, i think some quite stable 4.4 roms are more than we could have asked for!
first impression on this build:
runs pretty good so far, camera not working here, kickstarting the battery from TWRP does not really work for me (maybe i'm doing something wrong) and when using adb shell, the charging led stays forever on.
Camera working fine here !
and whats the purpose of turning the battery on..? I could reboot and its working fine. I did not execute any command. But the battery shows 66% even though its lower than that. So the only problem we face if we dont turn it on is that we cant see the real percentage or what....?
backb0ne5p1d0r said:
Camera working fine here !
and whats the purpose of turning the battery on..? I could reboot and its working fine. I did not execute any command. But the battery shows 66% even though its lower than that. So the only problem we face if we dont turn it on is that we cant see the real percentage or what....?
Click to expand...
Click to collapse
Pretty much, not tested to see if it doesn't charge though....it will ALWAYS show 66%
Also are you using a 3rd party app for camera??
I don't mind it showing 66 as it's not my main phone.
And No, but I flashed GApps.
All I did was full wipe, Flash boot.img, flash ROM, flash GApps. Then the ROM booted and had a working camera
I think I found a temporary fix for the battery problem!
Go to the store, download 2 apps.
1) Boot shell
2) sudo for android.
Open sudo for android and click "Install Sudo"
Then open Boot Shell and click add command button. And add the command "sudo /system/bin/htcbatt"
Now reboot your phone and the battery stats will still be there
backb0ne5p1d0r said:
I think I found a temporary fix for the battery problem!
Go to the store, download 2 apps.
1) Boot shell
2) sudo for android.
Open sudo for android and click "Install Sudo"
Then open Boot Shell and click add command button. And add the command "sudo /system/bin/htcbatt"
Now reboot your phone and the battery stats will still be there
Click to expand...
Click to collapse
Yeah, there's that.
I have it fixed here, just not happy with the fix at the moment. IF People want to fix it this temp way do the following :
reboot into TWRP
mount system
adb shell
chmod 777 system/bin/htcbatt
reboot
If your not happy with using a 777 chmod then that's understandable, I'm trying out a 2nd fix as we speak, this will also help me to fix the battery issue in TWRP too
Things that are now working on my local build
Device Encryption
Battery + Battery LED
IF I'm happy with the battery fix, I'll do that release today.
Still broken :
GPS --- Kinda borked.
Rotating
Button lights are a little yeah.
This is going to be replaced with omni-L
Stay tuned, Not releasing ANYTHING until I have a nice working build of a ROM, not going to be releasing half-assed builds anymore.
Ok, after 2 days of daily use i can say that this rom is very stable, no reboots or freezes. Only GPS and auto-rotate is not working for me, but (orig)cam does its job.
One tip for the battety sidekick:
Instead of doing the trick via pc do it in a shell on your phone but dont kill the process with ctrl-c.
Related
This thread has been superseded by this thread: http://forum.xda-developers.com/showthread.php?t=1366897
Changelog in Second Post:
Screenshots attached at bottom:
Link to Alpha8
This tarball also contains a userdata image where most of the gapps are.
People whose rotation/bluetooth doesn't work: Try flashing this new boot.img and see if it fixes it.
I will not be uploading any more flashable zips as they seem to be broken
Working:
Wifi
MMS
Calling (People I talk to say they can hear me better than the could when i was on CM7)(Probably coincidence)
Bluetooth (works for babijoee but broken for me)
TouchScreen (Multitouch)
Sound (Flawless)
GPS (works for me)
Accelerometer (rotation) (works for babijoee but broken for me)
Home button
3g (seems to like radio 5.08.00.04)(works for me)
Headphone jack
Network Stats and Quota
Click to expand...
Click to collapse
Not Working:
Trackball
Camera
USB mass storage (use adb)
Hardware Accelaration
Wifi Signal Strengh Icon in Status Bar.
Click to expand...
Click to collapse
Questions? Check out this FAQ (thanks alex_mobile)
Anyone that wants to colaborate
Join us in #ics_desire_nexus_dev on freenode
My nick is drewis.
Any help is welcome.
To flash the img files.
Code:
tar xjf ics-passion-alpha*.tar.bz2
adb reboot bootloader
fastboot -w
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
I'm using blackrose hboot (standard partitioning) but i dont think it matters what hboot you use.
Don't tell me whats wrong with it (i already know that) Tell me how to fix it!
Here's my sources to get you started:
I have set up an organization on git hub where you can follow the progress
https://github.com/ics-passion-dev
[Note:] I am updating these regularly.
Get source (cm ics repos)
Code:
repo init -u git://github.com/ics-passion-dev/android.git -b ics
repo sync
Fix Audio.
Code:
cd hardware/msm7k
git fetch http://review.cyanogenmod.com/p/CyanogenMod/android_hardware_msm7k refs/changes/03/10303/1 && git cherry-pick FETCH_HEAD
Build it.
Code:
. build/envsetup.sh
lunch full_passion-userdebug
mka
Note: The above is not enough to get a clean build you will need to debug some minor errors.
On amd hexacore w/ 12gb ram takes 40 minutes. (where CM7 takes 14)
CHANGELOG
CHANGELOG
Alpha8 Link to Alpha8
New apn list from cm
Update gapps with ones from koush's NS build.
Headphone fix (thanks zivan56)
Back to pershoot's BFS kernel as base.
Added network stats and quota to kernel.
Built with opengl enabled (currently causing blank screen)(REMOVED)(still no HWAccel)(disable Window/Transition effects makes it much nicer)
Alpha7 Link to: Alpha7
Same as alpha6
Rebuilt with openjdk (this is aosp after all)
Added Gmail and Market
Market: login, try and download an app (only one), it will error. Reboot. Open market and it should start downloading. Then you're good.
Market: I wiped and now market does not work. same error. Can't seem to fix it.
Change to IntersectRaven's 2.6.38.8 AVS Kernel based on pershoot's
Alpha6 Link to: Alpha6
Added liba2dp for audio over bluetooth. (untested) (removed: caused build problems)
AUDIO FIX: a real audio fix (thank you firesnatch [sean neeley])
Head phone jack does not work yet. plays through speaker while plugged in.
added back all apps but VideoEditor and its libs and Camera
added back all ringtones and notifications
switched back to userdebug build
No gapps: Sorry. They were deleted when i rebased my tree. But they had issues anyway. So not bothering with them on this release.
gralloc's back (hence the lag) Disabling animation in developer settings helps.
3g seems to start the connect/disconnect thing after a while of non use. fix is either reboot. or go into setting and disable mobile data for a minute then turn it back on.
Alpha5: Link to Alpha5
switched from userdebug to eng variant
got su back and some bluetooth files (still broke for me)
removed most sounds (ringtones,notifications) to save some space
removed apps: Camera, VideoEditor, libWnnJpnDic, PinyinIME, Email, Exchange, libvideoeditor_jni, libvideoeditorplayer, libvideoeditor_core
Added Gapps: Market wont show up untill you sign in through settings
Issues: screen now flashes an orange outline on edge of screen when you click some buttons
Alpha4: Link to Alpha4 as system and boot images
Home button works! (thanks again to rampv78)
Removed soft buttons
Changed lcd density back to 240
Alpha3:Link to Alpha3 as a flashable zip
Rebase latest changes in CM tree.
Try new GPS code in CM gerrit.
Better Audio fix: Still broken but more stable (closer to working out a real fix)
Leave out gralloc since we dont have HW Acceleration yet.
Alpha2:Link to Alpha2 as a flashable zip
changed ro.sf.lcd_density to 220 to fix softkeys
build with gralloc: kind of makes it laggy if it bothers you delete /system/lib/hw/gralloc.qsd8k.so (but not gralloc.default.so)
Working:
Calling: (mic works they can hear you)
Sound/Mic: sort of (thanks to tip from rapmv78 and the Desire guys)
Gps: I think (might just be googles location features even though its unchecked in settings)(tested by visiting maps.google.com in browser with wifi off)
Not Working:
3g: still very sporadic (a few reboots fixes it somtimes)(maybe i need to update to latest radio)
Home button
Trackball
Alpha1: Link to Alpha1 as system.img and boot.img
Migrate source to CM repos
Using ICS init (alpha0 used CM7)
Pershoots CM7 2.6.38.8 Kernel
Added Soft Buttons to give us a working home button (although this causes the bottom row of the keyboard to be half way covered up) You can fix this by changing ro.sf.lcd_density to 220 or 200 in /system/build.prop
Not working:
3g (severe connect/disconnect issues)
Audio
Home button
Trackball
Some other stuff I can't remember
texasice said:
I would like to get a functioning ICS build as soon as possible. Anyone that wants to colaborate im hangin out in #cyanogenmod-dev on freenode with nick drewis. There is no way I will be able to do this by myself. So any help is welcome.
Pic below is a first build
Issues:
nothing works except touchscreen but it is still broken. It acts like a trackpad.
But it did boot on the first try so thats something.
Click to expand...
Click to collapse
I would really like to help you. And I am also very excited about having ICS running on my nexus one. I'm a java developer. Please let me know if I would be useful building ICS on nexus one?
Thanks.
Update:
Bluetooth is working: I can pair my logitech dinovo keyboard to it and navigate.
Wifi is scanning but not connecting to wpa.
No progress on touchscreen acting like a trackpad. Upside multitouch works.
Did you manage to get GL acceleration working?
Does this help for the touchscreen issue? The touchscreen was working well on the SDK port
http://forum.xda-developers.com/showpost.php?p=18711543&postcount=55
Just use the IDC file from my SDK port.
sunnybhai said:
Does this help for the touchscreen issue? The touchscreen was working well on the SDK port
http://forum.xda-developers.com/showpost.php?p=18711543&postcount=55
Click to expand...
Click to collapse
dr1337 said:
Just use the IDC file from my SDK port.
Click to expand...
Click to collapse
Yup. fixed it.
dr1337 said:
Did you manage to get GL acceleration working?
Click to expand...
Click to collapse
No i havent even looked at that.
nice work
Will we get a test build to play with?
skitty said:
Will we get a test build to play with?
Click to expand...
Click to collapse
Soon. I've been trying to upload one but my internet f-ing blows and it keeps failing. Right now its no better than the sdk port.
Wifi turns on but won't connect.
3g won't stay connected
no audio
Touchscreen works thought
mms works
Great news! I wish I could help somehow. Why don't you collaborate with drew garen? I'm sure he could help you.
Sent from my HTC Flyer P510e using XDA App
this is awesome work , have you tried contacting any of the developers or contributors from TeamDouche ... they may help you to resolve any issues !!
Have you try to contact @drewgaren to ask him which trick did he use to correct the problems he was having with first sdk port?
Maybe he can share some drivers file which can be helpful.
Thanks for all the work you put in this DEV.
F.
Wow! Great initiative guys, good luck and hope move developers can contribute.
amazing work guys
I've since upgraded from an N1 but still use it to play around with builds so if you need testers i'd be more than happy to help!
great work
keep going
Keep Going guys, i wish i can help but i have no idea about developing at all.
Need help?
If you need help on development work, I might be able to help. I am also a Java developer. Thanks and keep up with the good work!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
AOSP+ 0.8 - Android 4.3
AOSP+ is a collaboration ROM from myself and Lloir. Lloir enjoys using pure vanilla AOSP whereas I have always enjoyed the features from CM or AOKP. After trying out AOSP I was impressed with its speed and smoothness and found I actually only missed a few small things from those other ROMs so decided to port over just those features. The result: AOSP+
For all the changes over AOSP, see the second post.
All code that is not built directly from the google repositories can be found on github here https://github.com/AospPlus/
3rd party apps included in the ROM:
Superuser by Koush
LockClock from CM - much as Lloir hates it, i quite like it so it's gone in
Torch from CM
ShareLogs from cornedor - we will provide NO support unless the logs from this app are included with your post!
We welcome suggestions of other things people like from other ROMs that you want included but we want to try and keep all changes as light as possible to stay as close to AOSP as we can. Also, feel free to add your own features and make pull requests to our repos to have them included.
Kernel
Source: https://github.com/AospPlus/android_kernel_htc_enrc2b-BLADE
The boot.img in the ROM is the BLADE kernel. This contains ramdisk changes required for 4.3 so must be flashed.
Downloads
ROM
GAPPS
Installation
Extract boot.img from ROM zip and install from bootloader
Code:
fastboot flash boot boot.img
A factory reset and system wipe is always recommended (use Titanium to backup/restore your apps and data) but may not be required. If you have issues, please try and recreate them after a factory reset/system wipe before reporting them.
Install ROM and GAPPS from recovery
Wipe cache/dalvik
Reboot.
Thanks to...
@Lloir for working with me to get 4.3 working
@maxwen for his BLADE kernel
@corne for his ShareLogs tool
CyanogenMod Team
XDA:DevDB Information
AOSP+ 4.3, a ROM for the HTC One X+
Contributors
tombriden, Lloir
ROM OS Version: 4.3.x Jellybean
Based On: AOSP
Version Information
Status: Testing
Created 2013-09-16
Last Updated 2013-10-28
Everything seems to be working except for...
Known Issues
Camera only at 5MP
MHL
SELinux is disabled
HD videos don't work
Video recording now works but freezes when you press stop
Some issues with calls over BT
Changelog
2013-10-28 - 0.9.0 - Experimental
Updated audio blobs to official enrc2b JB 4.2 blobs!!! (huge thanks to Thömy in the endeavoru forums for this one)
Back to a stock based kernel to work with new audio blobs, all BLADE features are now missing
Removed Advanced Settings menu as none of them are applicable to the current kernel
2013-10-14 - 0.8.9
Updated to AOSP 4.3.1_r1 (JLS36I)
Reverted KSM changes to see if that was the cause of random reboots
2013-09-20 - 0.8.8
Re-added T-Mobile theme engine
Re-added overlay to disable Nfc by default
Fixed bluetooth
Updated sources to AOSP 4.3_r3.1
No more Superuser countdown
2013-09-17 - 0.8.7
Fixed superuser daemon not starting from ramdisk
Enable KSM
Updated AOSP sources to 4.3_r3 (JLS36C)
2013-09-14 - 0.8.6
Fixed double tap home
Synced device tree with cm
2013-09-04 - 0.8.5
All other 4.2.2 libs that can be updated, now have been updated.
Synced up with the CM device repos to make my life easier when working on both
Fix for hardware decoding/encoding video (so HD videos and camcorder work (though now a different issue with recording))
SELinux now on in permissive mode
Fix audioflinger crash on receipt of notifications
2013-08-26 - 0.8.4
Update to android-4.3_r2.2 (JSS15Q)
Updated a whole bunch of blobs from 4.2.2 OTA
2013-08-19 - 0.8.3
Only override the picture-size-values if the string is actually broken (fixes issue with front camera resolutions also being overridden and so causing it to crash)
fix ramdisk issue that cause Torch to FC
2013-08-18 - 0.8.2
Modified camera wrapper to return picture-size-values from previous vendor lib as new one is >256 chars
2013-08-18 - 0.8.1
Back to using BLADE rom; still too early days for mine
Re-added Advanced Settings to control BLADE options
2013-08-17 - 0.8
New kernel based closely on HTC stock
Updated camera proprietary libs from latest HTC 4.2.2 dump
Option to map double-press on home
Existing AOSP+ features rebased on Android 4.3
Volume wake option
Disable safe headset warning
Hardware keys remapping option
Improved display of metadata on lock screen music widget
Green LED at 100% when charging, not 90
Reboot option
Swapped round the Wifi QuickTile press/longpress functionality (ie press to enable/disable, long press to go to settings)
Rearranged of the quick tiles to what I think is a better layout, with radio/network icons grouped together, ending with Airplane mode that disables them all
Integration of SuperUser into Settings
FAQ
Titanium Backup won't restore/backup apks
Open Preferences
Select Backup folder location
Press back until you get back to /
Select /sdcard
Press use current folder
Select 'No' when asked to move backup files
\o/ i suppose i better sort out PaP soon
Am I stupid or what, cause I see the EndeavorUParts.apk in the zip but no Advanced settings in the settings?
Oh yeh, I forgot to exclude it from the build. Normally you'd get to if from Settings but as the ROM doesn't come with BLADE it'd only confuse things to have it there as none of the options would work
Sent from my One X+ using Tapatalk 4
tombriden said:
Oh yeh, I forgot to exclude it from the build. Normally you'd get to if from Settings but as the ROM doesn't come with BLADE it'd only confuse things to have it there as none of the options would work
Sent from my One X+ using Tapatalk 4
Click to expand...
Click to collapse
Does the kernel have S2W support so I can activate it from an app on the market, and also should I flash the blade patched kernel after I flash the rom, cause I flashed it before and ended up with no signal at all, and then flashed the included kernel and everything works?
Ranomez said:
Does the kernel have S2W support so I can activate it from an app on the market, and also should I flash the blade patched kernel after I flash the rom, cause I flashed it before and ended up with no signal at all, and then flashed the included kernel and everything works?
Click to expand...
Click to collapse
No this doesn't have s2w, and i just realised that the script to copy the BLADE modules is in the ramdisk so won't be there once you've repacked it. What you can do though, is download this https://github.com/AospPlus/android.../aosp-plus_4.2.2-r1.1/scripts/01-module-check
then push to init.d while in recovery and make it executable
Code:
adb reboot recovery
adb shell mount /system
adb push 01-module-check /system/etc/init.d/
adb shell chmod 755 /system/etc/init.d/01-module-check
then flash blade and hopefully it'll work
failing that, it might be worth giving an existing blade-42 a try; i know it didn't work on open master (pre 4.3) but i don't think i've tried it on 4.3 itself
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Hi,
I just installed this ROM but I am having no sound
Is there a way to fix it?
Hmm, audio's working here; can you just try reflashing the kernel followed by
Code:
fastboot erase cache
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
In a call I get no sound if I try to switch to speackers, only normal calls working, also Viper4Android doesen't want to install the driver and gives an error asking if I am rooted and having busybox, installed busybox installer from sterycson from the play store and it says just Busybox installed and where it is, no version, Installing fails.....any help, allready reflashed the rom so thats not the problem?
EDIT: also included Camera app can only go to 5MP, and Focal can go to 6
tombriden said:
Hmm, audio's working here; can you just try reflashing the kernel followed by
Code:
fastboot erase cache
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Hi,Yes I just tried but the sound is still not working
ForceField said:
Hi,Yes I just tried but the sound is still not working
Click to expand...
Click to collapse
Ranomez said:
In a call I get no sound if I try to switch to speackers, only normal calls working, also Viper4Android doesen't want to install the driver and gives an error asking if I am rooted and having busybox, installed busybox installer from sterycson from the play store and it says just Busybox installed and where it is, no version, Installing fails.....any help, allready reflashed the rom so thats not the problem?
EDIT: also included Camera app can only go to 5MP, and Focal can go to 6
Click to expand...
Click to collapse
Ok, can you guy's flash this for me please:
It's a 43 build of @maxwens BLADE kernel, compiled inline using his source here (as always, huge thanks to him for his work on it)
Hopefully that'll sort the audio issues and i'll take a look at the Camera next
tombriden said:
Ok, can you guy's flash this for me please: http://downloads.kanger.me/getdownl...lusINTER/aosp-plus/boot-BLADE-43-20130818.img
It's a 43 build of @maxwens BLADE kernel, compiled inline using his source here (as always, huge thanks to him for his work on it)
Hopefully that'll sort the audio issues and i'll take a look at the Camera next
Click to expand...
Click to collapse
I just flashed another ROM.
OK,I will reflash AOSP+ and the new kernel and report back
---------- Post added at 09:58 AM ---------- Previous post was at 09:44 AM ----------
Ok,I Reflashed ASOP+ with the new kernel
Sound is Working but Wifi is broken
ForceField said:
I just flashed another ROM.
OK,I will reflash AOSP+ and the new kernel and report back
---------- Post added at 09:58 AM ---------- Previous post was at 09:44 AM ----------
Ok,I Reflashed ASOP+ with the new kernel
Sound is Working but Wifi is broken
Click to expand...
Click to collapse
Ok, i kind of expected that but now i know the audio is fixed i can do a new build. Thanks for testing
if you want wifi back you can do: adb shell su -c 'insmod /lib/modules/bcmdhd.ko'
tombriden said:
Ok, i kind of expected that but now i know the audio is fixed i can do a new build. Thanks for testing
if you want wifi back you can do: adb shell su -c 'insmod /lib/modules/bcmdhd.ko'
Click to expand...
Click to collapse
Ok thanks I will try this command. Really liked the speed of this ROM.It's a Porsche compared to others
0.8.1 uploaded with built-in BLADE kernel and EndeavoruParts accessible from Settings -> Advanced
Camera still at 5MP though :/
tombriden said:
0.8.1 uploaded with built-in BLADE kernel and EndeavoruParts accessible from Settings -> Advanced
Camera still at 5MP though :/
Click to expand...
Click to collapse
Perhaps using an other camer app would let us use the 8MP, because Focal lets us use 6MP?
Anyway your rom is great, close to perfection for me, the only thing missing would be any kind of lockscreen shortcuts but that's only me and I wanna say your rom is great.
Ranomez said:
Perhaps using an other camer app would let us use the 8MP, because Focal lets us use 6MP?
Anyway your rom is great, close to perfection for me, the only thing missing would be any kind of lockscreen shortcuts but that's only me and I wanna say your rom is great.
Click to expand...
Click to collapse
Thanks
Other camera apps will have the same issue. It's down to the new camera libraries from the 4.2.2 dump returning a 302character string for the supported picture sizes but they get read into a 256 string buffer thus cutting off all the higher resolutions :\
I've put a fix into our camera wrapper so it just returns the same supported resolutions as the previous library did. It's uploaded in a new ROM, 0.8.2 but the only file changed is camera.tegra.so so if you don't want to reflash, extract it from system/lib/hw and push in recovery with
Code:
adb shell mount /system/
adb push camera.tegra.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/camera.tegra.so
tombriden said:
Thanks
Other camera apps will have the same issue. It's down to the new camera libraries from the 4.2.2 dump returning a 302character string for the supported picture sizes but they get read into a 256 string buffer thus cutting off all the higher resolutions :\
I've put a fix into our camera wrapper so it just returns the same supported resolutions as the previous library did. It's uploaded in a new ROM, 0.8.2 but the only file changed is camera.tegra.so so if you don't want to reflash, extract it from system/lib/hw and push in recovery with
Code:
adb shell mount /system/
adb push camera.tegra.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/camera.tegra.so
Click to expand...
Click to collapse
Thank you, and thanks god I don't need to reflash, cause I started flashing 8.1 at my previows comment and just finished seting up all my things (xposed, touchwiz, playstation certs, viper4android and some others) and really don't want to flash again, lol.
Announcing Sailfish for the Sony Xperia SP
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Update 15 Feb 2016
I've uploaded a new version of SailfishOS 2.0.0.10 to the Mega folder, called sailfishos-huashan-release-2.0.0.10-1.zip. This is again based off CM-12.1, the same release as stated below. This release fixes a kernel bug which lets a lot of the Sailfish system crash. This also fixes the wlan connectivity, startup-wizard which sets the themes, on-screen keyboard not popping up, and SIM unlock never asked. I've got a fix for the backlight in the works.
Update 14 Feb 2016
A very experimental CM-12.1 based SailfishOS 2.0.0.10 build is uploaded to the Mega folder linked below.
This version is based off cm-12.1-20160212-NIGHTLY-huashan.zip. I want to stress that many things in this build are broken.
Update 05 Feb 2016
This port is heavily outdated. I do not have much spare time on my hands to continue porting but I will try to post a nightly version soon.
This version was based on Sailfish 1.1.6 and CM-11.0, but the world has moved on to Sailfish 2.0 and CM-12.1, and so must this port.
There's a photo up on imgur:
http://i.imgur.com/Vg3SZ6w.jpg
Special thanks to:
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Everyone from the SailfishOS team/community, sledges and mal- in particular.
Known issues:
Half the backlight doesnt work, this is clearly visible at the top of the screen
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Settings hangs for few seconds on first start (this seems to be related to bluetooth not being set up)
What works:
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi, GPS (does take a while to get a fix though), most of the sensors (proximity, lightsensor etc)
The half of the display backlight that does work is adjusted based on lightsensor input.
Charging, bottom ledbar basic functionality, audio works, audio via 3'5 jack also works.
Installation:
Insert default warranty void message here. Your warranty is now void
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an offical Sailfish OS build, and the Xperia SP is not the Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, search for it first on bit.ly/port-bugs, if your bug is not yet there, you can add it there or post it in this thread (I'll try to keep the xda thread and bugzilla in sync).
The Sailfish OS image does not provide recovery, and since the Xperia SP does not have a recovery partition, you need a seperate bootimage with only recovery on it to flash cm/stock/sailfishos upgrade.
The Sailfish OS image is based on a specific version of Cyanogenmod 11, which you will need to flash first.
You can find all the required files in a Mega folder: http://mega.nz/#F!7YhSTDIA!Akpjs8s3qT5_nEkN04fQ-Q
You can find a bootimage with only TWRP recovery in it called recoveryboot.img
This image can be flashed with fastboot (with phone turned off, hold vol up and plug in usb), then `fastboot flash boot recoveryboot.img`. After that reboot the phone (fastboot reboot), and it will boot into recovery. If you already have recovery from cm, then you can use that as well.
First do a full wipe (make a backup first if needed, TWRP can do this , then install CM11, the specific version you need is called: cm-11-20150712-NIGHTLY-huashan.zip
There is no need to reboot cause you wont use CM11 anyway, so just proceed and flash the Sailfish OS image, which is called: sailfishos-huashan-release-1.1.6.27-UNOFFICIAL-maikel-201508201214.zip
Flashing Sailfish OS is not as fast as flashing cm11, but it shouldn't take more than 10 minutes.
Then reboot. The first boot may take some time, during which the Sony logo is not displayed (WIP).
If the boot takes more than, lets say five minutes, try a reboot. You can power off the device by holding the power button until the LED bar turns red or the display brightness goes back to full, when the leds and display turn off the device is powered off.
If this doesn't work you can remove the back cover and press the little button in the little hole for 5 seconds, the device will vibrate thrice and the phone will be forced off.
If you want to return to your previous rom or restore a backup, use the recoveryboot.img using the commands stated at the top of this document, to boot into TWRP.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Sources
In order to comply with the GPL, the kernel sources used for this port are available here:
CM-11.0 based port: https://github.com/maikelwever/android_kernel_sony_msm8x60
CM-12.1 based port: https://github.com/maikelwever/android_kernel_sony_msm8960t
edit: make links + sailfish 2.0 notice, kernel sources, 2.0 link
You rock! Very interesting project. Sailfish is an unknown world for me (and for most of us I think), I might try this ROM out sooner or later.
Why do we need to install CM11 first? Is it based on it?
Goob job bro!!!!
But I'll try this port later since it's kinda buggy
Hope you will fix those bugs.
Tomoms said:
Why do we need to install CM11 first? Is it based on it?
Click to expand...
Click to collapse
SailfishOS uses libhybris to communicate with the hardware, which in turn is talking to the Android HAL (like hwcomposer), to avoid having to write drivers for each phone, which would be pretty much impossible due to the proprietary blobs used on almost every phone.
The libhybris build included in this SailfishOS port is based on CM11, so that's why you need that.
CM12 based SailfishOS is currently experimental, when that gets more stable I will try to make a CM12 based build.
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
boylush said:
I tried the earliest version that was available on your git earlier this month, working great, just that it gets frustrating when Settings try to crash when you just opened and i just can't seem to install openrepos Warehouse from the command line...
Click to expand...
Click to collapse
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
maikoool said:
Installing packages from command line was fixed in the version linked in this thread. This had to do with some repositories that were unavailable (cause they pointed to local disk of buildmachine), causing zypper to hang on updating.
Those packages have been moved to the community buildserver, which hosts the packages online, thus fixing the hang you experienced while trying to install openrepos. If you still experience problems with the latest build: try a 'zypper rr adaptation0' before installing an app. If it complains about missing libsailfishapp, do a 'zypper ref' and try installing again.
Ninja edit: I'm considering bundling the openrepos warehouse with the zip, since I use it a lot myself as well, and we are in the process of enabling the official Jolla store (without Android support though), which should smooth out installing apps as well.
Click to expand...
Click to collapse
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Tomoms said:
OMG Sailfish uses zypper? I must try this thing ASAP!
Can we install Android apps in it somehow?
Click to expand...
Click to collapse
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
maikoool said:
Yes Sailfish uses zypper, and also has pkcon (from PackageKit) available as a frontend. Sailfish is based on Mer, which is it's own Linux distro, so don't expect the huge amount of packages that are available on desktop Linux systems that use zypper. Multiple community members provide repositories with builds of common unix tools that are not bundled by default (openrepos) though. As far as I know, Mer is closest to OpenSUSE with the package guidelines (I'm no expert on this though).
Android apps are supported on the official Jolla hardware using AlienDalvik. AlienDalvik is proprietary and not gratis software and thus not available for community ports like this one. I just added a link to a XDA thread with a Sailfish user FAQ to the startpost, which goes into this subject in more detail and provides anwers to other common questions.
There are multiple community projects going on to provide support for running Android apps, which I'll look into when all the Sailfish native stuff works properly.
There's apkenv, which is a very basic way to run some Android games on Sailfish ports.
There's some way to run full Android in a chroot and pipe the UI to a Sailfish app window.
And then there's shashlick, from the KDE team, which tries to map Android UI to QT.
I have not tested any of these three (yet), and there may be more options than this available.
Click to expand...
Click to collapse
man i was waiting for this thing :fingers-crossed:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
will follow this thread closely...........
finally something new and different to use.
cheers
avi.singh9993 said:
will follow this thread closely...........
finally something new and different to use.
cheers
Click to expand...
Click to collapse
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
This looks really good, if it will ever be in daily driver state this will be my go to rom
sledges said:
And now the Jolla Store should be enabled! \o/ Please try it out and tell us
Click to expand...
Click to collapse
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Why don't you post please? DIT - doing it together!
sledges said:
Why don't you post please? DIT - doing it together!
Click to expand...
Click to collapse
well i asked my friend to post it,
many people saw it but unfortunately not much of a positive feedback.
now it's onto developer and his hardwork to develop and make it atleast daily driver. then some people will be interested in trying it
Tomoms said:
A small review of this OS:
The flashing process isn't very short, but in my case the OS booted in less than 30 seconds
There are only 10 - 12 installed apps: Settings, Contacts, Camera, Telephone etc.
The terminal emulator is fully-featured but it has got a bug: the screen orentation is the opposite of the real one (when the phone is horizontal, the terminal is vertical and vice versa). But as I've just said, it happens only in terminal.
WiFi doesn't seem to be working, but SIM card signal works (2G and 3G - no LTE); mobile data - I don't know.
The GUI is shiny and transparent and the whole OS is based on gestures. There's a little tutorial after the first boot thats help you understand how to use the phone fastly. I didn't open the Jolla store as I couldn't use mobile data at that moment.
During my 10-minute-long test, the screen randomly locked by itself; there is another bug: when the screen is locked, backlight doesn't turn off unfortunately.
A strange thing of Sailfish is that the app you're using is always fullscreen, there's no notification/status bar at all. The navbar also doesn't exist, as you can go back and to homescreen with gestures.
The developer mode is also interesting, it lets you connect to your phone remotely over the network.
Basically, this port of Sailfish at the moment is a very early alpha, but it's the dream of the geek: a full Linux experience with command-line package manager etc. I hope to see improvements in the future
Click to expand...
Click to collapse
I agree totally that it's the dream of a geek. I've noted all your comments and will try to fix them. Thank you very much for taking the time to test!
Spasik said:
This looks really good, if it will ever be in daily driver state this will be my go to rom
Click to expand...
Click to collapse
That's what I'm aiming for too!
avi.singh9993 said:
yeah i would love to try, but i need my phone as a daily driver many important work related.
why don't you all post on official facebook page, i'm sure 90 percent people do not know about this and are willing to try and submit bug reports which in turn helps in faster development of this project.
Click to expand...
Click to collapse
Sorry, but I couldn't care less about Facebook. I'm pretty convinced that everyone that is willing to try something like this is already on XDA anyway. Hopefully the work related part will be better possible when Android app emulation or something similar finally makes it to community Sailfish builds.
PS: I've been a bit busy with other things lately, sorry for not responding that fast. I'll try to roll a build with fixes and the latest Sailfish (1.1.7.28) asap.
This has changed the mac of my device
can I ask how's the development going?
If someone could port the only rom i would like to be ported on the SP: ColourOS, it will be AMaZING
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Download Links
Androidfilehost:
Download: https://www.androidfilehost.com/?fid=24391638059057759
Google Apps Minimal Edition:
Download: http://forum.xda-developers.com/android/software/gapps-google-apps-minimal-edition-t2943330
Installation
1.) You must have twrp installed follow this guide here
2.) Download the ROM and Gapps and place them on internal or external storage (depending on your model you may only have internal storage)
3.) In TWRP navigate to "Wipe" and wipe cache, data, and dalvik
4.) In TWRP navigate to "Install" find the location of the downloaded zips and proceed with installation
5.) Once both ROM and Gapps have been successfully flashed reboot system and wait for the device to boot
XDA:DevDB Information
CyanogenMod 12.1 for Alcatel ONETOUCH IDOL 3 5.5, ROM for the Alcatel Onetouch Idol 3
Contributors
Unjustified Dev
Source Code: http://github.com/TeamRegular
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2015-10-14
Last Updated 2016-01-28
Status
Working:
Radio (Includes Dual Sim, Data and SMS)
Sound
Camera
BT
Sensors
Wifi
Known Issues:
Please share your bug reports (include a log if possible)
Tap to wake (Works, but disables itself randomly)
Horrendous battery drain
Changelog
20160218
remove unneeded qcom usb script
disable boot freq limit for cluster
20160216
Updated prima driver to LA.BR.1.1.3_rb1.45
Updated kernel to LA.BR.1.1.3_rb1.45
add back various alcatel kernel changes
set usb properties on boot (Fix the usb product model defaulting to Android)
set variant from init and add support for I806 (pivoq)
selinux enforcing (wcnss fixes by pivoq)
add peripheral manager
wcnss: restore stock config
20160128
update storage configuration (fix internal storage access)
don't set tct properties
set taptowake control state to 2
remove window cover support (revisit later)
remove unused zram script
remove tct cmdline garbage
remove unused hdcpService
remove power engine
remove powerup reason
remove unused Tct Daemon
disable secure discard
remove camera wrapper
use half res bootanimation
update WCNSS cfg from firmware bin
Stop the QC-QMI message spam
switch to init.qcom.power and update devfreqs
add script to identify device variants
switch to new cm-12.1 kernel
update adreno blobs
FAQs
Q: Is the device fully reversible on CyanogenMod as well?
A: Unfortunately no, it does allow all rotations but the dialer app currently will not allow you to place calls upside down.
Q: Does Dual Sim work with this ROM?
A: Dual Sim devices are now supported
Q: Why is my device 6045X?
A: The script failed to identify your device the supported model are 6045I, 6045B, 6045K, and 6045Y
Q: How can I get my device supported?
A: Post the model number and stock build.prop
Q: Is the Aero flipcase supported on CyanogenMod?
A:At the current moment it is not supported
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
salzy said:
Good News! Any plans for supporting 4.7 version aswell?
Is your device tree based on a similar device like yu tomato oder something, could you give me some hints for setting it up?
Click to expand...
Click to collapse
No plans at the moment. There's is already someone handling 4.7 variants. Check out the CM port thread for details.
w00t!!!!!
Sent from my 6045I using Tapatalk
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
So close but yet so far.. I was so hyped when saw the thread but got down to earth quickly.. Stay focused my man, you're about to make something that's good into the great..
Just wondering if cm have some incompatibles with root apps like greenify, Viper 4 Android? Thank you
Sent from hell
Did you get the kernel to boot building from source or are you still repacking with stock?
Sent from my 6045I using XDA Premium HD app
brian117 said:
Like a kid on Christmas Eve. Waiting for what's to come. Can't wait to see future progress on this. I would give this a shot but WiFi and MMS are like my main two necessities. Thanks to all of those involved on this port for making this happen.
Click to expand...
Click to collapse
It's close. Just seeing how fast @Unjustified Dev has progressed to this point has been impressive.
Great Great Great my idol trembles park in the pits ready to receive new engine.
make sure everyone to get the minimal gapps as 5.1 before download
Whoohoo! so excited haha.
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:deleted
masterdex said:
One wonders why use those minimal gapps rather dated instead of gapps latest? On motog 2014 Cyan 12.1 latest release give FC using ones you reported.
While Cyanogen recommends these:http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Click to expand...
Click to collapse
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Unjustified Dev said:
They worked fine for the testers. I'm sure those gapps would cause issues because they aren't 64 bit compatible.
Click to expand...
Click to collapse
Then I immediately delete the link to avoid problems.
My ADB is ready.
will it be regular flash or aroma installer?
masterdex said:
Then I immediately delete the link to avoid problems.
My ADB is ready.
Click to expand...
Click to collapse
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Unjustified Dev said:
CyanogenMod
https://www.androidfilehost.com/?fid=24052804347837558
Bootimg with adb enabled
https://www.androidfilehost.com/?fid=24052804347837588
Flash cm then the boot.img can be done from twrp or fastboot.
To keep it from crashing we need to remove the wlan module
adb remount
adb shell rm -rf /system/lib/modules/wlan.ko
technically you could do that from twrp without ever flashing the boot.img by mounting system after installing cm and using the included twrp file manager
Click to expand...
Click to collapse
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
masterdex said:
Ok I'm downloading.
Then install cm after bootloader and still gapps and after I disable the WiFi with ADB or leave everything as it is?
Click to expand...
Click to collapse
You can flash gapps before and the boot.img isn't needed flash cm and gapps. Once they are done mount system and use the file manager to remove wlan module and that's it reboot and everything should be fine.
Mod edit: Thread closed on owner's request.
exNoShadez-EAS Kernel
Hey Pixel XL forum. I'm a Pixel/Sailfish owner, who also enjoys hacking on kernel code. I recently released a Kernel in the Google Pixel forum => but we are all using the same kernel, sooo.... I thought after pushing my second stable release, that I should probably post on the XL forum too.
My kernel is a bit different than most kernels available, you will quickly notice. Lots of interesting features and some unique ones too.
FEATURES
- Current LTS release -> Linux-3.18.114
- Energy Aware Scheduling
- Schedutil (default Cpu Governor)
- RCU infrastructure backport (with expert mode enabled)
- Cpu-Boost / Input Boosting (enabled by default)
- BINFMT_MISC support (NOT mounted on boot).
- Kernel Hardening/Protection (CopperheadOS/Grsec/Pax Marlin kernel hardening features)
- leds-qpnp: Notification LED control - V1.1c (Boeffla) - Adapted for Marlin
- Binder_rt = My own re-implementation of AOSP Binder that uses rt_mutexes; supporting priority inheritance
- Improved scheduling/determinism for high priority threads/tasks
- Backported Scheduling, Locking and Workqueue subsystem code from Newer Linux kernels.
- Audio Driver enhancements / backports (from Wahoo/Pixel 2)
- Sound/Audio driver Tweaks (bug fixes, scheduling improvements)
- forced Interrupt threading enabled
- Wifi Mac Address Randomization
- WireGuard (VPN) kernel module support
- KCal Advanced Colour control
- Improved ASLR (in kernel)
- USB Fast Charge
- Wake Gestures
- GCC 6/7+ Fixes
- Built with GCC-8.x-dev
- and more
Contains code from everywhere: Code Aurora, Flar2/Marlin, CopperheadOS, AOSP, Project-EAS, Freak7/Kirisakura, Linaro, Pixel 2 kernel sources, mainline linux and elsewhere. Modifications and backports by me, as well.
BACKGROUND
I wanted a kernel for My Pixel that had 'all of the things', it didn't exist... So I'm working on my own kernel. I try to balance Security/hardening, experimental features with high Performance and battery life. <- not an easy task! ... Some of the security features do come with overhead, but if you use apps that are CPU heavy / processing and/or require low latency - they will perform well (at the cost of chewing some battery life, of course).... Battery life and SOT are very reasonable though.
WARNING / VERY IMPORTANT: This kernel isn't compatible with installing TWRP ~> meaning; you must use the fastboot version of TWRP (used in RAM) , flash the kernel and NOT install TWRP to your system (the kernel is too big for TWRP to co-exist).... This may sound inconvenient, but there are a number of valid reasons to avoid reducing a kernel's size in order to support TWRP installation, in the boot partition.
***Fun facts on not supporting TWRP below => 2nd post: PLEASE READ: to understand my motivation***
TWRP REMOVAL
*To remove TWRP from your system; You need the stock boot.img from your running/current firmware (which is inside of the factory image zips) or use the Nov Stock boot.img provided here. Then it's as simple as flashing the boot.img to wipe TWRP;
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Stock 8.1 July 2018 Boot.img => https://github.com/nine7nine/Apps/raw/master/MarlinStockJulyBoot.img
Now you can proceed with using the TWRP fastboot boot.img to flash my kernel, magisk/supersu or whatever else....
Fastboot twrp boot image => https://dl.twrp.me/marlin/twrp-3.2.2-0-marlin.img
WARNING: This shouldn't need to be said, but we did have someone on the Pixel forum who did this, so I'm adding a sticky/warning here; do NOT EVER re-lock your bootloader after flashing any kind of custom software, kernels, etc to your device - *it will brick your phone*. Meaning you are screwed would need an RMA / replacement device ... everyone in the XDA community should know better, but still; worth mentioning....
IMPORTANT:
Before asking questions; Please read through the thread (starting with the last few pages) - I shouldn't need to be repeatedly answering the same questions over and over again. It's good practice to get into the habit of reading through threads before asking questions in any thread on XDA, as more often then not; you're question has probably been answered. Thanks!
EXNS-EAS KERNEL DOWNLOAD:
JULY 2018 OREO 8.1 RELEASE exNoShades-eas Kernel Flashable zip
https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.2_f94351f.zip
It is stable, high performance and very responsive...
Important: You will need root; I don't support non-rooted devices && some features require it. I recommend using Magisk; https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 ...
NOTE: Make sure to flash the latest Magisk beta *before* flashing the kernel zip ...
More Background / Important Notes:
Binder_RT:
My own port and re-implementation of the Binder Kernel Driver; a slightly modified version of The AOSP binder.
Binder_RT uses rt_mutexes as oppsed to mutexes for locking in Binder, ion, ashmem, etc... rt_mutexes support priority inheritance and should improve determinism in Binder, speed up IPC, Ion and Ashmem => Allowing applications that require low-latency, tight deadlines, low jitter and deterministic behaviour to perform better ~ This re-implementation is proving to be the great for those types of applications. The goal here is to help ensure that the Kernel and Binder's high priority && time critical threads and tasks are properly prioritized... Example; audio buffers arriving on time / no buffer underruns... *Further development work is planned to research, experiment with and improve Binder_RT.
rt_mutex documentation, for those interested;
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex.txt
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex-design.txt
CPU-Boost / Input Boosting:
Touch inputs boost CPU frequencies (thus improves performance and responsiveness).
# Cpu-boot / Input boost settings
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:1363200 1:0 2:1900800 3:0"
write /sys/module/cpu_boost/parameters/input_boost_ms 100
IO/ CPU Governors:
This kernel doesn't include a thousand io/cpu governors. IO-wise; CFQ is the default, but we've got a few in there. chose your poison, but know that the majority of my testing is centered around cfq and deadline. CPU Governor-wise the common Linux CPU governors are there; along with Sched and Schedutil....
Stick with Schedutil - on idle, it draws very little power and in most 'peak performance situations, it should do very well..... I'm getting great battery life, sot and performance.
Managing Kernel Settings:
Get EX Kernel Manager - my original code on github was forked from EX kernel, before rebasing it - but EXKM will give you access to 99% of my kernel's settings.
My 8.1 Kernel Sources: https://github.com/nine7nine/Marlin_exns-eas
Donations via PayPal very much appreciated. I do put a significant amount of energy and time into researching, development, testing / QA and also providing support/help to end-users... It's definitely not mandatory to donate; but If you appreciate the effort, see value or benefits from using my kernel on your device and can afford to; Use the "Donate to me" button or the below link... It makes a big difference. thanks!
https://www.paypal.me/jrdnjhnstn
Why TWRP Installations are NOT supported:
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
(and why I'm not using it!)
Most custom/android kernel devs are using the above configuration in kernel compilation, which is arguably very BAD... I understand that boot partitions are small and the desire to install TWRP to them, thus there is a need to reduce the kernel's size....and yes, this will achieve that - However;
1. SUSE, RedHat, etc (Enterprise linux) disable CONFIG_CC_OPTIMIZE_FOR_SIZE -> it's original use case has proven to be invalid. Even Google (in their own documentation) advise against using this; https://source.android.com/devices/tech/perf/boot-times ....
2. It suppresses useful compiler warnings....
3. As SOCs have become more powerful, google has come to the same conclusion that Enterprise Linux did back in 2012.
4. by turning off CONFIG_CC_OPTIMIZE_FOR_SIZE, we achieve better performance, boot time and better cache utilization.
Clark Williams / Redhat Bugzilla said:
* Cause: CONFIG_CC_OPTIMIZE_FOR_SIZE set with assumption that smaller code would yield hot cache lines and good performance
* Consequence: this config caused gcc to generate jump-to-jump code which causes cache line bouncing, hurting performance
* Fix: turn off CONFIG_CC_OPTIMIZE_FOR_SIZE
* Result:slightly larger kernel but better cache utilization
Click to expand...
Click to collapse
(The Above is quoted from Clark Williams, A Senior Software Architect @ RedHat -> https://bugzilla.redhat.com/show_bug.cgi?id=796297)
I know of no other way to significantly reduce kernel size. Disabling some debugging, unneeded features, etc helps - but not enough.... I am focusing on optimization, using newer builds of GCC/Linaro, performance enhancements, fixing compilation errors, etc, etc -> these things are more important than trying to support TWRP installation.
Therefore; I do NOT support installing TWRP....
This sounds incredible. All those features.. and then some. Hard for me to test as I rarely use my PC but I may have to go and give this a try.
Edit: would it be possible to create a build for those who do want to use TWRP? Would be great to do some benchmarks (real work using DiscoMark and synthetic using geekbench/AnTuTu/etc) to see differences between the two.
All those features are welcome in this poor Oreo pixel community! thanks for your work..
i'll try it as soon as possible!
spr33 said:
This sounds incredible. All those features.. and then some. Hard for me to test as I rarely use my PC but I may have to go and give this a try.
Edit: would it be possible to create a build for those who do want to use TWRP? Would be great to do some benchmarks (real work using DiscoMark and synthetic using geekbench/AnTuTu/etc) to see differences between the two.
Click to expand...
Click to collapse
No. like I said. I don't/won't support installing twrp. it would require reverting a bunch of patches/ work that I've already put in... and also not using linaro GCC 7.2.1 compiler, either...
the time invested would be a complete waste for me and I would have maintain another separate branch. test another build, etc, etc'... i'm not doing it. my current goal is to reduce my branches into one single branch/build;. ... which will end up hopefully being binder_rt... not create more.
feature wise, pretty much a 'best of' what any other custom kernel offers for Marlin, all of the hardening stuff (I think I'm the only Marlin kernel on XDA with that), etc... afaict, I'm the only one rolling in EASv1.4, cpu-boost, dynamic stune boost; all of which I've ported myself... some of the audio driver stuff I personally ported (more coming) and binder_rt is my baby; I ported aosp binder and researched / Inplemented all of the changes to Binder...
in my yet-to-be-released binder builds I also have backported a large chunk of the linux locking, workqueues and scheduling code and some other bits from newer mainline linux kernels (which allow me to pull in some new features and use them).
so I'd rather work on this kind of stuff, over caring about twrp, doubling my workload to support running synthetic benchmarks between gcc's -Os vs. -O2 optimization levels...
Thanks for the new kernel. Sounds very interesting. Can't try it atm because i am on dp1 from 8.1. Hope you gonna also support 8.1 when official sources are out. For me battery life is already great on dp1.
housepabldroid said:
All those features are welcome in this poor Oreo pixel community! thanks for your work..
i'll try it as soon as possible!
Click to expand...
Click to collapse
haha. pixel community isn't too bad. there's just not a lot of custom oreo ROMs.... myself, I wouldn't want to run any of those custom roms anyway. they usually are built without odexing or proper signiture key signing = less secure and way less optimized... Stock ROM is great, just needs root and a few apps to modify / customize it a bit.
for me, the kernel has always been the issue. lol... therefore, roll my own. lol....
ya, for sure give it a try... I honestly would say binder_rt is the best build... the 'stable build' is a bit of a misnomer - all of the builds are stable, just the binder ones are running more experimental code... binder_rt blows the socks off any other Marlin kernel for certain kinds of workloads... I'm aiming fir it to become my default build...
Donric13 said:
Thanks for the new kernel. Sounds very interesting. Can't try it atm because i am on dp1 from 8.1. Hope you gonna also support 8.1 when official sources are out. For me battery life is already great on dp1.
Click to expand...
Click to collapse
yup. I have to wait until kernel sources are released. you got it!. but when they are / 8.1 is released; I will be upgrading to 8.1, so no worries - there will be an 8.1 version...
I've heard heard that battery life is pretty good on 8.1, there's a thread in the pixel forum about it... but by what they were saying, it didn't seem that much better than what I see from my kernel.....
I'm more interested to see what performance improvements are in 8.1 kernel sources... I've found stock kernel to be a bit crappy for some stuff...
well, if at some point you are bored and want to test my kernel on 8.1, go for it. ya never know: maybe it will work. the reason I say that?
IIRC - it was tested with my old kernel / sources build... could've been a bug, not present in the new one.... or something else. IdK.. being as I'm on 8.0 I can't even look into why that might be or have been...
just make sure if u do ever try it, keep the stock boot.IMG for 8.1 around, in case it doesn't work..... and report back, if it does work. lol
Gotta say super smooth. Thanks for sharing. Maybe it's just a glitch in ex kernel manager but zram "stopping..." Or nothing to worry about.
JS.zip said:
Gotta say super smooth. Thanks for sharing. Maybe it's just a glitch in ex kernel manager but zram "stopping..." Or nothing to worry about.
Click to expand...
Click to collapse
Ah yes, I should've mentioned that ~ zram is working fine - but EXKM is being denied permission to read those files on the file system - I think it's due to a change in cgroups code (from merging in EASv1.4), but I haven't gotten to the bottom of it yet....
No worries though ~ I HAVE completely verified that zram is working, mounted swapon and behaving as it should... Honestly, the defaults for zram are fine ~ if they ever weren't; you would have bigger problems on your hands, that changing swapping wouldn't help. lol
Which build are you using? (just curious)
nine7nine said:
Ah yes, I should've mentioned that ~ zram is working fine - but EXKM is being denied permission to read those files on the file system - I think it's due to a change in cgroups code (from merging in EASv1.4), but I haven't gotten to the bottom of it yet....
No worries though ~ I HAVE completely verified that zram is working, mounted swapon and behaving as it should... Honestly, the defaults for zram are fine ~ if they ever weren't; you would have bigger problems on your hands, that changing swapping wouldn't help. lol
Which build are you using? (just curious)
Click to expand...
Click to collapse
Thanks that's what I thought. The bad boy "Binder RT" lol
JS.zip said:
Thanks that's what I thought. The bad boy "Binder RT" lol
Click to expand...
Click to collapse
bad boy eh? haha.
Ya, no worries - I check that sort of stuff, when it crops in... fixing that particular issue just hasn't been a huge priority, over other stuff that I'm working on. (and because I think it's pointless that EXKM even displays it to begin with - it just gives users the false impression that they are tweaking something, that in 99.99999% of cases - is absolutely pointless to touch).
Anyhoo, cool - let me know how things are working out with the binder_rt build, as you get some more use in ~ I really want it to become my main focus / implementation. (I personally won't be going back to using any other build day to day, anyway.)
nine7nine said:
bad boy eh? haha.
Ya, no worries - I check that sort of stuff, when it crops in... fixing that particular issue just hasn't been a huge priority, over other stuff that I'm working on. (and because I think it's pointless that EXKM even displays it to begin with - it just gives users the false impression that they are tweaking something, that in 99.99999% of cases - is absolutely pointless to touch).
Anyhoo, cool - let me know how things are working out with the binder_rt build, as you get some more use in ~ I really want it to become my main focus / implementation. (I personally won't be going back to using any other build day to day, anyway.)
Click to expand...
Click to collapse
I just wanted to point out that I grabbed your stock kernel from the OP and had planned to use that to flash my stock image. However, I happened to have the latest boot.img release decompressed on my drive so I compared it to the one I had on hand.
MD5 for your Stock Image: 7A2D92981FDE96E5D60D806019ACFA0C
MD5 for Google's Stock Image: BF9EDA2888C8C6A1FCD0A7DB6E37F739 (Latest November build)
Now I don't want to sound like the suspicious type, because in reality the stock kernel you provided is just to get TWRP off the device before flashing your kernel, but I'm forced to ask why your stock image is not identical with the main stock image? Unless your stock kernel isn't from the latest release but instead from a prior month or something of that nature (It would take me quite awhile to download the other month's releases just to check so I was hoping to ask you instead)
AlkaliV2 said:
I just wanted to point out that I grabbed your stock kernel from the OP and had planned to use that to flash my stock image. However, I happened to have the latest boot.img release decompressed on my drive so I compared it to the one I had on hand.
MD5 for your Stock Image: 7A2D92981FDE96E5D60D806019ACFA0C
MD5 for Google's Stock Image: BF9EDA2888C8C6A1FCD0A7DB6E37F739 (Latest November build)
Now I don't want to sound like the suspicious type, because in reality the stock kernel you provided is just to get TWRP off the device before flashing your kernel, but I'm forced to ask why your stock image is not identical with the main stock image? Unless your stock kernel isn't from the latest release but instead from a prior month or something of that nature (It would take me quite awhile to download the other month's releases just to check so I was hoping to ask you instead)
Click to expand...
Click to collapse
Easy explanation - I'm on Sailfish, you aren't; so the md5 wouldn't match...
I can do one of two things; you can post a upload/link to your boot.img and I will replace the link for Marlin's nov boot.img (adding it to my github) OR I will remove the link from the post and Marlin users will have to fend for themselves. (have to download 1.8GB firmware themselves for a boot.img... Obviously i'm NOT downloading your guys Nov Firmware images).
nothing suspicious at all here, dude.
EDIT: I've removed the link to the sailfish Nov boot.img, as a sign of good faith; I can replace it with the Marlin Nov boot.img - but that will require you to post a download/link to me, so I can add it in. thx
nine7nine said:
Easy explanation - I'm on Sailfish, you aren't; so the md5 wouldn't match...
I can do one of two things; you can post a upload/link to your boot.img and I will replace the link for Marlin's nov boot.img (adding it to my github) OR I will remove the link from the post and Marlin users will have to fend for themselves. (have to download 1.8GB firmware themselves for a boot.img... Obviously i'm NOT downloading your guys Nov Firmware images).
nothing suspicious at all here, dude.
EDIT: I've removed the link to the sailfish Nov boot.img, as a sign of good faith; I can replace it with the Marlin Nov boot.img - but that will require you to post a downlink to me, so I can add it in. thx
Click to expand...
Click to collapse
No problem, I download every Marlin release so I'll just update my AFH folder to include the monthly kernel release and users can download it from there. You can either link to my folder or download from it to add to your repository; either one is fine with me Thanks, and I do appreciate what you're doing but I have a 'verify first' stance since these devices are a big part of people's lives. I'm going to give your kernel a spin now, I appreciate you getting back to me so quickly. If only AFH was this fast, I just spent 25 minutes trying to get it to create an empty folder...
Link to Marlin Stock Images: https://www.androidfilehost.com/?w=files&flid=231142
Edit: I attempted to flash the "exNoShadez_eas-3.18.83_Binder_b0b66e0.zip" from the fastboot installed version of TWRP after flashing the stock boot to slot_a and slot_b, but it is failing with an error that states, "New image larger than boot partition. Aborting..." Then updater process Error 1. Any idea what would cause that?
AlkaliV2 said:
Edit: I attempted to flash the "exNoShadez_eas-3.18.83_Binder_b0b66e0.zip" from the fastboot installed version of TWRP after flashing the stock boot to slot_a and slot_b, but it is failing with an error that states, "New image larger than boot partition. Aborting..." Then updater process Error 1. Any idea what would cause that?
Click to expand...
Click to collapse
Hey, I added your nov boot.img to the OP. put it on github to save a few clicks for people.
The error you are seeing would suggest that TWRP is installed to the system. That is the only time anyone has ever bumped into that message. So, I'm not sure what's going on with your end but it would seem you have twrp actually installed...?!
the TWRP that you are supposed to use, is this one;
https://dl.twrp.me/marlin/twrp-3.1.1-1-fastboot-marlin.img
that loads and runs from RAM. twrp can't be "installed from fastboot" ~ it installs to the boot partition; leaving not enough room for the kernel.
nine7nine said:
Hey, I added your nov boot.img to the OP. put it on github to save a few clicks for people.
The error you are seeing would suggest that TWRP is installed to the system. That is the only time anyone has ever bumped into that message. So, I'm not sure what's going on with your end but it would seem you have twrp actually installed...?!
the TWRP that you are supposed to use, is this one;
https://dl.twrp.me/marlin/twrp-3.1.1-1-fastboot-marlin.img
that loads and runs from RAM. twrp can't be "installed from fastboot" ~ it installs to the boot partition; leaving not enough room for the kernel.
Click to expand...
Click to collapse
Yeah, that actually explains it. I was using a kernel with TWRP installed last go round and now it seems just flashing the factory boot.img is not getting rid of the installed TWRP. I'll figure out how to get TWRP removed for good this time; thank you for letting me know where to look.
AlkaliV2 said:
Yeah, that actually explains it. I was using a kernel with TWRP installed last go round and now it seems just flashing the factory boot.img is not getting rid of the installed TWRP. I'll figure out how to get TWRP removed for good this time; thank you for letting me know where to look.
Click to expand...
Click to collapse
Yup. TWRP can't be installed along side. Running it from RAM has to be used. ie: I don't support TWRP installations. lol
Flashing the factory boot.img DOES get rid of TWRP for good ~ you just have to make sure to use the TWRP fastboot boot.img for flashing my kernel after (since fastboot/twrp doesn't install to the boot partition)...
I've added a link to the OP to Marlin's twrp fastboot boot.img....
I also updated all of the download links and double-checked to make sure that all of the Marlin zips are packed properly with AnyKernel2 + relabelling every file on my github (by re-packing all of them all... This is mostly just paranoia on my part - but now that I'm supporting 2 devices, best to make sure that nothing gets tangled together.)
@everyone
just a few notes, since you guys are just getting exposure to my kernel, the way I do things; in regards to development, etc.
-> I post test builds (this usually happens when I make big changes.). reports are helpful on these builds.
-> Development happens fast; *I routinely add new features, bug fixes, etc and i'm almost always ahead on LTS updates over the Stock kernel.
examples;
=> lts -3.18.83 build available on the day of release
=> my Binder_rt branch is currently 140+ commits (code changes) ahead of the the other branches.
(changes since in the current downloads/releases)
=> There are a number of bug fixes, a few added features (mostly in-kernel stuff), some optimizations *and* there are massive upgrades to parts of the kernel's subsystems. (100+ commits are related to that)...
(changes since the current downloads/releases)
NOTE: The binder Branch (non-rt) will see the majority of the above changes code, but the Stable branch will only see a subset of these commits + bug fixes.
I probably won't roll out a test build for Binder_rt builds, until I've had the newest code running for a couple of days.... At that point, once things have proven to be stable good ~ i'll roll out a test build for anyone who wants to help out and dogfood test builds....
Then, I will push back changes back into the Binder builds, Stable, etc... I usually try and line up actual releases to LTS and/or => more importantly monthly android security / firmware updates....
**So the gist is; there will be frequent updates. Update as you see fit - anyone who wants to help out - run test builds and report back issues.
So pending a detail or two, I likely will be phasing out my other builds in favor of the Binder_rt build.
- I've had quite a lot of feedback via the Pixel forum, PMs and email (and a couple of friends using it too).
- The Binder_rt build seems to be very stable for everyone.... not too mention just all around better.
- there seem to be no drawbacks and quite a few benefits to that build over the others.
The one thing I'm waiting on is; I've joined the Android Kernel Developers Google Group and am currently waiting to see if I can't get some help with porting a missing Kernel function into Marlin's sources ~ this particular kernel function is what's stopping me from having Binder be sync'd with the AOSP binder implementation.... I'm hoping to resolve this sooner than later, at which point I will be able to merge in those commits (and test them).
In the meantime I'm working on a few backports to the audio driver and a few other bits (taken from Wahoo/Pixel 2 kernel sources). I've also pulled in a few fixes to binder from Wahoo, as well....
So I might post a test build for Binder_rt tomorrow - as it's accumulated a number of changes, bug fixes, etc.... I'm not sure If I will have any resolution to the missing kernel function - but that doesn't affect pushing a test build....