Develop Bugs

[DEV][DEV-ONLY] Honeycomb Progress

[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================​
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol

******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528

ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================​
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)

updated approaches and new tools have been added

spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb

lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?

ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu

Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun

noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices

Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??

daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot

lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.

noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.

spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!

Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.

spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb

lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.

Goal and tools updated*

spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?

lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash

Testing Nand ics builds

Hi everyone - So arrrrgh somehow convinced me to work on rhod a bit and I need help testing.
I have an initial cooked build of ice cream sandwich version 4.0.1 based off the dream/saphire build ready to be tried out. I need testers with adb skills to give me a hand solving a few quick questions while I work on a compiled version that's actually optimized for rhod.
This is UNTESTED and for NAND only flash via recovery ONLY after backing up everything.
Nothing is guaranteed to work in fact if it boots all the way up it will be a happy surprise.
Things that REALLY SHOULDN'T work at all yet:
hardware acceleration
jit
wifi
TOUCHSCREEN - it needs to be patched
What this rom should do:
It really should boot all the way up to the launcher but graphics are likely to be pretty darned quircky and as mentioned previously touchscreen probably isn't going to work without my input patch.
I just need some intrepid users to give me some feedback and logs - logcat mostly not too interested in dmesg yet
here is the link:
http://www.mediafire.com/?f1o69oa37oiiqo6
Flash at your own peril - if you use your phone as a phone you probably should just stay away but if your rhod is collecting dust I'd appreciate the help

As of a couple of days ago, both my RHOD400's are collecting dust.
I should be able to carve some time out tonight after work.
Also, you're way too easy to convince. I didn't even try!

the xdandroid device tree is being a really big pita to compile I think I'm just gonna rebase off the hero cdma work
*edit
and it's compiling, this should work much better for my purposes
edit again
it finished compiling so now I've got some source to work with - I'll finish uploading test2 which is cooked from heroc anyways then you can test both and tell me what happens with each and I can start the process of adjusting the hell out of everything
edit even more
upload failed so I just merged in my compiled build with test 2 so that should hopefully correct touch screen issues if it boots at all that is.
*bah the upload keeps failing - probably at&t's way of increasing data usage a 100mb file becomes 1gb of failed data usage lol
ok here's test 2
http://www.mediafire.com/?ff82o4iahfv0jj1
let me know what they each do

If the recommended cpu speed was 1ghz for gingerbread, we are pushing that a bit.
What's it like for ICS?
Secondly I didn't think we had enough ram for ICS.
Must be some serious kick-ass optimizations going on
Is nand ready for all RHODs yet? I've been in the dark on the other side of the country for a while.
Nand investigation/research time!

Ics has the potential to be just as fast as gingerbread and yes there is enough ram this is mostly just for fun though. GSM rhods are supported in nand now
Anyways I want testers not negative nancys lol

randomblame said:
Anyways I want testers not negative nancys lol
Click to expand...
Click to collapse
Welcome to the forums
On another note, I can't seem to find my RHOD... ugh. I'm still paying for the damned thing monthly, so I hope it turns up soon. What the heck!!
Worse comes to worse I can try it on my donor.

it shouldn't touch the recovery partition at all so risk of a brick is slim however you need to wipe dalvik and cache and data to test so it is inconvenient I suppose

I would like to try this built but it isn't possible to install it. In recovery mode after "apply update from sdcard" I got this error:
"E:Error in /tmp/sideload/package.zip
(Status 6)"
Why?

try choose zip lol

randomblame said:
try choose zip lol
Click to expand...
Click to collapse
What do you think about??? Of course, after choice "apply update from sdcard" I had choose your zip named rhodicstestbuild2.zip. Install process begun, but after 2 seconds I got error (my previous post).

randomblame said:
try choose zip lol
Click to expand...
Click to collapse
This is because miss semicolon in update script.

