Root [Avail] [WIP]What we hope to do w/Avail and CM

[nickdalzell]

is there something i am missing in regards to tacking in APKs for CM ROMs? i just found all the app APKs for Cyanogen 7 but they give me a 'application not installed' error after they attempt to install. i tried system apps installer and it says 'app installed correctly' but no, it still isn't. the APK in question is CMParts.apk. DSP manager produces similar bad luck. am i missing something? i am rooted, have RW access to /system/app, and tried the manual copy trick to no avail. how do i force-install it?

first i'd like a force-install. 'application not installed' is of no help. not installed. why? it's not very helpful

 

[stayboogy]

is there something i am missing in regards to tacking in APKs for CM ROMs? i just found all the app APKs for Cyanogen 7 but they give me a 'application not installed' error after they attempt to install. i tried system apps installer and it says 'app installed correctly' but no, it still isn't. the APK in question is CMParts.apk. DSP manager produces similar bad luck. am i missing something? i am rooted, have RW access to /system/app, and tried the manual copy trick to no avail. how do i force-install it?

first i'd like a force-install. 'application not installed' is of no help. not installed. why? it's not very helpful

androidian.apk
androidterm.apk
cmparts.apk
cmscreenshot.apk
cmstats.apk
cmupdatenotify.apk
cmwallpapers.apk
cyanbread.apk


these apps will not install correctly on our phones when trying to make cm7, and these are all the apps that when removed i can boot the cm7 build i made many months ago (and by also using our kernel).

even when these apps are properly installed through update.zip into the system/app directory by using recovery they prevent system boot.

these apps must be removed in order than cm7 will boot on our phone. this means that all of the features of cm7 just will not work.

some of the reasons for this are because the init.rc within the cm7 boot.img ramdisk is too inconsistent with the oem one on our phone--file system structure is very different from ours in some respects. these inconsistencies make cm7 impossible to boot when it is fully installed on the phone. this is because (a) some things are not present in our kernel when it is used instead of the cm built one, and (b) the kernel produced by the cm sdk is incompatible with our phones when it is used instead of the stock kernel.

other inconsistencies are the scripts that cm tries to run at boot that are incompatible with the stock file structure of our phone when it is left intact, and which cause boot loops when the cm file structure is used.

when one strips all the specific parts of cm7 that are utterly inconsistent with our phone and prevent system operation, one is left with a sudo-cm build that is neither worth the effort nor the time to fix each individual inconsistency.

i've built cm7 for this phone. if you want the original build i've got that will not boot fresh off the sdk, let me know and i'll give you a link for it. you can try to play with it and see if you can get all the apps above working.

but i warn you, it's probably above your skill set. you will be better off learning how to build a rom (not nandroid) that will install from recovery and boot. and then making one that will do the same with all your custom apps and mods and theme work. much more, better, and pleasing things can be made by doing it manually than trying to resurrect a dead style cm rom for this phone.

i honestly think you could make a better rom than cm could for this phone.

i think my recent two roms are a testament to this fact. and those were quickly thrown together.

 

[nickdalzell]

i never could get the build environment working. i tried wiping all of it and starting over and now i get problems at the download repo step. so i just trashed that method. i would not mind playing around with the one you got that booted, even if the apps are stripped out...if it does not boot i am unsure how i could strip them out anyway first.

i did make a good copycat of CM 7 but i would like to have some of the tools added to the settings menu, like if there was a way to make a link there to open up say No-Frills CPU tool, thus integrating it, vs. having icons all over the dock that would be nice. also, i am not sure where CM gets those lock/wake animations at. i assumed CMparts.apk or Theme Chooser.apk. any word on if Theme Chooser.apk works? i did get dev tools and spare parts to port fine into a stock

oh, one more question if you may, how would i get Kernel1.0 into any ROM i am using? do i just flash it in Zip form like a ROM and reboot or what?

 

[stayboogy]

i never could get the build environment working. i tried wiping all of it and starting over and now i get problems at the download repo step. so i just trashed that method. i would not mind playing around with the one you got that booted, even if the apps are stripped out...if it does not boot i am unsure how i could strip them out anyway first.

