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

Root [Merit] ICS is coming...

just some screenshots
 

Attachments

  • droid@screen-1.png
    droid@screen-1.png
    88.6 KB · Views: 322
  • droid@screen-2.png
    droid@screen-2.png
    15.1 KB · Views: 308
Upvote 0
You are amazing ... You return the phone again and again to new life. Each part. I can not wait to try it, but I'm already worried about SMS. It's amazing that always arises the
problem.

keep in mind that both him and I are based in the u.s, so we can't really test every APN or SIM card in the world. the fact that vivo does some crazy stuff with their SMS layout anyways doesn't help
 
  • Like
Reactions: zajchik
Upvote 0
from the screenshots I see that the signal bar doesn't seem to be having signal is that one of the issues you are facing?

i didn't have the sim card in it. i'm working on this device and my new ZTE OpenC that i got two weeks ago, and the sim card is currently in that phone.

there's no reason to suspect it not to work. when it's ready for release i'll start fully testing. then i'll know for sure.


Is it aosp? Are there any issues with the gpu? I'm curious to know how smooth it is.

yeah, it's currently vanilla CM ics source in my dev environment. i'll be working on it as i go, however and modding as need be.

since this device is quite a bit different than the zte blade and skate in the way hardware on the board actually interacts with the kernel, gpu issues have been encountered.

however, i've moved past most of them. i'm working with several device trees for this one device in order to find the perfect configuration for the gpu.

hw acceleration is working from what i can tell. and running the qcom adreno ics binaries and not the gingerbread ones. getting genlock to fully work with the kgsl driver is another story however. until this is fixed, there will be graphical lag


right now there is no gpu sleep-of-death, very little graphical lag in basic functions, cpu and gpu overclock, working sensors, audio, and bluetooth, and presumably the ril.

not working is the camera and wifi, screenshot, and ums.

there are some problems with how the developers decided to handle internal and external storage in ics, and unlike my moto xoom tablet which had the same issues, the problem is a complicated one to fix for this device. i think i've fixed it completely in the kernel though. i'll know soon enough.
 
Upvote 0
updating kgsl driver in the gpu to work with genlock properly is proving to be very difficult.

because of all the work done to the zte blade kernel by so many people, its kernel source is cluttered with garbage and broken code and makes a kernel that is about .2 mb too large to use. the boot and recovery partitions can be resized to accommodate this but that is overkill really.

so, i'm trying to backport some 3.0 kernel features to the gpu.

as of now, graphics work, just really slow with hw acceleration going because genlock and kgsl are broken.

without hw acceleration, the phone is no worse than the stock gingerbread as far as responsiveness in my opinion. though this is not acceptable.
 
Upvote 0
i hope you figure it out it would be sad if because of those issues it doesnt get released publicly


i think everyone is going to be very pleased in the next few days...

ril is definitely working as i just made a test call and checked audio and proximity.

proximity is working just like it's supposed to with the sceen not locking despite having a proximity like it does in gingerbread source from CM

there is definitely some minor lag as things are right now, but i'll be working to remedy it in the future.

the only things not working are wifi and camera from what i can tell right now.

working to fix these things promptly
 
Upvote 0
good news!

finally got msm kgsl drivers CORRECTLY updated to 3.0 kernel source

and

genlock CORRECTLY updated to 3.0 kernel source

the only problem is that i had to use the kgsl from an lg device kernel as it was correctly ported.

zte sources of the driver from the blade2 3.0 source were broken--how anyone got it working on that end is beyond me.

but i've now got these two issues fixed.

there is hw acceleration using the old gralloc and copybit with the old adreno drivers in ics

however

there is minimal lag and the occasional glitch.

hopefully this new kernel will give the needed fixes to get genlock and kgsl working together with the new adreno libs making hw acceleration possible without a superlag that is present using the old kgsl drivers even with genlock imported.
 
Upvote 0
are you planning on doing an alpha or beta release to test it out?

as soon as i think it's stable enough i'm just going to release it and release updates as needed.

i didn't release gingerbread rom til it was near 100%.

it will definitely need testing though. i can already list a few problems it has that might not be correctable but these are very very minor issues.

i don't plan on releasing it til the camera works. and that is proving to be difficult. but i've got a couple things up my sleeve and motorhead has agreed to take a look at it as well.

all in due time :smokingsomb:
 
Upvote 0
as soon as i think it's stable enough i'm just going to release it and release updates as needed.

i didn't release gingerbread rom til it was near 100%.

it will definitely need testing though. i can already list a few problems it has that might not be correctable but these are very very minor issues.

i don't plan on releasing it til the camera works. and that is proving to be difficult. but i've got a couple things up my sleeve and motorhead has agreed to take a look at it as well.

all in due time :smokingsomb:

Is camera FCing or upside down?
 
  • Like
Reactions: Mrsevic
Upvote 0
Is camera FCing or upside down?

it's doing nothing lol

the last logcat i got using a camera skeleton it was looking for a 16 letter command that didn't seem to exist.

i'm fairly certain libcamera and liboemcamera were NOT prelinked in the oe rom, yet this command isn't found because libcamera can't be found / can't be mapped in memory while present on the device.

i have a feeling it's a very small setback, but since i couldn't get the camera working building a new lib from source to open liboemcamera for gingerbread, it's proving that much more difficult in the new environment since camera service and camera client also changed and can't just be reused from the old
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones