Develop Bugs

{Kernel-Source} GoDmOdE-2.6.29-GSM-HERO

i have pushed the board files to my github to compile a fully working kernel for the GSM Hero. i dont own the device, but Behnaam has been working with me testing and such. anyhow everything works. the link to my source can be found below:
GoDmOdE-KeRnEl-SoUrCe
anyhow enjoy i do this for the community and ask for nothing but in return. Devs have at it!!!

Behnaam already beat you to the punch, link.

gu1dry said:
Behnaam already beat you to the punch, link.
Click to expand...
Click to collapse
i seen but i can update this one plus i guess i forgot to add two files . btw they are there now and it will compile for sure. (i just did it) enjoy

will it say no more huge battery drain ?

Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
EDIT: Had a lapse and forgot to compile a new wlan module... will reupload after school today
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone

zjr8 said:
Quick and dirty compile by me in boot.img format (too tired to hack an update.zip together)
Credit to: Benocharm, and well everyone else who worked on this project... i just compiled it lol
Cant post links yet sooo h**p://w w w .mega upload. c o m/ ? d = 724NZ7Q1
** = tt
remove spaces
Method One Flash: (For those with unlocked SPL)
fastboot flash boot newBoot.img
fastboot reboot
Method Two Flash:
adb push boot.img /sdcard
adb shell
cat /dev/zero > /dev/mtd/mtd2
- write: No space left on device [this is ok, you can ignore]
flash_image boot /sdcard/boot.img
reboot your phone
Click to expand...
Click to collapse
Here ya go mate
http://www.megaupload.com/?d=724NZ7Q1

Are the video drivers included?

MerXury13 said:
Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn

Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)

Are the video drivers included?
Click to expand...
Click to collapse
I think that's very basic that they check it .
I'm more curious about other things that are not so obvious while testing:
volume keys while sleeping, battery usage, g-sensor, correct behavior of the audio jack (audio switches to jack instead of speaker), etc...
'gsm long text > 160 chars' issues can't have anything to do with the kernel used as I see it. That's something of the messaging app and / or the radio RIL used.
Hmm, new kernel to play with... might be the push I needed to try building my own android stuff to learn
Click to expand...
Click to collapse
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk

MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform

I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
It's too early for me^^ sorry

dipje said:
dude, he only did that on his 'OC' version. The normal 'stable' version has them... reading is an artform
Click to expand...
Click to collapse
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.

MerXury13 said:
I asked 'cause in the cronos Rom, the developer said that he excluded the Video drivers to f**k up the other devs ...what a jerk
Click to expand...
Click to collapse
Again... getting boring

Can someone please compile this one with overclock patch?I have no idea how to compile from source else I would do it

l0st.prophet said:
The normal 'stable' version of his ROM is built on the same test kernal that every other 2.1 ROM is built on.
Click to expand...
Click to collapse
Hence it got video drivers

Can anyone point me in the direction of a good write up on how to build a boot.img from this git repo please?im using ubuntu 10.4

so can we use this kernel on the vanilla roms?

anon2122 said:
Am I missing something with regards to the wlan module sources? Didn't see them so far...
Or am I being stupid (highly likely)
Click to expand...
Click to collapse
Do you have the latest commit? I believe initially there were some missing files. I know when I grabbed the source the first time i had wlan drive compile issues

I applied this to both cronos rom and to superhero rom and both got really sluggish after installing it (I used the boot.img posted among the first posts).

[DEV] UK Stock System Dump - Build ITL41D