muziling said:
This is because miss semicolon in update script.
Click to expand...
Click to collapse
Thanks Muziling, you are right. Install is now sucessfull.
Missed 2 semicolon on begin of script (\rhodicstestbuild2.zip\META-INF\com\google\android\updater-script, line 2 and 3)
---------- Post added at 02:46 PM ---------- Previous post was at 02:22 PM ----------
Successfully installed (thanks again muziling), but not booting. I'm waiting 15minutes on NAND splash screen (burning AndroidMan with text "ACL"), but nothing happend.
Any idea?

adb logcat
Many error, netd, lib crash, etc... you can post your log to randomblame for debug

what test rom was it and yes logcat please that was the whole point

randomblame said:
what test rom was it and yes logcat please that was the whole point
Click to expand...
Click to collapse
OK, here is some logs. I'm used continous logcat (without parameter -d). Hope this logs will be usefull.
Edit: my device is Rhod100 and used your rhodicstestbuild2.zip build.

k I see a few issues there wanna try the first rom I posted and log me too. They're built on different bases but I suspect it will also have the netd trouble maybe I included the wrong init.rc thanks for tha logs!

randomblame said:
k I see a few issues there wanna try the first rom I posted and log me too. They're built on different bases but I suspect it will also have the netd trouble maybe I included the wrong init.rc thanks for tha logs!
Click to expand...
Click to collapse
OK, I tried rhodicstestbuild1.zip and all logs using adb has only one line in log: - exec '/system/bin/sh' failed: No such file or directory (2) -
I don't know why.
btw: in update script are missed 2 semicolon again ...
edit: same result as with build2 - not booting.

I have a rhod100 collecting dust willing to use for testing have no programming skills bit happy to test from a user perspective

thatfreak said:
I have a rhod100 collecting dust willing to use for testing have no programming skills bit happy to test from a user perspective
Click to expand...
Click to collapse
same thing with me but rhod400. i can pull logs as much as we want though

Hardware graphics acceleration
We have an Adreno 205, right? Could this help ICS development for us? http://www.xda-developers.com/android/qualcomm-releases-adreno-2xx-gpu-binaries-for-ics/

[MOD] NFC with Screen Locked/Off CM10, 10.1 & 10.2

