yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] RukusX7:
Nothing beats building a ROM from the ground up :)

Everything works properly but the orientation sensor. It's being recognized as AOSP with limited function. I wonder if this is that orientation fix that [MENTION=2993366]ThdDude[/MENTION] was mentioning.
[Galaxy S II General] titanic_fanatic:
Yeah, but pa is kickin' me in the butt ;) I was thinking about trying this with an aosp rom, but not sure it would work since the hardware framework is so different.
[Galaxy S II General] RukusX7:
hmmm sounds a little out of my scope, but I see no reason why it shouldnt work? I'd try with just the boot.IMG replaced to see if it will boot.
[Galaxy S II General] ThdDude:
[MENTION=4859152]titanic_fanatic[/MENTION] I added your tile fixes but have not tested yet myself, just letting you know.
[Galaxy S II General] RukusX7:
There will be a hellkat port of a hercules build sitting in my Android File Host if anyone if interested in testing. You will need to calibrate your sensors in the advanced s ettings menu upon installation for the rotation to work properly.

Thank you.

[MENTION=4887322]iDynamics[/MENTION]
[Galaxy S II General] RukusX7:
Updated OP to include iDynamics in the Special Thanks section.

:)

overlays still don't work properly in the port. They do work, but glitch out when returning from screen off and the screen will blank then reboot.

will need to disable overlays at every boot or add [MENTION=4859152]titanic_fanatic[/MENTION] 's 91fixoverlays script to the init.d I'll include it next time. If you aren't interested in doing this yourself, then stick to the main hellkat build please.
[Galaxy S II General] RukusX7:
[MENTION=4859152]titanic_fanatic[/MENTION] I replaced all the ko files and lib/ hw folder anyway. I botched my work and couldn't replicate things but you're ideas worked. The other method retained most Hercules files with only a few replaced
[Galaxy S II General] titanic_fanatic:
Glad to hear :) I've decided to start trying to compile with the linaro toolchain. That with the mods from the hellkat kernel might give us a speedy build.

I'm doing this to take a break from pa, cause it's giving me a headache. I just haven't figured it out yet. I get no boot at all, just what looks like a command prompt only it looks like this:

Android_

And the _ flashes a couple of times and then stops. I can't find anything about what I'm calling the android prompt ;) if you come across anything related to this, please send it my way.
[Galaxy S II General] RukusX7:
Good news! I'm glad my kernel hacking has gave you some ideas for your new builds. :) Yeah, I dunno about PA. I tried building Beanstalk which is from the same developer. I gave up and started working on hellkat. :)

I have no idea, I didn't get far enough in my beanstalk build to even install it on my phone. I'll keep an eye out in the forums.

Anyone know anything about the ION_IOC_ALLOC out of memory error in the logcat? Ive been trying to take some logs, but my phone reboots with disable hardware overlays unchecked
[Galaxy S II General] RukusX7:
[MENTION=4887322]iDynamics[/MENTION] or anyone running my port or hellkat build, I need you to test something for me.

Please leave Disable Hardware Overlays unchecked. Head into Display settings and disable "DayDream" and use the phone as normal.

Please report with any issues (I hope none) or good news ( I hope lots)

edit: here is my report. Bad News. phone rebooted on lock screen. Of course I was clicking it off and on repeatedly for science.
[Galaxy S II General] iDynamics:
I'm currently in my college's library I'll test it out later.
[Galaxy S II General] formercontra:
I'd said before without hwoverlays I get the horizontal green lines, I haven't had those in the last few hours, but the screen does occasionally flicker. Nothing besides that.
[Galaxy S II General] RukusX7:
Can anything be done for the ION_IOC_ALLOC memory issue like TeamHackLG did here?
[Galaxy S II General] RukusX7:
This is running my port? or build? Please state which build. :)

I only get lines odd time and lines and RR's from turning the screen back on after being off. screen goes blank, keylights stay on, count to 5 and phone reboots.
[Galaxy S II General] formercontra:
This is your build, the Feb 16th upload on your site
[Galaxy S II General] RukusX7:
[MENTION=4859152]titanic_fanatic[/MENTION]