i did make a good copycat of CM 7 but i would like to have some of the tools added to the settings menu, like if there was a way to make a link there to open up say No-Frills CPU tool, thus integrating it, vs. having icons all over the dock that would be nice. also, i am not sure where CM gets those lock/wake animations at. i assumed CMparts.apk or Theme Chooser.apk. any word on if Theme Chooser.apk works? i did get dev tools and spare parts to port fine into a stock

oh, one more question if you may, how would i get Kernel1.0 into any ROM i am using? do i just flash it in Zip form like a ROM and reboot or what?

themechooser doesn't work either.

i'm busy and can't really go into all this right now. dev tools and spare parts work fine as they aren't cm only apps. and i'm giving you the standard cm build. the one that boots isn't for the public.

*link made private*

 

[out of ideas]

Dude. The animation is in gb already. Google it. You need apk tool

 

[nickdalzell]

i am not talking about the boot animation, i am specifically referring to the animation normally found in CM during wake/lock. normally found in CM Settings. it makes a cool TV style flip in or our depending on whether you're waking or locking. it's not in GB by default. only seen it in CM

currently i've tried using ROM toolbox to edit all the animations available on stock GB stock ROMs. and nothing. still just turns off or on normally.


EDIT: ok so far i have managed to edit out the APKs that Stayboogy said had to be removed to make the CM 7 build boot, but am still stuck where it gets to the ZTE logo, reboots itself, see ZTE logo again, and then just dumps me into recovery. am i supposed to install a different kernel too?

Also, had to remove an assert code because it wouldn't even install because of the error 'getprop assert failed'. then it installed, but still dumps into recovery. currently installing Kernel1.0 now

EDIT2: still dumps me straight into CWM. he said it would boot fine if i removed those APKs, so what gives? i tried kernel 1.0 with same result. it goes to ZTE, reboots itself, see ZTE again, then dumps me into recovery. this is the exact same result when i tried flashing the Blade version long ago. in fact, the logcat says ro.product.type = blade too, so am i running the merit build that didn't boot or the blade build that was unmodified? i'm lost

 

[cwwilson721]

The issue is alot deeper than just the apps.

'blade' is NOT the Z990 ('roamer'). Close, but not the same hardware.

The apps won't load/install because of other things it needs that are provided by Cyanogen Mod.

Cyanogen Mod, at the moment, doesn't work on our (Z990) phones because, as I've stated, the build/make files are NOT usable for our hardware. YET.

NOT because it is "way above you"
NOT because of any other reason.
It IS because Cyanogen has NOT made the "proprietary" part of CM available/modded for the Z990's YET.

So, the apps won't work.

The rest of the 'build' will, because it is 'super generic'

Patience

It will come. It takes time.

 

[nickdalzell]

i know the apps won't work. that is why i tried removing their APKs first to see if it'd flash and boot without, as Stayboogy suggested a few posts up. apparently it did not. he had sent me the build he made for our Merit but one which didn't boot yet. i was thinking if i removed the apps that he says causes it to not boot with that particular build, that it would boot.

 

[cwwilson721]

i know the apps won't work. that is why i tried removing their APKs first to see if it'd flash and boot without, as Stayboogy suggested a few posts up. apparently it did not. he had sent me the build he made for our Merit but one which didn't boot yet. i was thinking if i removed the apps that he says causes it to not boot with that particular build, that it would boot.

IF it boots, would be luck.

A CM build also needs a CM kernel built against that particular build, and a few other things.

While it may boot, odds are, it won't.

And, yes, I have a booting CM kernel and build, but:

• Not stable at all, so I won't post it
• Kernel has issues, too
• Most apps cause FCs or total hangs
• Other peoples work is involved, and I will not release until I get their OK for those parts

Slowly getting there, but it won't happen soon.

Same with a CWM 6 build that works fine, but has other parts in it.

It's coming, but may be awhile.
I'm just as impatient. But, I am working towards it. Proprietary is proprietary. Their work, even if it's just one line, is their work. Some of it has to do with a big player in the Android field. I can't even say who, or what.

Patience.

 

[stayboogy]

IF it boots, would be luck.

A CM build also needs a CM kernel built against that particular build, and a few other things.