I haven't posted enough on XDA to be able to reply to the appropriate development forum post, so I decided to post here. I'm running CM10 on a Sprint Galaxy Nexus (toroplus), and I had been in need of a way to use NFC while the screen was locked, but couldn't find one for the latest build of CM10. I found this thread http://forum.xda-developers.com/showthread.php?t=1709586 but the latest updates only had one for screen off (which is a little less secure IMHO), and when I used it, I would have to turn NFC off and then back on almost every time I used it, which defeated the purpose. I also saw that someone else was having the same issue, so I decided to compile one myself using the latest CM10 source. This was built from source as of 10/31/2012 and has only been tested on the nightly build with the same date. I figured I'd share it with everyone that might be needing the same.
Disclaimers: This requires a rooted phone! This has only been tested on the Sprint Galaxy Nexus running CM10 nightly dated 10/31/2012, but may work with other versions. Do a backup! I'm not responsible for any problems resulting from these files, so backup first!
To install, copy to your SD card. Reboot into recovery. DO A BACKUP! Install the zip from the SD Card. Reboot.
There are two versions I created. One is for when the screen is on, but locked. The other is for when the screen is off.
Update 1/2/2013:
I compiled a version of the screen locked for CM10.1 (Android v4.2.1) for anyone who would like it. I was getting mixed results with the previous file on 10.1. This one is working on my toroplus with the latest CM10.1 nightly. I'll build a screen off version later. I was having some problems with my build VM, so I didn't get to it yet. The new file for CM10.1 is called NFC_Screen_Locked_CM10.1.zip.
Update 1/3/2013:
The CM10.1 version of the screen off version is now posted. File name is NFC_Screen_Off_CM10.1.zip
Update 1/16/2013:
Previous version of NFC_Screen_Off_CM10.1.zip was not working. Should be working now.
Update 1/16/2013:
Added a patch that can be used against CM10 or 10.1 source code to add an option to the settings to switch between screen on, locked, or off NFC. You must build the entire thing from scratch to use this patch. There are logs of guides for building CM. Here's a link to the CM wiki article for toroplus for example. Before executing brunch, copy this file to the root of where you created the repo (the article uses the ~/android/system/ folder for instance) then execute the following two commands:
Code:
tar -xzf nfc-patch.tar.gz
./apply-nfc-patch.sh
Or in the use package manager to untar all of the files (maintaining the directory structure) and then double click and run the apply-nfc-patch.sh file. This will patch all of the necessary files in the build. Then continue with the instructions in the build guide and flash the resulting ROM.
Disclaimer Again: This could break your phone. I'm not responsible for any damages this may cause. This has only been briefly tested on my toroplus with the latest CM10.1 code from the repository.
Credits: Rick C who originally submitted most of this to the CM repository but was rejected.
Update 1/21/2013:
Looks like a recent commit to the repository broke one of the diffs in the patch. Uploaded a new version.
Update 2/13/2013:
Another update to fix an issue with the patch files. I also added a reset script that will do a hard reset for git repos of the affected packages. Don't use this script if you have made any other customizations to the Settings app, NFC app or the frameworks/base code as you will lose them. Just do things in this order:
1) run reset script
2) run repo sync
3) extract tar again
4) run apply script
5) run brunch again
You can use this sequence every time you want to grab the latest code.
If you get errors when running the apply script you can use this command to delete the error files that come up. These files might show up even if the patch works, but the code wasn't exactly what the patch was expecting, but enough to apply anyway.
Code:
find . \( -name \*.orig -o -name \*.rej \) -delete
This set of commands should do the trick for most people to get the latest code, apply the patch and build:
Code:
./reset-nfc-patch-repos.sh
repo sync
tar -xzf nfc-patch.tar.gz
./apply-nfc-patch.sh
source build/envsetup.sh && brunch <your-device-name>
Update 2/27/2013:
Made some fixes to the notes in the previous update based on feedback from mrplowdan.
Update 3/15/2013:
Compiled a new version of the CM10.1 files for those having issues.
Update 10/21/2013:
Added a test version of the screen locked version for CM10.2 now that toroplus has an official CM10.2 nightly. Let me know if there are any issues. I'll add a screen off version when I have some time.
Update 11/19/2013:
Finally getting around to adding a screen off version for CM10.2. The screen locked version has been running well on my toroplus for the last month with no issues.

Has anyone tested this on Maguro?

Just recently got my phone back from service (after 10 weeks) so i'm not re-rooted yet, hence i can not try this on stock myself. Just wanted to give a big thanks to you for creating and developing this this is really a truly great way to make use of the nfc and the way it should have been done from the very beginning. I.ex if your out running, listening to music and for some reason need to pause your music, just swipe a previosly attached nfc-tag on your sleve over your pocket with the phone in. And again to start music. Awsome work, thank you!
Sent from my Galaxy Nexus using xda premium

It may work on Maguro as long as you're using a fairly recent version of CM10. If I knew anyone with a device, I'd test it myself. It's fairly low risk to test. It only replaces a single file. It's the Nfc.apk in the /system/app/ folder. You could always rename your existing file; install this one; and then reboot and test it out. Also, if you're wary of the zip itself, you can just extract the Nfc.apk and copy it to your /system/app/ folder manually, just don't forget to reboot. Then if it breaks you can just delete the new one and rename the old one back. You could also just backup everything; install the zip; and just restore the backup if anything breaks. Anyway if you decide to be adventurous, let us know how it goes. I'll keep this thread updated if CM makes any other changes that break it again. I use it often, so I'll likely find out pretty quickly. Hopefully, they'll add this as a setting in CM10 some day.
Sent from my Galaxy Nexus using xda app-developers app

could i use it on every rom cm based?

It depends on how many modifications were made by the mod around NFC, if any. Also depends on when the last time was that they merged their code with CM. In theory it should work with most CM based mods. You can always try it out as I mentioned above and revert if it breaks. And post here with your results if you try it, so others can benefit.
Sent from my Galaxy Nexus using xda app-developers app

