Database Develop

Finally a fix for 2-3 call delay!

deleted .

Finally ! That bug was very annoying to me.

I'll try the fix asap, thanks a lot!
e: works like a charm!

Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .

I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing

jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something

j4n87 said:
Yeah, it was a so annoying issue...
I wonder why so less people visited this thread .
Click to expand...
Click to collapse
Because you posted it in the "Themes and Apps" section

thanks a lot for post here
great job

kackburt said:
Try adding the libaudio.so to your ROM.zip (with 7-zip or WinRAR) at the right directory and flash the ROM.zip again. That's what I am doing everytime I change something
Click to expand...
Click to collapse
you mean copy the actual zip file into the ROM zip and then flash?

jonny68 said:
you mean copy the actual zip file into the ROM zip and then flash?
Click to expand...
Click to collapse
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.

Tried on UD3.3.0 wont boot... :s

People dont understand that this work the best on CM7 nexus roms.
That by installing this fix on CM7 or AOSP you will probaly lose the robo and high volume on first call fix. That most roms have custom libs including this lib. Minimum requirements I would say CM7 2.34 and AOSP 2.34 since cm7 and AOSP are the most equal roms to each other.
To say it simple you cant just simply flash this on every rom also make sure your permission is right.

Is this fix able to work on an HTC Desire running 2.3.4 Oxygen ROM?

jonny68 said:
I copied this ZIP onto my SD card,rebooted, went into clockwork mod, install zip, choose zip and flashed this,rebooted but am stuck on the HTC screen now for over 7 minutes am i doing something wrong?
It's as well i made a backup or id lose everthing
Click to expand...
Click to collapse
If you have a nandroid backup, you should be on the safe side!
Try to wipe cache partition first, then the dalvik cache and then flash the zip-file.
All of these actions take place in the CWM.
Hope it works!

The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4

jens1288 said:
The libaudio.so fix was submitted to gerrit (Change I24a4a11b: Fix for a1026 suspend)by Jordon aka Jyxent. It was mergered with the latest nightlies, and should be merged with CM 7.0.4
Click to expand...
Click to collapse
Yes, that fix works fine. I'm not sure it fixes the few seconds delay that affects all Gingerbread phones though but there was another potential workaround submitted for that too.
http://review.cyanogenmod.com/#change,5420
I have yet to include it in my build and try it though.

The story on the front page links to the wrong fix. The libaudio fix was for the wonk on the Nexus One. The libaudio library is hardware specific and may cause issues on other devices that don't share the same processor.
I've submitted a patch to gerrit that helps with the call delay here:
http://review.cyanogenmod.com/#change,5420

