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!
I'm currently trying to fix errors during boot of CM11 and found a lot of
E/memtrack(146): Couldn't load memtrack module (No such file or directory)
E/android.os.Debug(146): failed to load memtrack module: -2
in the logcat.
It seems there got to be a memtrack.*.so in either system/lib/hw or vendor/lib/hw but there is not.
Is there no memtrack library for I9100G or is it missed during build? Is it actually something build by CM or a proprietary file that should have been pulled by extractFiles.sh?
If first: Which folder is the one, where it should come from (which MakeFile)?
memtrack module
im trying to find out what this mug is too
Be On the Lookout for memtrack
ElwOOd_CbGp said:
im trying to find out what this mug is too
Click to expand...
Click to collapse
I have had these errors on a Nook HD+ with CM 11-20140913-NIGHTLY-ovation and also on a stock rooted LG G pad 7.0 Kitkat. On the Nook HD+, the missing memtrack incidents sometimes lead to hard crash reboots. My LG G2 phone has Lolipop 5.01 and no missing memtrack problems. According to an article on Low RAM in Source Android dot com (sorry, I don't get to give you the actual url), memtrack is used to keep track of GPU memory use. My Nook HD+ only has 782 Mb, so I think this is why I have periodic crashes. My G Pad has the memtrack errors in logcat, but not the crashes. It has 1Gb RAM, maybe enough more to keep out of trouble. I think the memtrack problem is widespread and not related to CM11. I think it's a Google problem, maybe with the kernel. I hope somebody can track down memtrack, and make him available. I have logcat files for various flavors of CM11 and also PAC Man ROM. If you want, I can upload them. They all show the problem. If anybody is interested in fixing this, I would be happy to test work arounds or patches or new kernels or whatever. For Nook HD+, I used the build.prop option of
dalvik.vm.execution-mode=int:fast
to turn off dalvik cache. This seems to make hard crashes a lot less frequent. It also eats battery like mad.
This is thread for devlopment and discussion for cm10.1 (BCM21654)
myself working on Samsung galaxy pocket neo duos(S5312)
@Alonso1398 working on Samsung galaxy music
Contibutors:
@k2wl @Unjustified Dev @Alonso1398 @dhinesh77 @psych.half
Status for Cm10.1 on pocket neo duos (s5312)
Status for Cm10.1 on pocket neo duos (s5312)
First bootable cm 10.1 rom on S5312/S5310
Whats working ?
vibration
hardware buttons
external-sdcard
apps install
egl
camera(video recording force close because of antibanding feature)
sound
sensors
bluetooth ( minor bug only => unable to connect to any devices)
Wi-Fi
Storage
Ril,
whats not working ?
Source:
https://github.com/dhinesh77/android_device_samsung_corsica
Status for Cm10.1 on galaxy music
Status for Cm10.1 on galaxy music
Compiling again... I think thus time the bluedroid problem didn't show, hope it ends without more errors, also a question, when you managed to get to bootanimation, did you disabled hadware rendering by just editing build.prop?
Enviado desde mi GT-S6010L mediante Tapatalk
Alonso1398 said:
Compiling again... I think thus time the bluedroid problem didn't show, hope it ends without more errors, also a question, when you managed to get to bootanimation, did you disabled hadware rendering by just editing build.prop?
Enviado desde mi GT-S6010L mediante Tapatalk
Click to expand...
Click to collapse
for the first time disabled hardware rendering, due to that all apps force closes, after fixing egl force close error solved
dhinesh77 said:
for the first time disabled hardware rendering, due to that all apps force closes, after fixing egl force close error solved
Click to expand...
Click to collapse
Soo now finished compiling and installed but got a bootloop. Something interesting is that if restore boot from stock via cwm, it passes the bootanimation and a window that says android upgrading appears but when it finishes, then makes the bootanimation again and do the same eternally.
Updated a lot my device tree based on yours. Here is the device tree, the only folder that didn't modified was overlay, also the files from rootdir are the ones from my device (except init.recovery.rhea_ss_ivoryss.rc).
This are the files I'm using as proprietary blobs. Also I haven't modified my kernel source and had to comment"TARGET_USERIMAGES_USE_EXT4" from boardconfig.mk because for some reason was giving errors while compiling.
Also when trying taking logcat via adb it stucks on - waiting for device -
I was so close of getting it to boot :crying:
Edit: I think the files from the rootdir folder on my tree are the ones that should be edited, so already edited them to be like from your tree and I'm compiling again
Edit2: Editing those files to much do even worse, get stucked on the device logo so most of the files from rootdir are still the ones from the device. Also updated the system.prop file that was forgetting but still didn't worked to past bootanimation. Been really hard trying to fix it, could someone give me a hand?
Alonso1398 said:
Soo now finished compiling and installed but got a bootloop. Something interesting is that if restore boot from stock via cwm, it passes the bootanimation and a window that says android upgrading appears but when it finishes, then makes the bootanimation again and do the same eternally.
Updated a lot my device tree based on yours. Here is the device tree, the only folder that didn't modified was overlay, also the files from rootdir are the ones from my device (except init.recovery.rhea_ss_ivoryss.rc).
This are the files I'm using as proprietary blobs. Also I haven't modified my kernel source and had to comment"TARGET_USERIMAGES_USE_EXT4" from boardconfig.mk because for some reason was giving errors while compiling.
Also when trying taking logcat via adb it stucks on - waiting for device -
I was so close of getting it to boot :crying:
Edit: I think the files from the rootdir folder on my tree are the ones that should be edited, so already edited them to be like from your tree and I'm compiling again
Edit2: Editing those files to much do even worse, get stucked on the device logo so most of the files from rootdir are still the ones from the device. Also updated the system.prop file that was forgetting but still didn't worked to past bootanimation. Been really hard trying to fix it, could someone give me a hand?
Click to expand...
Click to collapse
yup sure i will.....from two days broad band is not working so I can't come to online. ....
you can take logs without adb too... if rom didn't booted just return back to cwm and flash aroma file mAnager and go to data/tombstones in that folder many files present. . copy allfiles to sd view in gedit ... error message will be in Brown colour... this helps to fix all bugs. .. I fixed for pocket neo like this method only.. since adb is working only after authorizing pc in development settings...
dhinesh77 said:
yup sure i will.....from two days broad band is not working so I can't come to online. ....
you can take logs without adb too... if rom didn't booted just return back to cwm and flash aroma file mAnager and go to data/tombstones in that folder many files present. . copy allfiles to sd view in gedit ... error message will be in Brown colour... this helps to fix all bugs. .. I fixed for pocket neo like this method only.. since adb is working only after authorizing pc in development settings...
Click to expand...
Click to collapse
Thanks a lot, didn't know that trick of aroma file manager, now finally made it boot :victory::victory:
Status:
Whats working?
-It boots
-Touch
-Hardware buttons (home fixed and now wakes the device)
-Camera (all modes)
-Vibration
-Rotation
-CRT effect
-Sound
-Wi-fi
-Bluetooth (it can receive files but not sure if it can send)
-Storage (both internal and external)
-Button for start reproducing music tough it can't stop it
-Microphone
-Ril
What's not working?
-fm radio
Notes:
-For some reason the glow effect wile sliding is orange instead of blue
Edit: Link to the thread here
Great going guys . Hatsoff to ur work. Waiting for completion
Sent from my GT-S6012 using Tapatalk
Alonso1398 said:
Thanks a lot, didn't know that trick of aroma file manager, now finally made it boot :victory::victory:
Status:
Whats working?
-It boots
-Touch
-Hardware buttons (home fixed and now wakes the device)
-Camera (I think)
-Vibration
-Rotation
-CRT effect
What's not working?
-Sound
-Ril
-Wi-fi
-Bluetooth
-Storage (both internal and external)
-No baseband
Notes:
-The button for start reproducing music I think it works but since there's no music because of storage problems, it can't reproduce anything but long pressing the button will open Apollo
-For some reason the glow effect wile sliding is orange instead of blue
-Also is it me or the unlock glow thing is kinda small?
Click to expand...
Click to collapse
Nice, i amanged to mount external storage but not internal memory, though external storage is working still many apps not opening because of no internal storage(since internal is seted as default)...
Latest strategy:
1.Wifi Hotspot working (but normal WIFI not working)
2. Bluetooth able to turn on and searching devices, but unable to connect to that..
3. Hardly tried still ril coulnt be fixed
dhinesh77 said:
Nice, i amanged to mount external storage but not internal memory, though external storage is working still many apps not opening because of no internal storage(since internal is seted as default)...
Latest strategy:
1.Wifi Hotspot working (but normal WIFI not working)
2. Bluetooth able to turn on and searching devices, but unable to connect to that..
3. Hardly tried still ril coulnt be fixed
Click to expand...
Click to collapse
I made dual boot to speed up process but for some reason every build made isn't booting even if I know it's going to boot and tombstones sometimes aren't generated so will going to download source again...
I keeped a booting build and fixed sound for it, so my next step is try fixing storage (since both internal and external aren't working)
Alonso1398 said:
I made dual boot to speed up process but for some reason every build made isn't booting even if I know it's going to boot and tombstones sometimes aren't generated so will going to download source again...
I keeped a booting build and fixed sound for it, so my next step is try fixing storage (since both internal and external aren't working)
Click to expand...
Click to collapse
bro over 95% of all bugs solved except one thats is ril
dhinesh77 said:
bro over 95% of all bugs solved except one thats is ril
Click to expand...
Click to collapse
Lol, I'm like turtle speed fixing problems then will try too with ril
Alonso1398 said:
Lol, I'm like turtle speed fixing problems then will try too with ril
Click to expand...
Click to collapse
any progress regarding ril ?
dhinesh77 said:
any progress regarding ril ?
Click to expand...
Click to collapse
Not so far, and this error 7 problem is worrying me, the builds shouldn't give that error since the device tree is almost the same as before when I was on the vbox, so being slowed down trying to fix it but I think my only actual solution is being replacing system folder on older flashable builds also storage seems like a headache for my device, already looked at your tree but still not working
Alonso1398 said:
Not so far, and this error 7 problem is worrying me, the builds shouldn't give that error since the device tree is almost the same as before when I was on the vbox, so being slowed down trying to fix it but I think my only actual solution is being replacing system folder on older flashable builds also storage seems like a headache for my device, already looked at your tree but still not working
Click to expand...
Click to collapse
dont worry bro i am here to help you between , all issues on samsung pocket neo duos is solved including ril....
Thanks a lot, the weird not installing problem it still there, however I can take the old working build and replace the system folder and boot.img with new ones compiled so somehow that way I can still be working however replacing the META-INF from the new builds doesn't work. I'm trying to apply the fixes for my device so now so far internal storage is finally working but external still doesn't, now that camera opens, discovered that camcoder isn't working for me, and bluetooth its activating but actually don't know if it can connect to other devices.
Thanks a lot for the help you are offering, really.
Edit: Wi-fi fixed however still without baseband and ril
Enviado desde mi MW0711 mediante Tapatalk
hi bro , i saw on github that you have merged pull request, w8ing for outcome
dhinesh77 said:
hi bro , i saw on github that you have merged pull request, w8ing for outcome
Click to expand...
Click to collapse
Thanks a lot for those pull requests, they fixed external storage tough internal just needed some changes. However ril still isn't working, I think that even my phone doesn't detect the sim card. Also I think microphone isnt' working too
At least most functions are working now thanks to you :highfive:
Alonso1398 said:
Thanks a lot for those pull requests, they fixed external storage tough internal just needed some changes. However ril still isn't working, I think that even my phone doesn't detect the sim card. Also I think microphone isnt' working too
At least most functions are working now thanks to you :highfive:
Click to expand...
Click to collapse
Do you patched the patches mentioned by pawitp in thread for grand duos ? ....
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.
So, I found a while back that setting "Profile GPU Rendering" in Developer Options caused all of the UI tearing that was happening in Treble ROMs to go away on my Mate 9; other Huawei devices and ROMs seemed to have the same result - scrolling views stopped tearing.
The problem, of course, is that the property had to be reset on every boot, or you'd end up with UI tearing yet again.
All this module really does is:
Code:
debug.hwui.profile=true
in a Magisk property file.
If you don't want Magisk, you can probably add that directly to /system/build.prop as well. (I haven't tried this yet: I've been trying to leave /system and /vendor alone.)
irony_delerium said:
So, I found a while back that setting "Profile GPU Rendering" in Developer Options caused all of the UI tearing that was happening in Treble ROMs to go away on my Mate 9; other Huawei devices and ROMs seemed to have the same result - scrolling views stopped tearing.
The problem, of course, is that the property had to be reset on every boot, or you'd end up with UI tearing yet again.
All this module really does is:
Code:
debug.hwui.profile=true
in a Magisk property file.
If you don't want Magisk, you can probably add that directly to /system/build.prop as well. (I haven't tried this yet: I've been trying to leave /system and /vendor alone.)
Click to expand...
Click to collapse
FWIW I've already included this workaround in my tree ( https://github.com/phhusson/device_phh_treble/commit/a9a6cba4ddf8227d43cec50fb6d48a410e9369c9)
So my next releases will already do that and won't require your magisk module
phhusson said:
FWIW I've already included this workaround in my tree ( https://github.com/phhusson/device_phh_treble/commit/a9a6cba4ddf8227d43cec50fb6d48a410e9369c9)
So my next releases will already do that and won't require your magisk module
Click to expand...
Click to collapse
Yeah, I figured that'd be the case. I've been using others and they don't include this, so I keep finding myself resetting that flag...
Still nice to have for those ROMs that don't have it.
How ui tearing looks like
I was so happy when i read the post title and then i read phhussons reply and checked the setting myself, so that wont help it.
Im experiencing screen tearing when using the front camera both in snapchat and the huawei stock cam port. P10 C432B371 phhussons PIE v106.
Idk if its directly related to the rom or if its because of my vendor, seeing as you have done some experimentation - maybe you have also run into this issue and know a fix?