Locked version tried and working maguro. I'm on latest Jellybro. Good work and thanks
Sent from my Galaxy Nexus using xda premium

CM10.1 Update
I compiled a version of the screen locked for CM10.1 (Android v4.2.1) for anyone who would like it. I was getting mixed results with the previous file on 10.1. This one is working on my toroplus with the latest CM10.1 nightly. I'll build a screen off version later. I was having some problems with my build VM, so I didn't get to it yet. The new file for CM10.1 is called NFC_Screen_Locked_CM10.1.zip.

irotsoma said:
I compiled a version of the screen locked for CM10.1 (Android v4.2.1) for anyone who would like it. I was getting mixed results with the previous file on 10.1. This one is working on my toroplus with the latest CM10.1 nightly. I'll build a screen off version later. I was having some problems with my build VM, so I didn't get to it yet. The new file for CM10.1 is called NFC_Screen_Locked_CM10.1.zip.
Click to expand...
Click to collapse
Great work! - many thanks from me!
I'm waiting so long for the Screen-Locked Version ...
Best regards
JoSch

can it be included in cm10.1?
I was just wondering, can't this be somehow merged with stock cm10.1? Add checkboxes in the settings.apk, lots of warnings when enabling it and people who know can use it.
nice work btw

Screen Off for CM10.1
The CM10.1 version of the screen off version is now posted. File name is NFC_Screen_Off_CM10.1.zip

cthulu said:
I was just wondering, can't this be somehow merged with stock cm10.1? Add checkboxes in the settings.apk, lots of warnings when enabling it and people who know can use it.
nice work btw
Click to expand...
Click to collapse
Yes, actually I've been wanting to do this for a while, but I never seem to have the time to dig into the settings UI and how to read that setting. If you or someone else would be willing to create the settings piece and tell me how to access the setting that you create, I'd be happy to alter the NFC service to look at those settings. Ideally there should be a preference with an integer value of 1 for screen off, 2 for screen on but locked, and 3 for screen on and unlocked (default) as that's the value that the service expects currently.

First of all i would like to thank you posting this, just what I was looking for.
Im running one of the latest cm10.1 nightlies (jan 1st or 2nd) and flashed the NFC_Screen_off_CM10.1zip however it doesn't work while the screen is off, though it does work when the screen is on and the phone is locked. I have a Galaxy Nexus (gsm).
When I logcat the phone I don't see NFC being discovered with the screen of but with the screen on and the phone locked I do see that it discovers an NFC event.
Is there anything that can be done about this?
Thanks!

dannyvanderzande said:
First of all i would like to thank you ting this, just what I was looking for.
Im running one of the latest cm10.1 nightlies (jan 1st or 2nd) and flashed the NFC_Screen_off_CM10.1zip however it doesn't work while the screen is off, though it does work when the screen is on and the phone is locked. I have a Galaxy Nexus (gsm).
When I logcat the phone I don't see NFC being discovered with the screen of but with the screen on and the phone locked I do see that it discovers an NFC event.
Is there anything that can be done about this?
Thanks!
Click to expand...
Click to collapse
That's odd. I didn't have an NFC tag handy when I built the screen off version, so I assumed the same changes I made in CM10 would work in 10.1 since the screen locked version worked. I'll test it on my device and see if I can figure it out as soon as I get some free time. Thanks for letting me know!

irotsoma said:
That's odd. I didn't have an NFC tag handy when I built the screen off version, so I assumed the same changes I made in CM10 would work in 10.1 since the screen locked version worked. I'll test it on my device and see if I can figure it out as soon as I get some free time. Thanks for letting me know!
Click to expand...
Click to collapse
I decided to check the files out myself to try and figure it out and maybe quick fix it myself (which would have saved you the time) by referencing to the 10.0 apk's however I found out they differ a lot more from eachother than I expected so it was a bit too much for my skillz. I found this out using a comparison tool and while I was at it I compared the 10.1 screen lock and 10.1 screen off versions. According to my program they are exactly identical in either file structure as in file contents so I'm guessing something must have gone wrong with renaming or I just don't know how to use the tool? I'm just mentioning this as something I came upon, not to ***** or anything! I really appreciate the work you did!
Anyway.. I had some fun figuring things out and learning about decoding apk's and all of that. Thanks for all the hard word so far and I'll just wait patiently upon the new screen-off version.