While it may boot, odds are, it won't.

And, yes, I have a booting CM kernel and build, but:

• Not stable at all, so I won't post it
• Kernel has issues, too
• Most apps cause FCs or total hangs
• Other peoples work is involved, and I will not release until I get their OK for those parts

Slowly getting there, but it won't happen soon.

Same with a CWM 6 build that works fine, but has other parts in it.

It's coming, but may be awhile.
I'm just as impatient. But, I am working towards it. Proprietary is proprietary. Their work, even if it's just one line, is their work. Some of it has to do with a big player in the Android field. I can't even say who, or what.

Patience.

although you are right about some of the kernel issues, it's not entirely true.

the problems you are having with your cm build kernel i assume are the modules (based on what you posted over at A51).

i had 16 modules built the first kernel i made--took very little correcting with manual placement of some of the libxxxxx files for the build errors that cropped during the build. wifi didn't work though. pretty sure i forgot to include the module it created when i installed it. but sadly it got deleted so i can't work with it now...

the second kernel i built had 14 modules, but the wifi never worked then either, and i couldn't figure out why.

both kernels worked in every other way though--minus some ipv6 stuff that i wasn't sure about???

it's possible to get it to boot without a new kernel and even by using the stock kernel as i've done it. but other things have to be modded in the process, both on the phone, and the rom structure. but it can be done.

the init.rc of the boot.img ramdisk created by cm is one main issue. our kernel can be used for the majority of the features, but some of the file structure creations and services that init.rc calls are wrong and would have to be completely customized by someone who had the patience in order to frankenstein a "proper, full build" of cm7 for these phones. i've done substantial work in the area already.

the fact is that some of the ways cm7 is structured are a waste of time when they can be bypassed and done more efficiently by modifying where many things install themselves by the rom.zip.

i'm still of the persuasion that we can create better by moving on from cm. there's quite a bit that can be done easily already. my way of adding init scripting proves this point, as instead of creating a new service to add scripting all that had to be done was the edit of one file already called init.rc and adding the init directory.

instead of building from the ground up, the way to go is by using what is already there and adding what is not. it's the most efficient way, but no one seems to understand that...

 

[nickdalzell]

personally a lot of what i like in Cyanogen is the built-in features. i know you can get them via apps but they scatter about the launch drawer or home screen or dock and make a mess. some run all the time too. tacking on every feature makes the ROM bloated and RAM hogging. it'd be nice if the apps could be inside the settings menu or a custom menu inside settings the way it's done in CM 7. so far it takes separate apps to overclock. in CM 7 you can just get into performance settings and overclock all you like.

i know those apps are non-functional now, but i'd still like to get the thing to boot up without, but i keep getting dumped into CWM for some reason.

My lookalike ROM, sans CM Settings, Theme Chooser and the TV-style wake/lock animations, is almost indistinguishable from the real thing. it's fast (got Kernel 1.0 in there now), and relatively ok on internal storage. i haven't tried modding a deodexed ROM yet to increase it but i got up to 70MB free so far, even with ROM toolbox Pro and Dolphin in there. i just can't stand all the scattered icons though. even when hidden in the app drawer they bug me.

 

[cwwilson721]

although you are right about some of the kernel issues, it's not entirely true.

the problems you are having with your cm build kernel i assume are the modules (based on what you posted over at A51).

i had 16 modules built the first kernel i made--took very little correcting with manual placement of some of the libxxxxx files for the build errors that cropped during the build. wifi didn't work though. pretty sure i forgot to include the module it created when i installed it. but sadly it got deleted so i can't work with it now...

the second kernel i built had 14 modules, but the wifi never worked then either, and i couldn't figure out why.

both kernels worked in every other way though--minus some ipv6 stuff that i wasn't sure about???

it's possible to get it to boot without a new kernel and even by using the stock kernel as i've done it. but other things have to be modded in the process, both on the phone, and the rom structure. but it can be done.

the init.rc of the boot.img ramdisk created by cm is one main issue. our kernel can be used for the majority of the features, but some of the file structure creations and services that init.rc calls are wrong and would have to be completely customized by someone who had the patience in order to frankenstein a "proper, full build" of cm7 for these phones. i've done substantial work in the area already.