Thank you for clearing that up jyxent. To go into a bit more detail...
The fix that was posted, as jyxent mentioned, is for the Nexus One. That is for the infamous "wonk" that has been plaguing N1 users since the Gingerbread nightlies started (who woulda thunk it was just a single line that needed to be added).
The 2-3 second delay is something that affects most (if not all) Gingerbread installs. Currently there isn't a simple "fix" for this. It requires recompiling portions of Gingerbread. jyxent's fix is submitted to CM, but I don't see any reason why this can't be applied to AOSP as well. It has yet to be reviewed by the CM dev team (at least it doesn't have any comments on it yet). It might be something that can be made into some device-independent flashable zip, but it has yet to be created.

j4n87 said:
Unzip the cwm with the fix and navigate to "system/lib" and copy the "libaudio.so".
then open the rom zip navigate to "system/lib" and paste the "libaudio.so" there.
Didn't understand your previous post..did you make a backup or not?
If not...just flash your current rom again, you won't lose your data if you do this.
Only the files that you edited in /system like gps.conf or other tweaks you have to edit again.
Click to expand...
Click to collapse
done thanks

Can this be done manually with root explorer, by copying the libaudio.so to/system/lib and a reboot?

[Q] ICS store camera pics on external sd

Hi,
I just switched to ICS(teamhacksung build 9) and cant find howto change the storage location of the camera pics.
Is it possible and if yes how ?
My phone is a SGS I9000 if that helps!
/T

Bump!!!
/T

Bump!!
/T

I would also like to know this. I have tried every camera I can think of. (MIUI camera, Camera 360, Camera Zoom FX, ect)...none of them will let me save to the external SDcard. Camera 360 came the closest but, you can choose the location of where you want to save the images, but there is not button to go up one level in the file system, so you can only access /mnt/sdcard but we need to access mnt/emmc....this is driving me CRAZY!

trollkarlen1 said:
Hi,
I just switched to ICS(teamhacksung build 9) and cant find howto change the storage location of the camera pics.
Is it possible and if yes how ?
My phone is a SGS I9000 if that helps!
/T
Click to expand...
Click to collapse
Ki77erB said:
I would also like to know this. I have tried every camera I can think of. (MIUI camera, Camera 360, Camera Zoom FX, ect)...none of them will let me save to the external SDcard. Camera 360 came the closest but, you can choose the location of where you want to save the images, but there is not button to go up one level in the file system, so you can only access /mnt/sdcard but we need to access mnt/emmc....this is driving me CRAZY!
Click to expand...
Click to collapse
Camera Zoom Fx did the trick for me.. don't know why it isn't working for you..
If Camera 360 almost worked for you, what you can do is create a link to /mnt/emmc in /mnt/sdcard using app like root explorer.. that link will work as external_sd folder worked in GB roms... so selecting that in Camera 360 will let you access your external sdcard

ishangoyal said:
Camera Zoom Fx did the trick for me.. don't know why it isn't working for you..
If Camera 360 almost worked for you, what you can do is create a link to /mnt/emmc in /mnt/sdcard using app like root explorer.. that link will work as external_sd folder worked in GB roms... so selecting that in Camera 360 will let you access your external sdcard
Click to expand...
Click to collapse
I actually realized I was using an older version of Camera Zoom that did not have that function. I have updated it and was able to choose a folder on /mnt/emmc and it seems to be working fine. Thanks for the help.

[ROM][SENSE][10-01-2013] UnoX SENSE4 for Optimus 4X HD - FIRST CUSTOM ROM!

LG O4X UnoX SENSE4 ALPHA RELEASE​You thought you never see a HTC SENSE with BeatsAudio interface on O4X? This is the ALPHA release of SENSE 4.0 (version 2.17.401.2) and using STOCK LG kernel for your LG Optimus 4X HD​
Latest update 10.Jan.2013
Changed build to avoid conflict with team venoms mods, this should be more stock now.
It is now a ClockWorkMod Update.zip using AROMA installer.
alot changed and yet, no GSM is working but i am getting closer.
***STATUS***
Click to expand...
Click to collapse
This is very early developer release, more a proof of concept, to help others start porting or even developing roms, without thinking the locked bootloader will limit the distribution. so regular users, will probably not use this for anything since mobile connectivity is not working.
but if you wish to check performance and maybe test some performance here, this is a way to do it and compare.
Any contribution to fixing the RIL driver in this one or other fixes are appreciated, feel free to make patches if you can help improve this.
***WHY***
Click to expand...
Click to collapse
So the O4X community have been almost dead and not a single custom rom has been released, primarily because many believe a unlocked bootloader is needed.
WHAT WORKS
Click to expand...
Click to collapse
GSM Mobile Radio - NO
AUDIO - YES (+ BEATS AUDIO works fine with headset)
PHOTO CAMERA - YES (FRONT is very,very dark, BACK camera is ok)
VIDEO CAMERA - YES (for now only 1080p recording, 1280x720 closes camera, change in settings)
VIDEO PLAYBACK - YES
MICROPHONE - YES
WIFI - YES
GPS - YES
BLUETOOTH - YES (Wifi seems affected by enabling bluetooth at bootup, and no wifi connectivity exists, so disable BT at bootup)
ROTATION - YES
YOUTUBE - YES
MOST SENSORS - YES
VIBRATION - NO
NFC - YES (No icon when activated, but works fine with included NFCtag+)
PC CONNECTION - NO (not worked on it)
INT / EXT SDCARD - YES (without sdcard, camera cannot save to internal storage)
NOTES ON FIRST USE​
Click to expand...
Click to collapse
- First start can take 5-6 minutes due to a process waiting for media scanner.
- in /system folder, you can rename "local.prop1" to "local.prop" , and you can enable adb root.
- its based on v10d, i do not know if the boot.img is required, but remove it if you wish to try it without. (remember to edit md5 checksum file if you do)
- do not try and install recovery from the CWM app, just use it to reboot into cwm, do NOT install recovery, its already in place and modified to work with sense.
DOWNLOAD
Click to expand...
Click to collapse
Download full as CWM update.zip ALPHA 1.0 here
Firefox users: Ignore warning, this is just a zip with a backup included, no executables here​

great! i will flash i tmr morning and have a taste on sense

Its online now!

2.17.401.2, so it's Android 4.0.4?

reas0n said:
2.17.401.2, so it's Android 4.0.4?
Click to expand...
Click to collapse
yes i believe so, it was based on a onex rom i found, nothing special, but a testrom.

Dexter you are GREAT !!! :good: :good:
THANK YOU !!

Looks amazing!

thank you very much... sense 4 on 4x

can someone make a backup for TWRP recovery??
---------- Post added at 06:51 AM ---------- Previous post was at 06:48 AM ----------
Dexter_nlb said:
Its online now!
Click to expand...
Click to collapse
finally first custom rom for LG4X..how about CM10 on LG4X?? btw, thanks for making first custom rom on our device :good:

razerblade17 said:
can someone make a backup for TWRP recovery??
Click to expand...
Click to collapse
you can modify the existing backup, by editing the nandroid.md5 checksum file, remove the "system.ext4.tar" line in the md5 file
and rename the "system.ext4.tar.a" to "system.ext4.tar" . and of course do the same with the real tar file.
then it should look pretty much like old backups
-------------------------------------------------------------------------------
Update:
after the upload,
i have checked GPS and NFC.
GPS is confirmed working
NFC needed fixing but it works now , althoug icon is gone, and the NFCplus app works too, so you can modify tags

wow NICE!! almost had a mini heart attack when i saw this post!:fingers-crossed:
looking forward to working CALL XDD
THX a lot for ur work!!!

Dexter_nlb said:
you can modify the existing backup, by editing the nandroid.md5 checksum file, remove the "system.ext4.tar" line in the md5 file
and rename the "system.ext4.tar.a" to "system.ext4.tar" . and of course do the same with the real tar file.
then it should look pretty much like old backups
-------------------------------------------------------------------------------
Update:
after the upload,
i have checked GPS and NFC.
GPS is confirmed working
NFC needed fixing but it works now , althoug icon is gone, and the NFCplus app works too, so you can modify tags
Click to expand...
Click to collapse
no luck...btw any other method to install via TWRP recovery?? my sd card has a problem, and no money to buy new one...so any solution to restore this backup??

i've been stuck in the setup wizard for so long now, i managed to get past the language/locale selection screen but I'm stuck in the next screen where venom setup is.
Anyone managed to get past this screen? can i delete setupwizard to bypass this process?
EDIT: finally get past the setup wizard!!! ultra smooth rom!!!
i know this is ALPHA but thought i should post a list of things i found not working so maybe someone can fix it =)
- Vibration not working
- Google Voice Search not working
- mount ext-sdcard not working
- Flashlight not working
- Whatsapp doesn't work (it says "Tablet is not supported" so i guess there's sth wrong with the IMEI or build.prop)
- pressing "settings" in camera app crash the app itself
- "Share" option is unusable (tested both by email and by Google+)
BUT
- Camera app works GREAT with rear camera!!!!!
- most if not all widgets work (though i didn't test all of them, most of them work!!! without a lag)
- Speaker works

tomanlam said:
i've been stuck in the setup wizard for so long now, i managed to get past the language/locale selection screen but I'm stuck in the next screen where venom setup is.
Anyone managed to get past this screen? can i delete setupwizard to bypass this process?
EDIT: finally get past the setup wizard!!! ultra smooth rom!!!
i know this is ALPHA but thought i should post a list of things i found not working so maybe someone can fix it =)
- Vibration not working
- Google Voice Search not working
- mount ext-sdcard not working
- Flashlight not working
- Whatsapp doesn't work (it says "Tablet is not supported" so i guess there's sth wrong with the IMEI or build.prop)
- pressing "settings" in camera app crash the app itself
- "Share" option is unusable (tested both by email and by Google+)
BUT
- Camera app works GREAT with rear camera!!!!!
- most if not all widgets work (though i didn't test all of them, most of them work!!! without a lag)
- Speaker works
Click to expand...
Click to collapse
thanks for the report back, and yes, i am aware of the setup screen bug, it also seems to relate to the customization process hanging in the background, so it will hang for some time too, sorry. porting is not always easy
edit: i believe the problem rely in the SIMcard not being detected as you might note, the simcard screen normally shown is not being shown, which asks to insert sim. it also seems the the firmware seems to tell the htc software it is a CDMA phone, so this might also be the problem why gsm is not working. this is seen in the radio log.
- i noted the other things, and flashlight is the only one i am not looking at, as our flashlight is different and can be damaged if i try to make it like a lightbulb i think. (do not know and do not want to find out)
- we got no IMEI yet, since phone is not working, so the whatsapp might have a different issue or as you say, it does not exist. build.prop is pretty much OneX original here.
- external sdcard works fine here, i wonder why you cannot see it in storage settings?
- i do not know why googlevoice do not work, ill check up on it, probably relate to recording format, which i noted only works with AAC and not AMR format.

Dexter_nlb said:
thanks for the report back, and yes, i am aware of the setup screen bug, it also seems to relate to the customization process hanging in the background, so it will hang for some time too, sorry. porting is not always easy
edit: i believe the problem rely in the SIMcard not being detected as you might note, the simcard screen normally shown is not being shown, which asks to insert sim. it also seems the the firmware seems to tell the htc software it is a CDMA phone, so this might also be the problem why gsm is not working. this is seen in the radio log.
- i noted the other things, and flashlight is the only one i am not looking at, as our flashlight is different and can be damaged if i try to make it like a lightbulb i think. (do not know and do not want to find out)
- we got no IMEI yet, since phone is not working, so the whatsapp might have a different issue or as you say, it does not exist. build.prop is pretty much OneX original here.
- external sdcard works fine here, i wonder why you cannot see it in storage settings?
- i do not know why googlevoice do not work, ill check up on it, probably relate to recording format, which i noted only works with AAC and not AMR format.
Click to expand...
Click to collapse
external sd is not accessible in the default file manager? but if i use another file manager (FX Explorer), i can access the extSD
but in storage settings, everytime i try to unmount the sd, settings.apk crashes
but as an alpha "port" (sort of), the rom is ULTRA-SMOOTH, wish at least GSM call work soon:silly:

tomanlam said:
external sd is not accessible in the default file manager? but if i use another file manager (FX Explorer), i can access the extSD
Click to expand...
Click to collapse
ok i see now.
this the the HTC way of having external sdcard, the semi way, since they officially do no longer make many top models with sdcard.
the location of external sdcard is at /mnt/sdcard2 and internal is /mnt/sdcard
let me check up on the unmounting, i already got some fixes, but not GSM, sorry, that require alot more it seems to fix.
about the GSM part, it is strange that both OneX and O4X uses a radio chipset with QUO 6260 radio, but they flash firmware different ways, so that makes it incompatible somehow.

Great job man!
I will join your development as soon as I finish my exams (2-3 weeks) so the LG 4X community gets alive. Will read your thread in the meantime.

Making a backup now while downloading this rom.
Thank you so much for your time and effort Dexter!

Sense 4.1 is actually pretty smooth on our O4X. Too bad radio is somehow turned off. I would rock this rom as my daily once radio gets solved. But for now, everything else seems to be working. Beats works great too. Camera is good, but video FCs.

babymatteo said:
Sense 4.1 is actually pretty smooth on our O4X. Too bad radio is somehow turned off. I would rock this rom as my daily once radio gets solved. But for now, everything else seems to be working. Beats works great too. Camera is good, but video FCs.
Click to expand...
Click to collapse
getting DRM working little better here, i simply copied the generated RSA keys from /data to a tar file and extract it at every boot, but not sure how i get the lgeril to load it now, since its htc based.
for the camera, i simply use a camera from another htc 4.0.4 release and it works fine. probably related to resolution of camera and it works now recording in 1080p as well.

Symlinked Gapps for CM9 And CM10 (w/ Google Now ICS instructions) (09MAY2013)

Hello everybody. After spending hours trying to figure out what I could delete from the system to make room for Gapps on CM10, I even tried to resize partitions, I came to the conclusion that the Gapps will have to be stored elsewhere. So, I came up with a solution, by installing the apps to /data/Gapps and then symlinking the files to /system. So since there are so many people trying to get Goggle Now on CM9, I figured I would make modified Gapps zips for both CM9 and CM10.
These are complete Gapp packages, they actually free up space on the /system partition, and are completely functional. Most of the files are installed to data/Gapps, this way the devs will not have to worry about trimming the ROMs, except to fit on the partition.
I'm sure this will help a bunch of other devices that have smaller system partitions also.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
I don't think Google should have any issues with this as I haven't changed any files that where in the zip just moved them around and modified the updater-script.
Installation for fresh install:
1. Boot to your favorite custom recovery
2. Factory reset, wipe cache and dalvik cache
3. Flash CM9/CM10
4. Flash these Gapps
5. Reboot
Installation for previous install:
If you are already setup , you will need to wipe the cache and reinstall the ROM to format system to remove any Gapps already installed. As long as you don't wipe data/factory reset you should be right back where you started.
1. Boot to your favorite custom recovery
2. Wipe cache and dalvik cache
3. Flash CM9/CM10
4. Flash these Gapps
5. Reboot
Google Now Installation for CM9:
Google Now Installation for CM9 (fresh install):
1. Boot to your favorite custom recovery
2. Factory reset, wipe cache and dalvik cache
3. Flash CM9
4. Flash Google Now (online)
5. Flash these Gapps
6. Reboot
Google Now Installation for CM9 (previous install):
1. Boot to your favorite custom recovery
2. Wipe cache and dalvik cache
3. Flash CM9
4. Flash Google Now (online)
5. Flash these Gapps
6. Reboot
[MOD][ICS] The Google Now for ICS Project [ARMv6 & v7]
Symlinked Gapps for ICS Ver3:
Fixed Facelock.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
Had to add placeholders in system/vendor for the symlinks to be created, but vendor is still 0 bytes
symlinked-gapps-ics-20120429-signed-Ver3.zip
Symlinked Gapps for JB Ver2:
Fixed Facelock.
Note: Facelock requires you to log in to an account, to even show up in lockscreen options.
Had to add placeholders in system/vendor for the symlinks to be created, but vendor is still 0 bytes.
symlinked-gapps-jb-20121011-Ver2.zip

thank you very much
this reduces the pain while trimming the rom for matching system partition
in this same way can we get google offline voice..?

reversegear said:
thank you very much
this reduces the pain while trimming the rom for matching system partition
in this same way can we get google offline voice..?
Click to expand...
Click to collapse
GNow offline for ICS still requires about 60mb. So it will depend on the ROM. But, it works with our Triumph ICS ROMs. And they should be almost identical, as far as I've seen. I use GNow offline with my PA ICS ROM, with no issues. I haven't spent much time on any of the X6 ROMs, as we can't use the newer kernel and still use our phone service.
Let me know how it goes.
Sent from my WX435 using Tapatalk 2

This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?

bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.

"Fixed Facelock.
Note: Facelock requires you to log in to an
account, to even show up in lockscreen
options."
what do you mean by this sir?
thanks.
^_^

It is okey to flash this gapps when already some gapps (gmail, voice etc) in our rom? ....
Or we just force to uninstall before flash this? ..
Btw thx dude, great job.... :thumbup:
Ps:im using jb rom by dr.rush
Sent from my Andro-Id using Pulsa

reversegear said:
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
thats not what i meant.. i was saying that partitioning our phone with what u said and also with some 100-200 mb to make internal memory detect it as sdcard?

bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Thanks, our partitions can not be repartitioned/resized, I tried everything except deleting the extended partition(4) that holds 5 - 17. That is why I made these.
This is the breakdown of the partitions on our phone:
BSydz said:
So, this is what I have found so far about the partitions on the Triumph, I can't guarantee that this is all correct, but if anybody has any input feel free to chime in.
WARNING, THE INFORMATION PROVIDED BELOW IS SPECULATIVE AND COMES WITH NO WARRANTY. IF YOU MESS WITH THIS STUFF, I AM NOT RESPONSIBLE IF YOU DAMAGE YOUR PHONE.
Partitions:
1 (FAT) Mobile Partition containing image folder, which is very well documented around the forums.
2 (crypt/QNX4.x) Primary Boot Loader (PBL) I believe that this is what the SOC uses to boot.
3 (crypt) Secondary Boot Loader I believe this is where the hardware layout is contained, as it changes button configuration and was key to getting back to normal after I flashed the wrong nb0. It is linked to the mobile partition, as the phone will not boot properly without the correct amss.mbn
4 (extended) Just an extended partition containing partitions 5 - 17.
5 (Boot) This is where the boot img is extracted.
6 (OnTrack DM) I think this manages and verifies integrity of partitions 13-17.
7 (ext3) This is where the system/rom is located. This is what you see in root explorer as "system", containing the build.prop and other stuff.
8 (ext3) This is the "data" folder .
9 (ext) This partition holds CDA info, with OEM apks, ringtones, and wallpapers, it seems to be mounted inside partition 10 (hidden) when the phone is on you can find the information merged into "hidden/data" using root explorer.
10 (ext3) This is the hidden partition containing boot images and CDA info. This can be found in "hidden" using root explorer.
11 (ext3) This is the cache partition.
12 (ext3) This is the Caivs, can't find too much info on this.
13-17 (unknown) I believe this is where the phone specific data is stored, including but not limited to MEID, ESN, and PRL.
Click to expand...
Click to collapse
reversegear said:
bandukia said:
This is great way of freeing up system partition..! So can our device be repartitioned? And make some internal memory available as internal sdcard?
Click to expand...
Click to collapse
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
Since there is no way to resize any partitions, that is why I made these. Data is the only partition that we can really use that won't require us to heavily modify the phone and be user friendly. Because not everybody who installs custom ROMs is gonna be able to do those types of modifications. This is the simplest way to fix the issue and won't impact anybody who wants to change ROMs.
aeoi said:
"Fixed Facelock.
Note: Facelock requires you to log in to an
account, to even show up in lockscreen
options."
what do you mean by this sir?
thanks.
^_^
Click to expand...
Click to collapse
I have had this posted in another forum for a while, the original tread is below. We (Triumph users) did not have camera working in ICS, and still don't on JB, So when I first released these, the optional script that installs facelock was not correct. Now that I have fixed the front camera, I got feedback that facelock was not working. While trying to fix it, I spent a few hours, never even getting the option in lockscreen settings, and finally added an acount one time so I could get some apps from google to figure out what was happening. Then I went in to the settings and it was there. So the hours I wasted was because I hadn't added an account. So face lock will not even show up in lockscreen settings until an account has been added to the phone. I think it has to do with having to have a second unlock option if facelock can't work, like low light situations.
http://androidforums.com/triumph-al...-w-google-now-ics-instructions-09may2013.html
adonwenas said:
It is okey to flash this gapps when already some gapps (gmail, voice etc) in our rom? ....
Or we just force to uninstall before flash this? ..
Btw thx dude, great job.... :thumbup:
Ps:im using jb rom by dr.rush
Sent from my Andro-Id using Pulsa
Click to expand...
Click to collapse
It may work, one of the issues I had was the script was putting the optional files in system (the wrong place) and then the symlinks would overwrite the files. So this leads me to believe it may work, but I can't promise anything. If it doesn't work I can add some stuff to delete specific files in the updater-script, or you can remove the files from the ROM zip before flashing. You will want to at least wipe cache before you try these. I hate to say it, but you may have to be the tester.
Now that you guys are aware of these Gapps, you should ask your dev to remove Gapps from the ROM if possible. That would probably be the best route to go.
bandukia said:
reversegear said:
Already we have a enough internal memory 1gb. What we need is system partition which is 245 mb needs expansion may be additional 100 mb from internal memory. that is where the pain area.
Click to expand...
Click to collapse
thats not what i meant.. i was saying that partitioning our phone with what u said and also with some 100-200 mb to make internal memory detect it as sdcard?
Click to expand...
Click to collapse
Sorry, as I explained above, this is not an option. Big SD cards are cheap now, and how would a couple hundred MB help anyway? If it is for swap, then it would be better to wear out your SD rather than your internal HD. Plus a good SD would be faster.
If anybody has any other questions feel free to ask.;

Thank you Bsydz for throwing light on the so far untouched topic in our forum
Lots of useful information.
Off topic question
Can you please let us know how do we port JB ROMs from triumph to ideos x6. Especially PA Rom

reversegear said:
Thank you Bsydz for throwing light on the so far untouched topic in our forum
Lots of useful information.
Off topic question
Can you please let us know how do we port JB ROMs from triumph to ideos x6. Especially PA Rom
Click to expand...
Click to collapse
Thanks. If I had another dev phone I would just build one for you guys. It is a pain switching over cause we never got an nb0, I have to manually swap out the partitions to get it back. That's where I got the info about the partitions. My PA JB is built on CM10, so it would be just like any other CM port except the headphones and most everything else should work. It is older since PA went to aosp instead of CM based. Are any of your CM10 ROMs built from source or just ports? It would be nice to see some of the edits made for our phone. The only thing that's not working on ours is 3G, video/camera preview, and HDMI. But you guys use sim cards so I don't think you would have 3G issues and your kernel should fix the previews.
I'll build a PA JB ROM if you are willing to test it. I have the device files and the kernels except ck's kernel. Let me know, cause I hate releasing something I can't test first.
Sent from my WX435 using Tapatalk 2

im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.

I've uploaded my modded kernel source, sorry... not in github.

reversegear said:
im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.
Click to expand...
Click to collapse
CacingKalung said:
I've uploaded my modded kernel source, sorry... not in github.
Click to expand...
Click to collapse
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.

BSydz said:
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.
Click to expand...
Click to collapse
Ready to test your ROM.. All the best.
visit Techlions.in for latest tech news..

reversegear said:
im ready to test the rom.
we have both the CM10. I.e built from source and port rom
This one built from source by master abenaigle
http://forum.xda-developers.com/showthread.php?t=2158624
This one is stable CM10 by Dr.Rush
http://forum.xda-developers.com/showthread.php?t=2160913
V0.2 is stable ROM presently.
Click to expand...
Click to collapse
Firmware and kernel of our devices are compatible, I checked when flashing CM 9 from Motorola TRIUMPH, running everything except the data and the camera upside down
Sory for my english

Dr. Rush said:
Firmware and kernel of our devices are compatible, I checked when flashing CM 9 from Motorola TRIUMPH, running everything except the data and the camera upside down
Sory for my english
Click to expand...
Click to collapse
No need to apologize for language barriers. Do you think, you could put together a zip of the files in /lib and /bin that are for fb0? I just need the files that you put in to get it working, not all of them. It will make it easier to setup a device files for building from source. I have built the ROM and it boots, but no display, with copybit errors. I think I can get past those errors but once it fully boots, I'm sure things will have to be fixed.
Also, yes our phones are almost identical. Our amss.mbn is not compatible with the new kernel so we can't use our phone after the update. Just like you can't install the newer ROMs unless you flash the sharp nb0. I have it installed on my dev phone right now so i can get this working. I can install the nb0 and everything works perfectly except phone and 3g. It sucks, cause we are stuck.
Sent from my WX435 using Tapatalk 2

How much, I realized you're talking about the incompatibility of your phone with our 35 kernel, 32 kernel but your compatible with our device, in MTDEV M9 worked even mobile network, except 3g that prevents replace the kernel to fix the library and enjoy the new firmware

BSydz said:
Thank you, I am building it right now, just working through the errors from the ICS device files. CK, I got your kernel source, so we will see how it goes. I'll start new thread when it is done building.
Click to expand...
Click to collapse
any update on status...?

[MOD] Front Facing Video fix for AOSP builds

In all of the current AOSP builds, the forward facing camera video fails because the information is pulled from msm8960-common. We share almost everything in common with the other devices, but our forward facing camera is of lower resolution so the base settings do not work with ff video on the xt907.
This is a relatively simple xml edit that I have played around with. I have tested on CM10.1 rc and CM10.2 nightly with the stock camera and hangouts video (it starts ok with hangouts, but I'm not where I can have a conversation with anyone right now so ymmv). It should work on all of the aosp based builds.
To apply use a root enabled file explorer, in directory...... delete your existing media_profiles.xml (or add .bak extension). copy this file, remove the .txt extension, and set permissions to rw-r-r then reboot.
I will try and get a flashable zip up later if anyone wants it. That way, you can simply flash it after flashing your rom of choice if you are running nightlies or like to try new builds often.
Let me know if it works or if anything looks like it needs tweaking.
********Update********
it may be necessary to clear data on camera/gallery app after updating the media_profiles.xml file
also adding flashable zip file

ej1911 said:
In all of the current AOSP builds, the forward facing camera video fails because the information is pulled from msm8960-common. We share almost everything in common with the other devices, but our forward facing camera is of lower resolution so the base settings do not work with ff video on the xt907.
This is a relatively simple xml edit that I have played around with. I have tested on CM10.1 rc and CM10.2 nightly with the stock camera and hangouts video (it starts ok with hangouts, but I'm not where I can have a conversation with anyone right now so ymmv). It should work on all of the aosp based builds.
To apply use a root enabled file explorer, in directory...... delete your existing media_profiles.xml (or add .bak extension). copy this file, remove the .txt extension, and set permissions to rw-r-r then reboot.
I will try and get a flashable zip up later if anyone wants it. That way, you can simply flash it after flashing your rom of choice if you are running nightlies or like to try new builds often.
Let me know if it works or if anything looks like it needs tweaking.
Click to expand...
Click to collapse
hmm, having some troubles getting the file to download - just showing up as a text in my browser....
edit: just copied to a notepad, saved it, and e-mail it to myself. downloaded it, placed it in the "system/etc" folder, changed permissions, rebooted.... but no dice for me, still get a force close. wondering if it has to do with me being on AOKP, since you said this is for AOSP ROMs....

jco23 said:
hmm, having some troubles getting the file to download - just showing up as a text in my browser....
edit: just copied to a notepad, saved it, and e-mail it to myself. downloaded it, placed it in the "system/etc" folder, changed permissions, rebooted.... but no dice for me, still get a force close. wondering if it has to do with me being on AOKP, since you said this is for AOSP ROMs....
Click to expand...
Click to collapse
Easiest way is to right click the file and save as.
Couple of questions. Which app is force closing, is it the camera? and Which AOKP are you on? I have most of them downloaded. I will try to flash it and see if I can figure it out.

ej1911 said:
Easiest way is to right click the file and save as.
Couple of questions. Which app is force closing, is it the camera? and Which AOKP are you on? I have most of them downloaded. I will try to flash it and see if I can figure it out.
Click to expand...
Click to collapse
well, the official message is that the gallery has stop responding (same as before) - but this happens when I attempt to launch camcorder in front-facing mode - so yes, it is camera, but I think android refers to it as "gallery".
i believe that video calls for hangouts works fine though (but I'll test again tonight).
I'm on the "unofficial" AOKP ROM

jco23 said:
well, the official message is that the gallery has stop responding (same as before) - but this happens when I attempt to launch camcorder in front-facing mode - so yes, it is camera, but I think android refers to it as "gallery".
i believe that video calls for hangouts works fine though (but I'll test again tonight).
I'm on the "unofficial" AOKP ROM
Click to expand...
Click to collapse
OK, thanks. You might have to clear the data in the gallery app, I'm not sure. I got the video camera to work on the AOKP 4.3 9/11 nightly, but I flashed the update zip that I made to test it and it was a fresh install. I couldn't do much testing though because I got the AOSP keyboard is force closing problem.
I will update the OP in a little bit with the flashable zip file.

ej1911 said:
OK, thanks. You might have to clear the data in the gallery app, I'm not sure. I got the video camera to work on the AOKP 4.3 9/11 nightly, but I flashed the update zip that I made to test it and it was a fresh install. I couldn't do much testing though because I got the AOSP keyboard is force closing problem.
I will update the OP in a little bit with the flashable zip file.
Click to expand...
Click to collapse
got it working now.
i downloaded the file this time, e-mailed it to myself, copied it to the "system/etc" folder, changed permissions, renamed the org as .bak, renamed the new file as .xml, then rebooted. after reboot, I went into the camera app and once again got a force close. however, I tried playing around with the settings "record mode" from 1020 to 480, and then went back to FF camcorder, and it recorded! I then changed the "record mode" back to 1080, and FF camcorder worked just fine.
so I think you are correct, perhaps one needs to clear cache/data in the gallery prior to use.
thanks for the tip and the mod! nice work!
to resolve your AOSP keyboard force closing problem, try wiping system before installing the update. this worked for me.

Bit of thread necro, I know... But it's for a good cause.
Have you pushed this fix to CM? I am looking into what exactly needs to change in the source, I suppose we can fix this somehow from CM, and then all of the ROM's will be fixed (assuming they all update with the fix )

The flashable zip worked perfect for me. Thank you so much!
---
Sent using my Droid Razor M- THE BEST SMARTPHONE ON THE PLANET!
Heard about Kettlebells... learn more: http://synergykettlebell.com

arrrghhh said:
Bit of thread necro, I know... But it's for a good cause.
Have you pushed this fix to CM? I am looking into what exactly needs to change in the source, I suppose we can fix this somehow from CM, and then all of the ROM's will be fixed (assuming they all update with the fix )
Click to expand...
Click to collapse
Argggh merged it into cm code. All it should flow to all ROMs as they sync and build.
Sent from my XT907 using xda app-developers app