The screen off one works perfectly for the Toro running the last stable 4.1.2 liquid smooth rom. Awesome work, thanks a million!
Edit: I'm not sure if it makes a difference but I didn't flash it, I pulled the apk from the zip, copied and pasted and reset permissions then restarted.

Fixed CM10.1 Screen Off
irotsoma said:
That's odd. I didn't have an NFC tag handy when I built the screen off version, so I assumed the same changes I made in CM10 would work in 10.1 since the screen locked version worked. I'll test it on my device and see if I can figure it out as soon as I get some free time. Thanks for letting me know!
Click to expand...
Click to collapse
OK, so I uploaded a new version. I actually tested it this time and this one worked for me on my toroplus. Let me know if there are any other issues, but you should be good to go after flashing this one. Sorry it took so long to get around to it. Enjoy!

Settings Patch for CM Source Code
cthulu said:
I was just wondering, can't this be somehow merged with stock cm10.1? Add checkboxes in the settings.apk, lots of warnings when enabling it and people who know can use it.
nice work btw
Click to expand...
Click to collapse
I did a little digging and found that there was a patch submitted to CM10 to include a switch for this in the settings. However, it was rejected by Steve Kondik and abandoned. I took all of the code and merged it into the latest CM10.1 code and it seems to work. I added a patch to the main post, but you have to compile CM from scratch to use it since it touches some framework components. The good news is it should work on any device that CM supports (that uses the NFC.apk though not devices that use NfcNci.apk like the Nexus 4) and should work on both CM10 and 10.1 in most cases.
The patch is basically just a few diff files and a bash script to automate the patching. If anyone is feeling adventurous, feel free to experiment with it. I can't promise it will work for you, but it's fun to try and learn a bit about building CM source code in the process. Basic directions are in the original post. As always I take no responsibility for anything it might break, but I'll be happy to try to troubleshoot if I can. Enjoy!

Thanks for all your effort.
Unfortunately it doesn't work on the nexus 4 but after some googling I found a working version for the nexus 4 on the forums here on xda. Im guessing there's a difference in chips or something...

dannyvanderzande said:
Thanks for all your effort.
Unfortunately it doesn't work on the nexus 4 but after some googling I found a working version for the nexus 4 on the forums here on xda. Im guessing there's a difference in chips or something...
Click to expand...
Click to collapse
Thanks for pointing that out. I clarified the previous post a bit. I should have said it should work with any devices that use Nfc.apk. Newer devices that use NfcNci.apk will not work with the patch.

[10-27-2014][ROM][KERNEL] UnityROM-2 v.3.0.1 [CM-11][GAPPS][Optimized]

UnityROM-2 v.3.0.1
LG Optimus G - Sprint US ONLY ( LS970 )
(INTERNATIONAL VERSION NOT HAPPENING || NO GEE/B EVER!!! || DO NOT ASK)
Basic Overview
Source built Cyanogenmod 11.0 with a bucket of butter poured on top .
Compiled and Built with SaberMod GCC 4.8 Toolchains with a lot of optimization flags set.
BUILDTYPE = SNAPSHOT ONLY
(Not meaning only once a month or so like CM Inc.)
Aroma Installation.
Purpose
Just trying to make a cleaner, faster, and generally more optimized build basically, without changing the ROM itself (apps & such). With some extra nice things thrown in even if there's is no visible difference in the ROM
Credits
@IAmTheOneTheyCallNeo for all of his help getting GCC 4.8 up and running finally. I owe you big man.
@Captain_Throwback for his original commits and help with the original thread & in this one as well.
@gruesomewolf for all of his help learning how to build a custom kernel.
Cyanogenmod Inc. & Google Inc. of course. For everything they do, way too much to try listing here.
LiquidSmooth for some additional build flags.
And please, if you like my work or the work others have contributed to this project, hit the thanks button. Thanks.
Features & Links
*** Global O3 & Strict-Aliasing=3 Optimizations & lots more ***
Full-Modular Aroma ROM & Gapps WITHIN the main package, yet still in separate directories.
Clean or Dirty ROM Flashing Options in Aroma.
Multiple LCD Density Options in Aroma.
System App Remover in Aroma.
Works with or without Gapps Installed
***UnityKernel-3.0.1 Features***
Optimized same as the UnityROM-2 only with GCC 4.9.
I/O Schedulers: SIO & FIOPS.
Governors: Intellidemand & Intelliactive.
LZ4 Compression/Decompression.
Current Release:
https://www.androidfilehost.com/?fid=95784891001602827
UnityKernel-3.0.1 Updater (includes previous 2.7.0 Kernel)
Current Release (UnityKernel Only):
Not available yet sorry ​​

