Database Users

Attn Froyo ROM devs: Hero vs. Eris libhtc_ril.so ?

Hi folks,
Have a peek at posts #27 and #30 over in the Q&A thread about spontaneous call drop/reconnects which appear to be due to segfaulting of the "rild" daemon in Froyo ROMs
At this point, it is speculative whether or not the Sprint Hero version of libhtc_ril.so has something to do with the problem or not (the "rild" daemon is also different in Froyo ROMs from the most recent Eris 2.1 OTA release), but it seems like that would be the first thing to look at (experimentally, since we don't have the source code for it.)
Your feedback would be appreciated - in particular - are you using the Sprint Hero version of libhtc_ril.so in all of your Froyo ROMs for the Eris?
bftb0

bftb0 said:
Hi folks,
Have a peek at posts #27 and #30 over in the Q&A thread about spontaneous call drop/reconnects which appear to be due to segfaulting of the "rild" daemon in Froyo ROMs
At this point, it is speculative whether or not the Sprint Hero version of libhtc_ril.so has something to do with the problem or not (the "rild" daemon is also different in Froyo ROMs from the most recent Eris 2.1 OTA release), but it seems like that would be the first thing to look at (experimentally, since we don't have the source code for it.)
Your feedback would be appreciated - in particular - are you using the Sprint Hero version of libhtc_ril.so in all of your Froyo ROMs for the Eris?
bftb0
Click to expand...
Click to collapse
Shouldn't be a problem if the person who compiles CM6 was using the extract-files.sh script in the device repo. It contains most/all of all the proprietary libraries necessary for a fully functional device.
Extracted from a working 2.1 build and then pre-linked(http://github.com/darchstar/android_device_htc_heroc/blob/froyo/prelink-linux-arm-heroc.map) for functionality.
Check conaps device repo: http://github.com/Conap30/android_device_htc_desirec
I don't see one for KaosFroyo, I just see and update.zip(?).
Either way, there's a lot of differences because of the proc type. Something we found out the hard way when we tried to merge the Hero(GSM) and the Hero(CDMA) device repos together.
There would be a lot of erroneous bugs until we finally decided it would be best to split them apart again.
Seeing as TazzFroyo is a direct port from the CM6 nightlies for HeroC, it's very likely that you guys are facing the same issues.
One of the things that Conap has been working on is fixing up the prelink map, something that you guys could help out on and finally have the most stable and functional froyo.
(Man, I really kill conversations)

Thank you Decad3nce - I learn a great deal from every one of your posts.
I unpacked a number of recent Eris Froyo (and legacy) ROMs for comparison:
Code:
[email protected]:~/Android/tmp$ md5sum `find . -name libhtc_ril.so -print`
939ed5e367b1291492c25915ce793a4b ./original1.17.605.1/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./21_julOTA/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./21_leak_v3/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./htc_sprint_hero_mr_2.27.651.6/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./update-cm-6.0.0-Heroc-RC1/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./CELBFroyo2.6/system/lib/libhtc_ril.so
fa6f724144bdb7b08c340fa264ecad27 ./kaosfroyo-V34/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./TazzFroyo-Vanilla-6.0/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./TazzFroyo-2.0/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./nonsensikal_v5.4/system/lib/libhtc_ril.so
64b4e08d3d34a3b662f3ba820c6bc306 ./tenzomonk_Vanilla2.0.3/system/lib/libhtc_ril.so
It looks like the TazzFroyo & nonsensikal ROMs have been using the Sprint Hero Vendor RIL;
KaosFroyo uses something I don't recognize - perhaps an earlier Sprint Hero Vendor RIL ? (it is internally timestamped "HTC-RIL 2.0.0053HM (Feb 24 2010,00:01:16)" - just two days earlier than the Sprint Hero MR2 version) ;
tenzomonk is using an older RIL in his AOSP Vanilla - "HTC-RIL 1.6.1045G (Nov 12 2009,11:19:21)" ;
Only Conap's CELBFroyo2.6 seems to be using an Eris Vendor RIL library.
( Note the last Eris 1.5 release ("MR2" or "1.17.605.1") had a version number of "HTC-RIL 1.5.1030H (Oct 27 2009,22:14:44)" - I don't know if tenzomonk is using a Leak-V{1,2} Eris library or a Sprint library.
bftb0

bftb0 said:
Thank you Decad3nce - I learn a great deal from every one of your posts.
I unpacked a number of recent Eris Froyo (and legacy) ROMs for comparison:
Code:
[email protected]:~/Android/tmp$ md5sum `find . -name libhtc_ril.so -print`
939ed5e367b1291492c25915ce793a4b ./original1.17.605.1/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./21_julOTA/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./21_leak_v3/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./htc_sprint_hero_mr_2.27.651.6/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./update-cm-6.0.0-Heroc-RC1/system/lib/libhtc_ril.so
2857bca5b51163004d2254a1b13ab0cd ./CELBFroyo2.6/system/lib/libhtc_ril.so
fa6f724144bdb7b08c340fa264ecad27 ./kaosfroyo-V34/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./TazzFroyo-Vanilla-6.0/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./TazzFroyo-2.0/system/lib/libhtc_ril.so
e921186c8e5342fdf8c2fccac9f9f632 ./nonsensikal_v5.4/system/lib/libhtc_ril.so
64b4e08d3d34a3b662f3ba820c6bc306 ./tenzomonk_Vanilla2.0.3/system/lib/libhtc_ril.so
It looks like the TazzFroyo & nonsensikal ROMs have been using the Sprint Hero Vendor RIL;
KaosFroyo uses something I don't recognize - perhaps an earlier Sprint Hero Vendor RIL ? (it is internally timestamped "HTC-RIL 2.0.0053HM (Feb 24 2010,00:01:16)" - just two days earlier than the Sprint Hero MR2 version) ;
tenzomonk is using an older RIL in his AOSP Vanilla - "HTC-RIL 1.6.1045G (Nov 12 2009,11:19:21)" ;
Only Conap's CELBFroyo2.6 seems to be using an Eris Vendor RIL library.
( Note the last Eris 1.5 release ("MR2" or "1.17.605.1") had a version number of "HTC-RIL 1.5.1030H (Oct 27 2009,22:14:44)" - I don't know if tenzomonk is using a Leak-V{1,2} Eris library or a Sprint library.
bftb0
Click to expand...
Click to collapse
You'll always have the best stability with your specific proprietary libraries created for your board, which as you've just presented means that the best stability may be in CELBFroyo2.6.
KaosFroyo RIL could be from anywhere; since he 'optimizes' his libs(still not sure what that means).
Hope that helps. Wasn't sure if you were asking a question with your response but oh well lol.

Decad3nce said:
Wasn't sure if you were asking a question with your response but oh well lol.
Click to expand...
Click to collapse
No questions. At this point I'm just going to use Tazz 2.0 with the lib replacement to see if the problem disappears or not. Hopefully I will get some help, either of the form "I tried the lib replacement, and still had the same problems", or "it used to happen to me all the time and has stopped since I started using the Eris library".
bftb0

bftb0 said:
No questions. At this point I'm just going to use Tazz 2.0 with the lib replacement to see if the problem disappears or not. Hopefully I will get some help, either of the form "I tried the lib replacement, and still had the same problems", or "it used to happen to me all the time and has stopped since I started using the Eris library".
bftb0
Click to expand...
Click to collapse
FWIW: I switched to CELBFroyo2.6 from KaosFroyo and have not had that problem any more...

eldouche said:
FWIW: I switched to CELBFroyo2.6 from KaosFroyo and have not had that problem any more...
Click to expand...
Click to collapse
That seems consistent with what Decad3nce is saying, although I don't know specifically what Conap might have done for his CM6 builds. He was aware of the problem with his CM5.0.8 builds - a couple of people reported it directly in his dev thread for his (CELB 2.8-CMS5.0.8) ROM, so maybe he took some measures in his CM6 builds.
As for my hypothesis about the libhtc_rild.so vendor library being the source of the problem - I experienced the same problem less than 8 hours after replacing only that library - again, a crash of "rild" was reported exactly at the moment of failure.
At this time, I am running a CM6 ROM with both "rild" and "libhtc_ril.so" replaced by the HTC Eris 2.1 (July 17 OTA) versions of the code to see if the problem will disappear.
bftb0

bftb0 said:
That seems consistent with what Decad3nce is saying, although I don't know specifically what Conap might have done for his CM6 builds. He was aware of the problem with his CM5.0.8 builds - a couple of people reported it directly in his dev thread for his (CELB 2.8-CMS5.0.8) ROM, so maybe he took some measures in his CM6 builds.
As for my hypothesis about the libhtc_rild.so vendor library being the source of the problem - I experienced the same problem less than 8 hours after replacing only that library - again, a crash of "rild" was reported exactly at the moment of failure.
At this time, I am running a CM6 ROM with both "rild" and "libhtc_ril.so" replaced by the HTC Eris 2.1 (July 17 OTA) versions of the code to see if the problem will disappear.
bftb0
Click to expand...
Click to collapse
I have had reports of this with my 2.2 rom as well....and this is not just a problem with the eris...other phones have reported it also...specifically someone with an DI running cm6 has the same issue...

bftb0 said:
That seems consistent with what Decad3nce is saying, although I don't know specifically what Conap might have done for his CM6 builds. He was aware of the problem with his CM5.0.8 builds - a couple of people reported it directly in his dev thread for his (CELB 2.8-CMS5.0.8) ROM, so maybe he took some measures in his CM6 builds.
As for my hypothesis about the libhtc_rild.so vendor library being the source of the problem - I experienced the same problem less than 8 hours after replacing only that library - again, a crash of "rild" was reported exactly at the moment of failure.
At this time, I am running a CM6 ROM with both "rild" and "libhtc_ril.so" replaced by the HTC Eris 2.1 (July 17 OTA) versions of the code to see if the problem will disappear.
bftb0
Click to expand...
Click to collapse
Take note if you see the linker library crapping out though. Replacing libraries seems kind of iffy if you want to conduct a proper experiment. The best way to go about it would be to compile with those replaced RIL libraries prelinked.

Conap said:
I have had reports of this with my 2.2 rom as well....and this is not just a problem with the eris...other phones have reported it also...specifically someone with an DI running cm6 has the same issue...
Click to expand...
Click to collapse
Might be bad prelink map

Decad3nce said:
Might be bad prelink map
Click to expand...
Click to collapse
i'll look at that...
Edit: They don't seem to be prelinked...

bftb0 said:
At this time, I am running a CM6 ROM with both "rild" and "libhtc_ril.so" replaced by the HTC Eris 2.1 (July 17 OTA) versions of the code to see if the problem will disappear.
Click to expand...
Click to collapse
How did you replace them ? Can you just 'adb push' them to the phone and reboot ?

Conap said:
i'll look at that...
Edit: They don't seem to be prelinked...
Click to expand...
Click to collapse
libhtc_ril.so is prelinked.
Ours:
Code:
# libraries for specific hardware
libgsl.so 0xA2E00000 # [~1M]
libhtc_acoustic.so 0xA2D00000 # [<64K]
libhtc_ril.so 0xA2C00000 # [~1M]
liblvmxipc.so 0xA2B00000 # [~1M] for vendor/nxp
libreference-cdma-sms.so 0xA2A00000 # [<64K] for hardware/ril

hallstevenson said:
How did you replace them ? Can you just 'adb push' them to the phone and reboot ?
Click to expand...
Click to collapse
You can do it with the OS running (I did). But, you do need to be careful about file permissions and owner/group ownership on all files you fool around with - "adb push" won't set those correctly. (In particular "rild" seems to have user/group = root/shell, mode 755 on Tazz 2.0). It is probably safest to do it offline (meaning, with Amon_RA booted, using adb and "mount /system").
I think I did something like this (interactively, with the regular OS booted):
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb push libhtc_ril.so /system/lib/libhtc_ril.so.Eris
adb push rild /system/bin/rild.Eris
adb shell
md5sum /system/bin/rild.Eris /system/lib/libhtc_ril.so.Eris [COLOR=grey]( safety check )[/COLOR]
chmod 755 /system/bin/rild.Eris
chgrp shell /system/bin/rild.Eris
chmod 644 /system/lib/libhtc_ril.so.Eris
mv /system/lib/libhtc_ril.so /system/lib/libhtc_ril.so.CM6
cp /system/lib/libhtc_ril.so.Eris /system/lib/libhtc_ril.so
mv /system/bin/rild /system/bin/rild.CM6
cp -p /system/bin/rild.Eris /system/bin/rild
ps | grep rild
kill -HUP <pid of the rild process>
logcat -d [COLOR=grey]( look for any complaints about rild failing ) [/COLOR]
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
reboot
Or something close to that
Note I did it this way so that it would be easy to revert - there seems to be plenty of space in /system with Froyo ROMs
bftb0

Decad3nce said:
Take note if you see the linker library crapping out though. Replacing libraries seems kind of iffy if you want to conduct a proper experiment. The best way to go about it would be to compile with those replaced RIL libraries prelinked.
Click to expand...
Click to collapse
I agree with you - I recursively walked through all the dependencies
Code:
arm-eabi-objdump -x $obj | grep NEED
and thought, "dlopen() is going to barf immediately", based on all the libraries that potentially get demand-loaded - but it didn't.
Sort of a low cost experiment in the meantime. Too bad we don't know how to force the segfault deterministically - getting any sort of result experimentally takes friggin forever because the incidence of the problem is sporadic. (Anybody want to run rild under strace for several days? - LOL)
I'm trying to keep my eyes on it. (In the meantime, I'll also try to figure out what "prelink map" means)
bftb0

Decad3nce said:
libhtc_ril.so is prelinked.
Ours:
Code:
# libraries for specific hardware
libgsl.so 0xA2E00000 # [~1M]
libhtc_acoustic.so 0xA2D00000 # [<64K]
libhtc_ril.so 0xA2C00000 # [~1M]
liblvmxipc.so 0xA2B00000 # [~1M] for vendor/nxp
libreference-cdma-sms.so 0xA2A00000 # [<64K] for hardware/ril
Click to expand...
Click to collapse
Maybe i'm checking the prelink wrong...i am using isprelink. I type ./isprelink libgps.so...it gives me the number. When i do it on the libhtc_ril it says its not prelinked...is there another way to do it?

bumpitty bump. I really want to figure this out. Any way for me to help.

Well, conap and I looked into it.
The first thing we noticed is that, even though libhtc_ril.so is in the prelink.map, it doesn't get linked properly.
One of two things could cause this:
1. The libraries being mapped before it(address wise), exceed their bounds and thusly don't leave enough allocated memory for libhtc_ril.so
Conap and I looked further into this and we noticed that libhtc_acoustic.so ALSO doesn't get mapped correctly, even though it is in the prelink map.
To fix this, we'd have to just simply restructure the prelink map.
2. Now this one would be a bit more tricky, and I think this may be what the cause is.
When the prelink map sets up all the addresses, everything gets mapped correctly. You can tell that it does because everything following libhtc_acoustic.so/libhtc_ril.so gets mapped properly. The thing that MAY be happening is that libhtc_acoustic.so(most likely) or something before it, exceeds its allocated bounds when it's ACTIVE. This is a problem that just about every Froyo compile has faced. Currently, libhtc_acoustic is mapped with \\ libhtc_acoustic.so 0xA2D00000 # [<64K] \\
At less than 64k space. If it exceeds that bound, while active, then it could offset libhtc_ril.so.
I haven't tested any of this, as I don't really mess with the froyo compilation side of things.

I went through all the libs in my build and found ten that are not prelinked but are on the prelink map.....
lib/libhtc_acoustic.so: not prelinked
lib/libhtc_ril.so: not prelinked
lib/libjpeg.so: not prelinked
lib/libmm-adspsvc.so: not prelinked
lib/libmm-omxcore.so: not prelinked
lib/libOmxCore.so: not prelinked
lib/libOmxH264Dec.so: not prelinked
lib/libOmxMpeg4Dec.so: not prelinked
lib/libOmxVidEnc.so: not prelinked
lib/libspeech.so: not prelinked
I guess off to google to figure out how to correctly change the prelink map so that these libs get prelinked...

I haven't had any call drop issues other than the normal amount being in the basement surrounded be concrete kills cell reception
Sent from my FroyoEris using XDA App

[ROM][DEAD]Froyolicious-v4[FROYO,AOSP,Vanilla,NOT CM6] -"Better than ice cream!"

[ROM][DEAD]Froyolicious-v4[FROYO,AOSP,Vanilla,NOT CM6] -"Better than ice cream!"
This is no longer supported.
Well, maybe not better than Rocky Road and Amaretto, but still pretty good!
This is direct port of the AOSP Froyo OTA for the myTouch 3G (http://forum.xda-developers.com/showthread.php?p=8607277#post8607277). In case you can't tell, it's AOSP 2.2 (Frozen Yogurt). This does not contain CyanogenMod parts at all. I've taken a few things from Official Obsession, which is a stock Eris ROM with the July OTA. And, I've used the DecafuctCFSv5 kernel. Otherwise, it's straight from the OTA linked above.
Thanks to:
Decad3nce and Conap for the kernel and corresponding modules
dasunsrule32 for the link to the OTA
dsixda for the fantabulous Kitchen
Framework for the eri.xml file from Senseless
amoeller for putting together Official Obsession
I highly recommend that you update Google Maps to the newest version. In a future update, I will most likely either do this or remove Maps entirely and leave it up to you.
What doesn't work that I noticed:
camera
browser screen rotation
soft button lights
gps is inaccurate
MMS
I've tested and found working:
phone functions
data/browser
SMS
Market
Exchange email
GPS
gmail
The UI is very responsive. And the phone seems to be very stable so far. (I've been running this since 10-19-10.) Unfortunately, it's not compiled from source, which is really the ROM that I would have liked to put out there. This is the next best thing though.
Here's what I did.
1) downloaded Froyo OTA and Official Obsession (http://forum.xda-developers.com/showthread.php?t=726604&highlight=Obsession)
2) copied both of them to the Kitchen's original_update folder
3) selected porting tools from the advanced menu and followed the prompts
4) used Kitchen to add root, busybox, bash, and nano
5) used Kitchen to deodex and zipalign
6) removed radio.img (don't want to flash that!), check_prereq, error.565, and install.565 files
7) changed all instances of 'sapphire' and 'opal' to 'desirec' in build.prop and update-script
8) removed 'assert getprop("ro.bootloader")...' line from update-script
9) removed 'run_program PACKAGE:check_prereq 1285103450' line from update-script
10) removed any lines with 'radio' from update-script
11) copied 'desirec-keypad.kcm.bin' and 'melfas-tsi-ts.kcm.bin' from OO to /system/keychars and deleted 'sapphire-keypad.kcm.bin'
12) copied 'desirec-keypad.kl' and 'melfas-tsi-ts.kl' from OO to /system/keylayout and deleted 'sapphire-keypad.kl'
13) copied 'sensors.desirec.so' from OO to /system/lib/hw and deleted 'sensors.sapphire.so'
14) copied /system/etc/firmware/*' from OO and deleted 'brf6300.bin'
15) copied /system/etc/apns-conf.xml from OO over top of Sapphire version
16) used Kitchen to extract boot.img
17) renamed init.sapphire.rc to init.desirec.rc
18) used WinMerge to compare init.desirec.rc with same file from OO AND made several changes
19) used WinMerge to compare init.rc with same file from OO AND made several changes
20) copied any binaries from OO that init.rc and init.desirec.rc call but are not in /system/bin and/or /system/xbin
21) deleted init.goldfish.rc from ramdisk
22) replaced boot.img-kernel with zImage from DecafuctCFSv5
23) copied modules from DecafuctCFSv5 to /system/lib/modules (overwriting existing wlan.ko)
23) deleted 'com.amazon.mp3.apk' from /system/app
24) used WinMerge to compare build.prop with the one from OO and add/change appropriate lines like ril settings, for instance...
25) copied /system/etc/gps.conf from OO over top of existing one
26) used Kitchen to create /data/app structure
27) copied eri.xml from Senseless to try and fix 'T-CDMA 64' text on lockscreen instead of trying to edit framework-res.apk (lazy @$$)​
DOWNLOAD HERE:
v1 - http://surrette.org/roms/Froyolicious-v1.zip
v2 - http://surrette.org/roms/Froyolicious-v2.zip
v3 - http://surrette.org/roms/Froyolicious-v3.zip
v4 - http://surrette.org/roms/Froyolicious-v4.zip
Have fun!

v2
updated bash shell to v4.1
fixed lights by copying lights.msm7k.so from OO
updated to DecafuctCFSv6 kernel and modules
added these to build.prop for possible UI speed increase:
windowsmgr.max_events_per_sec=60
ro.dalvik.heapsize=32m​added several lines to init.desirec.rc from kaosFroyo for power management, etc.
added several lines to init.desirec.rc from CELBFroyo because it looks good
added one line to init.rc from CELBFroyo that might help with camera?
opitimized entire ROM using opto_signer (http://forum.xda-developers.com/showthread.php?t=805766)
added wirless tether
added akmd binary from OO to /system/bin, overwriting original (I think this fixed screen rotation.)
v3
updated to CFSv8 kernel and modules
added Spareparts
fixed sending MMS by replacing /system/etc/apns.xml with one from CELBFroyo
removed Protips
changed "T-CDMA 64" to Verizon by hex editing eri.xml in framework-res.apk (<-- This worked.)
v4
integrated collin_ph's/Decad3nce's battery tweak
changed battery tweak's default config

Looks good!

Looks nice. I will check it out tonight.

most excellent!
i have one of these laying around here too... thanks to your builder!

looks good cant wait to try it....but I gotta wait for the Camera to work.....I have a 2yr old ...so always got to have a camera handy
thanks for the work

Great! Having more choice is good! Thanks for the work you did. I, too, will wait for the camera to be fixed, unless Camera 360 will work on this, but I'm assuming the stock has to be fixed more before a third-party can really work well.
Thanks, gnarlyc.

MMS
Does MMS work on this ROM? As far as I know MMS doesnt work for any 2.2 Roms. Looks great though.

bigshotrob22 said:
Does MMS work on this ROM? As far as I know MMS doesnt work for any 2.2 Roms. Looks great though.
Click to expand...
Click to collapse
mms works on my rom what are u talkin about?

I have my Eris flashed to Cricket. Is yours flashed to cricket or on Verizon? What ROM are you using?

bigshotrob22 said:
I have my Eris flashed to Cricket. Is yours flashed to cricket or on Verizon? What ROM are you using?
Click to expand...
Click to collapse
no im on verizon and using my rom sorry

O its okay..I really like 2.2 but I haven't gone to it yet until someone can fix the mms issue..I have my 2.1 Rom themed to look like 2.2..lol
Sent from my Eris using XDA App

bigshotrob22 said:
O its okay..I really like 2.2 but I haven't gone to it yet until someone can fix the mms issue..I have my 2.1 Rom themed to look like 2.2..lol
Sent from my Eris using XDA App
Click to expand...
Click to collapse
MMS works for me too using Nonsensikal (Froyo).

Is it Verizon or Cricket network?
Sent from my Eris using XDA App

bigshotrob22 said:
O its okay..I really like 2.2 but I haven't gone to it yet until someone can fix the mms issue..I have my 2.1 Rom themed to look like 2.2..lol
Sent from my Eris using XDA App
Click to expand...
Click to collapse
so this mms issue is a cricket thing?

Yup..
Sent from my Eris using XDA App

bigshotrob22 said:
Yup..
Sent from my Eris using XDA App
Click to expand...
Click to collapse
well i dont know and unless u plan on usin this rom i would make a thread and ask so this one dont get hyjacked

Ok Thanks
Sent from my Eris using XDA App

So the camera issue... is that the grid with the ball issue or something else?
Sent from my FroyoEris using XDA App

Stonent said:
So the camera issue... is that the grid with the ball issue or something else?
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
The camera app just shows a black screen and then FCs after a few minutes. Here's my most recent logcat. I haven't had a chance to dig around past this.
Code:
10-21 18:37:27.635: ERROR/dalvikvm(362): Failed to find cpu subsys
10-21 18:37:27.645: ERROR/dalvikvm(362): Failed to find cpu subsys
10-21 18:37:27.645: ERROR/dalvikvm(362): Failed to find cpu subsys
10-21 18:37:27.665: ERROR/ActivityManager(84): ANR in com.google.android.camera (com.google.android.camera/com.android.camera.Camera)
10-21 18:37:27.665: ERROR/ActivityManager(84): Reason: keyDispatchingTimedOut
10-21 18:37:27.665: ERROR/ActivityManager(84): Load: 0.0 / 0.0 / 0.0
10-21 18:37:27.665: ERROR/ActivityManager(84): CPU usage from 6435ms to 1298ms ago:
10-21 18:37:27.665: ERROR/ActivityManager(84): system_server: 5% = 2% user + 2% kernel / faults: 109 minor 4 major
10-21 18:37:27.665: ERROR/ActivityManager(84): m.android.phone: 2% = 1% user + 0% kernel / faults: 2 minor
10-21 18:37:27.665: ERROR/ActivityManager(84): adbd: 1% = 0% user + 1% kernel
10-21 18:37:27.665: ERROR/ActivityManager(84): rild: 0% = 0% user + 0% kernel
10-21 18:37:27.665: ERROR/ActivityManager(84): .android.camera: 0% = 0% user + 0% kernel / faults: 36 minor 1 major
10-21 18:37:27.665: ERROR/ActivityManager(84): smd_tty: 0% = 0% user + 0% kernel
10-21 18:37:27.665: ERROR/ActivityManager(84): kondemand/0: 0% = 0% user + 0% kernel
10-21 18:37:27.665: ERROR/ActivityManager(84): logcat: 0% = 0% user + 0% kernel
10-21 18:37:27.665: ERROR/ActivityManager(84): TOTAL: 12% = 5% user + 6% kernel

Swap Partition Testers on Atrix Wanted

Hello all in the Atrix forums.
I'm a Bionic user, and I recently created a guide for making and enabling a swap partition which works on both the Android side and the Webtop side simultaneously. An Atrix user sent me a PM today with an issue that I would like a few more Atrix users to attempt my guide and see if they have the same issue.
My guide can be found @ http://forum.xda-developers.com/showthread.php?t=1309712.
The Atrix user says he followed my directions to the letter and when he ran the script to enable the swap partition, he was faced with the following error:
Code:
swapon: /dev/mmcblk1p3: function not implemented
If anyone else is willing to try this out, I would be much appreciative.
Thanks in advance. :-D

Sounds like that user's kernel doesn't support swap
On a side note, swap is enabled on the CM7 kernel, and possibly faux's kernels too. I don't see the point in using swap on a phone with 1Gb of RAM though.
localhost / # dd if=/dev/zero of=/sdcard/swappy
^C81041+0 records in
81040+0 records out
41492480 bytes transferred in 3.653 secs (11358467 bytes/sec)
localhost / # sync
localhost / # mkswap /sdcard/swappy
Setting up swapspace version 1, size = 41488896 bytes
localhost / # swapon /sdcard/swappy
localhost / # free
total used free shared buffers
Mem: 834820 565916 268904 0 26440
-/+ buffers: 539476 295344
Swap: 40512 0 40512
localhost / #
Click to expand...
Click to collapse

If all you use is the phone itself, then 1 GB is plenty, sure, but if you use the webtop feature, 1 GB tends to run short pretty quickly. Myself and many others have confirmed that phone and webtop operate much more smoothly with a swap partition than without.

Banggugyangu said:
If all you use is the phone itself, then 1 GB is plenty, sure, but if you use the webtop feature, 1 GB tends to run short pretty quickly. Myself and many others have confirmed that phone and webtop operate much more smoothly with a swap partition than without.
Click to expand...
Click to collapse
Also, doesn't the webtop mode only have access to about 200MB?

I can confirm that enabling swap does not work in any of Faux123's or the stock 4.5.91 kernel on my Atrix. I tried the Op's method on a stock 4.5.91 fruitcake, alien 4, and darkside 2.5.1 with the webtopmod1.0 and the 2.3.4 webtop fruitcake. As well as on a locked 4.5.91 mostly stock rooted atrix with webtop2sd.
I don't have any machine set up for compiling linux kernels or experience doing it but it seems like, if you had the source for a kernel you liked, you could make the change or whip up a module for it then release it back here. It would be nice to see swap supported in faux123's 1300 OC UV kernel, that one seems to work very well on darkside and alien.

howie368 said:
I can confirm that enabling swap does not work in any of Faux123's or the stock 4.5.91 kernel on my Atrix. I tried the Op's method on a stock 4.5.91 fruitcake, alien 4, and darkside 2.5.1 with the webtopmod1.0 and the 2.3.4 webtop fruitcake. As well as on a locked 4.5.91 mostly stock rooted atrix with webtop2sd.
I don't have any machine set up for compiling linux kernels or experience doing it but it seems like, if you had the source for a kernel you liked, you could make the change or whip up a module for it then release it back here. It would be nice to see swap supported in faux123's 1300 OC UV kernel, that one seems to work very well on darkside and alien.
Click to expand...
Click to collapse
Wow you flashed a lot of ROMS! But thanks for trying. I'm also assuming that all that would be needed is someone with kernel expertise to make a module or just tweak the kernel slightly. But alas, I am no programmer yet.

paravorheim said:
Also, doesn't the webtop mode only have access to about 200MB?
Click to expand...
Click to collapse
There's an app by Sogarth called webtop2sd which repartitions the SD Card to allow for a larger amount of space available to the webtop. That app alone is recommended with or without swap, honestly.

Banggugyangu said:
There's an app by Sogarth called webtop2sd which repartitions the SD Card to allow for a larger amount of space available to the webtop. That app alone is recommended with or without swap, honestly.
Click to expand...
Click to collapse
Sorry, I knew that. I was talking about the RAM available to the webtop environment.
Sent from my MB860 using xda premium

Good news, everyone! Faux123 has announced that he will be building zram support into his next ATRIX kernel. That should ease webtop's memory woes.

[KERNEL][CM 7.x] Modified Delanoister`s kernel - OC, fast GPS lock, smooth scrolling

This is the Delanoister`s kernel v.1.2.1 with some modifications by gorolegov.
Futures:​
- kernel capabilities of the Delano for CM 7.x ONLY.
- smooth scrolling
- the possibility of overclocking.
- a lot of avaiable governors
- aviable frequency: 122, 245, 320, 480, 604, 672, 829, 787, 806, 825, 844, 864, 883, 902, 921, 940, 960, 979, 998.
- S97ramscript included with following lines:
Code:
#!/system/bin/sh
# Copyright© 2011 Juwe11
# 13.8.2011 Updated VM values - Thanks to [Kalis] for help
# 18.8.2011 Added oom_adj values
# 19.9.2011 Updated VM and LMK values
if [ -e /sys/module/lowmemorykiller/parameters/adj ]; then
echo "0,1,2,4,6,15" > /sys/module/lowmemorykiller/parameters/adj
fi
if [ -e /sys/module/lowmemorykiller/parameters/minfree ]; then
echo "2560,4096,5632,10240,11776,14848" > /sys/module/lowmemorykiller/parameters/minfree
fi
if [ -e /proc/sys/vm/swappiness ]; then
echo "20" > /proc/sys/vm/swappiness
fi
if [ -e /proc/sys/vm/vfs_cache_pressure ]; then
echo "70" > /proc/sys/vm/vfs_cache_pressure
fi
if [ -e /proc/sys/vm/dirty_expire_centisecs ]; then
echo "3000" > /proc/sys/vm/dirty_expire_centisecs
fi
if [ -e /proc/sys/vm/dirty_writeback_centisecs ]; then
echo "500" > /proc/sys/vm/dirty_writeback_centisecs
fi
if [ -e /proc/sys/vm/dirty_ratio ]; then
echo "15" > /proc/sys/vm/dirty_ratio
fi
if [ -e /proc/sys/vm/dirty_background_ratio ]; then
echo "3" > /proc/sys/vm/dirty_background_ratio
fi
- android.hardware.location.gps.xml included
- gps.conf included
- resolv.conf included
- libs are included:
lib\hw\
gps.cooper.so
gps.goldfish.so
gps.vision.so
- modules from last Kolja`s nightly are included:
lib\modules\
cifs.ko
tun.ko
zram.ko
- very fast GPS lock (less than a minute - when using a wireless network option in location & security settings)
- RAM DISK from skynet28`s kernel
Credits
Delanoister for his Delano Custom Kernel
skynet28 for his The Ace Kernel
All gps modules are from Angeeks.com_JAMT_Ju4.1 ROM.
Tested on Lewa ROM and it is based on CM 7.2.
BUGs
- CM`s torch does not work.
If you need torch you can use FlashLight HD LED from Google Play.
Installation:
- install zip with CWM5.​

Lovetz, do you know if this kernel is compatible with last kolja's nightly (14-05)? I'm asking you this because when I flashed TheAceKernel beta 4, proximity sensor was broken (although it worked great with kolja's kernel) and this kernel seems to be based in skynet28 and Delanoister's kernels!
Thank you!

gbueno6 said:
Lovetz, do you know if this kernel is compatible with last kolja's nightly (14-05)?
Click to expand...
Click to collapse
I do not know. You can try. Just use CWM backup first.

Lovetz said:
I do not know. You can try. Just use CWM backup first.
Click to expand...
Click to collapse
Ok! Right now I'm using last vo-1 CM7 build and it's working great! In a few hours I'll flash kolja's last nightly and give some feedback!
Thanks!

Is gorolegov afraid of XDA ?
You're posting instead of him , although I have to admit his kernels are excellent
This was sent from a Galaxy Ace. Problem?

EmoBoiix3 said:
Is gorolegov afraid of XDA ?
Click to expand...
Click to collapse
All people are different. They have different life principles and interests. Someone have the time and desire to write on the forums, and someone is not.

Lovetz said:
All people are different. They have different life principles and interests. Someone have the time and desire to write on the forums, and someone is not.
Click to expand...
Click to collapse
Haha im sure it he was kidding when he asked it. Why so serious?
Anyway.. currently using modified Skynet28's kernel. Believe this is better. Will report back

Great!

Btw I dont think this is legal. "FlashLight_HD_LED_Pro_1.3.2.apk"
Its the Pro version apk (not that it bothers me). But if a mod sees it..

Waiting for feedbacks...
This or TheAceKernel? XD
Sent from my WAREZ impulses.

hmm.. sorry for being nooby..
after flashing the kernel twice.. failed to boot twice..
after samsung appears, screen becomes completely white ?

kevintangi said:
hmm.. sorry for being nooby..
after flashing the kernel twice.. failed to boot twice..
after samsung appears, screen becomes completely white ?
Click to expand...
Click to collapse
White? Mine is blue. No prob. Just wait 1 or 2min.

Just in case anybody wants to know it, flashing this kernel (also TheAceKernel Beta 4) breaks proximity sensor in last official kolja's nightly!
I'll look for an answer and see if I can make it work! I'll keep you posted!

kevintangi said:
hmm.. sorry for being nooby..
after flashing the kernel twice.. failed to boot twice..
after samsung appears, screen becomes completely white ?
Click to expand...
Click to collapse
Can not confirm. Booting well)

gbueno6 said:
Just in case anybody wants to know it, flashing this kernel (also TheAceKernel Beta 4) breaks proximity sensor in last official kolja's nightly!
Click to expand...
Click to collapse
Can not say about Koja`s nigtly, but on Lewa proximity sensor works well with this kernel.

Whoops sorry ! i guess i'm too impatient takes a longer boot
Btw thanks for the kernel +1
Sent from my GT-S5830 using Tapatalk 2

Added to the fist floor: Antutu Benchmark test screens.

Lovetz said:
Can not say about Koja`s nigtly, but on Lewa proximity sensor works well with this kernel.
Click to expand...
Click to collapse
Well, I've tested this kernel after flashing an official's updated one (made by ilarrain) and proximity sensor seems to be working!
Thanks!

yeowwwai said:
Waiting for feedbacks...
This or TheAceKernel? XD
Sent from my WAREZ impulses.
Click to expand...
Click to collapse
I have the same question: this, TheAceKernel or Fire Kernel?
Sent from my GT-S5830 using xda premium

donzzy said:
I have the same question: this, TheAceKernel or Fire Kernel?
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Out of the 3, only this doesn't support link2sd.

Porting suggestions

Backstory:
Hello, I have had this wonderful phone for a year and a couple of months now and it is really good at what it does. Of course, the stock ROM (Touchwiz) is the big major at slowing this phone down. There is a lot of custom ROMs out there (I am personally running cm11) that can boost the phone and kernels to fix battery drain issues, but it still does not have a lot of custom ROMs like other devices, the developers are doing an amazing job at what they do and I have donated to several of them but if you look at a device very close to this phone (note 3) the ROMs available are more. Not stating that the devs are not working, just that a device that works pretty much the same should have the same ROMs.
So if anyone wants me to port a ROM just post it here.
Remember that the specs of the phone I will port it from needs to have the same specs as our device. Note 3 is a good example because both have a snapdragon 800 proccessor!!!
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Any ROM made will be posted here:
Have a nice day!

My personal opinion is that you should compile/build/port roms because you want to, not because you are asked to.
But it's the thought that counts, right?
Also, the note 3 seems to have the snapdragon 800 chip. This means it's closer to the S5 than the S4 (in terms of specs).

GDReaper said:
My personal opinion is that you should compile/build/port roms because you want to, not because you are asked to.
But it's the thought that counts, right?
Also, the note 3 seems to have the snapdragon 800 chip. This means it's closer to the S5 than the S4 (in terms of specs).
Click to expand...
Click to collapse
Well, the gt-i9506 has the snapdragon 800 and I dont have any fantasy when it comes to making a custom rom. I only used pac man and cyanogenmod roms on this device. But feel free to eat chicken and give me a suggestion about what to make.

I wanna suggest Dirty Unicorn. The second suggest will be Resurrection Remix, but now we have a new thread with this build. And the last, AICP. I think these rooms are well supported by a lot of devs working on it. Just my suggestion.
Sent from my GT-I9506 using Tapatalk

jefferzombie said:
I wanna suggest Dirty Unicorn. The second suggest will be Resurrection Remix, but now we have a new thread with this build. And the last, AICP. I think these rooms are well supported by a lot of devs working on it. Just my suggestion.
Sent from my GT-I9506 using Tapatalk
Click to expand...
Click to collapse
I will start with resurrection remix for the note 3 and attempt to port it.

RAZERZDAHACKER said:
I will start with resurrection remix for the note 3 and attempt to port it.
Click to expand...
Click to collapse
is it not easier just to compile from it's sources which are available ?

3mel said:
is it not easier just to compile from it's sources which are available ?
Click to expand...
Click to collapse
I dont have linux, nor do I have the knowledge. This is a project started by me that I want to port ROMs

A8 MM
I heard Samsung A8 will receive touchwiz marshmallow. Well A8 is running Snapdragon 615, while S4 (GT-I9505) is running Snapdragon 600. Will it be possible to port A8 mm to our S4?

troy. said:
I heard Samsung A8 will receive touchwiz marshmallow. Well A8 is running Snapdragon 615, while S4 (GT-I9505) is running Snapdragon 600. Will it be possible to port A8 mm to our S4?
Click to expand...
Click to collapse
Good question there, I think I might actually be able (if they release it) to port it. I will most likely de-bloat it because who likes bloatware? (You can always download them from play store if you wish, but they won't come as system apps)
Sent from my GT-I9506 using XDA-Developers mobile app

RAZERZDAHACKER said:
Good question there, I think I might actually be able (if they release it) to port it. I will most likely de-bloat it because who likes bloatware? (You can always download them from play store if you wish, but they won't come as system apps)
Click to expand...
Click to collapse
Hope that would work. Thanks though... I'll wait 'til sammy releases it, and I'll update you immediately :good:

jefferzombie said:
I wanna suggest Dirty Unicorn. The second suggest will be Resurrection Remix, but now we have a new thread with this build. And the last, AICP. I think these rooms are well supported by a lot of devs working on it. Just my suggestion.
Sent from my GT-I9506 using Tapatalk
Click to expand...
Click to collapse
Okay, compiling the dirty unicorn (no pun intended) when link is up, please report bugs and stuff
EDIT: kept getting error 6, there is nothing wrong with the code but I will check it again

Code
So I was using android kitchen to check for any wrong in the update script and I got 29 errors! I have 0 experience with this and if anyone could help that would be great! Here is the text
ifelse is_mounted SYSTEM: unmount SYSTEM:
copy_dir PACKAGE:system/addon.d" SYSTEM:addon.d
package_extract_file system/bin/backuptool.sh TMP:backuptool.sh
package_extract_file system/bin/backuptool.functions TMP:backuptool.functions
set_metadata TMP:backuptool.sh uid 0 gid 0 mode" 0755
set_metadata TMP:backuptool.functions uid 0 gid 0 mode" 0644
run_program PACKAGE:tmp/backuptool.sh backup
if is_mounted DATA: then
package_extract_file system/bin/otasigcheck.sh TMPtasigcheck.sh
package_extract_file META-INF/org/du/releasekey TMP:releasekey
set_metadata TMPtasigcheck.sh uid 0 gid 0 mode" 0755
run_program PACKAGE:tmp/otasigcheck.sh[sp]==[sp]0[sp]||[sp]abort Can't[sp]install[sp]this[sp]package[sp]on[sp]top[sp]of[sp]incompatible[sp]data.[sp]Please[sp]try[sp]another[sp]package[sp]or[sp]run[sp]a[sp]factory[sp]reset
else
package_extract_file system/bin/otasigcheck.sh TMPtasigcheck.sh
package_extract_file META-INF/org/du/releasekey TMP:releasekey
set_metadata TMPtasigcheck.sh uid 0 gid 0 mode" 0755
run_program PACKAGE:tmp/otasigcheck.sh[sp]==[sp]0[sp]||[sp]abort Can't[sp]install[sp]this[sp]package[sp]on[sp]top[sp]of[sp]incompatible[sp]data.[sp]Please[sp]try[sp]another[sp]package[sp]or[sp]run[sp]a[sp]factory[sp]reset
endif
show_progress 0.750000 0
block_image_update /dev/block/platform/msm_sdcc.1/by-name/system package_extract_file system.transfer.list system.new.dat system.patch.dat
delete SYSTEM:bin/otasigcheck.sh
show_progress 0.020000 10
copy_dir PACKAGE:system/addon.d" SYSTEM:addon.d
package_extract_file system/bin/backuptool.sh TMP:backuptool.sh
package_extract_file system/bin/backuptool.functions TMP:backuptool.functions
set_metadata TMP:backuptool.sh uid 0 gid 0 mode" 0755
set_metadata TMP:backuptool.functions uid 0 gid 0 mode" 0644
run_program PACKAGE:tmp/backuptool.sh restore
delete SYSTEM:bin/backuptool.sh
delete SYSTEM:bin/backuptool.functions
copy_dir PACKAGE:supersu TMP:supersu
run_program PACKAGE:sbin/busybox unzip TMP:supersu/supersu.zip META-INF/com/google/android/* -d TMP:supersu
run_program PACKAGE:sbin/busybox sh TMP:supersu/META-INF/com/google/android/update-binary dummy 1 TMP:supersu/supersu.zip
package_extract_file PACKAGE:boot.img /dev/block/platform/msm_sdcc.1/by-name/boot
show_progress 0.200000 10
Click to expand...
Click to collapse

RAZERZDAHACKER said:
Backstory:
Hello, I have had this wonderful phone for a year and a couple of months now and it is really good at what it does. Of course, the stock ROM (Touchwiz) is the big major at slowing this phone down. There is a lot of custom ROMs out there (I am personally running cm11) that can boost the phone and kernels to fix battery drain issues, but it still does not have a lot of custom ROMs like other devices, the developers are doing an amazing job at what they do and I have donated to several of them but if you look at a device very close to this phone (note 3) the ROMs available are more. Not stating that the devs are not working, just that a device that works pretty much the same should have the same ROMs.
So if anyone wants me to port a ROM just post it here.
Remember that the specs of the phone I will port it from needs to have the same specs as our device. Note 3 is a good example because both have a snapdragon 800 proccessor!!!
Any ROM made will be posted here:
Have a nice day!
Click to expand...
Click to collapse
How difficult would it be to port over a amazon firestick/fire tv rom or equivalent to the gt-i9505?
The reason I ask is I still have an old broken screen 1, with custom rom and various apps to eliminate battery drain, its used as a media streamer plugged into my tv with mhl.
Is this even possible?
Im running this just fine and runs loads better than a firestick, im even using the fire sticks Bluetooth remote.
My only issue with doing it this way is the apps I use (mainly tv apps) dont recognise the remote too well and run in phone mode, rather than fire sticks versions run in full mode (as its designed for tv using remote.)
Anyone know if its not possible to port this sort of thing of any work arounds/fixes to suggest?
Your help is very much appreciated.

sconnyuk said:
How difficult would it be to port over a amazon firestick/fire tv rom or equivalent to the gt-i9505?
The reason I ask is I still have an old broken screen 1, with custom rom and various apps to eliminate battery drain, its used as a media streamer plugged into my tv with mhl.
Is this even possible?
Im running this just fine and runs loads better than a firestick, im even using the fire sticks Bluetooth remote.
My only issue with doing it this way is the apps I use (mainly tv apps) dont recognise the remote too well and run in phone mode, rather than fire sticks versions run in full mode (as its designed for tv using remote.)
Anyone know if its not possible to port this sort of thing of any work arounds/fixes to suggest?
Your help is very much appreciated.
Click to expand...
Click to collapse
I think it can be done using the all mighty android kitchen, the setup is a hassle but once that's done you have all the different things you can do in there (that's what she said). One option is that you can port ROMs, it aint gonna be stable, it probably wont even boot and you probably will have the same error as I got when running the script checker. But then again, could be worse...
Try it if you want, though I am not responsible for anything that happens to your device(s).