• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [DEV] Continuing Triumph ICS Development

mantera said:
Yeah, I realized that, now that I saw your other post. :) You'll just need to go through all of my repos and pick out the needed fixes then.
Click to expand...

Do you know about how many commits in the frameworks/base are needed for RIL? I feel that I'm going to need quite a few..
 
gannon5197 said:
Do you know about how many commits in the frameworks/base are needed for RIL? I feel that I'm going to need quite a few..
Click to expand...

You're going to need this:

https://github.com/mantera/android_frameworks_base/commit/c36a4bd43ac205acb7de990558b2e89b22404365

However, in the commit above, the QualcommNoSimReadyRIL.java file was deleted in a recent commit from upstream so you'll need these commits to fix that:

https://github.com/mantera/android_frameworks_base/commit/9f810b42cabb010daa93d090c2479fa52e2f9ff9

https://github.com/mantera/android_...mmit/6a53901cad0343245f9dcd4c95d91d73621ad08e
 
From tj style regarding my question on getting this to work on our phone

"Never test on .32 kernel, and i don't know that will work since call mechanism on camera is different with .35 but still possible since fih is using same camera parameter method.

Iwill post all changes on the camera.fb0, libcameraservice, libcamera_client and kernel later, need to fix up the source. "
 
Anybody have a fix for this? I can't seem to surpass it.
Code: 
m/core/charger/charger.c:685: error: undefined reference to 'gr_fb_blank'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/triumph/obj/EXECUTABLES/charger_intermediates/charger.o: in function main:system/core/charger/charger.c:718: error: undefined reference to 'gr_fb_blank'
collect2: ld returned 1 exit status
make: *** [out/target/product/triumph/obj/EXECUTABLES/charger_intermediates/LINKED/charger] Error 1

EDIT: Weird enough, I'm running into this with both my AOKP and CNA build...
 
gannon5197 said:
Anybody have a fix for this? I can't seem to surpass it.
Code: 
m/core/charger/charger.c:685: error: undefined reference to 'gr_fb_blank'
prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/triumph/obj/EXECUTABLES/charger_intermediates/charger.o: in function main:system/core/charger/charger.c:718: error: undefined reference to 'gr_fb_blank'
collect2: ld returned 1 exit status
make: *** [out/target/product/triumph/obj/EXECUTABLES/charger_intermediates/LINKED/charger] Error 1
EDIT: Weird enough, I'm running into this with both my AOKP and CNA build...
Click to expand...

That function is defined in the included "minui/minui.h" which is part of the recovery files. Did you mess with the recovery files in bootable/recovery?
 
mantera said:
That function is defined in the included "minui/minui.h" which is part of the recovery files. Did you mess with the recovery files in bootable/recovery?
Click to expand...

Not at all, but odd enough a repo sync fixed it.
Now I'm having trouble creating the zip file. You probably won't know much about fixing this, but here is the error:
Code: 
ackage target files: out/target/product/triumph/obj/PACKAGING/target_files_intermediates/cna_mod_triumph-target_files-eng.gannon5197.zip
Package OTA: out/target/product/triumph/cna_mod_triumph-ota-eng.gannon5197.zip
./device/motorola/triumph/releasetools/triumph_ota_from_target_files -v \
	   -p out/host/linux-x86 \
	   -k build/target/product/security/testkey \
	   --no_assert=false \
	   --override_device=triumph,WX435,fb0 \
           out/target/product/triumph/obj/PACKAGING/target_files_intermediates/cna_mod_triumph-target_files-eng.gannon5197.zip out/target/product/triumph/cna_mod_triumph-ota-eng.gannon5197.zip

Given a target-files zipfile, produces an OTA package that installs
that build.  An incremental OTA is produced if -i is given, otherwise
a full OTA is produced.

Usage:  ota_from_target_files [flags] input_target_files output_ota_package

  -b  (--board_config)  <file>
      Deprecated.

  -k  (--package_key)  <key>
      Key to use to sign the package (default is
      "build/target/product/security/testkey").

  -i  (--incremental_from)  <file>
      Generate an incremental OTA using the given target-files zip as
      the starting build.

  -w  (--wipe_user_data)
      Generate an OTA package that will wipe the user data partition
      when installed.

  -n  (--no_prereq)
      Omit the timestamp prereq check normally included at the top of
      the build scripts (used for developer OTA packages which
      legitimately need to go back and forth).

  -e  (--extra_script)  <file>
      Insert the contents of file at the end of the update script.

  --backup <boolean>
      Enable or disable the execution of backuptool.sh.
      Disabled by default.

  --override_device <device>
      Override device-specific asserts. Can be a comma-separated list.

  -p  (--path)  <dir>
      Prepend <dir>/bin to the list of places to search for binaries
      run by this script, and expect to find jars in <dir>/framework.

  -s  (--device_specific) <file>
      Path to the python module containing device-specific
      releasetools code.

  -x  (--extra)  <key=value>
      Add a key/value pair to the 'extras' dict, which device-specific
      extension code may look at.

  -v  (--verbose)
      Show command lines being executed.

  -h  (--help)
      Display this usage message and exit.

** option --no_assert not recognized **
make: *** [out/target/product/triumph/cna_mod_triumph-ota-eng.gannon5197.zip] Error 2
gannon5197@icsbox:~/android/cna$
 
