[GPL] [KERNEL] noobnl's Andromeda v1.4.1 [ROM Manager] [Superuser.apk] compatible! - Epic 4G Android Development

flash it with clockwork
download: http://www.sdx-downloads.com/devs/noobnl/noobnl.andromeda.kernel.v1.4.1.zip
or
older aka one click version ( extract new kernel & just replace zimage in the main dir)
download: http://www.sdx-downloads.com/devs/noobnl/one.click.andromeda.flasherv1.3.0.zip
1. you need samsung galaxy s drivers
64-bit OS http://db.tt/mQv4SX
32-bit OS http://db.tt/8u6HeG
2. push MENU, select Applications > Development, then enable USB debugging.
3. extract and run run.bat
4. enjoy!
Features:
Codesourcery G++
Busybox, thanks joeykrim
Remount, thanks joeykrim
superuser.apk with su!
-O3 optimization
Cortex a8
ClockworkMod Compatable Kernel
kernel sources: http://www.sdx-downloads.com/devs/noobnl/andromedakernelsources.zip
*******changelog*******
v1.1 fixes root access, properly removes joeykrim root
v1.1.1 removes additional files
v1.2 broken build
v1.2.1 fixes build number & Cortex a8 with NEON Optimization
v1.2.2 took away neon optmization
v1.3.0 rebuild the modules with cortex a8 & -O3 optimization & enabled ThumbEE in the kernel
v1.3.1 ClockworkMod compatible Kernel!
v1.3.2 fixes broken root and fixes busybox permission
v1.3.3 adds superuser.apk!
v1.3.4 fixes the move superuser.apk to system & fixes a flaw with jk-su
v1.4.0 based on di18 kernel!
v1.4.1 prototype tvout (start a shell & type in "start tvout"
Code:
make -j$CPU_JOB_NUM HOSTCFLAGS="-g -O3" ARCH=arm CFLAGS_KERNEL="-O2 -march=armv7-a -mtune=cortex-a8 -mcpu=cortex-a8" CROSS_COMPILE=$TOOLCHAIN/$TOOLCHAIN_PREFIX
uninstaller: http://firon.net/xda/one.click.stock.flasher.&.root.uninstaller-di18.zip
my github: http://github.com/noobnl/]
Link to the stock samsung source that was used for these kernels.
http://opensource.samsung.com/ Please search for SPH-D700 DI18.

Do I need to root first or does it root when I flash and what does it exactly do. does it remove my programs or anything like that?
Thanks in advance

Excuse me but if I used your old method of rooting. Does this still work?

Updated without any problems. I assume that most of these "improvements" are more under the hood than stuff that would be noticable to the average user. Thank you for your work. I hope we get more talented people on this project. Of coarse this project didn't "explode" with new stuff multiple times a day, there's only a small fraction of people working on it. Once again, I wish I could help with something to get the ball rolling better, but I don't know how to code and I'm no linux guru either.
Helping finding bugs, giving help to people trying to do whatever, and giving feedback is contributing.

herbthehammer said:
Updated without any problems. I assume that most of these "improvements" are more under the hood than stuff that would be noticable to the average user. Thank you for your work. I hope we get more talented people on this project. Of coarse this project didn't "explode" with new stuff multiple times a day, there's only a small fraction of people working on it. Once again, I wish I could help with something to get the ball rolling better, but I don't know how to code and I'm no linux guru either.
Helping finding bugs, giving help to people trying to do whatever, and giving feedback is contributing.
Click to expand...
Click to collapse
Yeah I updated with no problems also.

Also, this is VERY important. If you have Auto Mount, you need to dismount the SD Card in order for this to work.

What is -03 optomizations? And is this a different version than you posted last night at sdx

Sorry for the dumb question, but what's the difference between this and "one click root"? And could someone please explain what installing one the these modified kernels do? Thanks.

jarnail24 said:
Do I need to root first or does it root when I flash and what does it exactly do. does it remove my programs or anything like that?
Thanks in advance
Click to expand...
Click to collapse
x2 been wondering this myself

specialk0324 said:
x2 been wondering this myself
Click to expand...
Click to collapse
It will Flash a Custom Kernel. Which will give you root access. It wont delete anything.

This is updated? Can we just run it again or should one remove then re-install
Well re-ran it doesnt seem to cause any harm lol
I had # at one point when doing ADB shell but now I get $

updated!!!!

noobnl said:
updated!!!!
Click to expand...
Click to collapse
Awesome work as usual. couple questions.
1. I know you have busybox included but its an older version "current "1.18.0" and I can not get that to install after doing your kernel. If I use just he exploit method I can ugrade it via the market.
2. The version number is still reading V1? do you plan on changing that with updates so we can tell what we have installed for us dumb peoples lol
Thanks so much donation coming your way

Worked with a hiccup but it must've been my fault. Other than that, awesome job my friend.

noobnl said:
updated!!!!
Click to expand...
Click to collapse
As stated here is your Redbull fund for the week hopefully its enough to get some more work done! lol
1XH33015CN7654102.

Fixter said:
Worked with a hiccup but it must've been my fault. Other than that, awesome job my friend.
Click to expand...
Click to collapse
Same here, I hope we are able to tell which version is which in the future.
Just ran Linpack, I got 8.0 nothing above that...hmmm how can I check im running the right kernel?

1.2.0 was pulled! broken build

noobnl said:
1.2.0 was pulled! broken build
Click to expand...
Click to collapse
Noob. Please explain. Is the Flasher we ran broken? :S

I realize that you pulled 1.2 bc of broken build but when i try to d/l 1.2.1 zip link not there? is it just me?
says page not found

all for now I guess.... wonder if i should uninstall the 1.2 or just wait

Related

[Ubuntu on EMMC] Automatic Kernel Updater

This script, when called, will download lilstevie's kernel source, build the default configuration, and flash it.
Thanks to lilstevie for the whole Ubuntu on emmc.
Let me know how it works
UPDATES:
12.4.2011
-Updated to ver. 4
-Added update checking feature...
11.30.2011
-Update to ver. 1.0.1
-Fixed Grammatical Error
-Added git dependency in apt-get line.
11.28.2011
-Initial release
link:
austinconn(dot)us(dot)to/repository/kernelupdater.sh
(Reason I have to post link like this is because I haven't posted enough. Will change when able...)
atc3030
Thanks, makes life a little easier.
Actually, i have some commands which come in really handy when you use ubuntu on a tab.
sudo apt-get remove appmenu-gtk indicator-appmenu overlay-scrollbar liboverlay-scrollbar-0.1-0
This will remove the global menus and that annoying scrollbar so you have to use your mouse/trackpad less often.
*edit: Hard reboot right after the install-part.
*edit2 git was missing on my ubuntu-install. I'd suggest you to add it to your apt-get line.
looked at the script, nice
Although not that i think you care but you might:
echo "If all was done correctly, your kernel shoudl be upto date"
Click to expand...
Click to collapse
should
up to *two words*
Gonna update the script. what else do you guys want to see in it??? let me know what else would be useful and ill see about adding them
atc3030 said:
Gonna update the script. what else do you guys want to see in it??? let me know what else would be useful and ill see about adding them
Click to expand...
Click to collapse
Great work! It would be good if it could build the CIFS, TUN and NFS modules
mitchelln said:
Great work! It would be good if it could build the CIFS, TUN and NFS modules
Click to expand...
Click to collapse
If you can get me like a guide or something to do that, i would love to. im working on something else right now, but should be able to do that really quick. next update will have an update feature to automatically check for updates.
i know this is a noob question (i think you wil get more off them since the one-click installer for windows)
- how to correctly use this script
- will this affect the working off my dualboot configuration (for one click installer)
very excited for this. is there a guide for this script or can we just execute?
download the script, right click on the file and mark it as an executable under properties.
open a terminal, ch to the folder you´ve downloaded the script and run
$sudo ./kernelupdater.sh
I would love to get Linux Mint (any flavor, but considering our hardware, prob LMDE or LXDE is most realistic, although IDK if any debian flav is compiled for ARM?) built into a flashable image. Ubuntu is wasted on a machine with limited RAM and a non-standard file system.
I am not a developer, but I certainly would help as much as possible any person who would like to get moving and use our hardware to its fullest extent!
Like I said, any interested parties, please PM me.
Sent from my Transformer TF101 using xda premium
atc3030 said:
This script, when called, will download lilstevie's kernel source, build the default configuration, and flash it.
Thanks to lilstevie for the whole Ubuntu on emmc.
Let me know how it works
UPDATES:
12.4.2011
-Updated to ver. 4
-Added update checking feature...
link:
austinconn(dot)us(dot)to/repository/kernelupdater.sh
(Reason I have to post link like this is because I haven't posted enough. Will change when able...)
atc3030
Click to expand...
Click to collapse
This link yields not (even without the "(dot)" and all I can find on his site is html and a couple android APKs and zips. Can someone please repost the most recent kernel update/build script? Muchos Gracias
If anyone has this script lying around. Please pm me. I must have lost it in a data transfer
Sent from my DROID2 GLOBAL using Tapatalk
Here is a link to the file. I take no credit for the work, just reuploading it since the original version has been missing for a while now.
http://dl.dropbox.com/u/6990784/kernelupdater.sh

[Build Guide][Flo/Deb] - Pure AOSP 6.0.0_r1

This is a PURE AOSP ROM build guide. I have opted not to post an actual AOSP ROM based on 6.0.0 due to the fact I just dont care for it much. The instructions are up to date as of 10/21/2015
Deprecated-> This thread is about learning to build your own ROM following the instructions in post #2. The ROM posted in this thread is for example output. Feel free to download and use the ROMS @GROGG88 and I build! Feel free to try and build your own. We will try to help!
Quick Change Log
10/21 - Updated guide to reflect Android version 6.0.0_r1. No ROM for download (at this time).
1/17 - Updated build with official 5.0.2 Binaries. Fixed Browser "Settings" crash.
12/19 - Updated my Flo builds to Android 5.0.2_r1
12/9 - Updated my Flo build. Will not be doing a Deb Build any more.
12/2 @GROGG88 has updated his builds. I have not! I will update tomorrow. I did however get thefactory stock rooted ROM up HERE!
11/18 - @GROGG88 and I have joined forces to create two ROMS! I will be creating PURE AOSP ROMS and he will be creating Modified ROMS with many useful features! Each ROM can als be user built because all commits are shared in post #2!!!
11/15 - B8 - Updated the 5.0.0_r6. Deb is only using preview binaries due to lack of final binary files.
11/14 - B7 - Updated the 5.0.0_r5. Deb is only using preview binaries due to lack of final binary files.
11/10 - B6 - File system install instead of block install, Added Google Location Services to framework, Fixed a root issue that couple DEB users were having
11/9 - B5 - Changed wallpaper again. Fixed stock recovery at source level (Thanks to @Gnome and @GROGG88)
11/8 - B4 - Changed wallpaper to android 5 Wallpaper, fixed reverting to stock recovery (No need for save-recovery.zip), pre-rooted boot.img (No need for extra boot.img!)
11/7 - B3 - Removed it. Bad files. Reverted back to Build 2.
11/5 - B2 -- Fixed MTP bug that google has left in every version of AOSP, made ROM recovery flashable and added 2 zips to the OP
11/4 - B1 - Update to 5.0.0_r2. PC install via fastboot
Additional Downloads
Root by @Chainfire HERE!
Gapps for Lollipop HERE! There may be others so shop around!
Stericson's Busybox in flashable zip format is attached! Thanks to @Stericson for the binaries!
@GROGG88's Special Builds are HERE!
MOD EDIT: Link removed as domain has expired. Thread closed until new links can be installed
Please hit Thanks! It just as easy as hitting Download! ​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ubuntu 14.04 Set up and Build Guide
Updated 11/05/2014
Feel free to ask any questions about the build process. Do not ask questions about Ubuntu!
This guide assumes the following
Have Ubuntu 14.04 setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processors.
You are not here to ask for help with Linux, only the Android build process!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Synch Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.0_r1
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
[url]https://developers.google.com/android/nexus/drivers[/url]
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch
Build it!
Code:
make -j8 otapackage
See Build Notes and ramblings from me in post #3!
Notes
The ROM build will be a PURE AOSP ROM with no Gapps at all. See links in post #1 to PA Gapps for a good set of Google Apps!
The ROM will also have terminal level SU. So becareful! In other words its fully rooted and could be open to vulnerabilities. Flash your favorite Superuser Package if you need it. I dont. I recommend SuperSU by @Chainfire HERE. Download the flashable zip and flash after you flash ROM.
make -j8 is the number of worker threads that the make command will use to build. To me 8 is a safe number for an i7 processors. For an i5 Processor I would use -j4. I have experimented with a multitude of different values and it seems to me that the number of logical cores is also the best number to use with the make command.
Google recommends between -j24 and -j32 (to me that is excessive and causes my machine to error out every once in a while). Keep in mind the higher you push the more load the CPU will undertake. If your O/C'ing real hard you better have some nice cooling! I had to cut back OC on my 4770k from 4.65 to 4.4 with a Corsair H60 cooler just so it wouldn't over heat. When in doubt start low.
My i7 machine clocked at 4.4 and 16 gigs of RAM on a Samsung 840 Pro 256 Gig SSD take about 38 minutes to build the entire ROM.
With a 50 Meg download link it took maybe 30 to 45 minutes to sync the repo.
Changes from Source
Check out @GROGG88 patches HERE!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Mindrocket said:
Right on Scott! Can't wait to give it a spin.
---------- Post added at 07:37 PM ---------- Previous post was at 07:15 PM ----------
Security settings crashes says"unfortunately settings has stopped" .
Click to expand...
Click to collapse
I think its the same error some other folks are facing. Rascarlo and a few others would release their AOSP builds but it appears this blocks them from releasing. Read this over on a few pages on a few ROMs in this neighborhood.
whoamanwtf said:
I have faith in you making it work
Click to expand...
Click to collapse
Can anyone post a snippet of logcat during the crash? Particular the actually error itself.
Place it in the
Code:
box if you can.
If not I get out of work in a few hours and can look then...
mjwhirly said:
Nice to see you venturing into new projects. Most people start with CM since its not to hard to compile, but you did it the opposite way which will make all the difference in the end
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
IMHO: If you dont start with the basics you will end in a mess
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
rocksyjj said:
got to try this as your clean rom works well iam sure this one will be great also
keep up the great work to you and who helps you.
Where would i start to try baking my own cake .. i use archlinux what programs needed to do a build
Click to expand...
Click to collapse
Never used archlinux but I used Ubunutu 13.04
Here is where I started: http://forum.xda-developers.com/showthread.php?t=2224142
(I hate nano so used gedit of course. )
But at the last two shell commands i didint use the AOKP tree I used the AOSP base so you want to look here for that: http://source.android.com/source/downloading.html
Then follow the instructions from that page on forward until you have yourself a ROM :highfive:
Also pay attention to the blurb about proprietary binaries
Obtaining proprietary binaries
The Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for the supported devices can be downloaded from Google's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
When building the master branch for a device, the binaries for the most recent numbered release or with the most recent date are the ones that should be used.
Click to expand...
Click to collapse
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
You fixed the security settings fc! Mind sharing how you managed to fix that?
Sent from my Nexus 7 using Tapatalk 4
scrosler said:
Also pay attention to the blurb about proprietary binaries
There is a link for the Nexus binaries in that blurb. Make sure you install them before building and you are good.
Click to expand...
Click to collapse
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
vibranze said:
Where is the link to download the Nexus binaries btw? I didn't see a proprietary binaries blurb in the above 2 links.
Thanks.
Click to expand...
Click to collapse
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
scrosler said:
Alright then...
Build 20131008.010041 up!
Changes
Re-synced repo for 2013/10/08
Fixed Settings -> Security F/C
Changed SU to SuperSU
Also can I have some people rate the thread 5 stars... The Nexus 7 FHD troll is at it again. He is going around rating my threads, and others, 1 star.
Any help with that would be appreciated. Damn trolls, lol!
Click to expand...
Click to collapse
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
scrosler said:
Its under the actual "Building for devices" page...
http://source.android.com/source/building-devices.html
Wich leads to...
https://developers.google.com/android/nexus/drivers
Click to expand...
Click to collapse
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
vibranze said:
Thanks Scotts, appreciated your fast response. :good:
Click to expand...
Click to collapse
Your welcome!
mpmilestogo said:
Hi Scott. Where is the download link for this one? I think a few folks would love to know the fix for the security fc since last I read it was blocking their update as well. Definitely want to try the aosp one.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its in the OP. Post 1. I just changed the link. Happy downloading!
TheDarkDefender said:
hi scott,
could you please share the sources you build from? and specifically how you fixed the Security settings FC?
thanks.
Click to expand...
Click to collapse
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
scrosler said:
Your welcome!
Its in the OP. Post 1. I just changed the link. Happy downloading!
Click to expand...
Click to collapse
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
mpmilestogo said:
Thanks Scott. I think I found something rather strange with my tablet with just about any of the AOSP builds. I found this on another as well. It seems whenever I enable locations in chrome or chrome beta the tablet soft resets immediately. If I turn off location reporting, nothing happens but I get no location updates. I decided to restore things using the factory images. For the umpteen thousandth time, thanks to the Android team for providing the safety net!
Gonna try again later today and see if this issue persists after resetting the device to the factory image and reflashing the AOSP build.
Click to expand...
Click to collapse
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
scrosler said:
No this very possible depending on the GAPPS used. I think this is more a GAPPS issue then a ROM issue. I cant say for sure but I might have time to look later.
If someone else knows then do tell.
However I dont much care for Chrome on mobile (love it on PC) so I use AOSP and it runs well. But have not tested location.
Im sure a fix can be found with enough effort.
Click to expand...
Click to collapse
Interesting. I've tried the BANKS minimal GAPPS core and photosphere as well as the goo.im gapps in clean flashes of other aosp based ROMs but still had the same issue. Perhaps I'll try the PA gapps next since they seem to have everything in them. Gonna give the whole thing a try a bit later today as well. I'm lucky enough to have two Nexus 7 tablets so one has your latest CleanROM on it which I love! The other seems to have descended into flashing heaven or the other place .
Any help appreciate on the issue though. I'd love to run AOSP on the second tablet since one of them is destined for my daughter when she realizes she wants one.
scrosler said:
The source is the AOSP tree and it can be found here: http://source.android.com/source/downloading.html (thats all I am using).
Fixing the Settings F/C was creative... had to Google to get the answer, lol
Here is what I found...
CM 10.2 initially had this issue as its based from AOSP like this rom (SOURCE). They did not explain a fix... Also, note this is a less than one week old issue. So I continued on with Google... (Google is a son of a ***** when you need it )
Then found this thread on XDA from the Nexus 4 about an update to 4.2.2 HERE! This started to make sense as they posted a fix for the N4. HOWEVER that fix was not applicable to our N7.2 because we did not have the keymaster files on the vendor partition!!!
So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM. VIOLA! It worked and solved the problem.
Now I will admit I am not sure why these files are not in the AOSP source tree as I am still learning... If you can shed more light then please do! But I do know that it fixed the issue. Was not seemingly prevalent before October 2nd (or maybe it was but thats when it was reported on CM10.2) and moving those files into the ROM base resolved (granted they are not in the same spot as the N4).
Please feel free to share anything you know in this thread.
Click to expand...
Click to collapse
Thank you very much. Did you figure out the commit in the CM repo that actually solved this issue?
Also, what do you mean by So test flashed the Google stock ROM /system/vendor/firmware/keymaster/* files into this AOSP ROM ? Could you elaborate please?
I'd be happy to share anything I get to know about this. Been researching about this too. Thanks.

[WIP/DEV] Kernel 3.4

So far I've got the basic A51x/A70x support added to my linux-tegra-nv-3.4 branch.
What works:
- The kernel boots
- Panel (partially?)
- USB
- Android is trying to start
Whatnot:
- everything else
So my first goal is to get display up. Currently, I've got a black screen after the bootloader logo, and the following logs:
dmesg
logcat
If anyone can help with this, hit me on hangouts, my g+ profile can be found on my xda profile. I'd appreciate any help, this would be a huge step forward for these devices.
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Shreps said:
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Click to expand...
Click to collapse
Agree on both
really awesome work
and we're already using hwcomposer.tegra.so from grouper
Shreps said:
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Click to expand...
Click to collapse
Newer ones may be needed for 3.4, dunno... also, I may have just missed something simple...
Code:
W/SurfaceFlinger( 266): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 266): no suitable EGLConfig found, giving up
...
D/NvOsDebugPrintf( 270): NvRmPrivGetChipIdStub: Could not read Tegra chip id/rev
D/NvOsDebugPrintf( 270): Expected on kernels without Tegra3 support, using Tegra2
Anyways, I'm still working on 3.1, refactoring Acer's mess with the kernel files outside the kernel files... minimizing those changes will ease 3.4 development a lot, as it's confusing to watch out for Acer ifdef's all around the kernel
Hi, any news of this project?
chacal1906 said:
Hi, any news of this project?
Click to expand...
Click to collapse
I don't have the device ATM, so I can't do anything related to this.
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Hi, great to see you back. ?
My A510 is still alive. ?
The battery is not the best anymore, but it's is always ready to test your great work.
HornetRider said:
Hi, great to see you back.
My A510 is still alive.
The battery is not the best anymore, but it's is always ready to test your great work.
Click to expand...
Click to collapse
Great, I'm in need of an A510 tester message me on Hangouts
Ziyan said:
message me on Hangouts
Click to expand...
Click to collapse
Done [emoji106]
When will we see a working version?
Hi !
It's nice to see that someone is still working on A700/510 !
I have a A700 and if you need feedback, don't hesitate !
Ziyan said:
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Click to expand...
Click to collapse
Have you abandoned the project?
I found the builds on Jenkins. I even ran them on my a700. If remove checks from the installer, they are flashed.
But the recovery does not work.
Ziyan said:
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Click to expand...
Click to collapse
sir yes sir! ancient tab is ready for reincarnation
i dont check the a700 forum often though, so if something needs eyes please quote, mention, or pm me. ill get an email and know to check back
edit: we may need a newer and functional TWRP version for some of the newer OS versions =/
Sterist said:
sir yes sir! ancient tab is ready for reincarnation
i dont check the a700 forum often though, so if something needs eyes please quote, mention, or pm me. ill get an email and know to check back
edit: we may need a newer and functional TWRP version for some of the newer OS versions =/
Click to expand...
Click to collapse
TWRP3 ready
Kaban4ik86 said:
Have you abandoned the project?
I found the builds on Jenkins. I even ran them on my a700. If remove checks from the installer, they are flashed.
But the recovery does not work.
Click to expand...
Click to collapse
A thread will be opened soon. Until then - feel free to use the aosp-6.0 builds from Jenkins (they're almost fully complete)
Ziyan said:
TWRP3 ready
A thread will be opened soon. Until then - feel free to use the aosp-6.0 builds from Jenkins (they're almost fully complete)
Click to expand...
Click to collapse
is the recovery mirrored somewhere? and what/where is this jenkins repository
Sterist said:
is the recovery mirrored somewhere? and what/where is this jenkins repository
Click to expand...
Click to collapse
jenkins.unlegacy-android.org/view/All/builds picasso2 builds…
But recovery don't work on my a700. Black screen... If press "Menu" button tablet reboots...
This sounds great, I am already running the UA build on my Nexus, time to dust of the A700 !
Kaban4ik86 said:
jenkins.unlegacy-android.org/view/All/builds picasso2 builds…
But recovery don't work on my a700. Black screen... If press "Menu" button tablet reboots...
Click to expand...
Click to collapse
what checks need to be removed?
I tried flashing with twrp 2.7.1 (newest publicly available) and ctr 3.3
twrp failed at unexpected contents (I previously wiped all partitions)
and ctr auto-rebooted in the process when I wasn't looking, and it apparently failed as well.
this was using the newest "stable" 6.0.1 build
Sterist said:
what checks need to be removed?
I tried flashing with twrp 2.7.1 (newest publicly available) and ctr 3.3
twrp failed at unexpected contents (I previously wiped all partitions)
and ctr auto-rebooted in the process when I wasn't looking, and it apparently failed as well.
this was using the newest "stable" 6.0.1 build
Click to expand...
Click to collapse
*.zip/META-INF/com/google/android/updater-script
Code:
if range_sha1("/dev/block/platform/sdhci-tegra.3/by-name/CAC", "36,0,32767,32768,32770,32849,32851,33341,65535,65536,65538,98304,98306,98385,98387,98877,106070,131072,131074,163840,163842,163921,163923,196608,196610,229376,229378,229457,229459,262144,262146,294912,294914,294993,294995,295485,313343") == "afd609f9867238c1cd370d82772817d744182c79" then
if range_sha1("/dev/block/platform/sdhci-tegra.3/by-name/CAC", "50,32767,32768,32770,32849,32851,33341,65535,65536,65538,66050,97792,98304,98306,98385,98387,98877,106070,106582,130560,131072,131074,131586,163328,163840,163842,163921,163923,164435,196096,196608,196610,197122,228864,229376,229378,229457,229459,229971,261632,262144,262146,262658,294400,294912,294914,294993,294995,295485,313343,313344") == "6b72a7b11b65c9ef1bb4c57ab78076d1ccd2e0e9" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;

[KERNEL][SOON] HakyKernel 3.1.2

Will be updated soon
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.
haky 86 said:
After done some google search about to find similar devices to our phone and some guys on Whatsapp group give me some useful information about Samsung Galaxy S Duos 2 that device share same broadcom chipshet but the kernel is more updated (3.4.5), so I decide to port this version to our phone Samsung Galaxy S2.
I start some tests witnout arch-capri drivers in kernel/samsung/3.4/arch/arm just to see if Android boot or not, the result was really fantastic so from today we can port 3.4 kernel without any problems.
Issues:
Settings app: closed automatically when activate Bluetooth.
Kernel information: still appear on 3.0.101, i guess modules of MoshKernel should be updated too.
Android rebooting each 10/15 minutes.
Wifi: not working.
Code:
[*]22/04/2015:
-initial build.
-I will make zImage and use as prebuilt kernel in my roms after add arch-capri drivers.
Click to expand...
Click to collapse
Okey. Is this for stock or asop based roms?
rs tony said:
Okey. Is this for stock or asop based roms?
Click to expand...
Click to collapse
for both roms :good::good:
thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone
SmzAmir said:
thanks @haky 86
I think in future u make this phone work so much better than iphone6
your one of the best developer for this phone
Click to expand...
Click to collapse
Sure once finish 5.1.1 i can recall other devs to share experience and make 3.4 work perfect:thumbup::thumbup:
Sent from my GT-I9105P using XDA Free mobile app
haky 86 said:
for both roms :good::good:
Click to expand...
Click to collapse
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?
cracker12 said:
amazing work :good: only a question, i am a newbie on android so what will be the difference betwen them?
Click to expand...
Click to collapse
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.
haky 86 said:
the differences are:
-roms will be more stable.
-kernel new and updated instead of old stock and slow 3.0.101.
-antutu test result about 13000 points with some fixes may get better result.
-fast booting.
-this version could be useful for android 6 when will out.
Click to expand...
Click to collapse
Thanks... Keep up
[*]23/04/2015:
-drivers are imported without problem.
-now i'm fix compilation errors to see if will done or not.
Hey u make this
It awesome
---------- Post added at 03:40 AM ---------- Previous post was at 03:37 AM ----------
Hope you will fixed the issues in future
Do it have enhanced gpu
Man, you do a lot of great work.
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
left it open haky..maybe they are busy for now..we need it bro
haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
sad news!
I was really looking forward if someone can port a new kernel, but as you said it's not an easy job and no devs are intrested
haky 86 said:
thanks guys but may i wil discontinued this project since no devs are interested to port newer kernel like galaxy w where started from 2.6 and updated up to 3.4..
Click to expand...
Click to collapse
So this one is really down? Hey, man, we need you, continue your work
why me? the best succeed I got is integrate part of capri's kernel archecture into 3.4 and entire code should be readpted to work on our phone. in case of even ported, I will not release the source coz I will not do the homeworks of others
3.1.2 Kernel
-update patch like 3.0.31 -> 3.0.32 is adapted as well.
-now im apply the patch to update the code see ya.
3.1.2 in progress
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance
haky 86 said:
I have a question dear @CoolDevelopment I manage to update the kernel of this phone from 3.0.101 to 3.1.2 using the patch of kernel.org's website.
here my questions:
-if got failed patch, should skip them in case can't found it code?
-I saw there are a lot of detected commit that already patched, should be skipped too and apply only the new code?
-is enough just downloading 3.1.2.patch and use patch -p1 method or should download kernel source too.
https://www.kernel.org/pub/linux/kernel/v3.x/
now I'm compiling a zImage seems no errors for now, if boot I will continue the port :good:
thanks in advance
Click to expand...
Click to collapse
Upload your source man, else noone can help you
I hope you don't have just changed the version numbers...
no i didn't, here my new branch
https://github.com/hak86/android_kernel_samsung_galaxys2plus-common/tree/3.1.2-lp
Compilation is work fine, now i will try to compile with make -j4 bootimage to get the modules and use them on nebula's flashable.

[KERNEL] [MTD] [TW/CM9/CM11] [DEV] Watson Kernel (MTD support on Gingerbread!)

Hello guys,
This is a project I was working on for a kernel for our SGY.
I made it with a few things in mind:
>Improve it's performance
>Be universally compatible (after I nearly given up on trying to get a snappier CM11 and after the need for a snappier SGY, I decided to go back to GB. However, BML is terrible, and it is annoying to come back to. I decided to build a MTD kernel for Gingerbread then, and it works!)
>Experiment and upgrade as much as I can (thanks @robcore!!!!)
But since I lost my device, I cannot continue developing it. I am then releasing the source code (sorry, no flashable stuff, I deleted it long ago ) for any of you to continue(?) my work if your heart so desires.
If I ever get myself another SGY (or another BCM21553 device), I will gladly continue development (and support whoever does it too), but before I lose all my data and the kernel code alongside it, I am making it available.
This kernel features:
-OC up to 1040MHz (It's questionable even today if the bcm21553 OCs really work, but I tried hacking a way that works very similarly to MarocOS's one, maybe even better. Be warned though, the source around it is messy)
-GPU hacks for performance (Again, even I don't know if they do work, probably the values are just there to be seen, I'm not sure. I do know though that increasing the CPU speed will much likely increase the speed of V3D too)
-DVFS disabled (I found out DVFS is mostly the culpirit in the "832MHz crisis" where the kernel would forcefully scale itself to 832MHz, so I eliminated any reference to it in kernel code. Apparently DVFS on the processor is only available under the bcm21553 governor, but it is present on the other drivers as well. The idea for disabling DVFS came from my friend @robcore)
-A few additional governors and a buggy interactive governor (which is the default xd)
-MTD support for Gingerbread (Thanks Samsung Epic 4G! Although it only works on TouchWiz (I tried it with SL v2 and v2.1 and it works, but under NougatME(CM7) I got no success and loads of segfaults), it works ALMOST perfectly. See bugs for details )
-Some scraped source code from Samsung's FSR I found on the internet (barely compilable, though)
Bugs:
>Gingerbread version:
-IMEI won't appear in the Status screen, I also faced problems with non-working radio for calls. Data works just fine, but calling and receiving calls is unavailable. I believe it is EFS-related. My suggestion is backing up the EFS partition's file structure, then converting it to MTD, then restoring the backup.
-TWRP will crash and panic when exiting, a workaround is force rebooting
>ICS version:
-TWRP will crash and panic when exiting (I believe fixing it here will fix the bug above too)
>KitKat version:
-Flashing images fail randomly, you may also be unable to reboot normally if you do so. I tried addressing this but I couldn't get anywhere.
DOWNLOAD THE SOURCE: Here!
Thanks to:
 @robcore - his development on the Snapdragon S4 breathes life on my dev soul!
 @zman0900 - I saw his thread on an MTD TW kernel for the Samsung Epic 4G, which led me to believe MTD on GB is possible.
nice kernel
It sound nice. I'm a newbie developer, I'm building a kernel to fix audio bug on cm9, hope it work. And thank you for the source
vdhero said:
It sound nice. I'm a newbie developer, I'm building a kernel to fix audio bug on cm9, hope it work. And thank you for the source
Click to expand...
Click to collapse
Have you gathered enough info on it? I would like to fix it too, but I couldn't get any info on whether if the audio bug is a kernel-side issue or an OS -side issue.
Best of luck for you
Building and fixing
sonickles9 said:
Have you gathered enough info on it? I would like to fix it too, but I couldn't get any info on whether if the audio bug is a kernel-side issue or an OS -side issue.
Best of luck for you
Click to expand...
Click to collapse
I don't sure so I decided to build a kernel from your source and another cm9 version from Mohamad.Afaneh's source and I'll merge the audio on both of them for the best think to fix the bug.Thank you .
Link for kernel?
(img files...)(stock/cm9/cm11)
TheRealModder said:
Link for kernel?
(img files...)(stock/cm9/cm11)
Click to expand...
Click to collapse
Compile one for yourself,man. It only takes like 15-25 mins
vdhero said:
Compile one for yourself,man. It only takes like 15-25 mins
Click to expand...
Click to collapse
I don't know how to compile....
TheRealModder said:
I don't know how to compile....
Click to expand...
Click to collapse
He wrote a script already, just add your toolchain and run the script. There's a guide in the readme
vdhero said:
He wrote a script already, just add your toolchain and run the script. There's a guide in the readme
Click to expand...
Click to collapse
Ok. The watson-kernel-bcm21553-src is used with other files?
Because i want to make cm9 mohhamad afaneh optimized version
TheRealModder said:
Ok. The watson-kernel-bcm21553-src is used with other files?
Because i want to make cm9 mohhamad afaneh optimized version
Click to expand...
Click to collapse
To make it, you have to sync the cm9 source code then add the files from his github to your localmanifest. This thing is not in anyway related to that except the MTD. This one is a kernel-compile only source
Oh man, i give up. I can't build a kernel from source, but i can modify a kernel.
Can someone give me the zimage for ics Please....
Sent from my Zenfone 2 Laser using XDA Labs
TheRealModder said:
Oh man, i give up. I can't build a kernel from source, but i can modify a kernel.
Can someone give me the zimage for ics Please....
Click to expand...
Click to collapse
zlimage? We don't have that here, we only have boot.img for kernel
vdhero said:
zlimage? We don't have that here, we only have boot.img for kernel
Click to expand...
Click to collapse
Or you can give me the extracted boot.img files. (ICS/KK)
I will rebuild it using dsixda's android kitchen.
Sent from my Zenfone 2 Laser using XDA Labs
TheRealModder said:
Or you can give me the extracted boot.img files. (ICS/KK)
I will rebuild it using dsixda's android kitchen.
Sent from my Zenfone 2 Laser using XDA Labs
Click to expand...
Click to collapse
Sorry but I can't because I'm bored of making ROMs so I switched back to Windows. I'm planning on making a ROM, I'll compile the kernel for you once I get linux installed
vdhero said:
Sorry but I can't because I'm bored of making ROMs so I switched back to Windows. I'm planning on making a ROM, I'll compile the kernel for you once I get linux installed
Click to expand...
Click to collapse
Ok. If you want to install linux i recommend using ubuntu or linux mint.
Ubuntu official website:https://www.ubuntu.com/
Linux mint official website:https://linuxmint.com/
Sent from my Zenfone 2 Laser using XDA Labs
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
vdhero said:
To make it, you have to sync the cm9 source code then add the files from his github to your localmanifest. This thing is not in anyway related to that except the MTD. This one is a kernel-compile only source
Click to expand...
Click to collapse
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
Assabtigle said:
VDHERO Please But a New Galaxy t Gt-S5360 and start the Development!
Click to expand...
Click to collapse
Sorry but I can't since my sgy is dead for a long time ago. I'll try to make one if I can find one. I've heard that there are some places that sell sgy for about 5 bucks, i'll find one ì possible
Be fast bro!!
vdhero said:
Sorry but I can't since my sgy is dead for a long time ago. I'll try to make one if I can find one. I've heard that there are some places that sell sgy for about 5 bucks, i'll find one ì possible
Click to expand...
Click to collapse
BE fast BRO Love U and Your WORK!!
All Your DEVELOPMENT are Faster than The ORIGINAL one Please Buy a NEW one!
and Yeah install the Stock Rom in your Phone by ODIN it will be fine!:laugh:

Categories

Resources