How did you come up with the hex value for

CONFIG_SEC_KERNEL_REBASE_FOR_PMEM_OPTIMIZATION

in our defconfig? Its not the same as the skyrocket or the hercules. I've tried following the error and its led me to

arch/arm/mach-msm/include/mach/ion.h

Where it appears to call on that FLAG I set in the defconfig. We appear to be having some errors when calling to our ram for memory allocation. Or if anyone can throw some insight into this? [MENTION=2993366]ThdDude[/MENTION] I'll ask Cl3kener too
[Galaxy S II General] titanic_fanatic:
The kernel config option was set in the stock rom's defconfig and I couldn't find any info on it, so I really don't know what it does and left it the same as stock for that reason.

As for the memory sizes, I think you'll find that information here:

WORKINGDIR/kernel/samsung/msm8660-common/arch/arm/mach-msm/board-msm8x60_celox.c

I do believe this is the file that will control all of that.

EDIT:

Also, my linaro build is almost done. Only one little hiccup so far. I think CM has done a considerable amount of work in making sure their repos will compile with Linaro which is why I haven't run into 40 build errors like I did the last time I tried to compile using Linaro.

This build will include most features from the Hellkat kernel as well as it's all compiled with Linaro ;)

EDIT 2:

Wholly crap, the build is done... I'm so excited to try this one out. You should be able to also compile with the linaro toolchain very easily.

If building for KK/CM-11, download this toolchain:

android-toolchain 4.8

If building for JB/CM-10.2, download this toolchain:

android-toolchain 4.7 (ICS, JB)

then extract the android-toolchain-eabi folder to WORKINGDIR/prebuilts/gcc/linux-x86/arm. After that, you need to setup the build environment to use the new toolchain. Use the following commit as a guide of what to change:

https://github.com/DJLaMontagneIII/android_build/commit/656fe94ce56904d26ac384a397c1d7036791aec7

Last, but not least, I needed to swap out this file:

WORKINGDIR/kernel/samsung/msm8660-common/arch/arm/boot/compressed/Makefile

with the one I've attached to this post (don't forget to remove the .txt extension. I had to add it to upload the file) ;) That should get you compiling with the linaro toolchain. Why use linaro? It's an optimized toolchain and applies many optimizations for compiling. It's also very strict and requires that you follow coding practices not checked by standard toolchains. This optimization is supposed to translate into smaller filesizes and which in turn results in less memory used to load a lib since the filesizes are smaller. All in all, it's supposed to give you 100% better performance. This is, however, debatable and there have been some who have done tests with the same build using both toolchains, and in those tests, the performance was only marginally better. This was done using Antutu and apparently using Linaro won't help your Antutu scores, but I'm sure it has some benefit. I guess testing is the only way to find out.
[Galaxy S II General] RukusX7:
hehe my kernels are compiled with the linaro toolchain too :) But i wanted to know how to compile alone without a ROM, so this is good!!

I might have some changes to my kernel and you might not be able to build it from hellybean sources anymore. I found possible memory

address errors that need to be resolved. I am comparing my work to opensource JB for reference and Cl3kener and I found some discrepency's. I'll keep you updated with my changes of course. This should fix the hardware overlays issues.
[Galaxy S II General] titanic_fanatic:
I see that the toolchain is included in their repo. wished I had noticed that earlier ;)

I'm not building from the hellybean sources anyways. I cherry-pick or manually add patches to my kernel, and I always diff the files in beyond compare (meld will do the same) before I change anything. I don't read all the code, but skim through it all so I have a visual.

Those memory address issues have always been there since JB (not sure about stock) and I just don't know how to fix them. I would love to see any and all documentation that you guys come up with. I eat that stuff up like it's chocolate :P

What files in the kernel are on your radar at the moment? If like to focus on something specific of I could. Also, hangouts is not notifying me of incoming messages so I end up checking, or rather forget to check frequently for messages do I apologize if it seems as if I'm ignoring you :P
[Galaxy S II General] RukusX7:
Turns out, all i need to do is modify the defconfig. Here is the scoop I found:

ION is the new unified memory management architecture that Google is advancing. Prior to ION, every SoC manufacturer had their own way of doing memory management. Qualcomm's was pmem, Nvidia's was nvram, etc. It made it's debut as an option in ICS and is preferred in JB. Being unified also means that it is a good candidate for integration into the Linux kernel mainline, which would mean that Android would no longer require it's own separate branch of Linux.

so, turns out, our kernel just isn't up with the times. everything wants to use ION to allocate memory, but pmem is in control.

New hellkat build and kernel on the way. Here are the changes to the defconfig (that is all) [MENTION=4859152]titanic_fanatic[/MENTION] (havnt commited)

-CONFIG_SEC_KERNEL_REBASE_FOR_PMEM_OPTIMIZATION=y

-CONFIG_PHYS_OFFSET=0x48000000

+#CONFIG_SEC_KERNEL_REBASE_FOR_PMEM_OPTIMIZATION is not set

+CONFIG_PHYS_OFFSET=0x40400000

This matches the skyrocket and hercules. Please try at own risk. I have the build on the way, but I have a tiny bit research first. I am comparing stock skyrocket/hercules to stock celoxhd
[Galaxy S II General] RukusX7:
here is the documentation on ION

http://lwn.net/Articles/480055/
[Galaxy S II General] titanic_fanatic:
If you change CONFIG_PHYS_OFFSET, don't forget to also change that in the BoardConfig.mk in our device tree as well.

---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------

What about the two pmem options below?
[Galaxy S II General] RukusX7:
config SEC_KERNEL_REBASE_FOR_PMEM_OPTIMIZATION

bool "Kernel Rebase for PMEM Optimization"

default n

help

This option is used to place kernel base to 0x48000000 instead of 0x40400000.

config PHYS_OFFSET

hex

default "0x48000000" if SEC_KERNEL_REBASE_FOR_PMEM_OPTIMIZATION

default "0x48000000" if SAMSUNG_MEMORY_LAYOUT_ARRANGE

default "0x40400000"

oops. I prob should leave that memory address at 0x48000000

?????
[Galaxy S II General] RukusX7:
no other changes.
[Galaxy S II General] titanic_fanatic:
Not even in the BoardConfig.mk??? This is the ramdisk offset I'm referring to. aren't they somehow tied together
[Galaxy S II General] RukusX7:
oops maybe change that so CWM builds properly. dammit I never noticed it there.
[Galaxy S II General] titanic_fanatic:
That's why we're in this together ;)
[Galaxy S II General] RukusX7:
but Skyrocket source doesnt have that included and I read somewhere that Samsung doesnt use that line anyway.... so I am going to omit it and see what I find out!!!

I am not sure if that hex address needs to bs 0x480 or 0x404 Because both are acceptable values. I should leave it as it and disable pmem.

the korean variant of our phone doesnt even have those flags included!!

I am going to build it with 0x480
[Galaxy S II General] titanic_fanatic:
All devices are required to have the ramdisk offset for packaging the boot.img. This is a requirement as of cm10.1 I think unless that has been modified in hellybean. I doubt it though since people just adapted to it anyways. It's specified for the celox family of phones in the celox-common device tree which we inherit from. You'll find the 404 hex specified there. It's overridden in ours, and I'm more inclined to say use it, so yeah. If you just remove that line, it will use the 404 hex anyways since we inherit that ;) then make the same change in the defconfig. I'm feeling more confident about this now. Did you pull the stock jb defconfig of a skyrocket? I wonder if they used pmem originally since we do virtually have the same phone.
[Galaxy S II General] RukusX7:
I get worried, because the skyrocket and hercules and it seems EVERY other variant out there has a slightly different board called MSM8660_SURF. and ours seems to relate more to the HTC msm8660... hm which i am now gonna research
[Galaxy S II General] RukusX7:
i set it as 0x480 and ommited that line from the boardconfig.mk

I dont know what to do.... lol I stopped my build. I need to look at this some more.
[Galaxy S II General] RukusX7:
jared@Satellite-L300 ~ $ adb shell cat /proc/iomem

00500000-00500fff : msm_ssbi.0

00700000-007060ff : hdmi_msm_qfprom_addr

00c00000-00c00fff : msm_ssbi.1

04100000-04100fff : kgsl_2d0_reg_memory

04100000-04100fff : kgsl-2d0

04200000-04200fff : kgsl_2d1_reg_memory

04200000-04200fff : kgsl-2d1

04300000-0431ffff : kgsl_3d0_reg_memory

04300000-0431ffff : kgsl-3d0

04400000-044fffff : msm_vidc.0

04600000-046fffff : msm_gemini.0

04700000-047effff : mipi_dsi

04a00000-04a00fff : hdmi_msm_hdmi_addr

04e00000-04efffff : msm_rotator.0

05100000-051effff : mdp

05300000-053fffff : msm_vpe.0

05300000-053fffff : msm_vpe

10200000-102000ff : pil_modem

12140000-121407ff : msm_sdcc.2

12180000-121807ff : msm_sdcc.3

121c0000-121c07ff : msm_sdcc.4

12200000-122007ff : msm_sdcc.5

12400000-124007ff : msm_sdcc.1

12500000-125003ff : msm_hsusb_host.0

12500000-125003ff : msm_otg

16000000-16000003 : gsbi_qup_i2c_addr

16000000-16000003 : qup_i2c

16080000-16080fff : qup_phys_addr

16080000-16080fff : qup_i2c

16200000-16200003 : gsbi_qup_i2c_addr

16200000-16200003 : qup_i2c

16280000-16280fff : qup_phys_addr

16280000-16280fff : qup_i2c

16300000-16300003 : gsbi_qup_i2c_addr

16300000-16300003 : qup_i2c

16380000-16380fff : qup_phys_addr

16380000-16380fff : qup_i2c

16500000-16500003 : gsbi_resource

16500000-16500003 : msm_serial_hs

16540000-16540fff : msm_serial_hs.0

16600000-16600003 : gsbi_qup_i2c_addr

16600000-16600003 : qup_i2c

16680000-16680fff : qup_phys_addr

16680000-16680fff : qup_i2c

16c00000-16c001ff : msm_rng.0

18200000-182001ff : msm_tsif.0

18320000-1841ffff : msm_dmov.0

18420000-1851ffff : msm_dmov.1

18500000-1850ffff : qce.0

18500000-1850ffff : qcrypto.0

18700000-18700fff : ssbi_base

18700000-18700fff : i2c_ssbi

19800000-19800003 : gsbi_qup_i2c_addr

19800000-19800003 : qup_i2c

19880000-19880fff : qup_phys_addr

19880000-19880fff : qup_i2c

19900000-19900fff : gsbi_resource

19900000-19900003 : gsbi_qup_i2c_addr

19940000-19940fff : uartdm_resource

19940000-19940fff : msm_serial_hsl

19980000-19980fff : qup_phys_addr

19980000-19980fff : qup_i2c

19a00000-19a00003 : gsbi_qup_i2c_addr

19a00000-19a00003 : qup_i2c

19a80000-19a80fff : qup_phys_addr

19a80000-19a80fff : qup_i2c

19c00000-19c00fff : gsbi_resource

19c00000-19c00003 : gsbi_qup_i2c_addr

19c40000-19c40fff : uartdm_resource

19c40000-19c40fff : msm_serial_hsl

19c80000-19c80fff : qup_phys_addr

19c80000-19c80fff : qup_i2c

1b800000-1b8000ff : smsc911x.0

28100000-2810dfff : msm-dai

28800000-288000ff : pil_qdsp6v3

48000000-777fffff : System RAM

48100000-48b79f8b : Kernel text

48c00000-4935537f : Kernel data

77800000-778fffff : ram_console

77900000-78bfffff : System RAM

IF this isn't affected by what we set in the kernel.... I probably should set it to 0x480.... Or what do you think?
[Galaxy S II General] titanic_fanatic:
It's not the board that's different, they all pull from the same code aurora forums repository, you should check that out, straight up Qualcomm source also referred to as (CAF). CAF had the entire build source of both aosp and the kernel. You can see the changes they make to source to get things to work on their boards. Cm inserts this into their code surrounded by special comments that allow the code to only compile for devices that are qcom. This is the same stuff applicable to all Qualcomm devices.

---------- Post added at 07:07 PM ---------- Previous post was at 07:03 PM ----------

My guess is it would affect the last 5 of them related to where the kernel and ramdisk are located. I don't know what effect this would have. Maybe I can get sunshine top post one grin the skyrocket for us to compare ;)
[Galaxy S II General] RukusX7:
There has to be NO way that is affected by what i set in the kernel. A physical address is physical right? meaning, they use that word because its NOT virtual ?
[Galaxy S II General] RukusX7:
Another GREAT read. I might learn something and clobber my build.. AGAIN. lol

http://lwn.net/Articles/394665/

We might lose our camera......
[Galaxy S II General] titanic_fanatic:
Why will we loose the camera? Does it have to do with the lib? How hard can it be to find this hex value and change it to support the new convention?

Yes, excellent read :)

EDIT:

Just thought if something, maybe the camera lib for the skyrocket has this modification?
[Galaxy S II General] RukusX7:
Something to do with the camera requiring pmem physical mapping and ION not having that support obviously. Or I could be entirely wrong.

also, iomem only shows the current physical mapping, so yes, what i do choose affects the map. At least from what I understand. So we have to remap so ION can work properly, but then the camera doesnt know where to look for its ram when it needs to decompress a jpeg or something. I really wish i knew where i read this.

here is kernel that looks like something I am talking about

http://xdaforums.com/showthread.php?t=2560386

Which will make you understand why I am starting to feel nuts, because the HTC devices seem to have more in common with our device than Samsung.
[Galaxy S II General] RukusX7:
So what I am trying to say about the kernel differences is that there is no need for further modification in the hercules/skyrocket kernel because it does't pose this problem. :) i am looking at the HTC source and coming up with a solution!! That is, if i require it.

Edit: I am not a programmer, but it appears that safety's were implemented that will fix this.... Only one way to find out. wish me luck.
[Galaxy S II General] titanic_fanatic:
What do you mean by that, to fix the ion issue?
[Galaxy S II General] RukusX7:
Yeah. Because we use a different physical mapping because of our camera for some reason, and so does the HTC which shares our generic kernel.
[Galaxy S II General] titanic_fanatic:
I can tell you that dsixda had to contact the manufacturer of the camera to get the lib in the first place. I think it was a company out of Hong Kong. I'll See if I can dig up the post.
[Galaxy S II General] RukusX7:
This is where I REALLY need your help. You can fork the hellybean kernel or my kernel for this. You will still need to make the defconfig changes as I havnt committed them. :)

You'll understand quickly whats going on.
[LG G Flex] mr pnut:
We'll I sure didn't know that you could add Widgets on the Locksceeen like 4.3 and above, even though we are running 4.2 but it seems that were running a higher version 4.2 lol

Sent from my Enormous G Flex.
[LG G Flex] reeher3287:
Lol yeah I didn't know either found out by accident. Even had I shortcut to the cam then found you can skip the to right like on 4.3 an bams the cam!
[LG G Flex] mr pnut:
Yup the same way I found out.

Sent from my Enormous G Flex.
[LG G Flex] sweets55:
Trying to figure out how to do this but can't. Scratch that it just popped up. Lol
[LG G Flex] wase4711:
I cant even get the shortcuts to work on the lockscreen, let alone set a widget...:eek:
[LG G Flex] mr pnut:
On your Locksceeen just swipe down.

Sent from my Enormous G Flex.
[G2 Q&A, Help & Troubleshooting] podagee:
After playing with mahdi rom and furnace kernel i liked the use of the proximity sensor how it turns the phone on and off. Ive tried a few apps from the playstore but none worked such as smart screen,etc. Would be very thankful if someone provides a link or app for the lg g2 stock. Thanks in advance.
[G2 Q&A, Help & Troubleshooting] mestguy182:
Did you try dynamic notifications on Google play?
[G2 Q&A, Help & Troubleshooting] podagee:
looking for something more like pocket mode. when you cover the proximity sensor the screen turns off and when you uncover it turns on.
[G2 Q&A, Help & Troubleshooting] dccoh:
I use Smart Cover from the Playstore. There is a Lite version also.

I've used this on my previous S3 and now on my LG G2 and it works great for me.

Good luck.
[G2 Q&A, Help & Troubleshooting] podagee:
thank you that was exactly what i was looking for.
[G2 Q&A, Help & Troubleshooting] mestguy182:
This is exactly what dynamic notifications does.
[G2 Q&A, Help & Troubleshooting] podagee:
It sure does drain battery though
[Sprint Samsung Galaxy Note 3] hobokenshmo:
So the way I rooted was I flashed CWM via Odin, and then flashed SuperSU zip in CWM. I used the correct versions and i verified I had root with Titanium Backup and even Root Checker. I have tried twice to flash roms and I end up in samsung logo boot loop, don't even get any further than that. I downloaded 2 different roms that are meant for the Sprint Note 3 and work on my build number. Perhaps my root method screwed it up some how? Any ideas what is happening? From reading other posts, I realize I may have to flash another kernel, but on the rom (MiniN3) it said nothing of the sort. So, what gives?
[Sprint Samsung Galaxy Note 3] slow_one:
what rom firmware where you be fore flashing the new rom? did you tried to wipe cache/date after flashing?
[Sprint Samsung Galaxy Note 3] hobokenshmo:
Well I restored back to factory 4.3 stock, then use another 4.3 custom rom.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] drkiller:
hi to all since yesterday i am trying to update my PDA2K form I-mate to W2005 but no luck i am getting an error messge

ERROR 100: Model ID ERROR

i have this error with all.. TuMa_v1.4 ..WM2K5_5.4.01_HN.. WM2k5_v4_R2.1.. WM5_ArtZ_upgrade_WWE 1.7.1.3400_SD_ROM..

i tryied to update using MaUpgradeUt_noID.exe

it did not work it just work when douwgreading to w2003

i tryed to use editfix.bat

xda3nbftool -x ms_.nbf ms_.nba 0x20040522

xda3nbftool -x nk.nbf nk.nba 0x20040521

xda3nbftool -x radio_.nbf radio_.nba 0x20040523

xda3nbftool -so CDL__001 -sl WWE ms_.nba -sd PH20B

xda3nbftool -so CDL__001 -sl WWE nk.nba -sd PH20B

xda3nbftool -so CDL__001 -sl WWE radio_.nba -sd PH20B

xda3nbftool -c -u NK.nba

xda3nbftool -c -u ms_.nba

xda3nbftool -c -u Radio_.nba

xda3nbftool -x ms_.nba ms_.nbf 0x20040522

xda3nbftool -x nk.nba nk.nbf 0x20040521

xda3nbftool -x radio_.nba radio_.nbf 0x20040523

del *.nba

but no luck...

btw what is the best update w2005..a lot of ver. and i am getting lost witch one is the newest.

:shock: please if anyone solved this problem let me know...thanks for help
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] drkiller:
SOLVED.....

problem Solved.....go here

http://xdaforums.com/viewtopic.php?t=49611

download the file unrar all files to same dir where u have the update files....and use MaUpgradeUt_noID.exe......

this one working fine...only this one....othere not working