Going to preface this with the fact that I'm relatively new to the dev scene. I'm still learning, but we all learn by doing right?
This dump is taken from my rooted UK retail O2 Galaxy Nexus. Rooted using adb method (not superboot method) - http://forum.xda-developers.com/showthread.php?t=1352004
Not entirely positive these are done perfectly (especially the .zip) but I think that may creatable from my dd image anyways. I'd appreciate someone with dev experience looking over these and okaying them, and maybe regular users staying away from trying to do anything with these until someone more experienced says they're alright?
I just figured that seeing I uploaded these for 2 people I may as well make them publically available for all.
I'm also including the steps I took inside code tags for anyone to point out any mistakes I may have made.
DD Image as requested by Maximilian Mary:
Code:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/sdcard/galaxynexussystem.img
Available here: http://www.megaupload.com/?d=KXFYSMT2 or http://multiupload.com/CPP4L2553Y
Zip file as originally requested by Revolution
I followed http://www.robmcghee.com/android/creating-an-android-update-zip-package/ - Thinking back I realise I probably didn't need to sign it, whoops
Code:
## Create folders dump, dump/system, dump/META-INF/com/google/android
cd dump
adb pull /system system
## Edited /META-INF/com/google/android/update-script with:
## show_progress 0.1 0
##
## copy_dir PACKAGE:system SYSTEM:
## set_perm_recursive 0 0 0755 0644 SYSTEM:app
## show_progress 0.1 10
##
## Zip system and META-INF folders into gnsys.zip
## Signed using testsign.jar
Available here: http://www.megaupload.com/?d=KXFYSMT2 or http://www.filesonic.com/file/3935308085/gnsys-signed.zip
If anyone spots anything wrong with either my commands or my files, please reply with what I did wrong so I can learn from that, thanks.

el3ctrik said:
Going to preface this with the fact that I'm relatively new to the dev scene. I'm still learning, but we all learn by doing right?
This dump is taken from my rooted UK retail O2 Galaxy Nexus. Rooted using adb method (not superboot method) - http://forum.xda-developers.com/showthread.php?t=1352004
Not entirely positive these are done perfectly (especially the .zip) but I think that may creatable from my dd image anyways. I'd appreciate someone with dev experience looking over these and okaying them, and maybe regular users staying away from trying to do anything with these until someone more experienced says they're alright?
I just figured that seeing I uploaded these for 2 people I may as well make them publically available for all.
I'm also including the steps I took inside code tags for anyone to point out any mistakes I may have made.
DD Image as requested by Maximilian Mary:
Code:
su
dd if=/dev/block/platform/omap/omap_hsmmc.0/by-name/system of=/sdcard/galaxynexussystem.img
Available here: http://www.megaupload.com/?d=KXFYSMT2
Zip file as originally requested by Revolution
I followed http://www.robmcghee.com/android/creating-an-android-update-zip-package/ - Thinking back I realise I probably didn't need to sign it, whoops
Code:
## Create folders dump, dump/system, dump/META-INF/com/google/android
cd dump
adb pull /system system
## Edited /META-INF/com/google/android/update-script with:
## show_progress 0.1 0
##
## copy_dir PACKAGE:system SYSTEM:
## set_perm_recursive 0 0 0755 0644 SYSTEM:app
## show_progress 0.1 10
##
## Zip system and META-INF folders into gnsys.zip
## Signed using testsign.jar
Available here: http://www.megaupload.com/?d=KXFYSMT2
If anyone spots anything wrong with either my commands or my files, please reply with what I did wrong so I can learn from that, thanks.
Click to expand...
Click to collapse
Thanks
Let my ROMs rock
---------- Post added at 03:46 PM ---------- Previous post was at 03:34 PM ----------
netchip said:
Thanks
Let my ROMs rock
Click to expand...
Click to collapse
UPDATE: I've unpacked the img file and imported the proprietary files.
So we can make ROMs

It appears MU is returning an error if you try to access the files.
I've uploaded the 2 files to other mirrors too, apologies if anyone has tried to grab these and failed.

I'm about to have some fun with this right now , i'm home from school i'm about to eat & work on something .

netchip said:
UPDATE: I've unpacked the img file and imported the proprietary files.
So we can make ROMs
Click to expand...
Click to collapse
I don't get it. What's here that's not at http://code.google.com/android/nexus/drivers.html#maguroitl41d ?
Sent from my Nexus S using XDA App

