TrustME90
Well-Known Member
androidboot.hardware parameter may be incorrect?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
androidboot.hardware parameter may be incorrect?
stayboogy
Android Expert
you know, i saw that mentioned somewhere else as well...
got any links to some corresponding info for me???
edit: i also changed one line in the kernel and am now rebuilding it as well. i moved the kgsl init from it's old position which shouldn't have been done since zte made a new init to handle all devices for the roamer.
i'm rebuilding now.
stayboogy
Android Expert
see, there's no reasonable logic why the cmdline would have anything to do with it.
it was what i did in the kernel.
it's now fine.
finally...
i do appreciate the link. that's exactly where i saw it mentioned before actually
out of ideas
Android Enthusiast
great. i finally get around to tinkering with 2.3.7 AOSP then you gotta go and get ICS working.
once again, great job dude. I'll be following.
once again, great job dude. I'll be following.
Motorhead1991
Android Expert
stayboogy
Android Expert
there's way too many problems with hw rendering using the new adreno libs with the proper kgsl and genlock updates.
i'm going to be trying using the legacy adreno libs with the full msm7x27 config and see what happens. i'm fairly certain it'll fail to load launcher once it boots but i'm going to try anyway.
preliminarily i am not going to be using the updated adreno libs until further notice. everyone is going to have to settle with legacy hw acceleration that has a very minor lag at times and screen dimming. it's the best of both worlds if my test doesn't work.
i'm going to be trying using the legacy adreno libs with the full msm7x27 config and see what happens. i'm fairly certain it'll fail to load launcher once it boots but i'm going to try anyway.
preliminarily i am not going to be using the updated adreno libs until further notice. everyone is going to have to settle with legacy hw acceleration that has a very minor lag at times and screen dimming. it's the best of both worlds if my test doesn't work.
micallan_17
Well-Known Member
Hope we can test something soon 
stayboogy
Android Expert
okay so here's what's going on...
back to old adreno for gpu and shading stability
back to old copybit and gralloc for framebuffer stability
still on my updated kgsl + genlock + binder kernel source
camera is working, but preview is glitchy. autofocus works. there is preview lag but i'm about to increase the framerate to fix that
i've added the cm10 file manager for completeness so no one has to install a closed source root file manager.
wifi is still not working. it was pia to finally get working in gb too though
back to old adreno for gpu and shading stability
back to old copybit and gralloc for framebuffer stability
still on my updated kgsl + genlock + binder kernel source
camera is working, but preview is glitchy. autofocus works. there is preview lag but i'm about to increase the framerate to fix that
i've added the cm10 file manager for completeness so no one has to install a closed source root file manager.
wifi is still not working. it was pia to finally get working in gb too though
Motorhead1991
Android Expert
I know the guy that ported CMFM to ICS on a personal level 
.
.
stayboogy
Android Expert
I know the guy that ported CMFM to ICS on a personal level
it's definitely a nice addition.
open source is always a plus
Dxnarutoboi
Lurker
Just wondering, is there a way you would incorporate something to swap the internal and external memory for more memory, or use the Int2ext script by CronicCorey such as this rom SpeedFreak 2.0 - Out Of Beta and Available Now!!![UNSUPPORTED] - Android Area51 , to add more internal space?
As quoted from this rom " Int2ext script by CronicCorey also runs on boot mounting any sd ext to your internal memory, thus combining the two and giving you an incredible amount of storage space with no symlinks and also zip aligning every app not previously zipped."
Sorry I'm a noob at this so just wondering...
As quoted from this rom " Int2ext script by CronicCorey also runs on boot mounting any sd ext to your internal memory, thus combining the two and giving you an incredible amount of storage space with no symlinks and also zip aligning every app not previously zipped."
Sorry I'm a noob at this so just wondering...
stayboogy
Android Expert
those are just init.d scripts,
and,
just like the aosp gingerbread rom,
init.d scripts are supported. just install it to the /system/etc/init.d directory and chmod 777 it
for those specific scripts, read the documentation associated with them (http://forum.xda-developers.com/showthread.php?t=1716124) for support as i don't support them and WILL NOT provide support for them.
thanks
Motorhead1991
Android Expert
IIRC, CM9 has that, but I haven't used that in like 2 years.
One advantage to mod ROMs is the fact that we can now send the dalvik cache from /system to /cache by default. This frees up a pretty substantial amount of space.
One advantage to mod ROMs is the fact that we can now send the dalvik cache from /system to /cache by default. This frees up a pretty substantial amount of space.
stayboogy
Android Expert
i'm almost thinking about not releasing the rom now...
it's usable by all means, but there are intermittent issues that seem to crop up using third party apps here and there
and some read write sdcard issues here and there
and
i really don't feel like dealing with anyone's nonsense when they incur these problems. they are easily fixed with a reboot most times, but i'm not going to answer a million questions about them.
it may be best to just be on GB in the end.
it's usable by all means, but there are intermittent issues that seem to crop up using third party apps here and there
and some read write sdcard issues here and there
and
i really don't feel like dealing with anyone's nonsense when they incur these problems. they are easily fixed with a reboot most times, but i'm not going to answer a million questions about them.
it may be best to just be on GB in the end.
micallan_17
Well-Known Member
I wouldn't complain if you sent me a link to try, its.sad that you might not release it
stayboogy
Android Expert
i'm still debating the idea...
the build is done. well as done as it's going to get for now.
i'm tweaking overlays right now.
gapps seem to cause the majority of the problems from what i can tell.
i'll make up my mind after i test drive it the next couple of days
stayboogy
Android Expert
so.
new development...
voice search won't work in ics, even using the modded app and google now app that is commonly available.
this makes the phone useless for my everyday use since i use the speech to text almost exclusively... i'm working on fixing the gb voicesearch at the moment to work in ics, which does work for actually searching the internet. it however won't do speech to text yet...
so there's that.
other noticeable problems are intermittent FC's and the occasional "app is not installed" error.
most of this has to do with the kernel being 3g/1g vmsplit. but, sometimes it's just plain because the device isn't apt enough to handle it all the way it is.
i promise i'll release something for everyone to play with this week. but the thread will be listed as exclusively EXPERIMENTAL and probably won't ever gain 1.0 status
unless this 3.0 zte kernel source i have starts to work properly... then we may be in business all the way with even the new adreno drivers. potentially even able to run JB.
it'd be nice if i could get another working phone though... i'm not going to be dev'ing using my daily driver merit because i'm not ready to activate my zte open c just yet since i'm working the hell out of it too lol
new development...
voice search won't work in ics, even using the modded app and google now app that is commonly available.
this makes the phone useless for my everyday use since i use the speech to text almost exclusively... i'm working on fixing the gb voicesearch at the moment to work in ics, which does work for actually searching the internet. it however won't do speech to text yet...
so there's that.
other noticeable problems are intermittent FC's and the occasional "app is not installed" error.
most of this has to do with the kernel being 3g/1g vmsplit. but, sometimes it's just plain because the device isn't apt enough to handle it all the way it is.
i promise i'll release something for everyone to play with this week. but the thread will be listed as exclusively EXPERIMENTAL and probably won't ever gain 1.0 status
unless this 3.0 zte kernel source i have starts to work properly... then we may be in business all the way with even the new adreno drivers. potentially even able to run JB.
it'd be nice if i could get another working phone though... i'm not going to be dev'ing using my daily driver merit because i'm not ready to activate my zte open c just yet since i'm working the hell out of it too lol
stayboogy
Android Expert
well,
overcoming speech to text and the problem i was having with latinIME not displaying the bottom half of the last row of keys--gone.
using the gb apps was the only way i could fix it. definitely a more appropriate fix than all the other nonsense i've seen posted several other places, xda included...
dalvik is permanently on data now. cache partition is not large enough to hold all the cache from a full system install so this was necessary.
if one slims down the rom and doesn't install gapps, this can easily be remedied by adding a # to the build.prop, then wiping the cache partition and rebooting.
system partition is at max with the full rom and gapps installed. of course all are welcome to slim the rom with the included open source root file manager.
who knows, everyone may be happier with it than i am.
i built it for all you guys anyway.
overcoming speech to text and the problem i was having with latinIME not displaying the bottom half of the last row of keys--gone.
using the gb apps was the only way i could fix it. definitely a more appropriate fix than all the other nonsense i've seen posted several other places, xda included...
dalvik is permanently on data now. cache partition is not large enough to hold all the cache from a full system install so this was necessary.
if one slims down the rom and doesn't install gapps, this can easily be remedied by adding a # to the build.prop, then wiping the cache partition and rebooting.
system partition is at max with the full rom and gapps installed. of course all are welcome to slim the rom with the included open source root file manager.
who knows, everyone may be happier with it than i am.
i built it for all you guys anyway.
micallan_17
Well-Known Member
I know you do all what you and i really i really appreciate.tour.efdort