i port cm12.1 from source
with original stok kernel(ramdisk change)
but not working
cell network( that is missing library from stock rom. i find it)
wifi network
blue tooth turn on but maybe not working (i tested it)
nfc not working
sound not working
almost not working
im newbie newbie
so i dont know how to fix
my github is https://github.com/wwwhana
somebody help me?
read thx
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kernel cmd
mkbootimg --base 0x00000000 --kernel <zImage> --ramdisk <ramdisk.img> --ramdisk_offset 0x02000000 --dt <dt.img> --tags_offset 0x01E00000 --pagesize 2048 --cmdline "androidboot.hardware=qcomyukon user_debug=31 msm_rtb.filter=0x37 androidboot.bootdevice=msm_sdcc.1 slub_min_objects=4 build_variant=user msm_rtb.enable=0" --output <boot.img>
Go to the cyanogenmod forums and ask there.
status
wifi is not working(i dont know why doesn't work it...pront wlan build with kernel....)
camera is not working *this is dosent work camera hal...
audio is sometime build working anothertime is not working
brigtness not working but modified /sys/class/leds/lm3630-lcd-bl/brightness can change
nfc is maybe working(possible turn on off)
bluetooth is working pair possible
baseband(cellular networking) is possible when dumping /bin, /lib, /vendor folder
sensors is maybe not working(i see logs.....many mnay errors....)
who are help me??
Help might have arrived... (I think)
wwwhana said:
wifi is not working(i dont know why doesn't work it...pront wlan build with kernel....)
camera is not working *this is dosent work camera hal...
audio is sometime build working anothertime is not working
brigtness not working but modified /sys/class/leds/lm3630-lcd-bl/brightness can change
nfc is maybe working(possible turn on off)
bluetooth is working pair possible
baseband(cellular networking) is possible when dumping /bin, /lib, /vendor folder
sensors is maybe not working(i see logs.....many mnay errors....)
who are help me??
Click to expand...
Click to collapse
Ah... another one. It seems you have gotten further than me. I'm having a look at your GitHub, maybe I can find something there. We are both new to this though, so maybe teaming up would be a good idea. Please contact me at [email protected] so that we can talk further.
Thanks
Riccorbypro
oh tanks
Riccorbypro said:
Ah... another one. It seems you have gotten further than me. I'm having a look at your GitHub, maybe I can find something there. We are both new to this though, so maybe teaming up would be a good idea. Please contact me at [email protected] so that we can talk further.
Thanks
Riccorbypro
Click to expand...
Click to collapse
i first try build from source. so, just booting but not working every thing
base device tree is tianchi(this device is same stock rom build! and family device)
so i dump from sony stock rom (if exist file not over write)
working cellnetworking
and i try something do...
i try insmod /system/lib/modules/wlan.ko
it working! wifi when type this command
but....i try now but not working....
i use
" http://forum.xda-developers.com/showthread.php?t=2545618 "
this trick
how to base cm rom and i just change lib folder from stock sony rom. i change file about runtime file(libart, linandroid~)
we can get cell networking, camera(!!!) HAL so, if this device need like sony openproject vendor file (that is not equeal) and some orinal library and /bin file need it
but not working gravity sensors...wifi(if shutdown se linux affter insmode...maybe working?).....and not led control(this front led, lcd backlight)
but working near seonsor(display off and do not touch when calling)
so i upload this result....
Just in case I'll put this file.
it's your devlopment and For those who are interested
http://www.mediafire.com/download/ewq6k6nda8a1ssc/and.7z
you can flash use
"fastboot flash system system.img"
fastboot flash boot boot.img"
and this is this rom logs
https://gist.github.com/wwwhana/2586f04fadf6bb59f5b5
thank you.
read my bad english.
xposed also working
Although of course, this is base is aosp so working
i try install xpoesed framework. so, not problem....
so i want this rom is perfect.....
and
that rom is working sound, nfc and already working list
wwwhana said:
Although of course, this is base is aosp so working
i try install xpoesed framework. so, not problem....
so i want this rom is perfect.....
and
that rom is working sound, nfc and already working list
Click to expand...
Click to collapse
*xposed working*
You now have my attention :good:
wifi f#[email protected]#$%
wifi need firmware file in firmware_bin where https://github.com/sonyxperiadev/prima 's prima tree
so now, Xperia c3 with C3(D2533) for cm-12.1 working list
cell networking
wifi
bluetooth
nfc
audio
maybe comming soon working
camera with torch(i find need camera files)
don't working
front led
rotation sensor
lcd-backlight
and i don't know any sensors....
i will comming final test this semester...
so i will comming 12/12 KST
Thank You
Dual sim model?
sorry
i Can't testable xperia C3 dual model
cause i'm not have them
if some one try my test rom, and say to here result
maybe Assuming working, that rom but not working 2nd sim
IF someone try it?
From what I've seen, the kernel for D2533 and D2502/D2503 is the same, there is no difference in the tree. So theoretically there should be one universal build, for both single sim and dual sim.
Sent via Carrier Pigeon
Sensors....
insert sensors.qcom.so
i get infomation about sensors but they not working...
maybe they not connect Android framework
and gps is not working....
cause FLP HAL is not initialize
show me error
missing library? no that.
logs say
07-03 14:18:25.128 764-764/? E/HAL: load: module=/vendor/lib/hw/flp.default.so
dlopen failed: cannot locate symbol "_ZN9LocApiV0216deleteAidingDataEj" referenced by "liblbs_core.so"...
07-03 14:18:25.128 764-764/? E/FlpHardwareProvider: Error hw_get_module 'flp': -22
07-03 14:18:25.129 764-764/? E/LocationManagerService: FLP HAL not supported
07-03 14:18:25.133 764-764/? E/LocationManagerService: Unable to bind FLP Geofence proxy.
Click to expand...
Click to collapse
why not?
Have you checked in CPU-Z if there is information coming from the sensors? I have no idea what's going on with the HAL though... Maybe the sensors.so is related to the HAL, so one won't work without the other...
Sent via Carrier Pigeon
Riccorbypro said:
Have you checked in CPU-Z if there is information coming from the sensors? I have no idea what's going on with the HAL though... Maybe the sensors.so is related to the HAL, so one won't work without the other...
Sent via Carrier Pigeon
Click to expand...
Click to collapse
i think that file name "jni" relate to HAL
Sony device have not camera hal
but jni file is replace that....
maybe sensor also?
Will CM12.1 remove the camera noise/blur?
sorry
AutumQueen92 said:
Will CM12.1 remove the camera noise/blur?
Click to expand...
Click to collapse
i don't know that
but we can't have camera sensor source
so maybe equal stock rom
wwwhana said:
i don't know that
but we can't have camera sensor source
so maybe equal stock rom
Click to expand...
Click to collapse
Well that's disappointing. I was hoping to find a mod for the camera but nothing came up, only Bravia Engine stuffs.
collect sensor log from stock
under link is log from stock rom about sensors
https://gist.github.com/wwwhana/983cae21f13b4e5ed29f
QTI waring/Error is also stock rom....
camera also sam error and warnig my rom
but other sensors?
we know light sensor name is apds9930_als.....
Input path = /sys/devices/virtual/thermal/thermal_zone[0~5]/temp
Ah! i tested near sensor working when call
but others not working....
sensor made me hard....
dual sim kernel maybe not equal single sim
Riccorbypro said:
From what I've seen, the kernel for D2533 and D2502/D2503 is the same, there is no difference in the tree. So theoretically there should be one universal build, for both single sim and dual sim.
Sent via Carrier Pigeon
Click to expand...
Click to collapse
i see about board-sony_tianchi.c and board-sony_tianchi_dsds.c
so i see that difference gpio.....
maybe also difference C3
who try made gpio map for dual sim?
wwwhana said:
i see about board-sony_tianchi.c and board-sony_tianchi_dsds.c
so i see that difference gpio.....
maybe also difference C3
who try made gpio map for dual sim?
Click to expand...
Click to collapse
No one that I know of... I'm the only person that I know that has this phone, and my carrier never sold the dual-sim version anyway, so i think we're going to have to try our best and get a tester for the dual-sim kernel.
Also, any idea why the f2fs compile is failing?
The error:
Code:
system/extras/f2fs_utils/f2fs_utils.c:53:13: error: 'struct f2fs_configuration' has no member named 'kd'
make Error 1
Riccorbypro said:
No one that I know of... I'm the only person that I know that has this phone, and my carrier never sold the dual-sim version anyway, so i think we're going to have to try our best and get a tester for the dual-sim kernel.
Also, any idea why the f2fs compile is failing?
The error:
Code:
system/extras/f2fs_utils/f2fs_utils.c:53:13: error: 'struct f2fs_configuration' has no member named 'kd'
make Error 1
Click to expand...
Click to collapse
.....?
I never get error like that....
if try "rm system/extras/f2fs_utils " and retry repo sync
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First of all, I am from China, my English is poor.
Camera solution:
1.Revert the commit about offset in MemoryHeapBase, make MemoryHeapPmem binary compatible.(commit: f24c4cd0f204068a17f61f1c195ccf140c6c1d67)
2.Add Overlay stub to libui, make libcamera.so symbol compatible
3.Implement a adapter CameraHardwareInterface.h to camera.h
sample implement, this a snapshot of local git repo
all source based on aosp ics-mr1 branch
libcamera.so liboemcamera.so libmmipl.so libmmjpeg.so from 2.36.405.8
I code patch and hal last weekend, but I do not have time to do it better, but it can work.
my git repo github.com/zbwu, but don't include libcamera now.
enjoy~
hello everyone
Now is office hour
I will post the source and detail tonight(GMT +8:00)
Could this work on other devices also? Like the desire s or z?
Sent from my HTC Vision using XDA App
johrie said:
Could this work on other devices also? Like the desire s or z?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
You can found several libcamera wrapper, for example TwistedUmbrella is working on it, but this problems are HTC specific. I think it can be used in most of HTC devices.
Here's some examples:
E/HAL ( 1207): Cannot load library: link_image[2048]: 1207 could not load needed library 'libcamera.so' for 'camera.default.so' (reloc_library[1384]: 1207 cannot locate '_ZN8SkMatrix10setRotateZEf'...
It's the first test, you can easily pass it with some smart google search
Here's my step:
E/HAL ( 1203): Cannot load library: link_image[1965]: 1203 could not load needed library 'libcamera.so' for 'camera.default.so' (reloc_library[1314]: 1203 cannot locate '_ZN7android7Overlay5setFdEi'...
Here am I, I tried to make a wrapper to overlay::Overlay::* to android::Overlay::*
But i'll w8 for source... It will be faster
frits666 said:
Something like Ndiswrapper used on some Linux distro's???
Click to expand...
Click to collapse
Like gpsshim (https://github.com/CyanogenMod/android_hardware_gpsshim)
I have posted more photos and source
I scale photos in gimp, not edit
zbwu86 said:
I scale photos in gimp, not edit
Click to expand...
Click to collapse
You alone have cured the threads of CQP (Camera questioning plague).
And for that, I commend you.
Someone give this man an OBE.
Regards
Please stop writing Chinese. Thank you!
Errrrrr I just had a quick glimpse of his github, this guy knows what he's doing and is pretty far ahead, everyones better off pulling his git compiling the whole thing and providing it as a rom, reason? youll most likely have wifi teathering aswell, I havent look at everything, but @OP well done!
It's promising, but it's not working me on CM9-KANG, i think, because of overlay (dummy) implementation... Or, I just need a full recompile... Dunno... Tomorrow, i'll try to implement liboverlay, maybe it's working... Anyway, it's a good start...
THANKS!
dh.harald said:
It's promising, but it's not working me on CM9-KANG, i think, because of overlay (dummy) implementation... Or, I just need a full recompile... Dunno... Tomorrow, i'll try to implement liboverlay, maybe it's working... Anyway, it's a good start...
THANKS!
Click to expand...
Click to collapse
You need to pull the whole source code off him
dh.harald said:
It's promising, but it's not working me on CM9-KANG, i think, because of overlay (dummy) implementation... Or, I just need a full recompile... Dunno... Tomorrow, i'll try to implement liboverlay, maybe it's working... Anyway, it's a good start...
THANKS!
Click to expand...
Click to collapse
in english
don't depend liboverlay.so
the overlay in the Overlay.patch.txt, patch it to framework/base
need full recompile,
in chinese
不依赖liboverlay.so
overlay 在 Overlay.patch.txt里面，在framework/base里使用这个补丁
需要重新编译所有东西
shaky156 said:
You need to pull the whole source code off him
Click to expand...
Click to collapse
Are you set up to do it?
wildchild048 said:
Are you set up to do it?
Click to expand...
Click to collapse
I would if I had a quad core or something that can compile fast, 2 core pc wont do it, I'm sure LC is already pulling from his git or something he has an i7
EDIT: just realized he doesnt have the whole thing up, only kernel/hal lol
zbwu86 said:
in english
don't depend liboverlay.so
the overlay in the Overlay.patch.txt, patch it to framework/base
need full recompile,
in chinese
不依赖liboverlay.so
overlay 在 Overlay.patch.txt里面，在framework/base里使用这个补丁
需要重新编译所有东西
Click to expand...
Click to collapse
I've recompiled libbinder and libui.so but not worked... full recompile is started, i'll see tomorrow... If it's not working, i'll try liboverlay
well my build won't load camera HAL, it saiy that it can't connect to libcamera.so
where can I find libs from htc sense rom base 2.36.405.8??
LorD ClockaN said:
well my build won't load camera HAL, it saiy that it can't connect to libcamera.so
where can I find libs from htc sense rom base 2.36.405.8??
Click to expand...
Click to collapse
I found this, http://forum.xda-developers.com/showthread.php?t=1042986 , but not sure if its the exact same thing hes talking about or not...But says Based on RUU Ace Gingerbread S 2.36.405.8 ...so probably could pull libs from it?
Yelp... !
I am not entirely familiar with the process to get the Camera working. Ca someone please help ?!
apocalypse.v said:
I am not entirely familiar with the process to get the Camera working. Ca someone please help ?!
Click to expand...
Click to collapse
You will have to wait till someone puts out a working rom with it.., this is for getting it to work building from source
Installation (unlocked boot loader required):
If you don't have stock JB installed (11.3.A.2.1), you need to flash that first because this ROM only works with the baseband firmware that gets flashed with the stock JB ROM. GSM will be unavailable if you're coming from ICS.
Flash a recovery if you don't have one, e.g. CWM, or the boot.img (TWRP) included in the ROM's .zip.
Boot to recovery and...
Wipe data+caches
Install the ROM .zip
Optionally install GApps
Backup instructions not included because you should be smart enough to do that yourself.
Current releases:
Xperia E single
Xperia E dual
Other files, including incremental updates from previous releases
Multi-SIM operation:
Enable/disable SIM cards in Settings / Multi-SIM.
Only one SIM card can have 3G enabled, but it's not toggled automatically. To enable 3G on one SIM you have to make sure the other one is set to 2G-only mode first.
Some of the dual-SIM features in Sony's ROM, such as auto-toggling SIM cards based on time, different ringtones, or data usage tracking aren't included.
SMS are currently always sent from whatever subscription is set as the SMS send subscription. This includes sending an SMS reply from the "incoming call" screen or the "missed call" notification.
Note that battery life is shorter when two SIM cards are enabled. The reason for this is that the modem has to keep switching between two networks to remain registered and be able to receive network events, causing higher power consumption, higher latency, and lower throughput. This also causes the data connection to become slower when two SIMs are enabled. This isn't something that can be "fixed" because it's not software-related. Having only one SIM card enabled will improve battery life and data connection speed.
Kernel:
The inluded kernel is based on Sony's sources, so no additional governors, schedulers, etc.
Sources on GitHub.
USB mass storage mode:
I have enabled the USB mass storage driver to support mounting two storage devices simultaneously, so you can share both the "internal" and "external" SD cards as UMS.
Recovery will always mount both storage devices, but the Android GUI for USB mass storage will share the external SD card only, because the internal SD card is intended to remain available to the OS. However, you can manually mount the internal SD card from the shell:
Unmount storage from the OS:
Code:
vdc volume unmount sdcard
To unmount forcibly:
Code:
vdc volume unmount sdcard force
Share to USB:
Code:
vdc volume share sdcard ums
To disconnect from USB and re-mount storage to the OS:
Code:
vdc volume unshare sdcard ums
vdc volume mount sdcard
Known issues:
Video recording doesn't work
Video playback uses software decoders, not hardware
Magnetometer doesn't seem to be working
USB mass storage speed is slow
FM radio not included (hardware and driver work, and tuning works as well, but it's going to require quite a few changes to the audio subsystem to actually get sound out of it)
Turning off screen in recovery doesn't work (screen timeout disabled by default)
Inserting an unmountable SD card (unformatted, or unknown file system) will trigger a notification offering to format it. However, doing so will format the internal SD card
A data connection disabled due to roaming might not re-enable when switching back to the home network (Workaround: toggle airplane mode on/off)
Enabling ADB over network disables charger/USB detection
What I haven't tested:
Emergency calls. I assume these will work because generic telephony works, but especially in the cases of the phone not registered on a network, or calling without a SIM or a PIN-locked SIM, I really can't say (and I don't plan on calling up emergency services just for testing purposes). If anyone tests this, please post your results.
Third-party telephony/messaging apps (Dialers, SMS, etc.). Those might only work with whatever SIM is set as the default.
Bluetooth headset
MMS
RUIM card operation
CM's SMS limiter (Settings / Security)
All of my sources are on GitHub, and should be used with a manifest file to download the code base.
Credits:
CM devs for CM10, FXP for device bringup, TeamWin for TWRP, Code Aurora for the multi-SIM implementation.
That's great!
I'll try it out as soon as i get my larger SD card and backup all Internal Storage Data lost by Bootloader Unlock!
---------- Post added at 10:24 PM ---------- Previous post was at 10:16 PM ----------
jjm34 said:
All of my sources are on GitHub, and should be used with a manifest file to download the code base.
Click to expand...
Click to collapse
Regarding the Source Look, its looks like you have cherry-picked the code from certain revisions, so any new feature releases made by CM/FXP would not be available to compile right?
Was that intentionally done as only certain revisions might compile, or was it an over-sight?
Thanks
hsr
The projects I have modified are branched off either CM's or Code Aurora's. The manifest just points to the specific commits on all the projects that make up my release, so it can be used with repo to set up a code base with all the projects on the same revision at the time of release. What I'm doing to incorporate changes from CM is to add CM's branches as a remote, and then pull in the changes.
Edit: Since some of the projects are massively different from CM (frameworks/base), or not based on CM at all (packages/apps/Phone), these sources don't build as part of a "regular" CM10 tree.
Finally...!!!
download it right away...
will test this on XE SS then report.... great job mate... :good:
thanks button smashed!!!
jjm34 i dont have xperia e but if it works you did excellent job
Sent from my Xperia Tipo using Tapatalk 4 Beta
Tested on C1505
everything that doesn't work on FXP CM10, solved in here...
following on what you mentioned above, Networking is like a charms on my XE SS...
just found MTP doesn't work (only UMS), and hey... where's the camera app? :cyclops:
will report you another bugs when i have some free times
great job... you're hero for now... keep it up :good:
ps: where's your donate to me button???
@jjm34 this work is fantastic. Think you can drop me a pm?
Sent from my Nexus 7 using Tapatalk HD
yayakuya said:
just found MTP doesn't work (only UMS), and hey... where's the camera app? :cyclops:
Click to expand...
Click to collapse
On my E dual MTP is working, and the camera works for photos as well, so there may be incompatibilities with the device or with the kernel (which is based on the E dual's kernel sources). A logcat of the boot process and when trying to enable MTP may help. Do these things work on FXP's release?
yayakuya said:
where's your donate to me button???
Click to expand...
Click to collapse
Uh... haven't really considered one because I haven't had any public releases till now (and I'm not one to beg for thanks and/or donations either)
This notice is very nice!!
Not working on C1604!
@jjm34
Unfortunately basebands for 1604 and 1605 do not match i guess, 1605 is dual band whereas 1604 is quad band.
Hence not working for me now, i tried switching ril libs also. I guess best would be to recompile the compile from source with proprietary files from 1604.
Thanks
hsr
Just deodexed this awesome work today... (doesn't fit with my taste as Modder )
MTP now working like a charms, SDCard speed running as hell (seems like using stock or yours CWM 4 stock kernel)...
didn't know how's it's changed, coz after fresh installed this odexed, SDCard like snail
just made some lil Mods for this....
btw, dude... may i release your Deodexed CM10 my self? or you have a plan for it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next: Running MIUIV5 from this base... :fingers-crossed:
Thanks for your hard work bud...
yayakuya said:
Just deodexed this awesome work today... (doesn't fit with my taste as Modder )
MTP now working like a charms, SDCard speed running as hell (seems like using stock or yours CWM 4 stock kernel)...
didn't know how's it's changed, coz after fresh installed this odexed, SDCard like snail
just made some lil Mods for this....
btw, dude... may i release your Deodexed CM10 my self? or you have a plan for it?
Next: Running MIUIV5 from this base... :fingers-crossed:
Thanks for your hard work bud...
Click to expand...
Click to collapse
can u pls upload the deodexed version??
thnx!!
Help!
Can anyone confirm if this works on 1604/1504. Indian Baseband/Quad Baseband as its not working for me, want to know if its something i did wrong or something with firmware.
Thanks
micromaxa60 said:
can u pls upload the deodexed version??
thnx!!
Click to expand...
Click to collapse
i need confirmed by jjm34 first... just waiting for him...
hsr0 said:
Can anyone confirm if this works on 1604/1504. Indian Baseband/Quad Baseband as its not working for me, want to know if its something i did wrong or something with firmware.
Thanks
Click to expand...
Click to collapse
maybe you have to flash C1605 before using this...
or maybe you just edit build.prop comments as what I've done for my C1505
ps: forgot to tell, USB tethering working fine but not for wi-Fi tether...
we need Wi-Fi tether also...
thanks
Nice Work!
I have a C1604
Flashed with a C1605 ICS, Then again flashed with a C1605 JB... Working all OKAY till date
Still using it.
would be nice if Pulse mood light and video recording is available.. and if it uses Hardware buffering for playback
Basically flashed this to get relieve from that Less RAM problem!
hsr0 said:
Unfortunately basebands for 1604 and 1605 do not match i guess, 1605 is dual band whereas 1604 is quad band.
Hence not working for me now, i tried switching ril libs also. I guess best would be to recompile the compile from source with proprietary files from 1604.
Click to expand...
Click to collapse
Unfortunately that's not something I can check myself. What's important though is that stock JB ROM was installed before flashing CM10, because otherwise it won't work with the baseband at all.
This is the list of included proprietary files, if you want to try replacements; in my release these are from the C1605 JB ROM (11.3.A.2.1).
yayakuya said:
may i release your Deodexed CM10 my self? or you have a plan for it?
Click to expand...
Click to collapse
I guess that's fine. It won't work for updating, but if I released a non-odexed version myself any customizations would probably have to be re-done as well, so updating wouldn't be a simple flash either.
yayakuya said:
USB tethering working fine but not for wi-Fi tether...
we need Wi-Fi tether also...
Click to expand...
Click to collapse
Crap, looks like I've missed that, because I already had it working at one point. I'll include the fix in an update. Meanwhile, if you're modding framework-res.apk, this should be the fix to include in res/values/config.xml.
jjm34 said:
Unfortunately that's not something I can check myself. What's important though is that stock JB ROM was installed before flashing CM10, because otherwise it won't work with the baseband at all.
This is the list of included proprietary files, if you want to try replacements; in my release these are from the C1605 JB ROM (11.3.A.2.1).
I guess that's fine. It won't work for updating, but if I released a non-odexed version myself any customizations would probably have to be re-done as well, so updating wouldn't be a simple flash either.
Crap, looks like I've missed that, because I already had it working at one point. I'll include the fix in an update. Meanwhile, if you're modding framework-res.apk, this should be the fix to include in res/values/config.xml.
Click to expand...
Click to collapse
Thanks a lot... it's working!!! :victory: actually i'm using Wi-Fi tethering right now...
i'm sorry for more my curriously question;
> This is the only one CM's ROM that haven't a SAME as another devices? you can see it very different frameworks files.. coz when i ported another ROMs based on CM10 (e.g MIUIV5, PACman and PA) from LG Optimus one, Optimus L5 and MIRO, it's just the same bug i found... No RIL....
> Did you know which one (RIL files in framework.jar) that should be replaced from your CM10? i'd decompiled both framework.jar then i found many files are differents... such as no SemcRIL, Samsung RIL, or another that i found in another CM10's framework.jar....
i assume you just compiled from different sources.... (have no experiences about Linux coz i've never use that OS/ need AutoCAD on Windoz)
> Any hope that you will help for my problem? XE users need more ROMs though...
oh, trying to replaced framework-res.apk from FXP one, it's not working... so, i'm very sure it's different source
anyway, thanks again for your hard work... really appreciated it... and :highfive:
I've had to replace the entire frameworks/base/telephony with Code Aurora's sources, and then adapt the rest to make work with it. Merging the changes into CM and still be compatible with CM's source tree would not be worth it, considering the immense amount of effort it would take (and it still wouldn't work with any bytecode/smali patches).
Pretty much everything internal telephony-related in this ROM works Code Aurora's way, e.g. no multiple device-specific RIL implementations. This will break many bytecode/smali patches that are written for CM, but other than integrating the changes and building from source or modifying the smali patches there's not really any other option. There are a lot of differences in the framework though, and it's probably not worth the effort.
When there's an FXP release this will be different because it'll use CM's implementation, and it'll work for single-SIM, but CM10's official source tree will never see dual-SIM support.
I have tried everything.
Interestingly C1605 ftf firmwares have a working RIL.
Is it possible that a different frequency from c1605(turkish) is being used by code aurora and hence im not being able to get connectivity no matter what i try.
" Just wanna share some info "
video recording will work if we use 3party app called " video cam illusion "..i try it myself using VCI pro version ..try with other cam app only get fc and hot reboot..
@ To OP
u really awesome..keep up the good work ... :thumbup:
Sent from my Xperia E dual using Xparent Cyan Tapatalk 2
[DESIRE HD NOKIA X PORT]
I've decided to open a new thread, especially since the previous thread is discontinued. I wanted to highlight progress is very much being made on the Nokia X port for the Desire HD.
When I mention progress, the build boots now; As I've re-based, re-structured and circumvented the issue's preventing a boot.
That's not to say this ROM is functional as a daily driver in it's current status, as it is quite the opposite.
However great strides are being made and success comes with the cost of time, effort and dedication from our developers.
This thread is open now as an invitation to ANY developer that:
1) is interested in this project
2) capable of pushing the project forward in effort to solve existing bugs
3) willing to spare their time to aid development.
As it stands I've done all the leg work getting the build to boot, and only since then I've had some assistance from a couple of sources in solving a few other issues in build.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Developer Activity Status:
At the moment I'm getting some priceless help in patching MSimTelephony references in build from another XDA Dev here, doing wonderful work and I anticipate that we can in fact succeed in a functional port in the near future.
Thus far our current efforts are focused on fixing radio, data and ril so bare with our current working/non-working log below...
(as a result of the above SystemUI is now beginning to respond as should, albeit a few flaws which are actively being ironed out)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Updates:
07/04/14 - [SYSTEMUI] System Statusbar and MSimTelephony references patched @SystemUI/classes.dex [Developer: opssemnik]
07/04/14 - [LIBRARY] Proximity and capacitive Light Sensors are now working [Developer: s89]
08/04/13 - [UPDATE] Investigating possibility of a System Wrapper to patch boolean isMultiSimEnabled @TelephoneManager and other related MsimTelephony calls globally. Eclipse app wrapper begun...
08/04/13 - [STUCTURE] Re-established 4.1.2 kernel, modules, hw and libraries to establish a common base and satisfy kernel requisites. [Developer: s89]
10/04/13 - [UPDATE] Wrapper implemented in build now and loading. Let the MSimTelephony patches commence [Developer: opssemnik]
12/04/13 - [SYSTEM] WIFI Fixed - Correct mismatched blobs and re-worked boot.img to fix Wifi and module loading issues. [Developer: s89]
12/04/13 - [SYSTEM] USB Mount Fixed - Patched storage-list.xml [Developer: opssemnik]
12/04/13 - [UPDATE] GPS Fixed
Click to expand...
Click to collapse
.............: Working :.............
USB Storage
Wifi
GPS
Vibrate
Touchscreen
Hardware|Capacitive Buttons
Display
Battery Sensor
Hardware Acceleration
Light Sensors
..........: Not working :..........
USB Storage
Sound
Camera
Radio
GPS
Wifi
Bluetooth
Light Sensor
.................Probably more
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please note: This ROM and Thread is intended for Developer activity only. Please do not fill this thread with spam, jargon and/or testing requests. This includes update requests (FYI All progress will be documented regularly within this post).
I am aware of most if not all of the currently not working and am actively resolving what I can, when I can.
All I ask is for is your patience and support > Public testing will be announced when most if not all the major show stopping bugs have been resolved.
Click to expand...
Click to collapse
If you are interested in joining efforts in minimizing our "Not working" list, feel free to contact me or write a request of interest here.
All and any updates to our current build that address an issue in our bug's list must be communicated back and consolidated into our output build to ensure all developers are up-to-date with the latest changes/bug fixes.
Current Team | Contributing Developers::
stickman89 [s89;] - Porting NokiaX build inc, fixing libraries, patching framework & ramdisk updates.
opssemnik - SystemUI, MSimTelephony Patches & continued wrapper development
Click to expand...
Click to collapse
Reserved...
good job,thanks
wow.......nice work devz
chrisb906 said:
I know this..just letting dev know
Sent from my Desire HD using Tapatalk
---------- Post added at 05:18 AM ---------- Previous post was at 05:15 AM ----------
Oops. Just realized he didn't want test requests on here..lol. My bad
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Yup, this is a DEV thread. Still lots too fix i.e. would like a dev collaboration since I've spent a lot of hours getting us to this point and feel it would be less stressful on me having some more capable hands in the kitchen.
OK NokiaX isn't dependent on ION so I rebuilt with correct kernel, modules, hw and added libraries from our 4.1.2 build however audio is NOT getting loaded for some reason. As far as I'm aware __strlen_chk is referenced at libc.so and libcrypto.so however I've replaced these libraries with that from a functional 4.1.2 build of ours and it's still not loading. Any devs here encountered this? If so which libraries are associated with it?
Code:
E/HAL ( 1424): load: module=/system/lib/hw/audio_policy.default.so
E/HAL ( 1424): Cannot load library: reloc_library[1331]: 1424 cannot locate '__strlen_chk'...
I think we have the same problem with sense 5 too
Gesendet von meinem One X mit Tapatalk
besimm said:
I'm interested on this ROM, can you give me the link??
Click to expand...
Click to collapse
All I ask is for is your patience and support > Public testing will be announced when most if not all the major show stopping bugs have been resolved.
Click to expand...
Click to collapse
No he can't , please be patient , the OP has his own closed testers group and he will release a public test rom when ready.
SO be patient !!!!
EDIT: THREAD CLEANED, STOP ASKING FOR LINKS !!!
THE DEV WILL RELEASE WHEN READY.
Stickman89 said:
OK NokiaX isn't dependent on ION so I rebuilt with correct kernel, modules, hw and added libraries from our 4.1.2 build however audio is NOT getting loaded for some reason. As far as I'm aware __strlen_chk is referenced at libc.so and libcrypto.so however I've replaced these libraries with that from a functional 4.1.2 build of ours and it's still not loading. Any devs here encountered this? If so which libraries are associated with it?
Code:
E/HAL ( 1424): load: module=/system/lib/hw/audio_policy.default.so
E/HAL ( 1424): Cannot load library: reloc_library[1331]: 1424 cannot locate '__strlen_chk'...
Click to expand...
Click to collapse
Did you try with "readelf" ? Maybe you can compare after with what you have and what is missing.
Wrapper implemented in build now and loading. Let the MSimTelephony patches commence. Lots of good stuff happening
RIL work's at this moment (SMS, Calls, USSD, 3G) ?
RazGame said:
RIL work's at this moment (SMS, Calls, USSD, 3G) ?
Click to expand...
Click to collapse
Not just yet, but we haven't finished tracing, debugging and adding Telephony calls to our wrapper. By all mean's not a quick process and ended up being a late night, I'm still wearing my sleepy face aha.
Telephony isn't registering a network as we've intentionally left methods out for the time being as there is more patching to do to SystemUI in regards to directing our new calls. More to continue tonight I imagine so all on your list is a nono for the time being.
If you can give me the files of the ROM I an take a shot in fixing the Storage issue as I am experienced in porting and specifically fixing this bug Have a nice day bro.
CedArctic said:
If you can give me the files of the ROM I an take a shot in fixing the Storage issue as I am experienced in porting and specifically fixing this bug Have a nice day bro.
Click to expand...
Click to collapse
Excellent, be more then welcome to have you aboard. We have a new SystemUI patch to update in build at some point tonight, once that's applied, I'll upload the updated build for your handy work good sir. You'll receive a PM once uploaded.
dont tell anyone you saw this, shhh
usb fixed
wifi fixed
plot twist:
gps fixed
Stickman89 said:
OK NokiaX isn't dependent on ION so I rebuilt with correct kernel, modules, hw and added libraries from our 4.1.2 build however audio is NOT getting loaded for some reason. As far as I'm aware __strlen_chk is referenced at libc.so and libcrypto.so however I've replaced these libraries with that from a functional 4.1.2 build of ours and it's still not loading. Any devs here encountered this? If so which libraries are associated with it?
Code:
E/HAL ( 1424): load: module=/system/lib/hw/audio_policy.default.so
E/HAL ( 1424): Cannot load library: reloc_library[1331]: 1424 cannot locate '__strlen_chk'...
Click to expand...
Click to collapse
Just an update, we already fixed this, just need some smali patching and then audio should work.
any processing?
we are waiting for it
opssemnik said:
Just an update, we already fixed this, just need some smali patching and then audio should work.
Click to expand...
Click to collapse
where is the updating?
if the sound IS ok,upload it plz,thx in advance.
admet615 said:
we are waiting for it
Click to expand...
Click to collapse
Update & Download Link
hi, its been months now, pls whats the progress? we are patiently waiting for an update and download link.
I know the issue has been the sound, how far has it gone. pls keep us updated.
This post is closed. All developers had been informed and I think this thread is not explained as it must be (is not a thing of aquas only). Just two different sensors in each device...
https://github.com/sonyxperiadev/kernel/issues/353
However it's not something exclusive from Aqua, but also for some other models like D2303 in the 'new period' as you can see here: http://forum.xda-developers.com/showpost.php?p=60797370&postcount=192
I thought the normal m2 was the same, it must be a model revision due to the Accelerometer bug that has been affecting certain production runs. Gonna find out when mine was made had it since beginning of Sept last year not had this bug yet
D2303 stock deodexed 4.4.4 KK rooted philz touch recovery xposed Bravia engine 2 x-reality
Nice one @linuxct!
Development wise, for custom ROMs here, not much, but atleast 3.4 Omni, you could find one with old accelerometer, and one with the new accelerometer. See what firmware version they run out of the box.
After that, download matching kernel archive from Sony's website, and check difference in accelerometer driver.
galaxyfreak said:
Nice one @linuxct!
Development wise, for custom ROMs here, not much, but atleast 3.4 Omni, you could find one with old accelerometer, and one with the new accelerometer. See what firmware version they run out of the box.
After that, download matching kernel archive from Sony's website, and check difference in accelerometer driver.
Click to expand...
Click to collapse
Sounds interesting!
I'd like to do it. But unfortunatetly, I dont' know too much of ROMS, and I don't know exactly for compare the accelerometer drivers and do it compatible with custom roms
galaxyfreak said:
Nice one @linuxct!
Development wise, for custom ROMs here, not much, but atleast 3.4 Omni, you could find one with old accelerometer, and one with the new accelerometer. See what firmware version they run out of the box.
After that, download matching kernel archive from Sony's website, and check difference in accelerometer driver.
Click to expand...
Click to collapse
I've tried to do it. But I don't find any accelerometer driver in Sony's archive (?)
Also, exams are very close... Might try again after finishing
linuxct said:
I've tried to do it. But I don't find any accelerometer driver in Sony's archive (?)
Click to expand...
Click to collapse
drivers/input/misc/kionix_accel.c
galaxyfreak said:
drivers/input/misc/kionix_accel.c
Click to expand...
Click to collapse
Oh thanks, I was actually looking for an 'accel' folder :silly:. As I said I will try after exams
@linuxct Now when panel on new models and Aqua is solved, before I pull the trigger (add Aqua models to OTA assert, so you can flash the zip), I wanted to look into this.
I don't seem to have accelerometer (kxtj2) on any input. And I'm sure it's working.
How am I supposed to debug this
getevent:
[email protected]:/ # getevent
getevent
add device 1: /dev/input/event7
name: "msm8226-tapan9302-snd-card Headset Jack"
add device 2: /dev/input/event6
name: "msm8226-tapan9302-snd-card Button Jack"
add device 3: /dev/input/event0
name: "cyttsp4_mt"
add device 4: /dev/input/event3
name: "qpnp_pon"
add device 5: /dev/input/event2
name: "proximity"
add device 6: /dev/input/event1
name: "lightsensor-level"
could not get driver version for /dev/input/mice, Not a typewriter
add device 7: /dev/input/event5
name: "gpio-keys"
add device 8: /dev/input/event4
name: "qpnp_chg_unplug_key"
[email protected]:/ # getevent -li /dev/input/event6
getevent -li /dev/input/event6
add device 1: /dev/input/event6
bus: 0000
vendor 0000
product 0000
version 0000
name: "msm8226-tapan9302-snd-card Button Jack"
location: "ALSA"
id: ""
version: 1.0.1
events:
KEY (0001): KEY_MEDIA BTN_1 BTN_2 BTN_3
BTN_4 BTN_5 BTN_6 BTN_7
input props:
<none>
[email protected]:/ # getevent -li /dev/input/event7
getevent -li /dev/input/event7
add device 1: /dev/input/event7
bus: 0000
vendor 0000
product 0000
version 0000
name: "msm8226-tapan9302-snd-card Headset Jack"
location: "ALSA"
id: ""
version: 1.0.1
events:
SW (0005): SW_HEADPHONE_INSERT SW_MICROPHONE_INSERT SW_LINEOUT_INSERT 000e
000f 0010 0011
input props:
<none>
[email protected]:/ #
Click to expand...
Click to collapse
galaxyfreak said:
@linuxct Now when panel on new models and Aqua is solved, before I pull the trigger (add Aqua models to OTA assert, so you can flash the zip), I wanted to look into this.
I don't seem to have accelerometer (kxtj2) on any input. And I'm sure it's working.
How am I supposed to debug this
getevent:
Click to expand...
Click to collapse
Oh, wow. And also you have the gpio-keys placed in event5, it's the first time I see this.
However I must say, the person who had the event7 problem is @iFlashed, not me, as I have old D2303, with event6. I only helped him to discover what was wrong.
Now, if the accel is not placed in any event, then how is it working? Other way of input ??
I'm checking in my device and there's not kxtj2 nor accel... event3 throwed an out-of-memory error btw.
Tell us what to try/do and we'll try.
stock 3.4 and 3.10 have very different sensor implementation.
How did you relate bootloops on Omni and CM12 with sensors.
linuxct said:
Oh, wow. And also you have the gpio-keys placed in event5, it's the first time I see this.
However I must say, the person who had the event7 problem is @iFlashed, not me, as I have old D2303, with event6. I only helped him to discover what was wrong.
Click to expand...
Click to collapse
Information for shifted gpio-keys is known by more than two months.
source
AleksJ said:
Information for shifted gpio-keys is known by more than two months.
source
Click to expand...
Click to collapse
They found before... LOL
That's the problem of local forums, people have to discover things twice if they don't publish it in global-english forums like this one.
However, we still don't know why Sony did this... I can't understand them.
linuxct said:
They found before... LOL
That's the problem of local forums, people have to discover things twice if they don't publish it in global-english forums like this one.
However, we still don't know why Sony did this... I can't understand them.
Click to expand...
Click to collapse
Yes, and that was the reason for the changes, and why they were made hardly anyone here can say with certainty.
What does it matter forum or palace if problem still exist ?
btw, they already published here
AleksJ said:
Yes, and that was the reason for the changes, and why they were made hardly anyone here can say with certainty.
What does it matter forum or palace if problem still exist ?
btw, they already published here
Click to expand...
Click to collapse
What he published didn't work tho, as iFlashed device uses event7 and inside!out give him a boot.img with event4 in bootrec-device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If sony could give us any explanation on why they did this...
messing with sensors in 3.10 will not work. It will probably lead to more bootlooping.
Could you try this workaround? it is sony's stock solution for inputdevices.
https://github.com/android-legacy/a...mmit/491bb77288a5941eba7bdd14fbf5d28470971f0b
you will have to implement it in 3.10 kernel. If you cannot succeed pm or gtalk me, I will do
keep in mind it is a workaround. If this works out, well, with my truly panel fresh in mind, we have to check for a proper solution to get it in sxd kernel.
linuxct said:
If sony could give us any explanation on why they did this...
Click to expand...
Click to collapse
It is probably a hardware mounting things. A lot of electronics have to be mounted in a small device.
If hardwaremounting changes because of using another part for whatever reason (innoluxpanel is mounted up-down, truly is not), that has consequences for programming hardware in kernel. (innolux is flipped up-down in paneldriver, truly is not in de same driver).
Using different hardwareparts for same model is quite common in phones.
It kind of surprises me that no users haven't complained about a sensor not working. In the kernel there is another sensordriver present (bma250 if I remember correctly) which is compiled for eagle, but not fixed yet. Apperently there is still no user who has this particular hardware part in his phone and we (untill now) all share the same sensor hardware so it functions for everyone
erikcas said:
messing with sensors in 3.10 will not work. It will probably lead to more bootlooping.
Could you try this workaround? it is sony's stock solution for inputdevices.
https://github.com/android-legacy/a...mmit/491bb77288a5941eba7bdd14fbf5d28470971f0b
you will have to implement it in 3.10 kernel. If you cannot succeed pm or gtalk me, I will do
keep in mind it is a workaround. If this works out, well, with my truly panel fresh in mind, we have to check for a proper solution to get it in sxd kernel.
Click to expand...
Click to collapse
Nice. I just contacted you through Hangouts.
Thanks!
linuxct said:
What he published didn't work tho, as iFlashed device uses event7 and inside!out give him a boot.img with event4 in bootrec-device
If sony could give us any explanation on why they did this...
Click to expand...
Click to collapse
Means nothing, bootrec-device is no longer used with new recovery.
galaxyfreak said:
Means nothing, bootrec-device is no longer used with new recovery.
Click to expand...
Click to collapse
Yeah, true, but I was just showing what was the problem with prebundled recoveries in boot.img...
Hi
I tried to port Lollipop to our thl 4000 using this tutorial http://www.mtkroms.com/2015/08/install-real-lollipop-on-all-mtk.html with resurrection remix rom
It works almost all
Bugs so far:
-Camera (Only rear, and no video record)
-2g works, 3g no service. (Only SIM1 data)
-Radio FM not sound
I dont renember any other, Wifi, Bluetooth, Games, Audioetc works
For install it, first download this rom http://www.mtkroms.com/2015/07/resurrection-remix-lollipop-rom-for-mt6582.html
Then download my patch (v4b 26/08/2015) https://drive.google.com/open?id=0B6ydSl9VOrADNDhnZi1rQmFvWU0
Go to recovery. Make wipes. Install rom, and then install my patch
A bit tweaked and deleted things for be faster
Images
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA:DevDB Information
Lollipop THL 4000, ROM for all devices (see above for details)
Contributors
kprkpr
Source Code: http://www.mtkroms.com/2015/08/install-real-lollipop-on-all-mtk.html
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2015-08-20
Last Updated 2015-08-26
Will be glad if you can update your ROM link or upload to Dropbox.Thanks for doing your best.
koylaaa said:
Will be glad if you can update your ROM link or upload to Dropbox.Thanks for doing your best.
Click to expand...
Click to collapse
I made it easier to install, and uploaded to another site, see now
If you have any ideas to fix this bugs, tell me please
Sorry my friend, I have no idea in bugs fixing.
I tested your lollipop ROM and I can confirm this is the best lollipop ROM for our THL 4000.
3G Works fine on both voice and data.
Camera can't connect at all as you mentioned already.
USSD codes not working(Dialer).
Can't show Contacts on SIM.
Only SIM1 can connect to Data as you mentioned.
Network Data connection Goes off anytime.
Network signal goes off when one is busy.
FM force stop.
Developers option force stop after disabling it.
Engineering Mode force stop.
Can't set Ringer tone for SIM2.
Your ROM is nice,I hope developers will look into this topic and help us solve these bugs.
koylaaa said:
Sorry my friend, I have no idea in bugs fixing.
I tested your lollipop ROM and I can confirm this is the best lollipop ROM for our THL 4000.
3G Works fine on both voice and data.
Camera can't connect at all as you mentioned already.
USSD codes not working(Dialer).
Can't show Contacts on SIM.
Only SIM1 can connect to Data as you mentioned.
Network Data connection Goes off anytime.
Network signal goes off when one is busy.
FM force stop.
Developers option force stop after disabling it.
Engineering Mode force stop.
Can't set Ringer tone for SIM2.
Your ROM is nice,I hope developers will look into this topic and help us solve these bugs.
Click to expand...
Click to collapse
Network signal off when busy¿?
For me Network data works, but only in 2g (maybe you have to enter in dialer -> *#*#4636#*#* and select "only GSM" option)
Contacts of SIM, I dont have any, but maybe is it a option to enable it in the contacts apk
USSD, I dont used it ever
Yes..It can be good if anyone knows anything related to fix that bugs..
I contacted with the dev of official LP rom, but he doesnt like sharing things with people..
kprkpr said:
Network signal off when busy¿?
For me Network data works, but only in 2g (maybe you have to enter in dialer -> *#*#4636#*#* and select "only GSM" option)
Contacts of SIM, I dont have any, but maybe is it a option to enable it in the contacts apk
USSD, I dont used it ever
Yes..It can be good if anyone knows anything related to fix that bugs..
I contacted with the dev of official LP rom, but he doesnt like sharing things with people..
Click to expand...
Click to collapse
Good, Can't send SMS too.
Wait,you mean the developer for LP didn't respond to you? He should at least give a helping hand.
Meaning this THL 4000 ROM is a real lollipop ROM and can install lollipop based applications?
koylaaa said:
Good, Can't send SMS too.
Wait,you mean the developer for LP didn't respond to you? He should at least give a helping hand.
Meaning this THL 4000 ROM is a real lollipop ROM and can install lollipop based applications?
Click to expand...
Click to collapse
He answer me, but he say that he knows fixes, but a no for share things and help me because that.. , you can contact it in her page in google+.. Maybe you have more luck than me
I didn't tried sms sending, but I received two. When I reinstall it I will try. I'm with 4.4 modified by me hehe
Is a real Lollipop 5.1.1 rom, you can install all lollipop things
Hey come back to lollipop hahaaa, I like your ROM even with bugs, you tried a lot , I think I should contact her too for her to know how serious we are.Can you post her name?
koylaaa said:
Hey come back to lollipop hahaaa, I like your ROM even with bugs, you tried a lot , I think I should contact her too for her to know how serious we are.Can you post her name?
Click to expand...
Click to collapse
I like too the lollipop, but I need at least camera..its bad, but I use it, is my main phone..xd
The guy is this: https://plus.google.com/+AjitUchiha/posts
But I recieved answers like this: "yes i know fixes
but sorry i cannot tell you because i am having doubt that you will modify and share my ROM"
Be careful xd
Thank you,I will talk to him and am hoping he accepts to help us.
kprkpr I think he made some bugs fixed in his new ROM, check it out www.mtkroms.com/2015/08/cyanogenmod-carbon-rom-for-mt6582.html?m=1
What's the size of your boot.img you used to modify the ROM? Is it 16mb? or 5mb?
How did you port the zimage and kernel?
or you didn't port with zimage and kernel?
koylaaa said:
What's the size of your boot.img you used to modify the ROM? Is it 16mb? or 5mb?
How did you port the zimage and kernel?
or you didn't port with zimage and kernel?
Click to expand...
Click to collapse
I will try when he upload it, thanks
Is 5.2 Mb or similar. But if you extract kernel from phone with dd or similar, maybe stock kernel will size 16 Mb, but when you redo the kernel, will be 5.2+-
The port is extracting the stock kernel, and the port kernel, and putting the stock zImage in port, and then using it (My english is bad..I hope you understood me)
OK,I understand you well but I am confuse. The boot.image 5mb different from the kernel file which is 4mb. Now,after getting the kernel file from stock ROM,where or which folder in the port ROM should I place the kernel file in?
And can you upload your modified boot.img for me? I can't extract and replace the kernel from stock boot.img to the port boot.img
Thanks.
koylaaa said:
And can you upload your modified boot.img for me? I can't extract and replace the kernel from stock boot.img to the port boot.img
Thanks.
Click to expand...
Click to collapse
Mm... I think I confused you.
In this page, you have a good tut for do this http://www.mtkroms.com/2015/08/install-real-lollipop-on-all-mtk.html
The boot.img modified is in the patch zip, if you uncompress it, you will have it
koylaaa said:
kprkpr I think he made some bugs fixed in his new ROM, check it out www.mtkroms.com/2015/08/cyanogenmod-carbon-rom-for-mt6582.html?m=1
Click to expand...
Click to collapse
I recently tried this, but, althought camera worked first time, RIL doesnt worked, and wifi disconnects..
New patch v3b has fix for camera (rear) and flashlight, thanks to the another rom that have it
For me I can send SMS good (SIM1, I only have 1 sim) , only big bug is 3g (and radio FM, that I think is of dev not correctly initialized)
Thanks,link to new patch v3b
I put it on the first post (now v3c,im trying things xd maybe fix something, maybe not)