Related
Ill organize this and make it look good later...but for now lets get to the point:
This is an Android 4.1.1 Jellybean (JB) ROM, it is an unofficial version of a popular after market firmware known as CyanogenMod. it is essentially AOSP with some cool added features by the CyanogMod team -this has no sense, and it is not based off a sense stock rom
Befor i even begin stating what works and doesnt i would like to thank Synergy, he is the one who got this started, he is the one who got the first version of this to boot...unfortunately he quit due to frustrations with HTC and how hard they have made things, i am just picking up where he left off...
What works:
WiFi
Audio
Calls? **check out not working***
SMS...aka texting
home button -I know it sounds funny, but for a while the home button didnt work on CM10
Not working:
Data
Bluetooth
GPS
MMS...aka picture messaging and othe multimedia messaging (will work as soon as data works)
Camera
Video-likely a driver issue...mx player allows for videos to be played but they are extremely laggy...only tested with mp4's of videos i filmed while on ICS
Calls? i need people to test calls...i believe if you have ATT in call mic wont work...so the other end wont be able to hear you work...i cant verify it...but if you use any other carrier (even if you have an ATT vivid but are unlocked and using a differnt carrier) then i believe in call mic does work...i need people to verify...so make some calls and let me know if they work and if the other line can hear you, and also let me know what carrier you have
Instructions
1) Wipe data/factory reset
2) Wipe cache
3) wipe dalvic cache
4) flash CM10
5) flash GAPPS
S-ON?
just fastboot flash the boot.img located in the zip then follow the instructions above
Download
CM10
http://goo.im/gapps/gapps-jb-20120726-signed.zip
All versions of GAPPS: http://goo.im/gapps/
what are GAPPS? GAPPS are just google applications...like Play store, GMail...ETC, its not necessary...but if you wanna get any apps your gonna need it
Other stuff...
Featuring Synergys Kangbang-rebirth kernel...supports OC up to 2052 MHz...or about 2 GHz (you can change clock speed under settings/performancee
Features a built in file explorer...not included in most cm builds
Thanks/Credits
once again...synergy...cant thank him enough
kevstheblast, he also worked on cm10 for a little bit
TeamCodefireAOSP - most of my device trees are from you...some with slight modifications
DragunKorr - i am using your msm8660-common device tree
...ill add to this list later, but its late and i need to finish my homework and go to bed
-Its time to bring the vivid back to life...CM10 opens the door to numerous AOSP based JB ROM ports...lets get this stabilized!
Screenshots...coming soon
How to build:
1) First you need to sync CM10 source:
A)
Code:
mkdir cm10
-this creates a folder for where the source will be downloaded
B)
Code:
cd cm10
-this navigates you to the folder the source will be downloaded in
C)
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
-this initializes the repo...gets it ready/prepares for the sync
D)
Code:
repo sync
-this downloads the source...depending on the rom can range from 8-15+ GBs!
E)
Code:
./vendor/cm/get-prebuilts
-downloads necessary prebuilts for CM10
2) Now you need to clone my local manifest:
A)
Code:
cd ~/cm10/.repo
-this navigates to where the local manifest will be cloned
B)
Code:
git clone git://github.com/mg2195/local_manifest.git
-this makes a copy of the local manifest in your .repo folder
C)
Code:
repo sync
-downloads the sources that were added by my local manifest
3) Now you can build:
A)
Code:
. build/envsetup.sh
-prepares the system to build
B)
Code:
lunch
-opens the device menu for you to choose your device
c)
Code:
6
***or whatever number the holiday pops up as*** -the item number of the device
D)
Code:
mka bacon
-begins the build...can take a few hours depending on your computers CPU
4) relax, eat some pizza, go for a walk...do something, this can take a while...your finished product will be located in /cm10/out/target/product/holiday
How to build other roms from source:
1) First you need to sync there source:
A)
Code:
mkdir workingdirectory
you can name "workingdirectory" whatever you want...i suggest the name of the rom for organization purposes...so for AOKP i would do "mkdir AOKP"
B)
Code:
cd workingdirectory
C) repo init there manifest...for AOKP:
Code:
repo init -u https://github.com/AOKP/platform_manifest.git -b jb
found from here: AOKP...so basically find the roms source, then find there manifest, type "repo init -u gitreadlinkhere -b branchnamehere"
D)
Code:
repo sync
2) Now you need to clone my local manifest: (this gets you all the device specific stuff...device tree, common device tree, kernel...ETC)
A)
Code:
cd ~/workingdirectory/.repo
B)
Code:
git clone git://github.com/mg2195/local_manifest.git
C)
Code:
repo sync
3) Now you can build:
A)
Code:
. build/envsetup.sh
B)
Code:
lunch
c)
Code:
6
***or whatever number the holiday pops up as***
D)
Code:
mka bacon
***please note, this may or may not work for every roms source...some require a little extra work...but this should get you the core files needed...look at how other official devices are set up, try and match them...specifically in the workingfolder/vendor***
4) relax, eat some pizza, go for a walk...do something, this can take a while...your finished product will be located in /cm10/out/target/product/holiday
SOURCE
https://github.com/mg2195
https://github.com/KangBangKreations/KangBanged-Kernel/tree/kb-rebirth
CHANGELOG
10-08-2012
-First real release/started thread...
Post any bugs...and if possible get me some LOGCATS
To save a log to a file:
Code:
adb logcat > logcat.txt
Press
Code:
ctrl+c
once you are done collecting information
Then upload the logcat.txt as an attachment so I can look at it with ease...DO NOT JUST COPY AND PASTE THE LOGCATS HERE! that just hogs space and is a pain for those on mobile devices...if you really want to copy and paste there is this great site called pastebin paste it there, hit submit and post the link here
Absolutely awesome man! I love the persistence . Picking up where others left due to frustration, so x10 thumbs up for the dedication!
Will definitely be testing this out and posting back as much bug info I can get you (I will edit this, not just a thank you post). I can't agree more, hopefully you can bring the Vivid back to life . I have faith!
LOG/BUG UPDATE:
Ok so whooo again, great build! Very smooth and speedy, just love this phone without sense (sense works good, but this JB is so refreshing - 0 lag).
Cant wait for the bugs to be worked out, it will be very worth it. Anyway, onto the my report:
_______________________
First boot, it restarted after the white and green HTC screen, so anyone testing no worries when it reboots.
Everything loaded up pretty quickly, and no FCs or bugs besides the known ones. I did notice I think its new probably because of the work you did to get audio to work (messing with the display), when rotating it sometimes makes the screen go all funky (part of the current image is displayed like 4 times in a horizontal line for about .5 seconds) then its fine. So not a big deal.
Bugs:
I tested the calls using my VM, sound works . Now if I try to change the volume of the headset speaker it changes ringer volume I believe, as I didnt notice a difference in volume when the VM automation was talking to me. It also showed a telephone, not w.e it supposed to be (shows same image as not in a call - like its not realizing its 'in' a call). I tried to record a new greeting message, but mic does not work still (tmo).
Data is still the same [as your test builds], blinks E real quick (.5 seconds) then goes away. Under phone status it shows Mobile network type as EDGE:2. Then DCed for network state (changes to connected for the .5 secs when E pops up). Changing bearer to LTE or unspecified doesnt change anything. Also forcing LTE/GSM/WCDMA or GSM/WCDMA Preferred doesnt change anything either.
Camera I tried but FCs with gallery. So also with a few other apps that wouldnt be linked to gallery (though gallery works), no go. They all FC for some reason.
Now no worries, I got you logcats of everything here. I tried to slim them to just the problem although I dont know exactly where the problems end in these huge scripts lol. So I apologize for the length of some, rather you get more than less and I miss the problem line.
Making Calls while changing Volume: http://pastebin.com/gXmiHrCc
Changing bearer to LTE: http://pastebin.com/9hXBiNmS
Clicking Enable Data: http://pastebin.com/xH3AWUp4
Stock Camera: http://pastebin.com/xRsyUTmj (Sorry for lengthy, couldnt tell if it was looping or just straight erroring out million times x( )
Camera Illusion: http://pastebin.com/NFxf2nxd (Again sorry for lenthy, same ^^)
Camera 360: http://pastebin.com/YmRfXBxJ
Maybe hopefully you can get some matching errors on the camera, narrow the problem on that. And hopefully you can figure out the data, thats really big. Same with mic of course. But, again, very good job first actual alpha build.
Unless you wanna damage your hearing....I don't suggest using DSP manager while wearing headphones...went to change the bass and as soon as I changed it my volume went to like full blast lol...definitely some work needs to be done there
Anyways its bed time for me
Sent from my Holiday using Tapatalk 2
Lied about going to bed...found a work around for video...
Go to settings/developer options
Make sure its on
Then disable hw overlays
-my mp4s now play...but they are really laggy...YouTube app now playa video s flawlessly now... maybe its the resolution/quality?
Now I go to bed...
Sent from my Holiday using Tapatalk 2
Would love to try this now, but as this phone is my only phone, I'll have to wait. But once calls and data are working, I'd be more than happy to test out the rest for you. Thank you for your efforts!
Sent from my De-Sensed HTC Vivid using xda app-developers app
finally some JB love for Vivid. as soon as most of the features work, ill test it out.
Dear Santa.....
Can confirm in-call mic doesn't work with AT&T. Everything else is exactly as you described. Let me know if you need a reliable, thorough, tester on AT&T. Will be following this project very closely. Thanks for picking up the project. Keep it up and good luck sir
This thing is wicked fast, and buttery smooth. If in-call mic worked this could be my daily driver. Don't give a damn about data ATM
Internal/External storage works as well, but they arent auto-mounted you need to go into storage settings and manually mount. no usb mount either. but it does recognize the cord.
MisterSchnapps said:
Can confirm in-call mic doesn't work with AT&T. Everything else is exactly as you described. Let me know if you need a reliable, thorough, tester on AT&T. Will be following this project very closely. Thanks for picking up the project. Keep it up and good luck sir
This thing is wicked fast, and buttery smooth. If in-call mic worked this could be my daily driver. Don't give a damn about data ATM
Internal/External storage works as well, but they arent auto-mounted you need to go into storage settings and manually mount. no usb mount either. but it does recognize the cord.
Click to expand...
Click to collapse
Didn't think to test USB as it was working on previous builds...since it was previously working it shouldn't be to hard to fix
Sent from my Holiday using Tapatalk 2
It may be because data doesn't work lol, but I'm getting great battery life!
Anyways...doing some research...trying to figure out how to fix what's currently broken...
Also, it appears that many different devices have graphics/video problems caused by hw overlays....no real fix has been discovered except the work around I mentioned earlier about disabling hw overlays under developer options in settings
As far as USB...I think I might've deleted a line in accident that "defines" its function...
Once I get this stabilized I'll do a tutorial on how to build from source using my existing device sources and plug them into other source ROMs like aokp...
Sent from my Holiday using Tapatalk 2
:fingers-crossed:
Do both mics not work? Could we maybe use the camera mic instead?
Brand New said:
Do both mics not work? Could we maybe use the camera mic instead?
Click to expand...
Click to collapse
The mic works for everything except calls...ive tested it using the voice search app...i searched pizza lol, but it recognized what i said and BAM...all the local pizzerias
Apparntly ATT payed HTC extra to add some extra "security" features...the result is broken in-call mic for ATT users...still waiting for confirmation but if you are a non ATT user then in-call mic SHOULD work...
i stopped my research for a little bit and got my github set up...if you understand how it works you can track my progress there whenever i upload changes...also i edited the third post with instructions on how to build CM10 using my sources, you must already have a build environment set up though...ill add that part later https://github.com/mg2195 ***ill only push changes to github if something is fixed...or improved, so my sources should always produce a working build of the most stable CM10 available***
mg2195 said:
The mic works for everything except calls...ive tested it using the voice search app...i searched pizza lol, but it recognized what i said and BAM...all the local pizzerias
Apparntly ATT payed HTC extra to add some extra "security" features...the result is broken in-call mic for ATT users...still waiting for confirmation but if you are a non ATT user then in-call mic SHOULD work...
i stopped my research for a little bit and got my github set up...if you understand how it works you can track my progress there whenever i upload changes...also i edited the third post with instructions on how to build CM10 using my sources, you must already have a build environment set up though...ill add that part later https://github.com/mg2195 ***ill only push changes to github if something is fixed...or improved, so my sources should always produce a working build of the most stable CM10 available***
Click to expand...
Click to collapse
Please take a look at my updated post (a few up).
Mic for calls do not work for T-Mobile either. Logcats for all of that in that post, which should help you pinpoint some [hopefully].
theslam08 said:
Please take a look at my updated post (a few up).
Mic for calls do not work for T-Mobile either. Logcats for all of that in that post, which should help you pinpoint some [hopefully].
Click to expand...
Click to collapse
Thanks! I'll take a look later...and you have an Att vivid unlocked for T-Mobile?
Maybe in call mic will work for the velocity/raider...me having Att with a vivid...I don't really know, i just remember when syn was working on this he stated in call mic didn't work on Att...but he said it worked for other carriers...
I was able to use mic for voice search...so the problem isn't with the mic its self...has to be with the way the vivid handles calls...
Sent from my Holiday using Tapatalk 2
What about including as littlemount of HTC framework as possible for phone calls?
Just throwing ideas out hahah
PCM 10.1
CyanogenMod 10.1 & PDroid 2.0
What is this?
It's very easy to answer that. PCM is a new initiative I want to begin that brings to the masses the privacy and protection of PDroid. Instead of reaching only a very little user base, PCM will serve completely unmodified CyanogenMod builds with the PDroid framework applied. There will be no need for the end user to patch sources or go through the hassle of compiling CyanogenMod. And by the way, building ROMs is bad for the environment!
Starting with my own device, the Sony Xperia Z, I will publish the ROMs I build for myself on an unregular basis. Most likely when there are new RC or M builds of CyanogenMod or when there is a new version of PDroid. I actively use them myself, so I'll know when, however unlikely, a bug apart from the CM bugs has made it into PCM.
This is not limited to PDroid 2.0. Some of you users may be aware of the ongoing merge of PDroid 2.0 into OpenPDroid. When I feel like the time is right, PCM will switch to OpenPDroid. Looks like it's not going to happen.
A later goal of PCM is to have a completely automatic buildbot that builds weekly, RC, M and stable versions for a variety of CyanogenMod 10.1+ supported devices.
How do I download?
All downloads will be served through BitTorrent by me. I strongly believe that BitTorrent is the best distribution method for a community driven project and I will not serve direct downloads. It has error correction, is resumable and can serve people with slow and unstable connections as well as people with fast and stable connections (which should stay to seed).
You can download the latest version here: cm-10.1-20130527-PDroid2.0-1.57-yuga.
All torrents are attachments of this post, so you can always grab an older version from the archive.
Don't forget to grab the PDroid 2.0 manager application: PDroid 2.0 Manager.
It will also be available in the Play Store very soon.
How is it named?
The naming scheme is almost the same as for CyanogenMod. The difference is that the string UNOFFICIAL ist replaced by <pdroid_framework>-<version>, e.g. PDroid2.0-1.57 or maybe in a future version OpenPDroid-1.0.1.
Now you can safely install that game from the Play Store you always wanted to try, but didn't because the developers want to spy on you.
Subscribe to this thread and to the PDroid 2.0 thread and stay up to date.
Enjoy!
Changelog:
2013-05-27:
No changes regarding PDroid 2.0.
Compiled with latest CyanogenMod 10.1. For CM 10.1 changes see CM 10.1 changelog.
Reserved.
xelra said:
PCM 10.1
CyanogenMod 10.1 & PDroid 2.0
What is this?
It's very easy to answer that. PCM is a new initiative I want to begin that brings to the masses the privacy and protection of PDroid. Instead of reaching only a very little user base, PCM will serve completely unmodified CyanogenMod builds with a PDroid framework applied. There will be no need for the end user to patch sources or go through the hassle of compiling CyanogenMod. And by the way, building ROMs is bad for the environment!
Starting with my own device, the Sony Xperia Z, I will publish the ROMs I build for myself on an unregular basis. Most likely when there are new RC or M builds of CyanogenMod or when there is a new version of PDroid. I actively use them myself, so I'll know when, however unlikely, a bug apart from the CM bugs has made it into PCM.
This is not limited to PDroid 2.0. Some of you users may be aware of the ongoing merge of PDroid 2.0 into OpenPDroid. When I feel like the time is right, PCM will switch to OpenPDroid.
A later goal of PCM is to have a completely automatic buildbot that builds weekly, RC, M and stable versions for a variety of CyanogenMod 10.1+ supported devices.
How do I download?
All downloads will be served through BitTorrent by me. I strongly believe that BitTorrent is the best distribution method for a community driven project and I will not serve direct downloads. It has error correction, is resumable and can serve people with slow and unstable connections as well as people with fast and stable connections (which should stay to seed).
You can download the latest version here: cm-10.1-20130520-PDroid2.0-1.57-yuga.
All torrents are attachments of this post, so you can always grab an older version from the archive.
Don't forget to grab the PDroid 2.0 manager application: PDroid 2.0 Manager.
How is it named?
The naming scheme is almost the same as for CyanogenMod. The difference is that the string UNOFFICIAL ist replaced by <pdroid_framework>-<version>, e.g. PDroid2.0-1.57 or maybe in a future version OpenPDroid-1.0.1.
Now you can safely install that game from the Play Store you always wanted to try, but didn't because the developers want to spy on you.
Subscribe to this thread and to the PDroid 2.0 thread and stay up to date.
Enjoy!
Click to expand...
Click to collapse
This looks good ! I want to wait until we get a stable release though. I see RC was a few days ago so Stable won't be far behind hopefully :fingers-crossed:
defsix said:
This looks good ! I want to wait until we get a stable release though. I see RC was a few days ago so Stable won't be far behind hopefully :fingers-crossed:
Click to expand...
Click to collapse
Well, it works almost perfectly. There are a few bugs. For example, when you press the loadspeaker button during a call, it won't do anything but disable your internal speaker. So don't press it.
I haven't noticed any other bugs.
What annoys me is that the delay for waking the device up is quite long.
Idle battery life is amazing. I had it lying here idly while I was compiling the ROM and I've lost about 5% / day. That's 20 days standby. The screen drains the battery very fast though. Much faster than it does on stock ROMs. So there's room for improvement there.
Thank you for your feedback.
xelra said:
Well, it works almost perfectly. There are a few bugs. For example, when you press the loadspeaker button during a call, it won't do anything but disable your internal speaker. So don't press it.
I haven't noticed any other bugs.
What annoys me is that the delay for waking the device up is quite long.
Idle battery life is amazing. I had it lying here idly while I was compiling the ROM and I've lost about 5% / day. That's 20 days standby. The screen drains the battery very fast though. Much faster than it does on stock ROMs. So there's room for improvement there.
Thank you for your feedback.
Click to expand...
Click to collapse
I have a stable release on my Xperia Neo - It's an unbelievable upgrade from what I had on it before (stock ICS from NeoV) . I can't get over the battery life. 2 days standby and only 4% battery used !!
New version, OP updated!
2013-05-27:
No changes regarding PDroid 2.0.
Compiled with latest CyanogenMod 10.1. For CM 10.1 changes see CM 10.1 changelog.
There are lots of kernel related updates.
Enjoy!
Still Nightlies though? I checked for a Stable release and didn't see it today.
And still the speaker phone bug too?
Sent from my Brain via my Keyboard on my Xperia Z
defsix said:
Still Nightlies though? I checked for a Stable release and didn't see it today.
And still the speaker phone bug too?
Sent from my Brain via my Keyboard on my Xperia Z
Click to expand...
Click to collapse
I haven't had a chance to test for the speakerphone bug, yet. It's very stable though. I use it as my daily driver and I really use it a lot for work. Didn't have a single problem, yet. Apart from the speakerphone bug that is.
But I am aware of 1 other bug that seems to be introduced by PDroid. In the mobile data screen, the button to limit data usage disappears.
xelra said:
I haven't had a chance to test for the speakerphone bug, yet. It's very stable though. I use it as my daily driver and I really use it a lot for work. Didn't have a single problem, yet. Apart from the speakerphone bug that is.
But I am aware of 1 other bug that seems to be introduced by PDroid. In the mobile data screen, the button to limit data usage disappears.
Click to expand...
Click to collapse
Thanks, I'm still thinking about it. I'm not sure I'll live without the Sony apps
Sent from my Brain via my Keyboard on my Xperia Z
Code:
[B][I][U][COLOR="Red"]WARNING![/COLOR][/U][/I][/B]
This is an ALPHA build. Everything is being worked up to come up to speed as
quickly as possible to be with its CM brother. Just be patient and all will
come in due time. But hey, at least is boots up into the system ... LOL
This is an UNOFFICIAL build of SlimKat (although built from offical SlimRom source) and by NO means is this my ROM. I am just compiling from SlimRom Source and credits go to elelinux, xda-garwyn, albinoman and all other coders who contributed to CyanogenMod device tree.
Code:
For which devices. The ROM should work with all klte versions that are qualcomm
chipsets.
Included in the build are:
kltexx,kltelra,kltetmo,kltecan,klteatt,kltedv,klteub,klteacg,kltedcm,klte
(UNOFFICIALLY SUPPORTED): kltespr,kltevzw,klteusc
Code:
IMPORTANT
* DO NOT expect daily builds. I'll build when I'm free.
* DO ask for support in this thread.
* DO NOT use this unofficial build and ask for support at the official threads.
* DO NOT be rude.
* RESPECT all users
* If u see a NOOB question and u don't feel like replying, DON'T, just ignore
that post. If u do reply, good for u.....and be nice in your reply.
Code:
[B][U]WORKING[/U][/B]
Audio
WiFi
Google Now
Bluetooth
GPS
Video playback
Audio playback
Code:
[B][U]NOT WORKING[/U][/B]
Service
Data
Calls
MMS
Hard keys
Camera
Internal/External SDcard mounting
Code:
[B][U]INSTALLATION[/U][/B]
Do NOT use superwipes
Wipe data, cache, and dalvik cache
* ((do not report bugs if you didn't full wipe))
Flash ROM
Flash GAPPS
Reboot
Report anything that is an issue
As of right now I have no way of testing NFC or IR Blaster, so I do not know if they are working on this build or not. Also on this build there is the infamous red box that appears when moving from screen to screen or app. I am going to fix that either today or tomorrow and then post the new build. The reason there is no data or cell reception is due to the APN list which will also be fixed in the next build.
I tested this on my T-Mobile G900T, so if others can please report back on their experience with this ROM on other devices that would be greatly appreciated and I will get those issues resolved as soon as possible. Thank you.
Code:
[B][U]DOWNLOADS[/U][/B]
ROM: [URL="http://d-h.st/2e0"]SlimKat 4.4.4 (QComm)(ALPHA 1)[/URL]
GAPPS: [URL="http://slimroms.net/index.php/downloads/dlsearch/viewcategory/1150-addons4-4"]Click me to pick your poison[/URL]
Great I'll try it out. I've 900F BTW
Thank you. Just remember what is working and what is not working please.
lunerceli said:
Thank you. Just remember what is working and what is not working please.
Click to expand...
Click to collapse
BTW, what the thing that you want me to report?
Just if it boots and the working list is working on your version please.
lunerceli said:
Just if it boots and the working list is working on your version please.
Click to expand...
Click to collapse
Slim minimal gapps.
1st edit: It's booting.
2nd edit: back key, home button and recent/menu key not working? Get NavBar. I like this!
3rd edit: Setting slow to response
4th edit: Stock camera has stopped. Google camera work but need to insert USB storage.
5th edit: Stock Music player not playing
6th edit: USB storage not mounted so can't test out audio/video but ringtone ringing at audio setting.
That's the issues at the moment besides of known issues. I guess i've to restore my backup now. Waiting for your new build thank you.
Ok. Thank you. I will get all of the issues fixed asap.
I'll try it tomorrow but I am also using a sm-g900t so I won't shed much light on the issues/bugs list cause its most likely to be the same as @lunerceli. Still going to flash thou, lol
Thanks for sharing your build with us.
Sent from my SM-G900T
I read your other post in the SlimRoms thread and I'd like to help a bit if I could. I'm going to flash this in the next hour after backing up my memory cards and then I'll grab you some logcats of crashing apps to save you some looking. I know enough to help, but not enough to debug so you aim me at the logs that help you and I'll get you as much as I can.
I run a SM-G900T as well so we will have similar errors. Thank you for taking the time to do this, I really like all the slim roms.
Working: (Mini Gapps)
- Booted and completed setup (hung on "Welcome..." for a bit, it got through)
- Wi-Fi
- Bluetooth/Stereo Bluetooth
- GPS (Took a minute, but did lock with "Device Only" setting chosen)
- Customization Options working (battery color, statusbar transparency, quick tile settings)
- Statusbar brightness slider
- Volume and power buttons
- Real Dark Slim (hangs for a few seconds, but it succeeds)
- Camera works with third party app (Camera ZoomFX) but crashes when taking photo since it can't save to storage (16MP!)
- Headphones (Music stops when unplugged; nice!)
- Music
- Keyboard
- Navigation Bar/Pie Controls
- Dialer
- Root Permissions (had to enable prompt in settings, but it works)
- Secure Lockscreen (Pin Number)
- Normal Apps (Browser, Calc, clock, Dialer, Hangouts, etc.)
Not Working:
- Hardware buttons (Back, Home, Menu/Recents) Tried to run a logcat here, but Android doesn't even see these other than vibration
- No Signal
- Storage (Internal and external can't be accessed) Startup Media Scan Pastebin
- Auto-brightness (Cannot be enabled) Auto-Brightness Log Pastebin
- Occasional Red Rectangle
-NFC (This, once turned on, cannot be turned off and the logcat feedback is about NFC every 7-10 seconds) NFC Feedback Pastebin
Not going to lie, this isn't far from being not only usable, but a daily driver. I'm going to see if I can pull a log later on for Auto-brightness failing and also for startup and maybe see why storage isn't being recognized and mounted. The file system sees both storage cards, /storage/sdcard0 and sdcard1 are both in the root explorer of android tuner, I just get permission denied when I try to access them.
Edit: Ran fix permissions scripts to see if it would mount the memory for me, and it did not. Also, adjusted media scan to prompt and it still didn't find anything. I'm going to try to pastebin you a log for each of the above failing. Got to work on a school assignment first though
Thank you for your feed back bro. I was on 24 hour duty last night and just spent like an hour to bring everything up and build it. I am going to work on it Friday night when I get off of work and hopefully by the end of the weekend it will be daily driveable and I can move to the next project.
lunerceli said:
Thank you for your feed back bro. I was on 24 hour duty last night and just spent like an hour to bring everything up and build it. I am going to work on it Friday night when I get off of work and hopefully by the end of the weekend it will be daily driveable and I can move to the next project.
Click to expand...
Click to collapse
There is no rush, I just wanted to get you some feedback putting things through its paces. I still intend to get you those log files if you find them helpful.
Get some sleep, this project will being be there tomorrow and thanks for tackling this for everyone in the community.
Edit: I put the logs I could get from my device in the last post next to the items in the list. Some things I couldn't pull, but you may know how. Also, and as I mentioned in the post, watching the Logcat scroll every 7-10 seconds I see the NFC log I pasted for you there. Not sure what is causing it, but NFC is toggling itself on and off.
Like I said, no rush on this I just wanted you to have it when you got around to working on it. Now it's my turn to get some sleep and if you need me to pull a log under a certain condition just quote me here and I'll get whatever you need. I'm looking forward to the next test build
Thank you for all of the info bro. I should have the next build up some time Saturday afternoon and almost everything should be fixed. Its been a while since I have done this so I am a little rusty. It is almost like riding a bike. Lol.
Build two is being compiled right now as we speak. I fixed a few things in the code so hopefully everything will work like it should. HAHAHAHA
Okay, so build two keeps stopping and ending in a segmentation fault for the framework.apk... I think I may have fixed it, but really don´t know .. LOL .. keeping the fingers crossed.
lunerceli said:
Okay, so build two keeps stopping and ending in a segmentation fault for the framework.apk... I think I may have fixed it, but really don´t know .. LOL .. keeping the fingers crossed.
Click to expand...
Click to collapse
Awesome thanks for your work! I would gladly test it when it's finished. I came from the Skyrocket a week and a half ago so I am still getting used to the Galaxy S5, but I helped the OP there for SlimKat by testing and providing logs, so just let me know if there is anything I can help with.
Well, every time I get close to getting another build done something gets in the way. I lost my system and had to set it up again. Now whenever I sync the repo it keeps not finding some of the repo saying it can't connect. Lol
lunerceli said:
Well, every time I get close to getting another build done something gets in the way. I lost my system and had to set it up again. Now whenever I sync the repo it keeps not finding some of the repo saying it can't connect. Lol
Click to expand...
Click to collapse
We appreciate that you keep on keeping on and that you keep us updated with this. Developing isn't easy, if it were we would all be making our own ROMs. Whenever you get this build out there will be testers around waiting to flash it to their devices. Me included
Sorry I haven´t posted anything in a couple of days, but I lost my system again and had to start from scratch. Some times I really have VM´s, but on my laptop I take everywhere It is too much of a pain in the ass to install Linux on the side or even straight up.
Just to update though, I am compiling the 2nd build right now and everything is going smoothly. I had to replace some of the Slim files with those from CM just to get past some build problems. I do believe that I have corrected most if not all of the not working. I am waiting for it to finish compiling and test it out before I release it to you guys. I will put up the download link regardless so that you fine ladies and gentlemen can test what and see what is going on in the development. The reason that I like to do this is so that the community can see active development and to compile the lists of what is and is not working with the ROM. I know it is a different approach to other developers, but this is just how I do it. Without you guys we as developers cannot do our jobs correctly and get a working daily driven ROM. Thank you for your support.
Mods please delete this thread. I am merging with another thread of the same topic. Thank you.
Will this rom work on G900FD as it has a qualcom chipset?
The idea behind this project is to compile a Pure AOSP ROM. The difference is I have been little by little including and testing new commits added to the for the most part unstable staging master branch code from Google AOSP that has not yet been tagged for a future Lollipop update., hence the reason for 5.0.2_Plus name. The only change added to the code that was not committed first by Google is that the ZIP can be flashed in TWRP without replacing TWRP with the Stock Recovery and that is it. At the moment because of limited testing as I do not own a Nexus 4 and all changes have been tested on the Nexus 5 felt untill a few return performance reports best to call this a beta version. With that said the same changes have made some improvments and fixed a few issues experienced by Nexus 5 users using the oficial 5.0.1 update or compiled from the AOSP android-5.0.2_r1 branch. So if start receiving comments that all has been well on the Mako build or see say 100 download without a complaint reported will remove the beta tag. I suspect this will be the case as the commits are not device related.
I honestly started the project for the Nexus 5 with the idea that maybe as a community a few developers could help work on the project so everyone had an updated version of the latest release version that included the latest fixes and had not intended on compiling for the Nexus 4. After my second release another XDA member had asked if it would be possible to make a Nexus 4 port for a friend. At that point as there had been little interest in the project by other Nexus 5 Developers I would post the Mako ota package I compiled for the user who had asked for one. I also have my own Starship Rom and am part of a new developer team so again was meant as a community project and not intended to be released as my Rom or really even released at all with the intention of being a resource for other developers to either use as the base of whatever new AOSP Rom they may intend on developing or selectively picking pieces or fixes. So going with the same idea after compiling the asked for Mako version thought why just limit the idea to just the Nexus 5 as all Nexus devices share the same code from AOSP with exception of needing to add a different set of propriety vendor blobs and choosing a different lunch command for building. So the same goes as intended for the Nexus 5. If any Nexus 4 developers would be interested in joining in on the project Just let me know and I will grant full access to the Github account and create a new branch so we can test and insure the master branch is always %100 stable if it is going to be used by other Nexus developers..
A few examples of the commits that have been added.
https://github.com/Android-AOSP/And...mmit/20063610490eabc91db5ef13a550ecbdcdc6dc1a
https://github.com/Android-AOSP/And...mmit/16c0cfd5920c6d09824d13b7ee94436de87b37e3
https://github.com/Android-AOSP/And...mmit/b9e7a844fc751b9fdda7d452dee361f15815199b
https://github.com/Android-AOSP/And...mmit/18cca2773e4f3890e2ff9ca416400d48f62b98f5
https://github.com/Android-AOSP/And...mmit/a05556633ae5a6d1db164597b93f8b6cbbdf2608
https://github.com/Android-AOSP/And...mmit/e6beb1369165f97a4df24a1d1966c41e392c44e7
https://github.com/Android-AOSP/And...mmit/be42994b5a42914071adddfd5d989950e8e47bd9
https://github.com/Android-AOSP/And...mmit/0c89e1b9395093f71cf73508553d5e4058093ec0
https://github.com/Android-AOSP/And...mmit/4c53a7872b1f37ec184801f16d39584ca3b9bcce
https://github.com/Android-AOSP/And...mmit/9d2f14442f2e1d1507dbdc6cc7b9348513a907f9
https://github.com/Android-AOSP/And...mmit/905c6e72ecdc6e170744649b78e8fbb919f71efd
https://github.com/Android-AOSP/And...mmit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/And...mmit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/Android-AOSP_bionic/commit/eaf5aa7d22bd2f6b2eae4c81a60950f89e2d7df4
https://github.com/Android-AOSP/And...mmit/74574e8aa5a2de32e10364fd2f495023fff2a267
https://github.com/Android-AOSP/Android-AOSP_build/commit/49657b7a459ee90b3635bef989f8f9728d564068
https://github.com/Android-AOSP/Android-AOSP_build/commit/1df3707a04651966ca17796f321d23ab3ed6ed2e
https://github.com/Android-AOSP/And...mmit/6fe9c73738e9da0192971576d120802d4c094556
https://github.com/Android-AOSP/And...mmit/44c1c3235d29095c4d987d19155c7260d1a33e0f
https://github.com/Android-AOSP/And...mmit/33baf53861712c3f84606a017943e36bdc680b50
https://github.com/Android-AOSP/And...mmit/a975a08cfb30ad6b2994647c0c6f09e2abd20e28
https://github.com/Android-AOSP/external_protobuf/commit/1a96e2b079e8007fe965bd30cd02cb191a613510
https://github.com/Android-AOSP/external_protobuf/commit/4fcbf285db7f9e20795783b676963d42499dbd64
https://github.com/Android-AOSP/frameworks_base/commit/cc50afe3bdcc3adfa0f4121bf461996996e69a3e
https://github.com/Android-AOSP/frameworks_base/commit/1be740dd60f4d95e1f9ac4aac7e4d6148e3b2dd1
https://github.com/Android-AOSP/frameworks_base/commit/1cca2282dc9a3b7ecc08729af201923842ddfc86
https://github.com/Android-AOSP/frameworks_base/commit/7db1192e72b45111556631dba125a635edff3235
https://github.com/Android-AOSP/frameworks_base/commit/b29136581cc3181e59193e0b6448f0c3f5990081
https://github.com/Android-AOSP/build/commit/de655233a4308340fc71490e86fd0f218cc7fec4
https://github.com/Android-AOSP/build/commit/ab6f841841a0930c7e178a949ada39152e24540f
https://github.com/Android-AOSP/hardware_libhardware/commit/9ede7f730bca338cd3ccad8962e253f28ae17976
https://github.com/Android-AOSP/hardware_libhardware/commit/d4f431fec4136f6eeee919ac3190762fba832942
https://github.com/Android-AOSP/hardware_libhardware/commit/898bcd96e3d80e99d9200cceb4af754bae6d5f4a
https://github.com/Android-AOSP/bionic/commit/d90f39af35c1f2a9972198f92e803e3ca73ac910
Downloads
Download Rom
aosp_mako-ota-ota-5.0.2_plus_r2.0_test.zip.zip - 184.51 MB
aosp_mako-ota-ota-5.0.2_plus_r1.0_test.zip - 184.52 MB
PA-Gapps
http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
So far I have been using the "Mini Modular package" for testing without any issues.
Root
Root is optional but recommend SuperSU
http://forum.xda-developers.com/showthread.php?t=1538053
Have had version 2.37 in storage and had been using without issue but updated to 2,40 with last test without any issues. What can I say Im lazy that way so unless having an issue just used what works but figured most would grab the latest so thought it best to give it a test before posting.
Kernel is %100 Stock but going with past experience if mrg666 has a Kernel availible for your device it should be the Kernel you are using.
Mirage Kernel for Stock Nexus 4
http://forum.xda-developers.com/nex...el-mirage-nexus-4-stock-rom-06-04-14-t2485368
Change Log 5.0.2_plus_r2
Removed the below commit "Add ip6-localhost to /system/etc/hosts."
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
Looks like a few apps are not fans of having an ip6 entry for localhost. Transparent Weather Widget for example can not find the device location with the enty included.
In looking for the cause of the above issue also reverted.
https://github.com/android/platform_frameworks_base/commit/e4ec09da0b4a31e23f1a19bdd1ea99e0f87cadac
Honestly reverted looking for the cause and did not remember to restore once identifying the cause. Overall is an old commit and dont think will make any difference whatsoever or would have been tagged for use in a past release so not going to bother.
As usual I am not responsible for your device and you are using anything posted in this thread at your own Risk.
This is %100 AOSP with no extra theming at all including bootanimation so no screen shots, as a Nexus User are probably aware what AOSP looks like at this point.
Don't mean to be rude, but you're still living in 2014, apparently. LOL . Classic mistake, I guess. Check the title dude.
Its cool, such a classic XDA first comment though. Could discover the holy grail and receive 15 comments about a spelling error. Adding I guess makes it that much better. Going to leave it in and see how many times your comment is over looked by someone so proud to have noticed it first, lol.
This is exactly what i have been looking for, we need more Roms like this. Thanks OP downloading now:good:
chairshot215 said:
Its cool, such a classic XDA first comment though. Could discover the holy grail and receive 15 comments about a spelling error. Adding I guess makes it that much better. Going to leave it in and see how many times your comment is over looked by someone so proud to have noticed it first, lol.
Click to expand...
Click to collapse
I hope you don't think it was something personal, man. Your title made my day. With all these exams, I've been all stressed out, and your title made reminded me of the time when I was sitting in bed with the laptop in front of me, thinking it's a long time till the exam session. LOL
Good rom so far, only thing was that data roaming was enabled by default.
dragos281993 said:
I hope you don't think it was something personal, man. Your title made my day. With all these exams, I've been all stressed out, and your title made reminded me of the time when I was sitting in bed with the laptop in front of me, thinking it's a long time till the exam session. LOL
Click to expand...
Click to collapse
I was just joking but still think it will be amusing to see how many skip past your post to point out the same. I actually test software for a living after it has been installed on an energy management diagnostic system both for new version testing and quality control before shipping and need to sign off that each system was checked out including the date. Had just recently worked on my birthday and was a highly unusually busy day but ended up signing off the date as 1976 (my birth year) on about forty systems. What is even more humorous is the amount of complaints from technicians who thought they received a system using a Nexus 7, now 9 for use as a portable User interface believed they had received software that had not been checked out since 1976. With that said most installers come from an HVAC technical school background and still use AOL as their contact email address. Lol!
nibla101 said:
Good rom so far, only thing was that data roaming was enabled by default.
Click to expand...
Click to collapse
Will look into that I'm happy to know it is working out. I basically just took my N5 source added the Mako vendor blobs and compiled using a different lunch command. Will go back and see if data roaming being enabled by default is a result of my updates or is set in general aosp 5.0.2 after work. Even though intention is keeping as pure as can be should still be looked at.
Think it would be nice if we could get a few devs together from across the current Nexus devices lineup and do our best to keep an aosp Rom available adding in the latest updates and bug fixes into the most current release for all Nexus devices. Not just for users but for other devs to use in their own aosp based work. Beleive if we could get something like that going would be pretty sweet and not all that time consuming. Still lots of updates added by Google devs every day. Some a bit more complicated then what I have done that a small group could easily bang out and test. Everything comes from the Master aosp branch that can get messy with constant new commits around the clock but think if selective in adding into latest release could be a beneficial project. So using my phrase of the week with that said I am going to build and post a version for all the Nexus devices in an attempt at gaining interest in the project. Again with that said I am torn for tonight as can try producing thr first N5 version that is sprint compatible or build for my Nexus 9. I am very much looking forwored to trying it out with jusst Simple ol aosp but at the same time feal bad for the Nexus 5 Sprint users who are all stuck on stock because other Roms are missing the aditional files added in for the radio to work. Decitions, decitions, decitions.
chairshot215 said:
I was just joking but still think it will be amusing to see how many skip past your post to point out the same. I actually test software for a living after it has been installed on an energy management diagnostic system both for new version testing and quality control before shipping and need to sign off that each system was checked out including the date. Had just recently worked on my birthday and was a highly unusually busy day but ended up signing off the date as 1976 (my birth year) on about forty systems. What is even more humorous is the amount of complaints from technicians who thought they received a system using a Nexus 7, now 9 for use as a portable User interface believed they had received software that had not been checked out since 1976. With that said most installers come from an HVAC technical school background and still use AOL as their contact email address. Lol!
Click to expand...
Click to collapse
LMAO. That was funny
flashed yesterday with nothing to complain until now
thanks for this build
edit: found first bug (maybe)
whle setting Chronus Weather and also Transparent Clock Widget
the phone couldn't find it's location.
Pop up on the screen stated....
"Cannot retrieve location!"
Network geolocation is disabled
Set a custom location or enable location
already try High Accuracy, Battery saving and Device only but it never show my location
the widget always appear with "Loading weather data"
If i choose Battery saving then Google Location Reporting will turn grey and not clickable, other two option made it clickable again but still my location show "Loading weather data"
maybe someone are having this too?
how to fix it please?
thank you very much
groovepeppy said:
flashed yesterday with nothing to complain until now
thanks for this build
edit: found first bug (maybe)
whle setting Chronus Weather and also Transparent Clock Widget
the phone couldn't find it's location.
Pop up on the screen stated....
"Cannot retrieve location!"
Network geolocation is disabled
Set a custom location or enable location
already try High Accuracy, Battery saving and Device only but it never show my location
the widget always appear with "Loading weather data"
If i choose Battery saving then Google Location Reporting will turn grey and not clickable, other two option made it clickable again but still my location show "Loading weather data"
maybe someone are having this too?
how to fix it please?
thank you very much
Click to expand...
Click to collapse
Think I got the fix and am compiling now. Hopfully have up by tonight if not morning. I am on the N5 though and have no issue with beatifull widgets finding my location or maps with navigation working which is my goto test apps along with GPS test. After reading your post tried Transparent Clock Widget and the app was not able to find my location. I did manage to fix this on my N5 so am rebuilding for Mako using the same source. Now have all the Mako Vendor proprietary blobs set up in vendor so can build either Hammerhead or Mako depending on lunch command. Still though will need testing on N4 as I am on the N5.
chairshot215 said:
Think I got the fix and am compiling now. Hopfully have up by tonight if not morning. I am on the N5 though and have no issue with beatifull widgets finding my location or maps with navigation working which is my goto test apps along with GPS test. After reading your post tried Transparent Clock Widget and the app was not able to find my location. I did manage to fix this on my N5 so am rebuilding for Mako using the same source. Now have all the Mako Vendor proprietary blobs set up in vendor so can build either Hammerhead or Mako depending on lunch command. Still though will need testing on N4 as I am on the N5.
Click to expand...
Click to collapse
will test it later
thank you for responding
groovepeppy said:
will test it later
thank you for responding
Click to expand...
Click to collapse
Know prob but had been unsuspectingly busy but compiling the what believe will fix the issue for the N4 and it comes down to the smallest commit.
Know prob but had been unsuspectingly busy but compiling the what believe will fix the issue for the N4 and it comes down to the smallest commit.
https://github.com/android/platform_system_core/commit/25147416bb105914c3cdf8fd65ca7cc20dae0f3e
well, I have done a little experiment with my Nokia, seeing that there is again between the sections of Nokia 6 and Nokia 5, I found that the Nokia 6 has already a semi stable rom of Android Oreo based on lineages os 15
and doing a bit of logic, I assumed that the rom could work on the n5, since the romes of the n6 and n5 are compatible with each other, and it really works, accepting that it has some details, one of them is that the buttons do not work. navigation, the fingerprint reader does not go either, and the audio does not go either, the latter works halfway, since adding the file mixer_paths_nd1.xml in the system / vendor / etc path manages to raise the audio service
and as usual, the camera is not as good as stock or gcam and also brings some minor bug when recording at high speed
if you want to try it here is the link, preferably try it having installed android 8.1 stock
link to post
https://forum.xda-developers.com/nokia-6/development/lineage-15-1-t3896279 :good::good::good:
Give the list of which is working and not working
What happened to this project?