Development Section

Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not

LiquidSmokeX64 said:
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
Click to expand...
Click to collapse
will this work on geeb?? ill defintely test if so

Extract the build.prop. It will tell you cause I really don't know lol. All I really know is I added the LS970 dependencies to my repo, did the UnityKernel mod and built it. So you tell me cause I'm not at my PC

dr3adl0ckd said:
will this work on geeb?? ill defintely test if so
Click to expand...
Click to collapse
LiquidSmokeX64 said:
Extract the build.prop. It will tell you cause I really don't know lol. All I really know is I added the LS970 dependencies to my repo, did the UnityKernel mod and built it. So you tell me cause I'm not at my PC
Click to expand...
Click to collapse
I am fairly certain it will run, but you might not have access to SD card or camera. If not, find out if there is a GEE/b kernel you can flash afterwards or if the OP can create a GEE/b kernel since it looks like it has a new kernel, aside from any other currently available. I know I've never seen UnityMod kernel anywhere.
To the OP, if you ask any of the other kernel devs what changes they made to produce a Gee/b kernel of the same settings I am sure they would provide some advice.
EDIT: some changes may be necessary in the build.prop as well to allow access to GSM.
EDIT: Don't really want to be part of this thread anymore and I haven't said anything useful

Ok. I am the OP BTW. Founder/Creator.
The UnityKernel cannot be found. It's the major unique feature of UnityROM-2. How it is done is quite simple. To me. But I remember when I had this phone. How badly it needs a good stable ROM. Just like jewel did till I did this.
So trying to do y'all a favor lol. The best ROM for Evo LTE now coming to the next Sprint "Problem Device".

LiquidSmokeX64 said:
Ok. I am the OP BTW. Founder/Creator.
The UnityKernel cannot be found. It's the major unique feature of UnityROM-2. How it is done is quite simple. To me. But I remember when I had this phone. How badly it needs a good stable ROM. Just like jewel did till I did this.
So trying to do y'all a favor lol. The best ROM for Evo LTE now coming to the next Sprint "Problem Device".
Click to expand...
Click to collapse
I saw you were the OP, that's why I quoted you too LOL. No worries. Thank you for building this ROM. I haven't tested it yet because I am working on getting the G3 port to work on our Sprint OG. But I am happy to check it out. I just wanted to let you know that you can build the geeb kernel too. I don't think it takes much, I think only adding or switching a branch for your build.
Also, if you created this ROM and built from sources, you might want to think about having this thread moved to Original Development instead of Development. This one is more for ports and changes to an existing rom in order for it to work on our phone. The new Roms and creations should go in the Original Development.
EDIT: Don't really want to be part of this thread anymore and I haven't said anything useful

LiquidSmokeX64 said:
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
Click to expand...
Click to collapse
You did a great job, it works fine. I think you should continue to work on perfection of Rom. As far as I understand, you need to go to another forum thread(Optimus G Original Android Development). When using the camera - got two crashes . everything else works perfectly, quickly and smoothly! Antutu received 20673 balls without my optimization. Thank you for a wonderful job. I know little about it, but it seems to me that all is well. This gproj or aosp based? You use the new driver for the camera? Excuse me for my english.

