Related
There is an awesome (non-root might i add) app for those who don't like your info being shared with anybody called PDroid that can be found here;
http://forum.xda-developers.com/showthread.php?t=1357056
Among its huge feature arsenal is the ability to block app's from seeing your IMED, SIM details, sms/mms, etc. It consumes no battery life at all and is very customizable. the only downside is that you must make a patch for each device and each ROM. i took the liberty of making said patch for the Ba2tF CM7 ROM and have posted the CWM-flashable zips for your enjoyment. all you have to do is boot into CWM and flash. if for some reason you don't want your phone to be awesome you can flash the "restore" zip and the original files will be back.
I am not responsible for literally a single thing you do with these files. have fun.
If you found this helpful or just enjoyable to read the thanks button is somewhere down to the right.. but whatever you do, don't hold down shift while you press it!
UPDATE: PDroid is not yet compatible with ICS/CM9 but the dev is actively working on supporting this, so sit tight and i will update the OP when he does so.
Since it works on Ba2tf, would it also work on weekly/nightly builds?
It is very rom specific, i wouldnt use my zip for Ba2tF with that rom.
Sent from my MB860
IUH1991 said:
Since it works on Ba2tf, would it also work on weekly/nightly builds?
Click to expand...
Click to collapse
It does work just fine on Neutrino ROM which is based on the weekly builds.
I have created patches for Dorians Redpill, Ba2tf, Neutrino GT/GT+ will also be creating one for EE shortly. I will post the patches for the API for PDroid shortly.
BTW this privacy app is awesome! You just need Linux to create a API patch for your phone.
EDIT: I had to create a new post to add the attachments..... kept failing every time I tried to add here. See post below.
Below are the API patches required to run PDroid for the specific ROMs. RESTORE patch included to remove the patch if it doesn't work. lol Don't hold me responsible if they don't work or if something funky happens..... but it worked for every ROM I have tested it on.
Keep in mind you don't need to be rooted to run the app, but you need to be rooted to run the patch.
EDIT: Also remember if your ROM ever gets updated odds are you will have to create a new patch for the newest version.
I got a PM from the dev today who had some good news.. Previously the patch maker was only available for Linux..
The good news is that you now can make a patch for your ROM yourself. Check out the PDroid patcher for Windows in the PDroid thread: http://forum.xda-developers.com/showthread.php?p=19570091. Or download it directly: http://goo.gl/oztqS.
Click to expand...
Click to collapse
Thanks for the info.
Setting up to try my hand at rom devel soon; once cm9 is a bit more stable ill build from git. Have compiled source for "true" linux but not android.
Since I'm making it security centric, this could be a nice addition. Will be researching further.
Sent from my MB860 using xda premium
I have been using LBE Privacy Guard, which revokes these permissions and more on an app-by-app basis. It's not ROM specific but a little time-consuming setting up rules for each app.
I don't have access to Linux unfortunately at the moment. Can someone make a patch for redpill-cm7?
Sent from my unlocked Motorola Atrix.
kshiuan said:
I don't have access to Linux unfortunately at the moment. Can someone make a patch for redpill-cm7?
Sent from my unlocked Motorola Atrix.
Click to expand...
Click to collapse
You don't need Linux. There's a link for the Windows version a few posts above mine.
Sent from my MB860 using xda premium
georgelopez said:
You don't need Linux. There's a link for the Windows version a few posts above mine.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
If you look on his original post (the developer's), you will see that there is a bug in the windows autopatcher. So yes...I do need Linux.
Oops...looks like I had someone on ignore who's done the work for me. Will send over a thanks anyways. Bygones.
schwann said:
If you look on his original post (the developer's), you will see that there is a bug in the windows autopatcher. So yes...I do need Linux.
Click to expand...
Click to collapse
You're absolutely right. Seems like the developer updated his OP right before I posted. Although, it does say to check back soon.
Sent from my MB860 using xda premium
ToALL
Can anybode made a patch for Neutrino ROM 1.4-S ?
What exactly does this do? If it's good, I might as well cook it in Neutrino
Notorious544d said:
What exactly does this do? If it's good, I might as well cook it in Neutrino
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1357056 read this.
Perfect patch for manual changing permissions of appz.
zhuchella said:
http://forum.xda-developers.com/showthread.php?t=1357056 read this.
Perfect patch for manual changing permissions of appz.
Click to expand...
Click to collapse
WOW, that's pretty sick!!
Notorious544d said:
WOW, that's pretty sick!!
Click to expand...
Click to collapse
it is! if you do bundle it make sure to also bundle the app or put a link to the market or something so users know!
schwann said:
I don't have access to Linux unfortunately at the moment. Can someone make a patch for redpill-cm7?
Sent from my unlocked Motorola Atrix.
Click to expand...
Click to collapse
Semi OT but...
If you have a cd drive, dvd drive, or usb drive you can run pretty much any nix distro in a "live cd" environment.
Sent from my MB860 using xda premium
n1ckr0th said:
it is! if you do bundle it make sure to also bundle the app or put a link to the market or something so users know!
Click to expand...
Click to collapse
My update will have the tweak and the app integrated
I can't thank you enough for the patch n1ckr0th. I've been using droidwall and an app called permissions to stop other apps from sending my data out. Now it's up to me who sees my real data. I understand that a lot of companies make their livings on advertisements and the like, but why do they have to know about and acquire my personal data for me to play a game or run a process that allows me to work more effectively. It's issues like this that make me want to learn how to code for android and write some great apps that won't steal everything on your device that it can see. Hmm, actually that's a good idea. Thanks again.
B.B.
Original APP folder from most current leak::
App Folder
Original Framework folder from most current leak::
Framework Folder
Tiny's One_V Port so far:
(Boots to the Bootanimation.)
tiny4579 said:
Here is my logcat, maybe someone can figure it out. I'm taking a break for now:
logcat.txt
My current ROM is below.
sense-ics-inc.zip
Click to expand...
Click to collapse
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTCCN_CHS_1.68.1400.2_Radio_20 .67.30.0831U_3831.15.00.28_M_release_254948_signed .exe
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
HTC_One_V_Ramdisk:
V_Ramdisk Download
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
PureMotive said:
I'd like to help you out with this project if you need it. There is a port of this on the DHD forums so maybe we can learn something from it:
http://forum.xda-developers.com/showthread.php?t=1545595
Click to expand...
Click to collapse
I thought of that too. But since the DInc is a 'QSD' (1000Mhz Qualcomm Snapdragon) and the Desire HD and the Desire S are 'MSM' (Mobile Station) We can't use their ports to help us :/
Being that the DInc is a qsd8k (8650 to be exact) we'll need to keep an eye out for ports with the same processor.. Oh man I wish the old Desire could get a port of this, lol. We'd have no problem at all..
Tribulattifather said:
Saw nobody was getting this started.
I am currently working on it a bit but I defenitley need help compiling a kernel.
Rom Update Utility:
RUU_PRIMO_U_ICS_40A_HTC_Europe_1.56.401.1_Radio_20.66.30.0831U_3831
(For the newbies)
Run the RUU
Wait a bit until the Rom Update Utility lets you press 'Next.'
Don't press 'Next' though,
Go to your Start Menu > Run > type in %temp%
Now sort the folder by 'Date.'
The first folder will be the folder that has a 'rom.zip' inside of it inside of the 2nd folder.
Kernel Source:
HTC Sensation XE (HTC Europe) - ICS CRC - 3.0.16 kernel source code
Look at the 9th one in the list
I hope that we can get this working for our DInc's.
Click to expand...
Click to collapse
kernel source wont help you at all for the 3.xx kernel from other htc phones, so dont bother
i ported sense 4 to the inc 2 (admittedly a lot easier cuz its msm7x30 which most of the ports are) and will give it a shot on my og inc time permitting
see inc2 port here: http://forum.xda-developers.com/showthread.php?t=1553357
the hacked .35 kernels from your ics aosp roms *should* be good (only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
When you say
nitsuj17 said:
(only need zimage) and then we d have to hack up the ramdisk from the htc one to work well enough to boot
Click to expand...
Click to collapse
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Tribulattifather said:
When you say
do you mean we'd need the zimage from HTC One V?
Edit: Updated first post with the zImage and Ramdisk that I extracted from the One V RUU.
Click to expand...
Click to collapse
no, you need the zimage from one of the ics aosp inc roms and the extracted ramdisk from the htc one v
Okay. Thank you for clarifying for me.
I'm getting down to business now ^>^
PonsAsinorem said:
Porting a ROM is one thing, porting a kernel is something else entirely.
If you've never done a port, look up wildstang83 porting guide. It'll at least point you in the right direction.
Click to expand...
Click to collapse
can u tell the link to wildstang83 porting guide thread?
orochi9999 said:
can u tell the link to wildstang83 porting guide thread?
Click to expand...
Click to collapse
★wildstang83's Guide For Basic Porting★
PonsAsinorem said:
★wildstang83's Guide For Basic Porting★
Click to expand...
Click to collapse
thank u!
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
2012oasis said:
I'd like to help if needed, have a lot of experience with ics on Og EVO don't have a inc but been working on sense4.0 Og port and kernel for a bit now..(same chipset) let me know.
Sent from my HTC OneX using xda premium
Click to expand...
Click to collapse
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Tribulattifather said:
Well, we're at a standpoint of figuring out which files need to be added/edited from the One_v ramdisk so we can make a working kernel.
Click to expand...
Click to collapse
can you get a logcat or pm me a ROM link? I'd like to look. No guarantees of success. Sadly the sense devs that could figure it out I think have left the incredible.
Also a working ramdisk still doesn't mean the kernel is good. The kernel may need some changes.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-5
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Tribulattifather said:
I'll upload the ROM port I just made a few days back. It has most of what I thought might work..
Click to expand...
Click to collapse
I'd like to try tonight if I can. I'm hoping that an HWA enabled AOSP ICS kernel works with it.
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Ahh! Excited..
Sent from my HTC Droid Incredible using Tapatalk 2 Beta-5
Tribulattifather said:
I'm uploading now. Been busy all day.
I think the only way that an HWA enabled AOSP ICS kernel will work is if we figure out which parts of the ramdisk we'll need to add to it.
I have the Ramdisk extracted and uploaded on the OP if you need it.
Edit: Upload at 38% - I have a terrible connection speed for upload bandwith, which is at 49Kb/s..
Click to expand...
Click to collapse
I'm actually stabbing in the dark as much as you. Never messed much with roms. I'm more of a troubleshooter rather than a rom/kernel chef. I find tweaks and adapt for my kernels. But I noticed there's no init.inc.rc in that ramdisk. Other than that my mind's dead so I'll have to look tomorrow/this weekend.
I apologize for the delay in posting the port link. You'll have to forgive my internet. But, I assure you that the download is as fast as I can get it with my own server that I use.
EDIT: Port is on the next page --->
Just to make sure that everyone is on the same page - This port is NOT a working port.
It will flash to the DInc and it will install properly but it does not boot. And it is obvious why, lol, because we are still missing the piece to the puzzle to make a working kernel.
I hope that this will give you what you need to get this project I started the thrust in the right direction.
As for my method thus far, I am using the zImage from and AOSP ICS port with Ramdisk parts from the One_V.
Post Script - Today is my third year anniversary being apart of XDA. And I can only hope many more years to come.
CHEERS ALL!
Hi i would like any information on how i would go about making an aosp kernel for a sense based phone.
the lack of support for this device has got me mad!! :crying:
im good with the linux side of things just need to know what is required to make an aosp kernel from sense source code??,
now obviously the sources are available for our phone but as i understand it its for a sense kernel only
so im going to start on an aosp rom for my phone, any advice or guidance would be appreciated
also would htc primo (v) be a good phome to port an aosp rom from
onejay09 said:
Hi i would like any information on how i would go about making an aosp kernel for a sense based phone.
the lack of support for this device has got me mad!! :crying:
im good with the linux side of things just need to know what is required to make an aosp kernel from sense source code??,
now obviously the sources are available for our phone but as i understand it its for a sense kernel only
so im going to start on an aosp rom for my phone, any advice or guidance would be appreciated
also would htc primo (v) be a good phome to port an aosp rom from
Click to expand...
Click to collapse
Well, i tried to port and some of the hardware works, not all.
This AOSP term to the kernel is pretty much an exageration... Mainly because PrimoU (v) runs a fully working CM9 on the sense kernel with no modifications (almost, i mean no porting or something like that).
This being said, the actually job you need to do is to find the right ramdisk configuration for it.
There are people working on this but with no experience or very little experience. Both me and anders are working on this, but i have my finals now and i will not work that hard for it, and compiling CM9 and testing it is pretty much a time-consuming job.
Well, you can start by making the enviroment ready and download the CM9 sources, hang around the irc channel and download the device tree from my github account.
hey lex just found your git while searching cms repo lol, made me smile seeing that, shame you havnt got the time right now, ill read up some more for now and see what i can do, thanks for the quick reply i appreciate your advice pal!
also would fastboot boot img be a good idea for testing
and how did you go about with the testing, eg used an aosp rom with the kernel tests or just used a logcat?
good luck with your finals btw!!
edit why has koush forked your git is he interested?
onejay09 said:
hey lex just found your git while searching cms repo lol, made me smile seeing that, shame you havnt got the time right now, ill read up some more for now and see what i can do, thanks for the quick reply i appreciate your advice pal!
also would fastboot boot img be a good idea for testing
and how did you go about with the testing, eg used an aosp rom with the kernel tests or just used a logcat?
good luck with your finals btw!!
edit why has koush forked your git is he interested?
Click to expand...
Click to collapse
He forked my git in order to get official CWM Recovery to our device, right now it does not compile for some reason, don't know why as on the same sources mine compiles... But that will be fixed some time in the future...
--
Other than that, flashing from fastboot the boot.img does not seem to me a great ideea as i like to minimise as much as possible the use of fastboot, so, i always use flashable zips for kernels, you can download one of my kernel releases and use the zip as a template, just change the files needed in it and flash at your own pleasure.
--
As for AOSP Rom and kernel, the thing is pretty much simple, at first i tried porting ROM's and things seemed to work to some degree, but not fully functional, so i figured out that the easiest way to do this is the hard way, compiling from source, putting up a device tree and so on, in this way we can keep up with any AOSP-based ROM released or that will be realeased, but as this device didn't recieved too much atention, the device tree needs to be made almost from scratch, well, i used as a template the PrimoU device tree, and made some changes to it to fit our device, but CM9 does not really like the actual tree as all that works is...booting fine, rotation, touch-screen...and that's it, also, the interface is buggy, so not usable at all, but i didn't work on it for some time now, will resume work after the finals.
--
I am also working on a project on porting 3.4.0 kernel for Dell Streak 5, this project will also benefit the future development of the custom kernel for our device, so things are still rolling around here, but at a slower pace as i'm rather new in this field.
Lexmazter said:
He forked my git in order to get official CWM Recovery to our device, right now it does not compile for some reason, don't know why as on the same sources mine compiles... But that will be fixed some time in the future...
--
Other than that, flashing from fastboot the boot.img does not seem to me a great ideea as i like to minimise as much as possible the use of fastboot, so, i always use flashable zips for kernels, you can download one of my kernel releases and use the zip as a template, just change the files needed in it and flash at your own pleasure.
--
As for AOSP Rom and kernel, the thing is pretty much simple, at first i tried porting ROM's and things seemed to work to some degree, but not fully functional, so i figured out that the easiest way to do this is the hard way, compiling from source, putting up a device tree and so on, in this way we can keep up with any AOSP-based ROM released or that will be realeased, but as this device didn't recieved too much atention, the device tree needs to be made almost from scratch, well, i used as a template the PrimoU device tree, and made some changes to it to fit our device, but CM9 does not really like the actual tree as all that works is...booting fine, rotation, touch-screen...and that's it, also, the interface is buggy, so not usable at all, but i didn't work on it for some time now, will resume work after the finals.
--
I am also working on a project on porting 3.4.0 kernel for Dell Streak 5, this project will also benefit the future development of the custom kernel for our device, so things are still rolling around here, but at a slower pace as i'm rather new in this field.
Click to expand...
Click to collapse
So then it is not only me that can't get the device tree to compile. Strange. ...
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
anders3408 said:
So then it is not only me that can't get the device tree to compile. Strange. ...
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Click to expand...
Click to collapse
You are using the ICS branch, that compiled fine, on Cyanogenmod repo is the Jellybean branch.
Lexmazter said:
You are using the ICS branch, that compiled fine, on Cyanogenmod repo is the Jellybean branch.
Click to expand...
Click to collapse
It first compiled fine after changing some stuff. Still struggling with audio
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
ok im going to do fresh setup today and get it compiled so i can test and have a look, is vold fstab ok for 1.28 s-off hboot? :fingers-crossed:
have you found any similar devices (board wise) we could take a look at? may give some insight to it..
also whats the current state of working not working, eg what works atall?
onejay09 said:
ok im going to do fresh setup today and get it compiled so i can test and have a look, is vold fstab ok for 1.28 s-off hboot? :fingers-crossed:
have you found any similar devices (board wise) we could take a look at? may give some insight to it..
Click to expand...
Click to collapse
There is 3. Desire HD , one v also called primou and incredible s also called vivo. They all uses same screen resolution , same CPU and GPU so that is the closes you get. I will soon be found at the Irc chat then we can have a look together. Just join #runny-dev at freenode, also to be found in my signature.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
onejay09 said:
ok im going to do fresh setup today and get it compiled so i can test and have a look, is vold fstab ok for 1.28 s-off hboot? :fingers-crossed:
have you found any similar devices (board wise) we could take a look at? may give some insight to it..
also whats the current state of working not working, eg what works atall?
Click to expand...
Click to collapse
Also, the current branch tree supports all hboots, you will surely still need the right vold.fstab file, but other than that, yes, is ok, i also use that hboot.
Hey what do i do about vendor srtup.sh and wheres the make directory for lex repo, had a little trouble with the build enviroment,
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Sv: How Is an aosp kernel made for sense devices ?
onejay09 said:
Hey what do i do about vendor srtup.sh and wheres the make directory for lex repo, had a little trouble with the build enviroment,
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
It is not included in his repo, if you find my repo : WWW.github.com/anders3408
The vendor files he used is there.
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
ok, figured it out thanks, whats your directory layout,
iv got
home/android_source/projects/device/htc/ now should i keep the name runnymede? (device)
home/android_source/projects/vendor/htc/ ????
ok so i extract files.sh first also then . build envsetup.sh && lunch?
also ive added the project to an xml file is that right ?
Sv: How Is an aosp kernel made for sense devices ?
onejay09 said:
ok, figured it out thanks, whats your directory layout,
iv got
home/android_source/projects/device/htc/ now should i keep the name runnymede? (device)
home/android_source/projects/vendor/htc/ ????
ok so i extract files.sh first also then . build envsetup.sh && lunch?
also ive added the project to an xml file is that right ?
Click to expand...
Click to collapse
Root of sourcefiles/vendor/htc/runnymede
And device tree in root /device/htc/Runnymede
And also the common files in HTC folder.
Then fix things envsetup.sh and lunch and buildwhatyouwant.
Then find out oh it is not working, make clobber
Then fix things and all over. No need to extract, only used when you have no vendor files.
Good idear is compare to others github
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Ok everything is setup, exept when i run . build/envsetup.sh it says no such file or directory? Am i typing in wrong folder? Or Am i missing some compile tool?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Sv: How Is an aosp kernel made for sense devices ?
onejay09 said:
Ok everything is setup, exept when i run . build/envsetup.sh it says no such file or directory? Am i typing in wrong folder? Or Am i missing some compile tool?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
I will be on irc chat after a cigaret then i will help you
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
You will need to be in the root of android sources then write it, and it should work...
Thanks think iv figured it out, iv not got android/system i pulled cyanogenmod/android.git -b ics it took 2hours/ terminal never prompted after the git pull though, what am i missing?
I must have wrong or incomplete source because i have no build directory in the repo i pulled, im at work right now so no internet connection, maybe tomorrow
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Turns out git gc had a thread issue with python, so i finally got it pulled with sync repo -j1, compiling runnymede now, is it booting with current board config etc?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Finally got a full build of cm 9, had to set
Board_uses_qcom_audio_resetall :=false in boardconfig common.mk in msm7x30 just to get it to compile
Ive added for now a stub
Board uses generic audio = true
so no audio in this build yet
Any advice?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
onejay09 said:
Finally got a full build of cm 9, had to set
Board_uses_qcom_audio_resetall :=false in boardconfig common.mk in msm7x30 just to get it to compile
Ive added for now a stub
Board uses generic audio = true
so no audio in this build yet
Any advice?
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app
Click to expand...
Click to collapse
Well, i got it fully built and booted with my current device repo, and anders reported he managed to get it compile only by using cyanogenmod's 7x30 common repo, i can't remember what common i used, but since he reported that, then most probably i used that too.
The kernel that will result in the flashable zip is unusable because of the ramdisk, i have a good ramdisk that get it booted so i need to update the repo when i have time with the right ramdisk so the resulting flashable .zip will work, probably.
Also, i did some changes in the flashable .zip to get some things working, so everything is pretty much WIP and i need to get past the finals to resume my work on this, so be patient and try to join IRC channels where other developers are hanging, so you can ask more experienced developers.
I'm pretty much a newbie in this field, as i didn't compile from source a fully working ROM so far.
I got working Recoveries on 2 devices for now, fully working ones so, this is pretty much what i can do, incorporate things in kernels and port recoveries from scratch.
UnityROM-2 v.2.5.0
*****Discontinued.... No way to test actively till I have a functional build.*****
HTC One M7 Sprint Edition ( m7spr )
Development Section...
Want to contribute to the project or become team member?
Contact Me by PM here or leave a post detailing what you can and are willing to do for the projects' advancement.
My Github: https://github.com/LiquidSmokeX64
All current project sources can be found there .
ALSO MY FOOL-PROOF BUILD GUIDE & SCRIPTS ARE THERE FOR THOSE TOO IMPATIENT TO WAIT FOR MY NEXT RELEASE .
**Sources current as of version 2.5.0**
**10/06/2014**
Direct link to guide:
https://github.com/LiquidSmokeX64/Guides-Scripts
Note: Noob Friendly. If you're new to building ROMs or have never done it at all. I will help for as long as you maintain civility and focus on the project goals.
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
gruesomewolf said:
Installation errors out. Here is a pastebin of log saved after error
http://pastebin.com/fz15gwwn
Edit: I was able to install after removing that set perm line from updater. I will let ya know how it goes.
Click to expand...
Click to collapse
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
LiquidSmokeX64 said:
Ok. I just removed it too. My bad adaptation from Evo LTE. Nothing too bad luckily.
Reuploading the fixed version now.
Click to expand...
Click to collapse
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Notorious said:
Will you be releasing this kernel for the Evo 4G? [emoji14] Evo4gnoob here
Click to expand...
Click to collapse
Umm....no I dont have any plans for that ATM
gruesomewolf said:
I wouldn't say Im a kernel dev....more of a dabler...lol. I sent you a pm with my makefile so you can see adjustments I made for my kernels latest build (not yet publicly released)
Umm....no I dont have any plans for that ATM
Click to expand...
Click to collapse
Was joking lol
Notorious said:
Was joking lol
Click to expand...
Click to collapse
So you're allowing the integration of it? Just to be clear.
So I'm not sure why but the kernel borked again. Maybe I need to go through one flag at a time? Or maybe forgot something....?
gruesomewolf said:
Seems to be running very well, once I got past that installation error....
Nice and smooth, especially with my aosp kernel...
Click to expand...
Click to collapse
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
LiquidSmokeX64 said:
Hey. Im having nothing but issues building it in the ROM so I was curious if you could tell me what I need to do after copying the msm8960 folder to a new place and adding in the makefile changes? Ive never built a kernel independently before but would like it to be a boot.img like normal so I can just replace the one in the ROM zip with the new one. Im sure it's pretty easy, just figured I'd ask you rather than comb through 80 guides saying different stuff lol.
Click to expand...
Click to collapse
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
I'm not seeing errors. Hell I removed everything but the -O3 spots and it still refused to boot. I dont know what the deal is....
Anytim I do ANYTHING to the kernel its dead, no matter how stupid it is.
gruesomewolf said:
Could you pm me with more info. Exact process of building, errors during build, any changes made to source, etc.
I'm gonna download your source later, together we should be able to figure this out.
Click to expand...
Click to collapse
BTW. The makefile is borked. And was curious if you knew how to build AOSP for this device? CM was pretty easy, I'd figure AOSP isn't too different. Then I can try to get Android L running once I have a working Android K to cross-reference to and make the version specific changes in device, kernel, vendor, qcom-common, and s4-common
LiquidSmokeX64 said:
So. You're a kernel dev... Got a question for you. How do I add more CFLAGS to the makefile without it not booting or whatever? I've tried adding -O3 to the 2 places I know to put CFLAGS. Same place I put the -w so it would work with GCC 4.8
Click to expand...
Click to collapse
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
thicklizard said:
When certain flags or 03 is added it creates a larger zImage. In order to compensate the boot.img needs needs modified, either by kernel installer or if baked in the rom hex edited. To change the ramdiskaddr.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
gruesomewolf said:
Absolutely correct. And to elaborate on this just a bit more. Since your source building here, you can actually adjust the ramdiskadd with the scripts, considering it uses mkbootimg commands to build the boot.img.
An additional line in your devices board config, to give it a new ramdiskaddr size. Then an additional line in the build folder factory_ramdisk.mk , to handle the command for a new ramdiskaddr size should do the trick.
As for your other question about building aosp. I'm afraid that would be beyond my area of expertise. You would have significantly modify aosp code to allow for caf. It would be much harder then building cm, cause cm already has all the adjustments needed for caf devices
Click to expand...
Click to collapse
I read this and my eyes glaze over. But you are in good hands with these two helping you. :highfive:
Yeah I'm working on it guys. Read the integrated kernel building guide and trying that. But if I could just get it to build me the boot.IMG and get my ramdisk sizes and whatever I'm looking at where to edit it in the device/BoardConfig changed the defconfig to a custom one I made based off the original one from the working boot.IMG but changed the I/O scheduler & CPU governed defaults. Gave it a local name (UnityKernel-x.x.x) and am fighting its last issues. So if nothing else help building it independently might be the most useful now. So if nothing else I can push a new boot.img
My bad. It just says the boot partition size so I think I might be almost there
Hey Guys,
anyone tried (sucessfully) to mount a NAS-Share on the Amazon Fire?
Im new to Folder Mounting on Android in General, but what i've learned so far (pls correct me if im wrong!) that your kernel needs to support cifs, witch is nowhere by default. So one could
- compile/patch the Kernel with cifs Components
- Use a functioning cifs.ko together with CifsManager
First one im definitly too dumb to do
Latter one i tried without success with several *.ko floating around. Maybe i found a work working, but didnt configure it properly?
So, anyone has a working solution for mounting a network folder?
dafunkydan said:
Hey Guys,
anyone tried (sucessfully) to mount a NAS-Share on the Amazon Fire?
Im new to Folder Mounting on Android in General, but what i've learned so far (pls correct me if im wrong!) that your kernel needs to support cifs, witch is nowhere by default. So one could
- compile/patch the Kernel with cifs Components
- Use a functioning cifs.ko together with CifsManager
First one im definitly too dumb to do
Latter one i tried without success with several *.ko floating around. Maybe i found a work working, but didnt configure it properly?
So, anyone has a working solution for mounting a network folder?
Click to expand...
Click to collapse
At one time Nexus ROM included support for CIFS components; not sure if that functionality made it into build for this device. Kernel can not be patched with a locked bootloader so may be a nonstarter.
Davey126 said:
At one time Nexus ROM included support for CIFS components; not sure if that functionality made it into build for this device. Kernel can not be patched with a locked bootloader so may be a nonstarter.
Click to expand...
Click to collapse
I should/might be able to build CIFS support as a kernel module. However last time I had it working due to changes in the upstream linux kernel CIFS Manager can no longer work. When I am up and running again I'll take a look.
Sounds really cool dude!
So, as the bootloader is locked, u wanna give the cifs manager a shot? Would be really awesome if its working!
ggow said:
I should/might be able to build CIFS support as a kernel module. However last time I had it working due to changes in the upstream linux kernel CIFS Manager can no longer work. When I am up and running again I'll take a look.
Click to expand...
Click to collapse
Hey ggow, did you have a chance to take a look and see if there's a possibility? Hope u dont mind me getting back to you!
dafunkydan said:
Hey ggow, did you have a chance to take a look and see if there's a possibility? Hope u dont mind me getting back to you!
Click to expand...
Click to collapse
I'll be working on a new build this week, so will definitely look into it before release.
Sent from my Fire Phone using Tapatalk
Awesome! Thankin u - im excited and crossing the fingers
dafunkydan said:
Awesome! Thankin u - im excited and crossing the fingers
Click to expand...
Click to collapse
- Good news overall
- I have compiled the required modules from the Amazon Fire Kernel sources
- Seems to be working in principle
- I can mount a network share via shell command prompt
- I can copy files to and from the share
- However I need to figure out how to let android apps see the mounted file systems
Edit:
- managed to setup a share using cifs manager [emoji3]
- Can now see the files now from a file manager
- Still needs some testing though
ggow said:
-
- managed to setup a share using cifs manager [emoji3]
- Can now see the files now from a file manager
- Still needs some testing though
Click to expand...
Click to collapse
Yieeehhhaa Wicked!!! Thats really really good news! You are the Man
When you need a Tester or whatever just let me know. Thats awesome! :good:
dafunkydan said:
Yieeehhhaa Wicked!!! Thats really really good news! You are the Man
When you need a Tester or whatever just let me know. Thats awesome! :good:
Click to expand...
Click to collapse
I'll include it in the next release, with some instructions on how to use it.
Awesome!!! Both Thumbs up! Cant wait for it!
Thank u so much, highly appreciated!!!
dafunkydan said:
Awesome!!! Both Thumbs up! Cant wait for it!
Thank u so much, highly appreciated!!!
Click to expand...
Click to collapse
- New Release is out with CIFS Support and User Guide is here