matt2053 said:
I don't get it. What's here that's not at http://code.google.com/android/nexus/drivers.html#maguroitl41d ?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That arent not all the needed files
Sent from my GT-I9100

Can I ask for boot image as well?

mike1986. said:
Can I ask for boot image as well?
Click to expand...
Click to collapse
You can generate your own with the AOSP repos
Sent from my GT-I9100

netchip said:
You can generate your own with the AOSP repos
Sent from my GT-I9100
Click to expand...
Click to collapse
Got one already, thanks

Why do you work with every single device , just saying ? Are you going to get the Galaxy Nexus , cause your doing work for the Amaze also now . I don't get it .
mike1986. said:
Got one already, thanks
Click to expand...
Click to collapse

Revolution said:
Why do you work with every single device , just saying ? Are you going to get the Galaxy Nexus , cause your doing work for the Amaze also now . I don't get it .
Click to expand...
Click to collapse
Because I like what I'm doing Is there any problem with it?

Nope , just asking a question .
mike1986. said:
Because I like what I'm doing Is there any problem with it?
Click to expand...
Click to collapse

@mike1986 - You cooking up anything for the DHD?

Running Init.d Script On Our Galaxy W

Hi everyone, i've such a good news for all the galaxy w users. I've tested that our device can run init.d script on startup(currently with Bionic Cow 1,dont know whether stock rom works or not). Here is the original post from DOOMLORD.
http://forum.xda-developers.com/showthread.php?t=1236446
Here is the guide for our device to run and support init.d script on startup:
What you need:
1)CWM for galaxy w
2)The file from DOOMLORD (init.d-autorunner-stock.zip),you can download from his original post (http://forum.xda-developers.com/showthread.php?t=1236446)
Step:
1)Boot to cwm recovery and do nand backup first(Just in case if got bootloop,you still can restore)
2)After backup, go to ADVANCE menu and mount system (this is important,if you didnt mount system, then the flash will not be install)
3)Select the file that you have download and flash it.
Test:
1)The easiest way to test whether the script running or not is to install ZEPPELINROX V6 supercharge script.
2)when install the script, do select to integrate to build.prop and enable init.rc
3)if you have installed the v6 script, please do unsupercharge first and do a clean install of the script. DO NOT RESTORE, cause restore will not make the script to auto start.
Hopefully this will help COWITHGUN to implement this to his next BIONIC COW 3.
EDITED:
i've try new improvement to our device. if you are using custom rom, you may wanna try this.first, you need to un-supercharge and download the adrenaline engine from this post by IMBAWIND :
http://forum.xda-developers.com/showpost.php?p=24390564&postcount=2
then,flash it using cwm recovery. when flashing remember to mount the /system/ first. And do remember, after flashing this adrenaline engine, you no need to supercharge again. cause the script is included inside already. try it out guys, and post your comment. happy modding!!

come on....56 views but no one dare to test or give comment???? i need to know whether it works with all of your gw or not!!! we supposed to share and learn. pls give comment. thank you.

Gonna try as soon as I come back home.
Sent from my GT-I8150 using XDA

Ehm, the files he provied are still update-scripts?

the flash file it self doesnt hv script inside. we need to install script by ourself. what i can suggest is v6 supercharge and adrenaline script. i hv combine this 2 script in my phone and it work like charm. i hv use it for a week without problem and battery for heavy 3g internet usage can last for 7 hours. try it and let every user know.
Sent from my GT-I8150 using XDA

It works, amazing find mate

you are welcome.....so now we can get rid of script manager already!!!

jamestts said:
you are welcome.....so now we can get rid of script manager already!!!
Click to expand...
Click to collapse
Indeed, too bad people don't seem to understand how awesome this is

Haha....sharing is caring. I just want sammy to know how good is thier phone, and how bad is it for us without ics update. If sammy really care for thier customer,surely they hv a team to develope new ics for us.
Sent from my GT-I8150 using XDA

Guys, can I ask.....
I am going to try this on stock ROM, just to see will it work......
I have Zepps V6 SC already, so I need to UnSuperCharge????
This installs run-parts binary in /system/xbin/run-parts (which is basically busybox 1.16.2 binary)
Will this overwrite already installed run-parts [Busybox]
I'm using stericson installer, and have busybox 1.19.3 already installed...
Also, is there not a test script called installed /system/etc/init.d/99test
Code:
#!/system/bin/sh
touch /data/local/tmp/init.d_log_test.txt
echo "done" >> /data/local/tmp/init.d_log_test.txt

Thanks for interesting with my topic. First, and yes you need to unsupercharge first. It will replace the run-parts, but you can copy and paste the command that you have inside. And make sure set back the permission. And last,it does hv 99test,but i think it doesnt matter for me.
This autorun init.d actually can run at most firmware....include stock. Just make sure u hv cwm recovery and make nand backup. When u flash,make sure u mount system in advance menu.
Happy trying.
Sent from my GT-I8150 using XDA

It works, thanks!

OK...I'll give it a go today.....
Just on the Busybox version, can't I run the stericson BB Installer again after I flash the init.d zip via CWM???
Ohh, and that 99test thing, it's just to verify that init-d has worked.....
if it works, all scripts which use init-d should work, including our beloved Zepps V6

irishpancake said:
OK...I'll give it a go today.....
Just on the Busybox version, can't I run the stericson BB Installer again after I flash the init.d zip via CWM???
Ohh, and that 99test thing, it's just to verify that init-d has worked.....
if it works, all scripts which use init-d should work, including our beloved Zepps V6
Click to expand...
Click to collapse
hi again.....yes you can still install busybox with this method. i have upgraded it to the 1.19.4 version.
thanks for the info on 99test.......glad you mention.
it should all work, i have run the v6 script again after reboot to check whether the process of v6 is 100% or not!!! by the way,fyi smuff out script is not suitable for our phone. i tried and the phone always hang when playing with angry bird space!!!

irishpancake said:
OK...I'll give it a go today.....
Just on the Busybox version, can't I run the stericson BB Installer again after I flash the init.d zip via CWM???
Ohh, and that 99test thing, it's just to verify that init-d has worked.....
if it works, all scripts which use init-d should work, including our beloved Zepps V6
Click to expand...
Click to collapse
I'm not pretty sure it will work to STOCK kernel
There is something missing to run /system/bin/sysint
Code:
"missing part" -> Run sysinit ("run-part" xbin binary to call bussybox to running the bin file) -> Run init.d folder
The missing part should have command for run sysinit
Code:
#!system/bin/sh
/system/bin/sysinit
If this run you must have init.d_log_test.txt in /data/local/tmp/ folder
If isn't not there the script is not run
Actually it's interesting
I will make one based on this
Regards

Rio Saputro said:
I'm not pretty sure it will work to STOCK kernel
There is something missing to run /system/bin/sysint
Code:
"missing part" -> Run sysinit ("run-part" xbin binary to call bussybox to running the bin file) -> Run init.d folder
The missing part should have command for run sysinit
Code:
#!system/bin/sh
/system/bin/sysinit
If this run you must have init.d_log_test.txt in /data/local/tmp/ folder
If isn't not there the script is not run
Actually it's interesting
I will make one based on this
Regards
Click to expand...
Click to collapse
hi, thanks for your information. It make sense by your explanation.
i've tried this auto init.d on both my galaxy w(cwm 5) and x10 mini pro(cwm 3.2) with stock rom. it really works, just not sure others people work or not. from the log file it all saids done. so i confirm it really works on stock. if you have others phone do give it a try, if it works, try to spread this good news. cause there is some user which dont wanna use custom rom but want to have auto script installed on stock rom.
thanks again for sharing information.

jamestts said:
Haha....sharing is caring. I just want sammy to know how good is thier phone, and how bad is it for us without ics update. If sammy really care for thier customer,surely they hv a team to develope new ics for us.
Sent from my GT-I8150 using XDA
Click to expand...
Click to collapse
Yes. Because you are special and deserve ICS while million of others don't. Take your head out of your ass for a moment and think like this:
You are Samsung executives. You own a line of smartphone called the Galaxy phones that are many and all very different from each other. Also you have MILLIONS of customers to please. Google announces ICS but only makes it available a few days prior to release. Now you have to update most of your entire line of phones in a matter of months and you had no way to prepare ahead of time for it. Do you:
1) Hire dozens of techs, programmers and testers to make updates for all your phones that you will most likely fire at the end; or
2) Hire a few that you can keep on board but only upgrade the flagship phones/tablets on your company?
If I was a Samsung executive, I would have gone for the 2nd. Why? Because no one promised ICS upgrade on phones like the Galaxy W, S, Ace, ect. Second because Google ****ing screwed up the timing in giving the manufacturers the SDK and source.
So if you blame Samsung, blame Google aswell. Also, if you blame them then get an iPhone or a WP. But shut up with your self entitlement issues.
When I bought this phone I wasn't expecting Samsung to give a middle-range, not widely known phone an ICS upgrade. I was however expecting the dev scene at XDA to grow around this phone because of its sheer potential. And guess what, I was right
I am thinking of releasing an update to my KezraVP with built-in supercharger support. I won't make promises though, because right now I am trying to get a job in Poland and thal will force me to move countries and stuff so I dunno how much time I'll have.

KezraPlanes said:
Yes. Because you are special and deserve ICS while million of others don't. Take your head out of your ass for a moment and think like this:
You are Samsung executives. You own a line of smartphone called the Galaxy phones that are many and all very different from each other. Also you have MILLIONS of customers to please. Google announces ICS but only makes it available a few days prior to release. Now you have to update most of your entire line of phones in a matter of months and you had no way to prepare ahead of time for it. Do you:
1) Hire dozens of techs, programmers and testers to make updates for all your phones that you will most likely fire at the end; or
2) Hire a few that you can keep on board but only upgrade the flagship phones/tablets on your company?
If I was a Samsung executive, I would have gone for the 2nd. Why? Because no one promised ICS upgrade on phones like the Galaxy W, S, Ace, ect. Second because Google ****ing screwed up the timing in giving the manufacturers the SDK and source.
So if you blame Samsung, blame Google aswell. Also, if you blame them then get an iPhone or a WP. But shut up with your self entitlement issues.
When I bought this phone I wasn't expecting Samsung to give a middle-range, not widely known phone an ICS upgrade. I was however expecting the dev scene at XDA to grow around this phone because of its sheer potential. And guess what, I was right
I am thinking of releasing an update to my KezraVP with built-in supercharger support. I won't make promises though, because right now I am trying to get a job in Poland and thal will force me to move countries and stuff so I dunno how much time I'll have.
Click to expand...
Click to collapse
first thank you for your comment. second....pls use nice words!!i'm not special,i'm just a human like u. if every people will think like you then we dont need this forum or any other developer like you!!! we appeal, we complaint just try to make this phone better. if we didnt complaint, how do sammy know that his customer is having so much complaint on the os upgrade??? u try to think like this way.......if there is no customer service....how ur company can improve??? no feed back???
i've tried your firmware also....no doubt it's very nice n beatiful rom. maybe u can try add in the init.d to ur rom so users can get rid of script manager. or another suggestion is add in adrenaline script v6 to your rom.
good luck in your job finding.....

KezraPlanes said:
Yes. Because you are special and deserve ICS while million of others don't. Take your head out of your ass for a moment and think like this:
You are Samsung executives. You own a line of smartphone called the Galaxy phones that are many and all very different from each other. Also you have MILLIONS of customers to please. Google announces ICS but only makes it available a few days prior to release. Now you have to update most of your entire line of phones in a matter of months and you had no way to prepare ahead of time for it. Do you:
1) Hire dozens of techs, programmers and testers to make updates for all your phones that you will most likely fire at the end; or
2) Hire a few that you can keep on board but only upgrade the flagship phones/tablets on your company?
If I was a Samsung executive, I would have gone for the 2nd. Why? Because no one promised ICS upgrade on phones like the Galaxy W, S, Ace, ect. Second because Google ****ing screwed up the timing in giving the manufacturers the SDK and source.
So if you blame Samsung, blame Google aswell. Also, if you blame them then get an iPhone or a WP. But shut up with your self entitlement issues.
When I bought this phone I wasn't expecting Samsung to give a middle-range, not widely known phone an ICS upgrade. I was however expecting the dev scene at XDA to grow around this phone because of its sheer potential. And guess what, I was right
I am thinking of releasing an update to my KezraVP with built-in supercharger support. I won't make promises though, because right now I am trying to get a job in Poland and thal will force me to move countries and stuff so I dunno how much time I'll have.
Click to expand...
Click to collapse
Take your head out of your ass for a moment and think like this:
Click to expand...
Click to collapse
KP, IMHO uncalled for and totally unwarranted attack on another contributor to our forum.....you got no right telling ppl what to think....no right at all!!!
But shut up with your self entitlement issues.
Click to expand...
Click to collapse
Where is this stuff coming from......and why do you attack ppl in such a fashion??
Everyone has got a right to their own opinion, and they are also entitled to express those without asking your permission....
Honestly, Man, I respect you for the work you have done on behalf of the community, but you disappoint me here....truely!!
I won't make promises though, because right now I am trying to get a job in Poland and thal will force me to move countries and stuff so I dunno how much time I'll have.
Click to expand...
Click to collapse
I am sorry for your employment situation, really.
We know in Ireland just what that is all about, I can assure you, I hope it works out for you......
But you gotta moderate your language and attacks on other ppl, who have just as much right as you to pass comment.

irishpancake said:
KP, IMHO uncalled for and totally unwarranted attack on another contributor to our forum.....you got no right telling ppl what to think....no right at all!!!
Where is this stuff coming from......and why do you attack ppl in such a fashion??
Everyone has got a right to their own opinion, and they are also entitled to express those without asking your permission....
Honestly, Man, I respect you for the work you have done on behalf of the community, but you disappoint me here....truely!!
I am sorry for your employment situation, really.
We know in Ireland just what that is all about, I can assure you, I hope it works out for you......
But you gotta moderate your language and attacks on other ppl, who have just as much right as you to pass comment.
Click to expand...
Click to collapse
I second that!
Sent from my GT-I8150

[Q]Ubuntu on the Nitro

Anybody seen/tried this yet? Looks pretty cool. I've been trying to get it working but I'm failing miserably.
https://wiki.ubuntu.com/Touch/Install

Ubuntu is all right look wise, but has no apps currently. Althouh I do like Ubuntu for my computer.
Sent from my LG-P930 using xda app-developers app

mattman86 said:
Anybody seen/tried this yet? Looks pretty cool. I've been trying to get it working but I'm failing miserably.
https://wiki.ubuntu.com/Touch/Install
Click to expand...
Click to collapse
Seen yes, tried no. I'm defiantly interested in porting this, just need to find the time. Please see here https://wiki.ubuntu.com/Touch/Porting.
We could work on it together.

I'm getting my Dev environment setup now

mattman86 said:
Anybody seen/tried this yet? Looks pretty cool. I've been trying to get it working but I'm failing miserably.
https://wiki.ubuntu.com/Touch/Install
Click to expand...
Click to collapse
Our phone is not listed as supported device on that list, you gonna have to make a compatible source tree for the p930, not easy to do, gonna try to take a look at it after i finish compiling aokp42 for my tf101 this ***** is killing me! But getting there!
EDIT: So i read you can use CM's device tree to build ubuntu touch for any CM officially supported device, such as the P930! syncing repo right now, will try to compile and report later!
Sent from my LG-P930 using xda app-developers app

Can we install Linux apps like aircrack in this os ?

mattman86 said:
I'm getting my Dev environment setup now
Click to expand...
Click to collapse
Any luck?
I keep getting this error:
Code:
Error: .size expression for pow does not evaluate to a constant
After some googleing I found that it seams to be related to linaro. Haven't gotten a chance to really look into it though.

nexwave-mat said:
Any luck?
I keep getting this error:
Code:
Error: .size expression for pow does not evaluate to a constant
After some googleing I found that it seams to be related to linaro. Haven't gotten a chance to really look into it though.
Click to expand...
Click to collapse
Yeah, I'm getting the same issue.

mattman86 said:
Yeah, I'm getting the same issue.
Click to expand...
Click to collapse
Edit the last line of file
Code:
bionic/libm/arm/e_pow.S
from
Code:
END(pow)
to
Code:
END(pow_neon)
---------- Post added 24th February 2013 at 12:51 AM ---------- Previous post was 23rd February 2013 at 11:56 PM ----------
If your running into an error with
Code:
dst->copybit_image_t::w
the make the following changes to the
Code:
hardware/qcom/display-caf/libcopybit/copybit_c2d.cpp
file.
Code:
// struct copybit_rect_t dr = { 0, 0, dst->w, dst->h };
// struct copybit_rect_t sr = { 0, 0, src->w, src->h };
struct copybit_rect_t dr = { 0, 0, (int)(dst->w), (int)(dst->h) };
struct copybit_rect_t sr = { 0, 0, (int)(src->w), (int)(src->h) };

Now,it is preview ,I will wait for it

I installed it on my Galaxy Nexus. There's not much working on it, so it's definitely a preview. I think you can watch review videos on YouTube and get the same experience as installing it on the phone.
I can't wait until it matures, it should be pretty slick
Sent from my LG-P930 using Tapatalk 2

Re: [Q]Ubuntu on the Nitrost
I was able to compile it for the p930, flashed it, i get past the two LG logos and then, just stays there, no bootanimation (dont know if there should be one) just a black/grey screen, didnt get a logcat yet to see whats happening, didnt have the time yet, will do later ...
EDIT: Noticed that i edited the wrong kernel file, edited the right one, re-compiled successfully, but now it boot loops and i cant get a logcat because adb cant see my device, the only thing i see when plugging usb, is a battery icon on my screen and then, boot loop! Gonna need some help with this thing ...
Sent from my Transformer using xda app-developers app

just1nsama said:
I was able to compile it for the p930, flashed it, i get past the two LG logos and then, just stays there, no bootanimation (dont know if there should be one) just a black/grey screen, didnt get a logcat yet to see whats happening, didnt have the time yet, will do later ...
EDIT: Noticed that i edited the wrong kernel file, edited the right one, re-compiled successfully, but now it boot loops and i cant get a logcat because adb cant see my device, the only thing i see when plugging usb, is a battery icon on my screen and then, boot loop! Gonna need some help with this thing ...
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
You tried killing adb and using sudo for starting it:
adb kill-server
Then
sudo adb start-server
Also, what are your build pc specs? I'm contemplating trying or helping on the port... When my phone ships tomorrow...
Sent from my iPod touch using Tapatalk

Booted Ubuntu Touch
Hey Guys,
I managed to boot Ubuntu touch on our phones yesterday. I've been really squeezed for time but will make a thread for is ASAP along with needed files.
BTW: Not much is working for our phones. Not even calling.
Later,

Kernel android-msm-marlin-3.18-pie-qpr2 build failed

Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.

me too

Adlismon said:
Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
Click to expand...
Click to collapse
ucantseeme said:
me too
Click to expand...
Click to collapse
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.

sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.

Adlismon said:
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Click to expand...
Click to collapse
The files are all outputted where they are meant to be (/out/android.../dist) already, and the image.lz4 is the normal output. If yours outputs elsewhere I would sync, delete the buildinfo line and rebuild in a new directory and see what happens.

sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
thank you, thank you
I solved it