Well thanks for the feedback. I'll run 2.7.0 for LS970 now. Tons of new things added for the build and kernel

dopy25 said:
I saw you were the OP, that's why I quoted you too LOL. No worries. Thank you for building this ROM. I haven't tested it yet because I am working on getting the G3 port to work on our Sprint OG. But I am happy to check it out. I just wanted to let you know that you can build the geeb kernel too. I don't think it takes much, I think only adding or switching a branch for your build.
Also, if you created this ROM and built from sources, you might want to think about having this thread moved to Original Development instead of Development. This one is more for ports and changes to an existing rom in order for it to work on our phone. The new Roms and creations should go in the Original Development.
Click to expand...
Click to collapse
interesting.. @LiquidSmokeX64 let us know if you do the geeb kernel def anxious to try this rom out!

+1 would also want a geeb kernel for this.

dr3adl0ckd said:
interesting.. @LiquidSmokeX64 let us know if you do the geeb kernel def anxious to try this rom out!
Click to expand...
Click to collapse
Well if I knew what I need for geeb I would gladly make it for you guys. I just grabbed the stuff listed in CMs LS970 device cm.dependencies file.
I can always add more or a new defconfig file to have it look at while building. Either way will work

If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?

LiquidSmokeX64 said:
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
Click to expand...
Click to collapse
Yes sir!

LiquidSmokeX64 said:
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
Click to expand...
Click to collapse
with impatience [emoji14] [emoji14] [emoji14]

Vadik56 said:
with impatience [emoji14] [emoji14] [emoji14]
Click to expand...
Click to collapse
UnityROM-2 v.2.7.0 has arrived and is now posted
Fully featured now with all my normal modifications.
Yes Google apps are built-in... technically...
The separated internal directories make it OK to do this legally.
Enjoy everyone

LiquidSmokeX64 said:
UnityROM-2 v.2.7.0 has arrived and is now posted
Fully featured now with all my normal modifications.
Yes Google apps are built-in... technically...
The separated internal directories make it OK to do this legally.
Enjoy everyone
Click to expand...
Click to collapse
Thank you, download started. I feel will be a bomb-)-)

UnityROM-2 v.2.7.0 has arrived and is now posted
Installation fails
View attachment cm-UnityROM-2-v.2.7.0-ls970.zip.log.txt

Vadik56 said:
UnityROM-2 v.2.7.0 has arrived and is now posted
Installation fails
View attachment 2974972
Click to expand...
Click to collapse
Looks like you're flashing for the wrong device, or wrong recovery.

How Can I Modify Nougat ROMs For The OnePlus 3T?

Hello.
Few days ago I tried to modify LineageOS 14.1 for my OnePlus 3T.
I managed to create a flashable zip that changes the UI to Blue.
Then I thought of implementing it into the ROM itself.
I tried many tools for system.new.dat & system.new.transferlist.
I was able to decompile the files, but I couldn't recompile it
Any help would be appreciated!

ViperXvenom8888 said:
Hello.
Few days ago I tried to modify LineageOS 14.1 for my OnePlus 3T.
I managed to create a flashable zip that changes the UI to Blue.
Then I thought of implementing it into the ROM itself.
I tried many tools for system.new.dat & system.new.transferlist.
I was able to decompile the files, but I couldn't recompile it
Any help would be appreciated!
Click to expand...
Click to collapse
Just build it from source then you wont have this issue.

zelendel said:
Just build it from source then you wont have this issue.
Click to expand...
Click to collapse
The thing is building it from the source takes a long time (Have to download about 20GB of data or so) I already have the ROM (.zip). I just want to modify the System UI color to Blue

ViperXvenom8888 said:
The thing is building it from the source takes a long time (Have to download about 20GB of data or so) I already have the ROM (.zip). I just want to modify the System UI color to Blue
Click to expand...
Click to collapse
Well then you will have o wait for apktool to fully support android O then. Yes it is alot but then again doing things the right way was never meant to be easy.