gannon5197 said:
Not at all, but odd enough a repo sync fixed it.
Now I'm having trouble creating the zip file. You probably won't know much about fixing this, but here is the error:
Code: 
ackage target files: out/target/product/triumph/obj/PACKAGING/target_files_intermediates/cna_mod_triumph-target_files-eng.gannon5197.zip
Package OTA: out/target/product/triumph/cna_mod_triumph-ota-eng.gannon5197.zip
./device/motorola/triumph/releasetools/triumph_ota_from_target_files -v \
       -p out/host/linux-x86 \
       -k build/target/product/security/testkey \
       --no_assert=false \
       --override_device=triumph,WX435,fb0 \
           out/target/product/triumph/obj/PACKAGING/target_files_intermediates/cna_mod_triumph-target_files-eng.gannon5197.zip out/target/product/triumph/cna_mod_triumph-ota-eng.gannon5197.zip

Given a target-files zipfile, produces an OTA package that installs
that build.  An incremental OTA is produced if -i is given, otherwise
a full OTA is produced.

Usage:  ota_from_target_files [flags] input_target_files output_ota_package

  -b  (--board_config)  <file>
      Deprecated.

  -k  (--package_key)  <key>
      Key to use to sign the package (default is
      "build/target/product/security/testkey").

  -i  (--incremental_from)  <file>
      Generate an incremental OTA using the given target-files zip as
      the starting build.

  -w  (--wipe_user_data)
      Generate an OTA package that will wipe the user data partition
      when installed.

  -n  (--no_prereq)
      Omit the timestamp prereq check normally included at the top of
      the build scripts (used for developer OTA packages which
      legitimately need to go back and forth).

  -e  (--extra_script)  <file>
      Insert the contents of file at the end of the update script.

  --backup <boolean>
      Enable or disable the execution of backuptool.sh.
      Disabled by default.

  --override_device <device>
      Override device-specific asserts. Can be a comma-separated list.

  -p  (--path)  <dir>
      Prepend <dir>/bin to the list of places to search for binaries
      run by this script, and expect to find jars in <dir>/framework.

  -s  (--device_specific) <file>
      Path to the python module containing device-specific
      releasetools code.

  -x  (--extra)  <key=value>
      Add a key/value pair to the 'extras' dict, which device-specific
      extension code may look at.

  -v  (--verbose)
      Show command lines being executed.

  -h  (--help)
      Display this usage message and exit.

** option --no_assert not recognized **
make: *** [out/target/product/triumph/cna_mod_triumph-ota-eng.gannon5197.zip] Error 2
gannon5197@icsbox:~/android/cna$
Click to expand...

This part of your command is not needed and is what's causing your error:

--no_assert=false \

If it were me, I would grep to find it and remove it from the command. Off-hand, I'm not sure exactly where the command is atm.
 
Sorry, I'm a huge noob when it comes to Unix terminal commands. I just learned cp. Lol.
How would you grep for this?
I've tried
grep -i 'no_assert=false' *
But it didn't bring anything back

EDIT:
Oh god finally.
Do you get excited everytime you see something like this?

Package complete: /home/gannon5197/android/cna/out/target/product/triumph/Codename-Android-(MOD)-2.0.0-RC-Triumph-UNOFFICIAL.zip
e57b78066d7f33e326b16c646293a887 Codename-Android-(MOD)-2.0.0-RC-Triumph-UNOFFICIAL.zip

Lol

Now here comes the logcats..
 
Okay. CNA boots up, RIL works (SMS and calling)
Headsets aren't working, I've found the commit for that though.
Data isn't working.
Of course, Camera isn't working.
Wifi isn't working:
E/WifiStateMachine( 202): Failed to load driver!
E/WifiStateMachine( 202): DriverFailedState

Mantera, is there a commit for a fix for wifi?
 
gannon5197 said:
Okay. CNA boots up, RIL works (SMS and calling)
Headsets aren't working, I've found the commit for that though.
Data isn't working.
Of course, Camera isn't working.
Wifi isn't working:
E/WifiStateMachine( 202): Failed to load driver!
E/WifiStateMachine( 202): DriverFailedState

Mantera, is there a commit for a fix for wifi?
Click to expand...

I'll be glad to test for you if needed, also you could try this out to get data working. :)
 
Twizted6789 said:
What's with u and patience I'm not impatient I didn't say hurry up mantera I just asked if he thought it would be possible
Click to expand...

Sorry if I came on a little strong, but these guys do what they do for free, and in their free time. They do it for the sake of everyone else and don't ask for anything in return. They have their own lives and jobs and families to look after and care for, so asking every few minutes if something's going to be done or can be done or when it will be done doesn't help at all. Besides that we need to fight the problems, not each other.
 
FrenchToast said:
Sorry if I came on a little strong, but these guys do what they do for free, and in their free time. They do it for the sake of everyone else and don't ask for anything in return. They have their own lives and jobs and families to look after and care for, so asking every few minutes if something's going to be done or can be done or when it will be done doesn't help at all. Besides that we need to fight the problems, not each other.
Click to expand...

I understand that but I'm not asking every few minutes and I'm not asking when something will be done I also think its sad that I can't ask a simple question without being criticized for it all I asked was if he thought it would be possible sorry if that was took the wrong way I've been on these forums long enough I know how hard everyone works and what all they sacrifice to give us These amazing roms that's all I'm saying. sorry again not trying to clutter up this thread with negativity
 
You must log in or register to reply here.
Back
Top Bottom