the fact is that some of the ways cm7 is structured are a waste of time when they can be bypassed and done more efficiently by modifying where many things install themselves by the rom.zip.

i'm still of the persuasion that we can create better by moving on from cm. there's quite a bit that can be done easily already. my way of adding init scripting proves this point, as instead of creating a new service to add scripting all that had to be done was the edit of one file already called init.rc and adding the init directory.

instead of building from the ground up, the way to go is by using what is already there and adding what is not. it's the most efficient way, but no one seems to understand that...

Please stop now. In a way we are in agreement.

BUT:

I didn't go into specifics, because I wanted it short and sweet.

As for WHY, it's because WE WANT IT.

Thus, title of the thread is :
"What we hope to do w/Avail and CM"

NOT "What only YOU want to do with anything"

EVERYBODY knows in this forum what your views are on CM.

And those views are fine.

But, that is YOUR VIEW.

My view, and others, is different.

We are working towards it, and progress is being made.

 

[cwwilson721]

personally a lot of what i like in Cyanogen is the built-in features. i know you can get them via apps but they scatter about the launch drawer or home screen or dock and make a mess. some run all the time too. tacking on every feature makes the ROM bloated and RAM hogging. it'd be nice if the apps could be inside the settings menu or a custom menu inside settings the way it's done in CM 7. so far it takes separate apps to overclock. in CM 7 you can just get into performance settings and overclock all you like.

i know those apps are non-functional now, but i'd still like to get the thing to boot up without, but i keep getting dumped into CWM for some reason.

My lookalike ROM, sans CM Settings, Theme Chooser and the TV-style wake/lock animations, is almost indistinguishable from the real thing. it's fast (got Kernel 1.0 in there now), and relatively ok on internal storage. i haven't tried modding a deodexed ROM yet to increase it but i got up to 70MB free so far, even with ROM toolbox Pro and Dolphin in there. i just can't stand all the scattered icons though. even when hidden in the app drawer they bug me.

Some of the CM settings are certainly 'sweet'

They 'rely' on some framework stuff in the CM build process, tho, thus may, or may not, be available thru addon apps or rc editing.

But as far as deodexing, have you tried?

You can get rid of apps you don't need. But just be careful, and test.

I'm always amazed at what depends on what.

As for "breathing room" have you checked CronicCorey's (XDA Dev) scripts (or talked to him, for that matter) about using/modding his int2ext scripts? You might get very happy...

Keep it up. I'm interested on what you come up with.

 

[stayboogy]

it's probably best that not be giving me orders there cw...

but if i want to share regarding this thread, it's my right to do so, and considering the validity of what i have to say based on personal experience, and the fact that it's perfectly in line with the rules here, you don't really get the privilege of telling me what to do...

aside from that though i'm only trying to help, and what i meant is that if cm is being built, then it should be built with the intention of assimilating its features into the stock system shell instead of trying to reinvent the wheel so to speak by totally rebuilding from the ground up. it will make things much easier and more efficient. not to mention pave the way for further porting of various roms in the future with known, proven methods.

but, like you implied yourself, i really don't care if it gets built or not. much better has been and is being done without it. but that doesn't mean i can't help or that don't want to help...

 

[nickdalzell]

i don't know what 'deodexing' even IS right now. i heard it gives you more internal storage but not sure. i also thought about SD partitioning but i got years of MP3s i am not about to lose on my only SD card and if i mess up there goes 10-years of downloads in one step!

CyanogenMod personally i found by accident. i had a Virgin Mobile LG Optimus V that had, via its stock ROM, even less internal storage (or so it seemed) than my Merit ever did, and everyone who has experienced the Low Disk Space error and how it causes your texts, emails and stuff to NOT sync, well some site suggested rooting it. the phone came with ancient Froyo, a minor upgrade from the horridly unstable Eclair, and during the rooting process, i must have thought that flashing the ROM was required as part of the root, and when the phone rebooted, i was all 'WHOA!' not only was this my first introduction to Gingerbread, my now favorite version of Android OS, but it was an unofficial CyanogenMod ROM too. it was called 'Inferior Human Organs' and included tons of stuff, had the low space issue edited out, and i am guessing it may have been deodexed or the SD was partitioned because i had far more space for apps than i did previously. ever since CM has become my de-facto and required ROM in any device i buy now.

 