zelendel said:
Well then you will have o wait for apktool to fully support android O then. Yes it is alot but then again doing things the right way was never meant to be easy.
Click to expand...
Click to collapse
Android O? Why?? I want to modify LineageOS 14.1 (Android 7.1.2)

ViperXvenom8888 said:
Android O? Why?? I want to modify LineageOS 14.1 (Android 7.1.2)
Click to expand...
Click to collapse
I made that assumption due to your last post being in a CM thread that was an 8.0 thread.
Best bet is to pull a logcat while it bootloops and that will tell you the issue. I have not done modding in this way in many years since I learned the proper way to mod them.

zelendel said:
I made that assumption due to your last post being in a CM thread that was an 8.0 thread.
Best bet is to pull a logcat while it bootloops and that will tell you the issue. I have not done modding in this way in many years since I learned the proper way to mod them.
Click to expand...
Click to collapse
I don't know how to pull logcats.
I modified it few days ago using some Windows 10 Tool I found on XDA that converts patch & transferlist to the old file system (app, priv-app, etc...) And used another tool to convert file_context.bin to file_context (file type). Tried to recompile and it bootloops... I just want to know how other developers apply changes to their ROM.
Thanks

ViperXvenom8888 said:
I don't know how to pull logcats.
I modified it few days ago using some Windows 10 Tool I found on XDA that converts patch & transferlist to the old file system (app, priv-app, etc...) And used another tool to convert file_context.bin to file_context (file type). Tried to recompile and it bootloops... I just want to know how other developers apply changes to their ROM.
Thanks
Click to expand...
Click to collapse
They build from source and make their changes.
You should learn how to do a logcat. It is trouble shooting 101 which will happen.
I will give you a hint. You are way off of where you want to be. The color is in the framework res. You either pull the apks from the device or have to build it from source.

zelendel said:
They build from source and make their changes.
You should learn how to do a logcat. It is trouble shooting 101 which will happen.
I will give you a hint. You are way off of where you want to be. The color is in the framework res. You either pull the apks from the device or have to build it from source.
Click to expand...
Click to collapse
I already pulled the framework-res and modified it properly. As I said before, I made a flashable .zip and it worked but the problem is how do I implement the changes into the ROM itself?

ViperXvenom8888 said:
I already pulled the framework-res and modified it properly. As I said before, I made a flashable .zip and it worked but the problem is how do I implement the changes into the ROM itself?
Click to expand...
Click to collapse
You would have to build it. Trying to do it your way will not work as roms are encrypting the files so they can't be pulled and edited that way. It was done to prevent people from making minor color changes and then calling it theirs.
Just build from scratch. It is easier and less hacky. Mainly with roms using private keys to sign their roms.

zelendel said:
You would have to build it. Trying to do it your way will not work as roms are encrypting the files so they can't be pulled and edited that way. It was done to prevent people from making minor color changes and then calling it theirs.
Just build from scratch. It is easier and less hacky. Mainly with roms using private keys to sign their roms.
Click to expand...
Click to collapse
Thanks for this info!
From the information I've gathered, I've found out that I need the Device Tree, Vendor Tree & Kernel of the OnePlus 3T from GitHub. Any idea on where to find those?
Thanks!

ViperXvenom8888 said:
Thanks for this info!
From the information I've gathered, I've found out that I need the Device Tree, Vendor Tree & Kernel of the OnePlus 3T from GitHub. Any idea on where to find those?
Thanks!
Click to expand...
Click to collapse
The easiest thing to do is use an already set up project like DU or (shudders) Los. Then all you have to do is sync the source. Los has a page set up to show you how to build as does DU. I would use du but that is just me.

zelendel said:
The easiest thing to do is use an already set up project like DU or (shudders) Los. Then all you have to do is sync the source. Los has a page set up to show you how to build as does DU. I would use du but that is just me.
Click to expand...
Click to collapse
Alright. Thanks a lot for all the information you have provided me!