yashsingh1/xdaforums huggingface dataset:
[Galaxy 3 Android Development] z3c0:
the su binary was already the same but the Superuser.apk was different. Still, no success when Titanium Backup or ClockSync try to grab root privileges.

Superuser even logs the attempts and claims to have denied them (even though it never asked, even when I set it to automatically grant requests).

When I call su from adb, the Superuser-log actually shows that a request from "root" was allowed.

right now I have su in /system/xbin and /system/bin with 0777 permissions (originally had rw-r--r-- and was only in /system/xbin).

What could this be?
[Galaxy 3 Android Development] kyrillos13:
Did you flashed it from recovery? If not, go on.
[Galaxy 3 Android Development] z3c0:
I used the Test 003 ODIN tar. I actually mounted the contained factoryfs.rfs and send the contents to my /system via tar but I'm confident that this shouldn't be the issue, since tar preserves all file attributes and seeing that someone else reported root problems first.

Since I never had this issue before, think it might have something to do with the way cm9 regulates Root Access in its own options, on top of Superuser. Perhaps something isn't optimally implemented there yet.
[Galaxy 3 Android Development] hillbeast:
I have a phone not booting issue at the moment. Ever since trying to use mini_config it crapped it's pants. Something to do with it now making the odex files correctly...

su should be 06755.

Wait until the next build which will be update.zip (yes another change to the format but this is the one I wanted from the start). The update.zip seems to have fixed SU.
[Galaxy 3 Android Development] hillbeast:
Update: Camera has started working, and the phone doesn't crash...

Not to moan... but WHY ARE THESE PROBLEMS FIXING THEMSELVES!?!?!?!

I shall make clean and make an update.zip and if it all works fine then I'll upload it.
[Galaxy 3 Android Development] hillbeast:
Another update: yep everything is all working now. I have everything all contained inside the device and vendor files, so no need to fiddle with webkit or mesa3d or any of that other stuff. So if you want to make it yourself, all the items you need to pull are listed on the first page. The hillbeast vendor repo is empty for now, but that's where I will put Kyoralock and all that stuff later.

Also I have shrunk down Google Apps by removing pointless files that won't work on our phone anyway (like video chat) and I am uploading that along with the latest version (20120503) as I speak, so you can install Google Apps with this version. After installing Google Apps, there is 16MB free, and more will be freed up when I get rid of the junk in the system. The space savings have come from simple optimisations.

Test 2012-05-03 uploaded to Mediafire

Link Link Link

View first page for changelog, but as far as I am aware everything that works in ICSforG3s build works here. Let me know though in case I made a mistake so I know to fix it. I tested everything that was broken (except for ringing people, however before Phone.apk did crash for me when I tried to and now it comes up and says no service, so that means to me it's working). Camera works (without previews, just gotta find the right preview device), rotation works, it's all there. Now just gotta get Mobile AP, Greenteeth and camera preview working and then I think we have CM9 working on our phone.

Also link for Google Apps is on the first page.
[Galaxy 3 Android Development] Darius_AWS:
Also do you know how to fix music playing trought streamin app ? (Vkontakte spotify grooveshark)
[Galaxy 3 Android Development] hillbeast:
What are they doing (or not doing)?
[Galaxy 3 Android Development] harkan89:
Nice work bro! Gonna test it out when I get back home from work.. :)
[Galaxy 3 Android Development] mankokoma:
in the updater-script I can see that /system will be EXT4:

run_program("/sbin/busybox", "mke2fs", "-m", "0", "-O", "has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize", "-L", "system", "-M", "/system", "/dev/block/stl6");
ui_print("Mounting system ...");
run_program("/tmp/busybox", "mount", "-t", "ext4", "/dev/block/stl6", "/system");

Do you think it would cause problems to comment out "run_program("/sbin/busybox", "mke2fs",.........." and mount /system as EXT2 (- what I'm using always for /system) before flashing the rom?
[Galaxy 3 Android Development] pante5:
Ok, I got a question.

On the first page there is the update.zip which is around 115 MB, my question is how to install it. I'm currently on Kyorarom 0.5.2.
[Galaxy 3 Android Development] m1trand1r:
flash it within cwm:)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sent from Galaxy

Hercolubus Rom v 2.2

powered by

Hillbeasts test 002 kernel.zip

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Galaxy 3 Android Development] pante5:
Tried it doesn't work. I get some error.
[Galaxy 3 Android Development] m1trand1r:
what error:eek:?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sent from Galaxy