[out of ideas]

i am not talking about the boot animation, i am specifically referring to the animation normally found in CM during wake/lock. normally found in CM Settings. it makes a cool TV style flip in or our depending on whether you're waking or locking. it's not in GB by default. only seen it in CM

currently i've tried using ROM toolbox to edit all the animations available on stock GB stock ROMs. and nothing. still just turns off or on normally.

Neither am I for the 100th time. its called cRt animation and you can put it in any GB, but thats way beyond where you are now.

looks like this?
Video 1.avi - YouTube

 

[IOWA]

Looks like some great progress is being made here

Let's work together (and not against each other) and try to get the results we all want =D

 

[nickdalzell]

Its not in the play store out of ideas. The closest I got is screen off and lock. That video is exactly what I'm wanting but I don't know how you do it. I've only seen it in CM builds. You can access that setting on my Kindle Fire running it via settings-->cyanogenmod settings-->Display-->screen on and screen off animation

 

[cwwilson721]

I know most "phone animations" are fairly launcher-dependant, but not sure about "screen on/off" animations. Maybe I'll look at another CM rom and see if there is anything we can do.

But, we may be out of luck, too. There are some things that,while possible, may not be worth it yet. I'm always amazed at how one thing can be dependent upon something else, that needs a third, and so on..

Let me look and see (and I believe it needs a bit more than an app to get it, but not 100% sure)

 

[cell2011]

All these are from ZTE blade and flashed but didnt boot past Zte logo but maybe can if ported right. I dont know but it seems strange not one installation aborted. Hope this might help somewhat. Found these on XDA under The ZTE Blade ICS thread1.update-cm-9-20120531-SNAPSHOT-blade-ColdFusionX-tilal6991-signed.zip 2.


Pre-CM9-AOKP-REMIX-RC7.1.0-BLADE-full-signed.zip3.

cm-9-20121031-KonstaKANG-blade.zip And need the latest


Latest Google Apps for CM9

 

[nickdalzell]

my attempts don't hang, they just boot, stay a bit at the ZTE logo, then reboot, see ZTE logo again, then dumps me into recovery. seems whatever happens it's trying to boot, then fails, and reboots recovery automatically. sadly, any logcat apps aren't telling me a thing.

CyanogenMod 9 is based on Android Ice Cream Sandwich (4.x) and i highly doubt that given the extremely low spec of the ZTE Z990G (600 MHz, single-core, no GPU, no hardware accel, etc) i highly doubt that it is even possible to run that version on our phones. and even if it could, it would run horridly slow, much like running Windows 98SE on a i486

 

[stayboogy]

my attempts don't hang, they just boot, stay a bit at the ZTE logo, then reboot, see ZTE logo again, then dumps me into recovery. seems whatever happens it's trying to boot, then fails, and reboots recovery automatically. sadly, any logcat apps aren't telling me a thing.

this is where it takes meticulous examination of how the system operates...

it is is possible to get it to boot, but as i've explained so many times up to this point, it takes a lot of work and ingenuity...

also there are too many fundamental differences from the blade and merit hardware that prevent several parts of a blade rom being ported completely to the merit...

 

[nickdalzell]

yes but it also happened on the *.ZIP you sent me, so unless something is up deep down or the boot.img is not compatible, it would be Merit/Avail ported, no?

 

[stayboogy]

yes but it also happened on the *.ZIP you sent me, so unless something is up deep down or the boot.img is not compatible, it would be Merit/Avail ported, no?

i told you the one i gave you a link for wouldn't boot...

none of them will unless there is some frankensteining done that i've mentioned numerous times in this conversation and others... even where i specifically address what you mentioned above...

how you continue to miss this i have no idea...

 

[cwwilson721]

I know.
You know everything.

Look HERE!
http://androidarea51.com/***-all-th...-full-ext4-and-swap-enabled-package-for-z990/

HA FREAKIN HA!