This thread is for everyone who compile's Cyanogenmod Kang build's from source and would like to post/share with everyone. If you want your build included in this post just pm me and I will update this post asap.
Warning these are unofficial CM7 build's (with myself cherry-picking comments from CM's Gerrit for testing) which may have unfinished mods and/or broken code that is continually changing, ONLY THOSE WHO KNOW WHAT THEY ARE DOING SHOULD FLASH THEM. Don't file bug reports on the Cyanogenmod issue tracker from any of these build's. Please don't bother cyanogen or #teamdouche as you have been warned these build's are unofficial and come with no support except on this thread. If you have any question's try searching as your question might have been already asked and answered. Note: I, nor is anyone else is/are responsible for any bricks or problems you may encounter.
I no longer have a G2 as I gave it to my mom, but will update this periodically. Sorry for the delay I have been super busy with the move, my new job and fixing this house I am now living in.
All credit goes to cyanogen & #teamdouche, thank them not me as all I do is compile
Items from CM's Gerrit that I cherry-picked:
* Give me time
Last Commit repo synced before building-
* Enable access to Audio Effects Settings
I understand that this build is unofficial and I take no responsibility if you brick your phone- Will be update in about an hour and half as I plan on running it when I get home
Please visit @cmsrc, CM's Gerrit or Nightly Device Changelog for a complete list of changes or commits.
Also those who don't know a Kang is an unofficial nightly that someone builds from CM's github.
I will update this post as often as needed to stay current or change as necessary.
Hey everyone, here are the kangs and cherry picks that i will be providing. I want to thanks plasmadragon007 for allowing me to post here.
Everything in the above post applies to here. We will most likely be making these at a different time of day with possible different commits. I do not own a g2 but i do have a couple of decent guys willing to test each kang before posting. If they are not available, i will let you know that the build has not been tested. I do this because i enjoy it and want to. I hope you enjoy it also.
All credit goes to cyanogen & #teamdouche.
Items from CM's Gerrit that I cherry-picked:
Lockscreen background http://goo.gl/5p5Np
you can find my builds on Euroskank http://goo.gl/U7xx6
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
All Builds + recoveries can be found here. I have included a date + md5sum
http://xdafiles.net/rhcp/
More Builds/Gapps can be found here:
gridlock32404 - cm7rc0 built by gridlock will be http://www.crackflashers.com/ cause of dropbox excessive traffic, will build new ones tonight if new commits
I uploaded it just now.
You will need to flash CWRecovery 3.0+. Which can be found at
http://xdafiles.net/rhcp/
This has been all built from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
If you want to see protected apps. You need to edit your build.prop in system with the following:
Code:
ro.build.description=soju-user 2.3 GRH55 79397 release-keys
ro.build.fingerprint=google/soju/crespo:2.3/GRH55/79397:user/release-keys
This is built from current src as of 30 mins ago.
So, there is a few video fixes and others.
You can read the updates at: http://r.cyanogenmod.com/#q,status:merged,n,z
I appreciate it man. I just moved and I don't have an internet connection yet. It's hard to repo sync on a 1mbps Android tether.
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
smjfosho said:
Is there any difference between this one and the other one?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
This one is more recent, with the newest commits.
Is your link supposed to point to recovery.img?
bivio said:
Is your link supposed to point to recovery.img?
Click to expand...
Click to collapse
Thanks. I mistyped fixed now.
Camcorder still borked?
rhcp0112345 said:
Hey Guys,
I figured i would share this.
All credit goes to cyanogenmod team. and cyanogen for being a killer coder
The rom can be found at: http://www.mediafire.com/?15l284rnq1zjt1h
I uploaded it just now.
You will need to flash this with CWR 3.0. Which can be found at
http://mrcellphoneunlocker.com/recovery.img
This has been all buit from source.
You need to put your phone in fastboot.
1) fastboot flash recovery recovery.img
2) reboot into recovery
3) backup your current rom
4) adb push the zip
5) flash the zip
As for gapps I can not post any gapps here. (Hint Paul obrians dump of the nexus S)
Notes: I am not responsible for any bricks or problems you may encounter I am just sharing this. If you follow the step you will have 2.3.1 on your phone.
Please help the devs who put this togther for us. fix some bugs. If you know how.
so far, It seems the video has been fixed up a bit. and the wifi works. So, Far the only thing not working video cam. (which is under works so i hear)
Also. Protected apps do not show since this is 2.3.1 (You can fix this by modding your build.prop or wait for google to add 2.3.1)
Thanks and I hope you enjoy this. Please someone mirror the build. I dont think mediafire will keep it up.
Click to expand...
Click to collapse
the link to the recovery img is broken because it says reovery not recovery
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Vandale said:
Im in no rush. Im just going to wait for the cyanogenmod team to fully finish it & wait for RC1.
Click to expand...
Click to collapse
Sure your not Thats why your watching these threads like everyone else, including me!!
Downloading now, Thanks for the build!
Been waiting for this all day. Thank you!
[ROM]cm7 gingerbread flavor
[Recovery]clockwork 3.0.0
Glad everyone likes.
My pleasure
Sent from my HTC Vision using XDA App
do you know if usb issue was addressed in this build
Have not tested it. Nor do I see any commits. So I assume same issue.I don't mount usb so doesn't bother me. I use adb
Sent from my HTC Vision using XDA App
is the "unknown" thing still showing up in phone number? its the only thing keeping me from sticking with Gingerbread @[email protected] silly, i know.
having problem flashing the img help
I get an assert failed error trying to flash the ROM, too bad I was really looking forward to trying CM7 .
cough..... cough http://forum.xda-developers.com/showpost.php?p=10083640&postcount=151 cough..... cough... man I'm really sick
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveat List
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from my RHOD400 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
Just to get people going on some of the newer kernels.
2.6.35 is currently auto-built at:
https://code.google.com/p/zimages/downloads/list
Emwe has been maintaining this tree, and he is most qualified to speak about it, but pretty much everything is functional barring camera.
Head over to this testing thread for more information on 2.6.39/3.0/3.1 kernels for Rhodium.
arrrghhh said:
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Download
Click to expand...
Click to collapse
You probably saw this problem coming but I have just the stock windows rom, how would i go about doing this? (or do i have to go and find each and every CSV file )
I googled and downloaded total commander on my laptop, and i got it to show my phone, but it only shows up with my SD card stuff, not my phone itself (unless thats whats supposed to happen )
Will keep trying! -determined-
A cool username said:
You probably saw this problem coming but I have just the stock windows rom, how would i go about doing this? (or do i have to go and find each and every CSV file )
I googled and downloaded total commander on my laptop, and i got it to show my phone, but it only shows up with my SD card stuff, not my phone itself (unless thats whats supposed to happen )
Will keep trying! -determined-
Click to expand...
Click to collapse
Sigh, are you freakin serious? I even link to Total Commander's website in my instructions.... Not sure how much easier I could've made it.
I also just attached the CSV's for the lazy... .
It does say TESTING in the title, no? Yea. It does..
Hehehe I know, I know, i guess i just don't have very much knowledge with this kinda stuff (obviously) Thanks!
A cool username said:
Hehehe I know, I know, i guess i just don't have very much knowledge with this kinda stuff (obviously) Thanks!
Click to expand...
Click to collapse
Testing/development threads usually mean "please pitch in and help test if you can. If not, please wait until the final stable release".
Make sense?
Okay, i'll be glad to help test it if someone could post the CSV files for a rhod300 (if its not too much trouble). If not, I will wait for the stable release. Thanks arrrghhh!
Yes, makes sense
Installed the rom but i've got a problem with the fact that the screen dissapaers after about 5 seconds, so i can't even put in my pin.
also i'll put in the csv files from my rhodium100.
Edit: Works good on second boot, had to change the calibration file and it's works good and fast. Only thing i have is that i now have got 919 contacts instead of the (normal) 135.
A lot of text messages for tonight
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Camera works when you don't move a lot, otherwise it's blocked.
bleutooth doesn't work for me it connects to my parrot but i can't make a phone call.
Schumi_wk said:
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Camera works when you don't move a lot, otherwise it's blocked.
bleutooth doesn't work for me it connects to my parrot but i can't make a phone call.
Click to expand...
Click to collapse
Sounds like a proximity sensor issue - not sure if some of the GSM rhod proximity related adjustments made it into the acoustic .27 kernel. You should try one of the newer kernels (not sure what's the status with .35 and GSM-proximity, but on 39+ I expect you won't have this issue).
This GB build, and these new kernels are kexec enabled. Meaning if you are on .35 or newer, and would like to interchange the kernel on-the-go, without re-booting to WinMo you can do the following:
1. While in Android, copy the new kernel and modules to the same location (over-writing the zImage) as your current kernel (adb push).
2. Go to the shutdown menu in GB, and select "Kexec".
3. Phone will reboot within Android, using the new kernel.
Again, this feature only works with the new kernels.
---------- Post added at 06:20 PM ---------- Previous post was at 05:38 PM ----------
Schumi_wk said:
Edit 2:when i make a phone call i get a black screen and the phone crashes after that.
Click to expand...
Click to collapse
Let me know if you are willing to test a prox support for rhod 100. I'll pm you a kernel pack.
Just tried the .39 kernel and bluetooth didn't work with that one. The phone did work with this one.
Than did the 3.0 kernel and bluetooth works but there i don't have wifi.
The 3.1 kernel doesn't load it stops at
3.711395 mmcblk0:mmc1:1234 SA0BG 7.42gb
3.728118 mmcblk0: p1
Than did the .35 kernel and bluetooth worked but no wifi.
No more testing for me today, i'm getting ready for the last hours of 2011.
For all of you enjoy the last moments of 2011 and start 2012 with a lot of fun!!
Schumi_wk said:
Just tried the .39 kernel and bluetooth didn't work with that one. Than did the 3.0 kernel and bluetooth works but there i don't have wifi. The 3.1 kernel doesn't load it stops at 3.711395 mmcblk0:mmc1:1234 SA0BG 7.42gb
3.728118 mmcblk0: p1
Than did the .35 kernel and bluetooth worked but no wifi.
No more testing for me today, i'm getting ready for the last hours of 2011.
For all of you enjoy the last moments of 2011 and start 2012 with a lot of fun!!
Click to expand...
Click to collapse
You must understand that BT is only functional in 3.0 and .35 (well, and .27). I don't know about the state of wifi in any of 'em... Should work in .39, I thought it worked in .35 as well. Haven't booted .35 in quite some time myself. Logs are really going to be necessary to triage any of your problems tho. Thanks, enjoy New Years.
arrrghhh said:
Caveat List
The CSV files from my RHOD400 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
Click to expand...
Click to collapse
Here are my .csv files for the Tilt2 (Rhod300). Have not compared to the RHOD400 yet.
Here's my CSV files from my RHOD500
BTW, I can't use the Wi-Fi
I'm using the default kernel and settings that came in the bundle...I will try using a new data.img
Logcat says: "E/WifiService< 1328>: Failed to load Wi-Fi driver."
nickleby said:
Here's my CSV files from my RHOD500
BTW, I can't use the Wi-Fi
I'm using the default kernel and settings that came in the bundle...I will try using a new data.img
Logcat says: "E/WifiService< 1328>: Failed to load Wi-Fi driver."
Click to expand...
Click to collapse
You didn't start on a new data.img...?
This makes me think the modules didn't copy, but I force them to every time. Perhaps I should rm them all first... bleh.
You're not mixing and matching anything are you...?
arrrghhh said:
You didn't start on a new data.img...?
This makes me think the modules didn't copy, but I force them to every time. Perhaps I should rm them all first... bleh.
You're not mixing and matching anything are you...?
Click to expand...
Click to collapse
I'm using a new data.img, but the wifi still not work...I'm using the rootfs, zimage, kernel, initrd, startup.txt and system.ext2 that came in the bundle, I just added my ts-calibration
nickleby said:
I'm using a new data.img, but the wifi still not work...I'm using the rootfs, zimage, kernel, initrd, startup.txt and system.ext2 that came in the bundle, I just added my ts-calibration
Click to expand...
Click to collapse
Hrm. Can you pull some logs? I tested wifi every which way and it was always working. I did make some rootfs tweaks, so I guess it's possible it's using the wrong firmware...?
Someone had a wifi issue, rebooted and it went away. I hate wifi .
Yay! Merry Christmas and Happy New Year guys. Can't wait to try this and get back on .39. And sort-of hot-swapping kernels? Sweet.
arrrghhh said:
Hrm. Can you pull some logs? I tested wifi every which way and it was always working. I did make some rootfs tweaks, so I guess it's possible it's using the wrong firmware...?
Someone had a wifi issue, rebooted and it went away. I hate wifi .
Click to expand...
Click to collapse
I rebooted the phone, but it doesn't work...Here's a logcat, if you need another type of logs, please tell me...
nickleby said:
I rebooted the phone, but it doesn't work...Here's a logcat, if you need another type of logs, please tell me...
Click to expand...
Click to collapse
I just see a lot of this
E/WifiService( 1320): Failed to load Wi-Fi driver.
So uh... I think that indicates a modules mismatch? rm -rf /lib/modules and rebootski. I guess I need to make that change in init... copying and extracting every time doesn't work.
Please accept my apologies if this has been answered before. I did a search and did not find a similar problem. I am a noob and will read any guide or how to that you refer me to in order to learn how to get better. I am new to Ubuntu/Linux and terminal but if you point me in the right direction I can probably figure it out. I will try to provide as much detail as possible.
I have recently built a Jelly Bean AOSP ROM following this XDA Guide.
I am using Ubuntu 10.04 LTS x64.
repo synced with this branch
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.1_r3
which is build JRO03H
I downloaded and extracted the binaries on the Nexus Binairies page. I did notice that prior to building that unlike the ICS branches the JB device/samsung/toro folders do not have a extract-files.sh file
I made an otapackage using the full_toro-userdebug command.
I flashed the rom using ClockworkMod 6.0.1.0. I did a factory reset and wiped the cache prior to flashing. I also installed gapps-jb-20120726. Everything booted up fine and for the most part everything works except for the camera app. When I press the camera button I receive a message that says "Unfortunately, Gallery has stopped working." Or I get a black screen and nothing happens then I'm back in the app drawer. I have tried fixing the permissions and that did not fix the problem.
Can you explain to me what I need to do to get my camera and gallery app working? This is the only issue I have with my rom thus far. Do I need to extract the camera binary some how?
The camera and everything works fine my AOSP IMM76L build but not with my JB Build.
I have flashed other roms such Peter Alfonso's JB rom and his camera works fine, so any directions or links would be greatly appreciated.
Seeing the same.
I have this same JRO03H build (except I use CentOS 6.3 to compile AOSP 4.1.1_r3) with the EXACT same issue you describe. When the camera applet is selected it complains "Unfortunately, Gallery has stopped". Everything else in the build (24hours+ fresh) appears okay so far.
I fixed it.
I figured out the problem and was able to get the camera and everything to work. I did a couple of searches on Google and came across a thread from Android Central. I cant post the link since I have less than 10 post, but pm and I will send it to you.
We are still missing some proprietary files. Namely 6. The camera is named ducati or something and you have to either get it from another rom or extract it from ICS. I personally used Peter Alfonso's github for Jelly Bean and compared his vendor folder to mine and copied lines from his make files. Took me a couple of hours of comparing every file to realize that you need to focus on vendor some other files in core folder.
You can get his github information from his webpage and also look inside his OTA compared to your OTA to make it work. Also if you want to use Google Wallet you are going to have to edit your build.prop file in your OTA to make it not say full_toro use the 4.0.4 release keys.
I'm not at my testbox to walkthrough the steps but that's what I did. But sure to backup your source folder before you start tweaking, Came in handy twice before I got it right.
Hope that helps. Good luck.
could you please share your Rom? I also have the same issue. but still not fix it.
paternal_techie said:
I figured out the problem and was able to get the camera and everything to work. I did a couple of searches on Google and came across a thread from Android Central. I cant post the link since I have less than 10 post, but pm and I will send it to you.
We are still missing some proprietary files. Namely 6. The camera is named ducati or something and you have to either get it from another rom or extract it from ICS. I personally used Peter Alfonso's github for Jelly Bean and compared his vendor folder to mine and copied lines from his make files. Took me a couple of hours of comparing every file to realize that you need to focus on vendor some other files in core folder.
You can get his github information from his webpage and also look inside his OTA compared to your OTA to make it work. Also if you want to use Google Wallet you are going to have to edit your build.prop file in your OTA to make it not say full_toro use the 4.0.4 release keys.
I'm not at my testbox to walkthrough the steps but that's what I did. But sure to backup your source folder before you start tweaking, Came in handy twice before I got it right.
Hope that helps. Good luck.
Click to expand...
Click to collapse
wangyu7988 said:
could you please share your Rom? I also have the same issue. but still not fix it.
Click to expand...
Click to collapse
I am uploading to mediafire as I don't think I have a high enough post count to post the rom here.
Hey guys,
I am having a problem patching the 11-18 IOKP build for use as my second ROM on my S4. I am using chenxiaolong's PATCHER app, so his DUALBOOTPATCHER supports IOKP and have never had a problem with it until now. Whenever I drag the IOKP .rar file to the "patch-file" batch file to patch it, it gives me an error. When the batch file is extracting the ramdisk, it says " ---ERROR BEGINS--" Ive included a screenshot of the entire error its giving me. Ive even tried to patch the boot.img file with no luck. I would ask chen himself, on his thread, but XDA wont let me since im new. Any help will be greatly appreciated. Thanks! :highfive:
also
also im using CWM and Dirty Unicorn as my primary ROM
Anything guys?? I still cant figure out why im getting this error. Any help would be great!:fingers-crossed:
I'm pretty sure you have to use touchwiz as primary unless something has changed that I don't know about
Ive been using Dirty as my primary since it has been available for tmo and IOKP as my second ROM with no problems before the 11-18 build. I haven't had any problems until now. Plus, I talking about the DualBootPatcher file that automatically patches a ROM to use as your second ROM. Whenever I try to patch the 11-18 IOKP .rar file, it gives me the error that is shown in the picture I uploaded. Thanks though man!
The zip will change the system build.prop build fingerprint and description to match the vendor prop.
This will stop the "There's an internal problem with your device" dialog on boot.
This should work with any ROM and vendor combination.
Installation
Flash after every ROM flash
Download
Zip is attached to this post
Changelog
1.0 - Initial Release
Hashbang173 said:
The zip will change the system build.prop build fingerprint and description to match the vendor prop.
This will stop the "There's an internal problem with your device" dialog on boot.
This should work with any ROM and vendor combination.
I have tested this with my own device so far.
Installation
Flash after every ROM flash
Download
Zip is attached to this post
Changelog
1.0 - Initial Release
Click to expand...
Click to collapse
Hey there,
I already made an update-zip package that generates the /vendor/build.prop file from scratch with the information found in /system/build.prop. Does your zip do the same?
Cheers gladiac
gladiac said:
Hey there,
I already made an update-zip package that generates the /vendor/build.prop file from scratch with the information found in /system/build.prop. Does your zip do the same?
Cheers gladiac
Click to expand...
Click to collapse
My zip does the opposite, it updates the build desc and fingerprint on the system build.prop.
I chose to do it this way so users easily tell what vendor they are on.
This also leaves open the opportunity to give users a warning message in recovery when they flash a ROM on an old vendor. (I have not yet implemented this in the flounder device tree)
Thx for your work... As i understand your way to fix it will be a problem for nightly flashers right? If you change system/build.prop it will be replaced with every flash of a new nightly right? So for nightly flashers @gladiac's way of changing the values in vendor will stay if you flash a new nightly. Or am i missunderstanding this?
Donald Nice said:
Thx for your work... As i understand your way to fix it will be a problem for nightly flashers right? If you change system/build.prop it will be replaced with every flash of a new nightly right? So for nightly flashers @gladiac's way of changing the values in vendor will stay if you flash a new nightly. Or am i missunderstanding this?
Click to expand...
Click to collapse
Well, modifying /vendor could break verity...
Hashbang173 said:
Well, modifying /vendor could break verity...
Click to expand...
Click to collapse
Agree with you, but more comfortable
maybe isnt the right topic.. but every time i flash a rom when android starts gave me always the same error..with every rom!.. or maybe that i need the latest vendor.....god why??