Hercolubus Rom v 2.2

powered by

Hillbeasts test 002 kernel.zip

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Galaxy 3 Android Development] pante5:
So it writes...

assert failed: getprop ("ro.product.device") == "apollo" || getprop("ro.build.product") == "apollo" E:Error in /mnt/sdcard/update-cm-9-20120505-apollo-hillbeast-signed.zip

(Status 7)

Installation aborted.

I have no idea what anything of this means :D
[Galaxy 3 Android Development] m1trand1r:
i guess hillbeast will know more then me:)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Sent from Galaxy

Hercolubus Rom v 2.2

powered by

Hillbeasts test 002 kernel.zip

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[Galaxy 3 Android Development] cdesai:
Are you sure you are installing on a Galaxy 3? (Sounds kinda dumb but that's what the assert is for - to check if it's being installed on the device it was meant for

Remove that line(open updater-script in the zip - META-INF/com/google/android with Notepad++ if on windows, or any editor on linux/mac ), or edit your ROM's /system/build.prop, changing ro,product.device to apollo from whatever it is.
[Galaxy 3 Android Development] pante5:
Thanks for the feedback guys, and yeah its Galaxy 3 :D, and for me to go editing, well lets just say I'll wait till hillbeast takes a look at it :D
[Galaxy 3 Android Development] raja4sure:
Hey Mark,

When i use your test kernel 002 in ICS builds i get wrong colors......can you help me out here......
[Galaxy 3 Android Development] harkan89:
That's prolly because you're missing the OpenFIMG files..
[Galaxy 3 Android Development] hillbeast:
Yeah I have just used the default command that was in the script that I believe came from the P1. I want to change it to EXT2 but haven't gotten around to it yet.

Just edit the line to tell it to rm -rf /system/* so that you don't get any crap left over from your previous OS.

That assert basically checks the build.prop for what system you currently have. I need to either remove that line or make it allow whatever the device is called in old Froyo ROMs. I thought this issue might pop up to haunt me at some point, was just hoping not now. Delete your build.prop and try again.

Which ICS? Mine or ICSforG3s? If it's on ICSforG3 then update it to build 4.1
[Galaxy 3 Android Development] harkan89:
Is it just me or is the build missing a file manager??
[Galaxy 3 Android Development] hillbeast:
Yes because they haven't put that in CM9 yet... don't ask why...
[Galaxy 3 Android Development] harkan89:
Lol.. Okay.. I thought it was something I did when I removed some files from /system/app of the update.zip.. Btw. I tried to adb install root explorer but ended up getting an error saying "/sbin/sh: pm: not found" ..
[Galaxy 3 Android Development] raja4sure:
Well I am on build4 update 1 ...and i flashed the kernel & now bad colors....

So i tried again to update to 4.1 through CWM but still the same....

I am actually waiting for your next release....so can you share yours libGLES_fimg.so so i can replace it in here...if there is no prob in your build with colors
[Galaxy 3 Android Development] hillbeast:
That's really odd. Using adb push I assume?

Latest build is already up and colours are all fine. Everything in it works. At this stage the only thing that will go into the next release is just an updated CM9 repo (more language stuff pretty much), and a fixed update.zip which supports more firmware to install from.
[Galaxy 3 Android Development] harkan89:
Nope.. Using "adb install". "adb push" works fine, although adb pushing the apk into the /system/app or /data/app doesnt seem to have any effect..
[Galaxy 3 Android Development] pante5:
Thanks, and one more question, how to delete build.prop?
[Galaxy 3 Android Development] raja4sure:
Are you saying the build listed above is build 2012-05-03 ????
[Galaxy 3 Android Development] hillbeast:
Can you install apks from Market? ie install ES File Explorer from the Market? I will add a File Manager in the next version. Promise.

adb shell

mount -o rw,remount /system /system

rm /system/build.prop

reboot recovery

You can do that from Terminal Emulator if you wish, just do su at the start.

Yes.
[Galaxy 3 Android Development] harkan89:
Lol.. Already taken care of that.. Installed ES File Explorer from market, and then installed Root Explorer from SD card and deleted ES File Explorer.. :P

EDIT: Just one more thing I noticed.. The Soft button lights dont seem to be turning on at all... Anyone else facing this issue?
[Galaxy 3 Android Development] pante5:
Ok,

so I deleted as you said and the phone went on some sort of seizure :D when you turn it on its starts flashing white, and vibrates and so on so on :D

Nevermind, gonna flash something else. :)
[Galaxy 3 Android Development] hillbeast:
You need to reboot into recovery. Hold down both volume buttons and home while the phone is turning on, so have those buttons pressed before the GT-I5801/5800 logo shows on screen.
[Galaxy 3 Android Development] moole:
Not sure why you're bothering with busybox and those long format/mount commands in the updater script.

A simple

format("ext2","stl","/dev/block/stl6");
mount("ext2","stl","/dev/block/stl6","/system");

should work.
[Galaxy 3 Android Development] hillbeast:
I don't know why either, I'm just working with what was there. I have just been adapting the current code to make it work. Best to not change something that was already there in order to make something else happen when it could cause issues. Perhaps I will change it later.
[Galaxy 3 Android Development] moole:
I'm testing it right now by modifying your update.zip. Will let you know if it works properly. :)

---------- Post added at 01:43 PM ---------- Previous post was at 01:18 PM ----------

Seems to be working properly, just need to change the format command to

format("ext2","stl","/dev/block/stl6","0");

since the CM9 update-binary requires a 4th argument to format.

P.S. Thank you for the latest build - enjoying it so far!
[Galaxy 3 Android Development] hillbeast:
Not sure why... but I found a problem most likely with G3MOD where it CANNOT unmount /system in CWM. As a result it won't format /system AT ALL. I had to actually zero-fill it just to get it to unmount. Something weird is going on here and I'm going to get to the bottom of it...
[Galaxy 3 Android Development] moole:
The camera app is crashing for me in the latest build.
[Galaxy 3 Android Development] hillbeast:
Might be linked to the fact the system won't format...
[Galaxy 3 Android Development] moole:
Nah, formatted fine with my commands + I manually formatted it before running the update.zip.
[Galaxy 3 Android Development] propsia:
for mee too

1.camera ap crashes

2. titaniumbackup restore fails

3. Facing several freezes while going through settings

4.not able to install app from ADB via install command some error arises

and also by using push command nothing shows in app drawer

else all is good
[Galaxy 3 Android Development] VinC0deur:
From MPics 2.0, can I flash this update ?

Envoyé depuis mon apollo avec Tapatalk
[Galaxy 3 Android Development] hillbeast:
I can't see why not.
[Galaxy 3 Android Development] hillbeast:
I seem to have ironed out all the weird kinks, except for the Camera app crashing. It was working, and then it stopped. Really bizarre. I will take another look and see why it's doing that. I was taking photos with it earlier before it died again.

As far as adb install, that's fixed. I've added File Manager (the proper CM one built from source), added Kyoraapp (whether it works is up to you to test but I cna't see why the basics of it won't work). Check the first page for the full list of fixes I've gotten going in the last 6 hours of solid coding I've done. I'm exhausted now and I have work in 8 hours so it's time for bed for me.

I might release it tomorrow night but don't hold me to that. Feed me some more bug reports over the next day so I can iron out any more weird kinks that it has.

Also I took a look at the GPS and that thing is pretty screwed. Something is seriously wrong there. No simple fix will fix how broken that is. Gonna have to add that to the not working list.
[Galaxy 3 Android Development] Darius_AWS:
Apps like vkontakte sporify and grooveshark launch but they don't play the music...not even a noise but they didn't force close like youtube app
[Galaxy 3 Android Development] pmanian:
Try removing the following code from https://github.com/dharamg3/G3MOD/blob/master/initramfs/init_ics.rc to make init.d work.

service playlogo /sbin/post-init.sh
user root
oneshot
[Galaxy 3 Android Development] z3c0:
Interestingly the Camera did work for me in the previous 05-01 build (without preview, but photos were taken correctly). In 05-03 it won't even start.

Other things I've noticed:

no sound recording

no livestreaming of audio (already mentioned elsewhere, just wanna recommend Xiialive Beta for testing, as it features 3 alternative streaming methods in its settings, none of which work now)

so GPS isn't working, but also the Wifi-strength triangulation method for localization fails. Usually it works without GPS, especially in denseley populated areas. While this might be related to the Wifi indicator in the status bar showing no signal strength, it's interesting that signal strengths are displayed correctly in the Wifi-settings (where all present networks are scanned). Maybe the data source can be copied from there?

Some Apps can't be installed, neither via Google Play nor by Titanium, even though they worked flawlessly up until cm7.2 (Glympse, Google Currents, Google Goggles, myTaxi, Parcels, TweetDeck, Windfinder). Now they're supposedly "not compatible with your device". Only a few among 80+ Apps which I successfully reinstalled though.

This must be a new problem with the 05-03 build because for an instance I had no problems installing TweetDeck on 05-01, which then uninstalled itself when I upgraded to 05-03. Most of the missing apps seem to have in common that they use the Google Maps API, but I don't think Currents and Goggles do. (disregard this one. my fault)

There are other issues but it's probably no use discussing them now (very App specific / low priority). All in all this ROM is already working surprisingly well.
[Galaxy 3 Android Development] kyrillos13:
For the last issue, you must install google apps. It will be fixed.
[Galaxy 3 Android Development] z3c0:
I did. I'm on gapps-ics-20120429, using symlinks as described here, just as I was on the 05-01 build. Google Maps is working just fine on 05-03 (except for the known slight FIMG glitches and it being unable to find my location either way).

Or did you mean the network location finding method (my 3rd bullet point)? There's a NetworkLocation.apk among gapps that might differ from the other versions of gapps but I doubt this is the problem. If network location is actually working for someone else though, I'll try whatever version they're using.

---------- Post added at 10:00 AM ---------- Previous post was at 09:26 AM ----------

:eek: dammit, I lacked com.google.android.maps.xml in /system/etc/permissions.

Now the issue (bullet point 4) is fixed, had nothing to do with hillbeast's build.

Thanks for the hint, kyrillos!
[Galaxy 3 Android Development] hillbeast:
The Camera is being a right pain in the bum. I'm not sure why it's coming and going. It's as reliable as a plumbers estimate.

Sound recording, I assume from a voice recorder or such?

Livestreaming will be looked into when I get the chance.

As for GPS, that is also a weird one and will be looked into.
[Galaxy 3 Android Development] z3c0:
For all kinds of Apps that require getting something from the microphone, so not only sound recording but all of the speech recognition stuff and visualizers.

I experimented with all kinds of input sample rates (since sometimes either 44.1kHz or 48kHz aren't supported) and sources (since e.g.RecFroge seems to offer a front and a rear microphone) but all you get is a flatline.

Perhaps it's most useful to look at the logcat of the visualization app Audalyzer, since it uses no hardware graphics and doesn't encode the input, limiting the verbose clutter: logcat on pastebin
[Galaxy 3 Android Development] bioniclizard:
Regarding music streaming, Deezer seems to work fine.
[Galaxy 3 Android Development] hillbeast:
New Build on MediaFire

Link

Check the first page for the changelog.
[Galaxy 3 Android Development] nishant_713:
Microphone is already known not be working (Except phone calls). And for me ROM is quite smooth. Not tested GPS and Camera.
[Galaxy 3 Android Development] DiGaTTo:
Please fix wating call problem
[Galaxy 3 Android Development] h4r5h:
Tried flashing the latest build (04-05-2012) over CM7 Alpha8.1, but unfortunately got stuck at the I5801 bootlogo. The screen just keeps on blinking.:eek:

Anyways, downloading the Test 003 .tar file now and then will try to flash it over that. Hopefully it'd work fine after that (fingers crossed) :)
[Galaxy 3 Android Development] z3c0:
Looked into it, Deezer seems to be accessing simple music files from webservers, thus it's not quite the same as playing a continuous stream.

In case it might help, here are the logcats using Xiialive Beta's different stream engines on the 05-04 build: Android (Stable) | FFMpeg | Android (Beta)
[Galaxy 3 Android Development] DoR2:
When I try to flash Serenity from Kyorarom Ascendency I get the mistake

assert failed: getprop("ro.product.device") == "apollo" || getprop("ro.product.product") == "apollo"

and installation stops. What's wrong???
[Galaxy 3 Android Development] pante5:
I got the same msg, then I flashed CM9, and tried to update trought CWM and it worked.
[Galaxy 3 Android Development] h4r5h:
EDIT: Working fine now! *Phew* :)
[Galaxy 3 Android Development] DoR2:
Serenity installed only from MIUI build 4. I hate this evil mistake!!!:mad::mad::mad:
[Galaxy 3 Android Development] hillbeast:
Please explain what the bug is. I can't replicate it on my end without more details on what happens.

and

Try the new build (2012-05-04). Link on the first page.
[Galaxy 3 Android Development] DiGaTTo:
During the call you have incoming call and sound diseapers, if you want to put one on hold phone freez.
[Galaxy 3 Android Development] Rekooo:
-- Installing: /sdcard/update-cm-9-20120504-apollo-hillbeast=signed.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "apollo" ||
getprop("ro.build.product") == "apollo" ||
getprop("ro.product.device") == "GT-I5800" ||
getprop("ro.build.product") == "GT-I5800"
E:Error in /sdcard/update-cm-9-20120504-apollo-hillbeast=signed.zip
(Status 7)
Installation aborted.

Installing on CM9 build4.1
[Galaxy 3 Android Development] moole:
Should just remove the assert in the updater-script.

As for a temp fix, try toggling script asserts on and off in CWM recovery.
[Galaxy 3 Android Development] ABD3Fs:
Only to me??

Hi, Hillbeast:

I´m having a bug with ALL the 4.0.x roms. The music player scratch the songs...it happens in some songs, not in all, but is not a file bug. Until yesterday I had a 2.3 rom and it works perfectly, but flash your great rom and it happens again (I tested all the 4.0.x rom before this 2.3).

This happens only to me or anyone else?

Thanks for your great work!!!
[Galaxy 3 Android Development] z3c0:
Did you change something about the notification-area in recent builds? When you drag down the status bar, that blue circle symbol is now always 2/3 to the right instead of centered. Same in horizontal mode. (tough stuff we have to put up with here... ;))

Also, very occasionally the notification area first appears completely empty (not even the power widgets showing up) until you try again a few times or wait. Not quite sure yet.
[Galaxy 3 Android Development] hillbeast:
For the little blue circle, I know about that one but haven't bothered with that as it's more of a themeing issue, most likely related to the fact I have chosen the device as an MDPI device rather than an LDPI device like ICSforG3 did. Reason for that is because LDPI is slowly being deprecated and it gave me a hell of a headache while compiling with it trying to find all the LDPI files (which are gone now because, as I said they are being deprecated), so in the end I just gave up and told it it's an MDPI device. Unfortunately this makes the APKs a little bigger, but really it's a price worth paying in order to get a device to compile without issues and having to resort to modifying CyanogenMods files.
[Galaxy 3 Android Development] pkatsaras:
Wow man! In this way I believe it will be easier to work in 3.0 kernel?

P.S. Why didn't you post all these stuff in Kyorakernel thread? I am dying to test this kernel! Are you going to release it both in OC and NON-OC version?
[Galaxy 3 Android Development] hillbeast:
Because this is not Kyorakernel. This is ICS kernel which is based on G3MOD. I might make it non-OC at some point but I need to figure out how I will distribute it. Perhaps a second update.zip or something.
[Galaxy 3 Android Development] hillbeast:
New version uploaded to Mediafire

Link

Check the first page for the changelog. A few things there that may be interesting to some. If you use Hybrid Data2SD then DON'T update to this version, or if you do, use G3MOD. The kernel provided has NO support for Hybrid Data2SD at this stage.
[Galaxy 3 Android Development] alb3rtt:
will this kernel support cm7? or will you keep it cm9 only?
[Galaxy 3 Android Development] pkatsaras:
So does this support froyo or are you planning to release a froyo based kernel with these features?
[Galaxy 3 Android Development] harkan89:
Er.. Was it a little too "bloody" as some claimed?? How about this one? Based on the G3MOD Rebirth poster I had made sometime back?? The bootlogo feature was kickass.. Would love to still have it rather than the boring "GT-15801" message :p
[Galaxy 3 Android Development] hillbeast:
To be honest, I am not sure. It may work, but I won't hold my breath.At this stage I will say no, but in the future yes it will.

In the future, yes it will support everything. At this stage it's ICS only.

It doesn't say GT-I5800 now. It doesn't say anything in fact. Just a black screen with a little progress bar that goes along. I have kept it black until I find a good logo, and that looks sweet. Might use that.

I just need to remember how to add a boot logo...

What I might do is use initlogo.rle and then people can put one on the SD card to replace it if they don't like it. I just have to learn how to use initlogo.rle then.
[Galaxy 3 Android Development] cdesai:
If you ever read the whole boot log, you'll know that the kernel in fact does try to load and display /initlogo.rle, so you could try making one (loads of guide out there, i remember using a to565 binary to make one)
[Galaxy 3 Android Development] metalfeild:
i am unable to download titanium backup...after downloading the phon reboots automatically :confused:

EDIT: infact i cant install any app from market