[Q] Porting Flyme OS to Sensation, radio not working - HTC Sensation

Hi,
I'm trying to port Flyme OS to Sensation using http://forum.xda-developers.com/showthread.php?t=1908008 guide. I'm using latest CM9 as base ROM. I tried to port using nexus S and Xperia ray Flyme OS ports. I've to replace libandroid_runtime.so in order to make ported ROM boot.
The ROM boots fine and WiFi works but Radio is not working. I tried updating framework.jar with Ril*.smali and QualcommShared*.smali files. But that did not resolve the issue. (Even replacing com\android\internal\telephony folder completely could not make radio work).
So it looks like replacing libandroid_runtime.so is probably causing Radio to not work .
I'm attaching radio logcat if that could be useful. It will be great if someone can help .

Got it working .

webharsh said:
Got it working .
Click to expand...
Click to collapse
How?
xpirt

xpirt said:
How?
xpirt
Click to expand...
Click to collapse
Its been a while since I posted that. I think following was the solution -
Decompile framework-res.apk
Go to \framework-res\res\values\bools.xml and change change <bool name="skip_restoring_network_selection">true</bool> to false
See: http://forum.xda-developers.com/showthread.php?t=1908008
Btw, I abandoned this because I could not fix graphical glitches for which I need to recompile some libraries. Also it became irrelevant once Jellybean was released.

Related

Request [ROM] PARANOIDANDROID [CM9HYBRID]

rom request paranoidandroid [CM9HYBRID] from galaxy nexus and 'possible?
CM9 base. http://for: Silly:um.xda-developers.com/showthread.php?t=1619582
I want you to do well no worries
you'll have the keys to the nexus xD
I let you test the bugs and report them to me
EDITED
Testing only
Base CM9 alpha 8
No tested
No fixed
pa-maguro-GalaxySL-IMM76L-1.4c > http://www.mediafire.com/?276wz85jyc49wt1
nice to know that when we have a stable ICS kernel, we could install mods such as this without problems
EDIT:
works! but I might change display density dpi, and would be great to disable the virtual keys from the nexus
2nd EDIT:
I've managed to fix it and works like a charm Trebuchet launcher transition effects doesnt give me FC anymore
Why to port from galaxy nexus ,we can port from galaxy s i9000
I'm testing mode 'hybrid screen and application icons too big tried to edit does not work, mode' tablet only icons are fine,
I keep testing, thanks.
Vasishta Reddy said:
Why to port from galaxy nexus ,we can port from galaxy s i9000
Click to expand...
Click to collapse
Maybe cause the Nexus' hardware is closer to the I9003's than to the I9000 ?
Anyways, is the ROM from the link working well ? Can I flash it over alpha 8 ?
Thanks
OrbitalDroid said:
Maybe cause the Nexus' hardware is closer to the I9003's than to the I9000 ?
Anyways, is the ROM from the link working well ? Can I flash it over alpha 8 ?
Thanks
Click to expand...
Click to collapse
yes, reset and then install google apps.
I tried porting this rom, but could not get it to boot , I'll try building from source.
swapnilraj said:
I tried porting this rom from SII but could not get it to boot , I'll try building from source.
Click to expand...
Click to collapse
great good fortune: Dita incrociate:
it remains to fix it, I can set an improved version
I just want you to tell me if ca worth the shot to continue
LoLaTiOn said:
it remains to fix it, I can set an improved version
I just want you to tell me if ca worth the shot to continue
Click to expand...
Click to collapse
it is worth, but you also review the status bar that is positioned at the bottom with mode 'tablet. etc.
i still problems in the media logcat
I think everyone is related
I will make some changes to please you
I have a prepared a build, it should work (at least in theory) I'll test it and maybe upload it later.
__________________________________________________________________________________
Update: I used LoLaTiOn's updater script on my port (had it for weeks but it just wouldn't boot), and the Nexus S 1.4a build instead of the Galaxy Nexus build that LoLaTiOn used, it provides for better framework compatibility, since both are WVGA phones.
swapnilraj said:
I have a prepared a build, it should work (at least in theory) I'll test it and maybe upload it later.
__________________________________________________________________________________
Update: I used LoLaTiOn's updater script on my port (had it for weeks but it just wouldn't boot), and the Nexus S 1.4a build instead of the Galaxy Nexus build that LoLaTiOn used, it provides for better framework compatibility, since both are WVGA phones.
Click to expand...
Click to collapse
swapnilraj said:
Hi bro I used your updater script to make my Nexus S port of Paranoid Android to boot, it works a bit better since the native resolutions are identical on both the phone, I'd just like to know what procedure did you follow to port the maguro build?
Thanks for your work.
Click to expand...
Click to collapse
updater script? This is the same as Dhiru
I'm doing this port in 2 minutes, why create a topic so this is a test version?
could anyone port the sense 4 all rom ?? it would be amazing ..
this is the link --> http://forum.xda-developers.com/showthread.php?t=1593939
@lolation can you make a new thread with the paranoidandroid rom ??
Why another topic, it was fine at first.
I'm sorry but the work was resumed and I do not want history.
recomandation> [delete this topic]
Closed as it's here.

[TOOL][13-AUG-12]PARANOID ANDROID/AOKP RomPorterV5. Port ROMs in one click

This is my new tool to port AOKP, PARANOID ANDROID to our Defy/Defy+
CREDITS
brajesh.sharma87 for his tutorial on porting CM based ROMs and testing!
jurgen99 for spending a lot of time testing V5 and soft-bricking his phone a 1000 times!
phaelox for his awesome singing tool
Google for its amazing search engine
Requirements
Windows
Java
CM10/CM9 Rom for Defy
AOKP/PARANOID ANDROID Rom for a device similar to your device!(DEFY). Eg ROM = NEXUS S AOKP
500 MB on Hard Drive (Tool is < 1 MB. The ROMs need space)
Whats new
PARANOID ANDROID porting added! (For defy user, porting ICS PARANOID ANDROID works super fine. JB has issues)
Technically Galaxy S is also supported. Someone with a Galaxy S please confirm if it works fine.
[*]Add support for new devices to be added by just entering the name of apps to be backed up and removed in a plain .txt file
(Instructions to add support to new devices are in the README.txt
[*]Script now detects which phone is to recieve the port!
[*]Option of FORCE-PORT if their device isnt yet supported by this tool.
[*]Super easy way to add support for new devices.
[*]Code cleanup thanks to balika01
Instructions
Extract the AOKP/PARANOID ANDROID ROM and put its contents in the INPUT folder. So the input folder should have now META-INF and system folders at its root.
Extract the Defy/Defy+ CM10/CM9 ROM and put its contents in the OUTPUT folder. Same as above.
Run Port.bat!!
Notes
During the process you will be asked if you want to copy libandroid_runtime.so. Press y to copy or any other key to ignore(CAPS Y is not a yes).
If you choose not to copy and your ROM boots, its fine!. If ROM doesn't boot, then delete the output zip and run the tool again and this time choose to copy the libandroid_runtime.so. If still ROM doesn't boot then we have a problem . Post here and someone will try to help you!.
For PARANOID ANDROID try pressing y first. It needs libandroid_runtime.so
When porting for second time, empty the input and output folders and re-copy the files. Do this each time.
Coming Soon
Paranoid Android Porter. DONE!
Ability to port from devices other than Nexus S. (DONE!!)
Ability to port to devices other than Defy (95% done! only need a list of stuff to be deleted according to each device. I can add device support when users of that particular device submit a list of APKs that are in other ports which is not used by their device and a list of APKs which are in their CM ROMs and need to remain after the port)
Want to see this tool working for your device?
Please give me the following information:
-Information like which apps are specific to your device (eg, for defy we have defyparts,motohelper,etc)
-Apps which are present in AOKP/PARANOID roms which are useles on your device (eg fo defy NFC.apk, tvout.apk)
Click to expand...
Click to collapse
Ps- Included is an awesome automatic build.prop editor which took me quite a while to code
Removed Older versions by accident
at the moment, u dont have to copy "libandroid_runtime.so" for porting AOKP JB from Nexus S, so just press "n" when asked to copy that file.
THANKS
can we port AOKP roms from other devices as well ?
like - maguro ??
and will there be any need to add any DEFY specefic apps , like defy settings etc..?
thanks again for this work ( highly appreciated)
Shubhamqweasd said:
THANKS
can we port AOKP roms from other devices as well ?
like - maguro ??
and will there be any need to add any DEFY specefic apps , like defy settings etc..?
thanks again for this work ( highly appreciated)
Click to expand...
Click to collapse
The Defy apps are taken care of!
Its best if you use only Nexus S ROMs right now! The build.prop editor is now tailored for Nexus S ROMs. The ROM may boot but build.prop will have false info.
I have ported manually aokp maguro and is better than SGS, more features.
Maybe we can use ROM Control and SystemUI from that in this port, I will try ..
Nice work!!
hmm , any fix for button backlight ??
everything else is working fine
some things u might have missed :
automatic brightness settings , navigation inside ( setting > display ), etc .. are these options defy specefic and they should be merged , or its AOKP specefic ??
pabloltg said:
I have ported manually aokp maguro and is better than Gnex, more features.
Maybe we can use ROM Control and SystemUI from that in Gnex port, I will try ..
Nice work!!
Click to expand...
Click to collapse
Using nexus s. Nt galaxy nexus
The problem is my build.prop editor searches for crespo and changes to jordan. Thats the only issue. In maguro it cant find crespo.
Sent from my MB526 using xda app-developers app
pabloltg said:
I have ported manually aokp maguro and is better than Gnex, more features.
Maybe we can use ROM Control and SystemUI from that in Gnex port, I will try ..
Nice work!!
Click to expand...
Click to collapse
Well its just a trial version at the moment, from next version onwards u can port from any of the nexus s, galaxy nexus and galaxy s2. One-click and done.
Sent from my MB525 using xda app-developers app
hmm , any fix for button backlight ??
everything else is working fine
some things u might have missed :
automatic brightness settings , navigation inside ( setting > display ), etc .. are these options defy specefic and they should be merged , or its AOKP specefic ??
guys , i also cant find DEFy parts neither in settings nor in app drawer ??
i took quarx 8/04 rom and latest crespo AOKP
kadavil said:
Using nexus s. Nt galaxy nexus
The problem is my build.prop editor searches for crespo and changes to jordan. Thats the only issue. In maguro it cant find crespo.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Yup, my fault..
Download from fitsnugly.
Start the work and replace with this in OutputRom_signed
ro.goo.developerid=Euroskank
ro.goo.rom=aoskp
ro.goo.version=1344088502
ro.aokp.version=aokp_maguro_jb-Aug-04-12
Shubhamqweasd said:
hmm , any fix for button backlight ??
everything else is working fine
some things u might have missed :
automatic brightness settings , navigation inside ( setting > display ), etc .. are these options defy specefic and they should be merged , or its AOKP specefic ??
guys , i also cant find DEFy parts neither in settings nor in app drawer ??
i took quarx 8/04 rom and latest crespo AOKP
Click to expand...
Click to collapse
This only automates porting. Whatever doesnt work in the base ROMs dont work in the output. Check if defyparts is there in system/app in the output zip.
ROM booted right?
Thats what the tool does
Aokp functionality is not under its control
Sent from my MB526 using xda app-developers app
pabloltg said:
Yup, my fault..
Download from fitsnugly.
Start the work and replace with this in OutputRom_signed
ro.goo.developerid=Euroskank
ro.goo.rom=aoskp
ro.goo.version=1344088502
ro.aokp.version=aokp_maguro_jb-Aug-04-12
Click to expand...
Click to collapse
Il try making the editor more flexible.
Sent from my MB526 using xda app-developers app
kadavil said:
This only automates porting. Whatever doesnt work in the base ROMs dont work in the output. Check if defyparts is there in system/app in the output zip.
ROM booted right?
Thats what the tool does
Aokp functionality is not under its control
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
yes defyparts.apk is in OUTPUT directory ( system/app) ..
also the button backlight and automatic backlight options , are present and working well on the rom i extracted in output directory >..
m just saying that , there might be some things left .. do check for them no offence
Shubhamqweasd said:
yes defyparts.apk is in OUTPUT directory ( system/app) ..
also the button backlight and automatic backlight options , are present and working well on the rom i extracted in output directory >..
m just saying that , there might be some things left .. do check for them no offence
Click to expand...
Click to collapse
Decompile your output framework and edit the ButtonsBacklightValues in arrays.xml.
Shubhamqweasd said:
yes defyparts.apk is in OUTPUT directory ( system/app) ..
also the button backlight and automatic backlight options , are present and working well on the rom i extracted in output directory >..
m just saying that , there might be some things left .. do check for them no offence
Click to expand...
Click to collapse
Maybe it doesnt work on AOKP.
I donno i havent tried aokp so far. Has it worked on other aokp builds?
Sent from my MB526 using xda app-developers app
kadavil said:
Maybe it doesnt work on AOKP.
I donno i havent tried aokp so far. Has it worked on other aokp builds?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
we dont have any other aokp builds
on AOKP port by brajesh button backlight doesn work , but it does have defy settings
cause i dont have any singnal until i set correct baseband on defy parts
will try:laugh:
Shubhamqweasd said:
we dont have any other aokp builds
on AOKP port by brajesh button backlight doesn work , but it does have defy settings
cause i dont have any singnal until i set correct baseband on defy parts
Click to expand...
Click to collapse
Ohhh. Wil wait for brajesh.sharma to tell how he got defyparts working
Sent from my MB526 using xda app-developers app
i'm try to port codename android 3.0.1 ... have some problems with media scaner the room boot and run fast
As I have both defy mb525 and lg optimus 2x I find this tool interesting and ask: what does it take to rebuild the tool to do the same porting to o2x? If it's possible?
Thanks alot for this toom, appreciated
Sent from my latest DjangoManouche and latest Spica Kernel

[DEV][ROM]PANTECH Burst 4G MIUI JB PORT UNOFFICIAL

MIUI JB 4.1.2 for Pantech Burst 4G
WARNING
FLASH AT YOUR OWN RISK . THIS IS STILL ALPHA. SO IT GOES UNSAID, I'M NOT RESPONSIBLE FOR BRICKED / BROKEN PHONES OR ANY NUCLEAR WAR THAT YOU TRIGGER
DEVS CURRENTLY ON WORK
ujjwalchhabra
deathscream
DOWNLOADS
MIUI-presto-20130420-UNOFFICIAL
MD5SUM : 1b84a6e17e0848c05fd46a6ad0f74a96
Features
What works?
Camera
Calls
wifi
data
....you tell
What's borked?
Bluetooth call audio
System UI closes unexpectedly. (Known Bug : Can't see Status Bar ) Work in progress
That being said....HOW TO FLASH?
The flashing method is the same as always.
Only for devs for now those who want to experience MIUI on their devices.
SCREENSHOTS
Gimme some time...I don't wanna put ugly screenshots.....Coming Soon.
Go ahead happy flashing.
Reserved.:laugh:
hi, nice to see additional roms for the Pantech Burst! Is this better than CM and if so, in what way(s)?
Edit: sorry I did not notice the "dev" only label.
alan-31 said:
hi, nice to see additional roms for the Pantech Burst! Is this better than CM and if so, in what way(s)?
Click to expand...
Click to collapse
MIUI is based on CM10. And its not upto me to tell if its better than any ROM. It depends on which ROM has features that suite the end user. For now this ROM is still in alpha build. A lot of things are still broken.
Lol , I was working on porting MIUI from Evo 3D . Its good you did source build . BTW can you brief me a little ? Its the same as building CM or some other steps ? Kindly provide a brief tutorial how you compiled as other devs did . That way everyone can compile and do debugging .
Thanks and regards
-UC
EDIT : It doesn't seems its a source build . Its a port , you should mention it in first page.
Many things don't work -
System ui
No miui launcher
backlight
torch app
...
BTW for all others who are willing to support and ready to work , read this thread and start porting . We all can work together on latest version of MIUI to port .
ujjwalchhabra said:
Lol , I was working on porting MIUI from Evo 3D . Its good you did source build . BTW can you brief me a little ? Its the same as building CM or some other steps ? Kindly provide a brief tutorial how you compiled as other devs did . That way everyone can compile and do debugging .
Thanks and regards
-UC
EDIT : It doesn't seems its a source build . Its a port , you should mention it in first page.
Many things don't work -
System ui
No miui launcher
backlight
torch app
...
BTW for all others who are willing to support and ready to work , read this thread and start porting . We all can work together on latest version of MIUI to port .
Click to expand...
Click to collapse
My bad ...I forgot to mention its a port...I'm currently working on modding the system ui to fix the force close issue. Any ideas on fixes?
Sent from my PantechP9070 using xda premium
deathscream said:
My bad ...I forgot to mention its a port...I'm currently working on modding the system ui to fix the force close issue. Any ideas on fixes?
Sent from my PantechP9070 using xda premium
Click to expand...
Click to collapse
There must be something wrong with either these files
-Framework-res.apk ( wrong public.xml values causing problems to any of the functions in systemui .)
-services.jar ( maybe some imp base string might be missing )
--systemui.apk itself ( but less chance , or maybe resolution problem too .)
-Any other files , you ported you must be knowing . Gimme some more info I'll work a little on it too ,
- your MIUI's Base rom link ? Which device ?
- What you did while porting ? Replaced app,framework,fonts,media with MIUI ( after checking everything you found necessary ) and tweaked updater script ?
MY suggestion : I think its better if we work on another greater version of MIUI to port . Its a very appreciable effort of yours to atleast give kind attention to MIUI also . I think making things work on this port won't be that hard but if same amount of work given on latest version that will be more good . :good:
ujjwalchhabra said:
There must be something wrong with either these files
-Framework-res.apk ( wrong public.xml values causing problems to any of the functions in systemui .)
-services.jar ( maybe some imp base string might be missing )
--systemui.apk itself ( but less chance , or maybe resolution problem too .)
-Any other files , you ported you must be knowing . Gimme some more info I'll work a little on it too ,
- your MIUI's Base rom link ? Which device ?
- What you did while porting ? Replaced app,framework,fonts,media with MIUI ( after checking everything you found necessary ) and tweaked updater script ?
MY suggestion : I think its better if we work on another greater version of MIUI to port . Its a very appreciable effort of yours to atleast give kind attention to MIUI also . I think making things work on this port won't be that hard but if same amount of work given on latest version that will be more good . :good:
Click to expand...
Click to collapse
I'll recheck those. I used nexus s 4g port ROM. It was just a trial that I made. Started this thread to bring all the devs to work together since we have very few for our device. What miui did you think of porting?
Sent from my PantechP9070 using xda premium
deathscream said:
I'll recheck those. I used nexus s 4g port ROM. It was just a trial that I made. Started this thread to bring all the devs to work together since we have very few for our device. What miui did you think of porting?
Sent from my PantechP9070 using xda premium
Click to expand...
Click to collapse
First will try with MIUI version 3.4.12 - 3.3.x . Those are also based on 4.1.2 and are latest . I'll link you to some good device's source build .
EDIT : [ROM] MIUI v5 3.4.12 - OR - Unofficial MIUI V5(See nexus S link) What you say ? . I personally Prefer both . Sensation's build because its chipset will be similar to ours (quallcomm) and Nexus S for same resolution , though resolution isn't a big deal i think :/ through MIR we can resize framework-res.apk and rest the needful apps will be resized . But since you successfully made nexus S build boot , I think we should go with that ? What you say ?
ujjwalchhabra said:
First will try with MIUI version 3.4.12 - 3.3.x . Those are also based on 4.1.2 and are latest . I'll link you to some good device's source build .
EDIT : [ROM] MIUI v5 3.4.12 - OR - Unofficial MIUI V5(See nexus S link) What you say ? . I personally Prefer both . Sensation's build because its chipset will be similar to ours (quallcomm) and Nexus S for same resolution , though resolution isn't a big deal i think :/ through MIR we can resize framework-res.apk and rest the needful apps will be resized . But since you successfully made nexus S build boot , I think we should go with that ? What you say ?
Click to expand...
Click to collapse
Hope you guys get this together, a shame im not very into development, but anything I can help just say it
ujjwalchhabra said:
First will try with MIUI version 3.4.12 - 3.3.x . Those are also based on 4.1.2 and are latest . I'll link you to some good device's source build .
EDIT : [ROM] MIUI v5 3.4.12 - OR - Unofficial MIUI V5(See nexus S link) What you say ? . I personally Prefer both . Sensation's build because its chipset will be similar to ours (quallcomm) and Nexus S for same resolution , though resolution isn't a big deal i think :/ through MIR we can resize framework-res.apk and rest the needful apps will be resized . But since you successfully made nexus S build boot , I think we should go with that ? What you say ?
Click to expand...
Click to collapse
I feel sensation is a better choice ...resolution shouldn't be a problem. Will try it tonight and post the results. Lets try out what's best for our devices.
Sent from my PantechP9070 using xda premium
deathscream said:
I feel sensation is a better choice ...resolution shouldn't be a problem. Will try it tonight and post the results. Lets try out what's best for our devices.
Sent from my PantechP9070 using xda premium
Click to expand...
Click to collapse
okay , I'll download sensation one . I think still we need to resize framework-res.apk first to even make it boot. Still Lets see . :good:
ujjwalchhabra said:
okay , I'll download sensation one . I think still we need to resize framework-res.apk first to even make it boot. Still Lets see . :good:
Click to expand...
Click to collapse
Yes. The framework-res definitely needs to be re-sized. Let's see how the port comes out.

BOOTING ! XPERIA Z5 Lollipop 5.1.1 Rom - Porting need help

EDIT : PROJECT DELAYED
Trying to port a custom Xperia Z1 Rom to Nexus 5.
This custom Rom has all features from Xperia Z5.
Here is base rom : http://forum.xda-developers.com/xperia-z1/development/rom-z5mx-rom7-5-0extended-battery-t3224245
Edit : Advanced, see logcat
Edit 2 : fixed mediadrm fatal crash. Now, i need to fix SDCARD
Edit 3 : seems i need to fix sound
Edit 4 : Booting, as logcat says. The problem is : Google Logo stays displayed. Bootanimation doesnt displays and so, it seems it prevents phone from displaying Setup Wizard, and Android UI. Maybe the problem is "libsecureui.so" dlopen failed. I still didnt found the solution and any help would be greatly apreciated.
Heres logcat
Thanks for any help
Getting advanced a little. Now, getting an issue with sdcard. See OP
You should try removing all links to sdcard and just make it internal only, Nexus 5 don't have externalsd
Also, you'll better off porting z5 stuff to a cm12.1 base, its easier.
The official sony roms have a lot of proprietary kernel stuff that can't be ported, stamina mode is one
besides, camera wouldn't work
Do try first tho
TakuyaZ said:
You should try removing all links to sdcard and just make it internal only, Nexus 5 don't have externalsd
Also, you'll better off porting z5 stuff to a cm12.1 base, its easier.
The official sony roms have a lot of proprietary kernel stuff that can't be ported, stamina mode is one
besides, camera wouldn't work
Do try first tho
Click to expand...
Click to collapse
I see, man, thanks !
I did "ro.build.characteristics=nosdcard" into build.prop. tried some other stuff and got as far as here : http://pastebin.com/bmHJQ0ke
I tried Cm12.1 and got so much other issues and inarborded cm12.1 to use UntouchedAOSP as base now.
Maybe I need to port Xperia kernel too, as Xperia z1 has kinda same hardware as Nexus 5, and that's the reason I used a custom Xperia z1 ROM
dekefake said:
I see, man, thanks !
I did "ro.build.characteristics=nosdcard" into build.prop. tried some other stuff and got as far as here : http://pastebin.com/bmHJQ0ke
I tried Cm12.1 and got so much other issues and inarborded cm12.1 to use UntouchedAOSP as base now.
Maybe I need to port Xperia kernel too, as Xperia z1 has kinda same hardware as Nexus 5, and that's the reason I used a custom Xperia z1 ROM
Click to expand...
Click to collapse
I mean making a entirely new rom using cm12.1 as a base and just port sony's launcher, systemui, lockscreen. etc
Reading the logcat, it said unknown permission for nearly all jars/apks. did you break the signature or something?
Sorry i cannot help much, its been years since i last ported a entirely new rom to a different device
TakuyaZ said:
I mean making a entirely new rom using cm12.1 as a base and just port sony's launcher, systemui, lockscreen. etc
Reading the logcat, it said unknown permission for nearly all jars/apks. did you break the signature or something?
Sorry i cannot help much, its been years since i last ported a entirely new rom to a different device
Click to expand...
Click to collapse
I see. I don't know at all why theses permissions are fcked up. No problem man. Lollipop seems way more tricky to port. Maybe because Apk/jar are odexed
Can i use this on my Nexus 5
Can i use this rom on my Nexus 5 ?
vk4111 said:
Can i use this rom on my Nexus 5 ?
Click to expand...
Click to collapse
Man are u kidding me ? Its a thread about getting a port booting. It doesnt even work, so, obviously, you cant get it working on your Nexus 5.
Got mediadrm fixed. Need to fix sdcard, for sure. See logcat.
dekefake said:
Got mediadrm fixed. Need to fix sdcard, for sure. See logcat.
Click to expand...
Click to collapse
I see a lot of the custom rom's theme's errors.
have you tried to port the bone stock Xperia rom before this?
TakuyaZ said:
I see a lot of the custom rom's theme's errors.
have you tried to port the bone stock Xperia rom before this?
Click to expand...
Click to collapse
Yeah, tried, a while ago, but sticked to google logo too but didn't remember how far I gone with the logcat
Restarted the project. Here's logcat : http://pastebin.com/ACkZRAzd
Got progress. Please see OP
ROM not installing
The base Rom does not install on my nexus 5. TWRP and CWM show error. Does it have to do something with logcat?

CM 13

Dear all,
We have Unofficial CM ROM for Samsung galaxy S5 G900H but there is some bugs in it major is Camera & Call audio
But we won't have now developer to continue this ROM so is there any other way to get rid out this major bugs with externally,
I means like other developers who gave falshable patch zip which contains some libs or app. We have 6.0.1 TW so can anyone tell me which lib files or anything else will help me.
Thanks in advance!!!
Major camera libs are libdpframeworks,libfeauterio,libcameracustom,libcameraparamsgr(I'm nor sure of the correct name of this one),libjpego.so
Libcamdrv,libcamalgo.
For audio the only I can think of is Libaudioprimarydefault.so.
PS if the camera still doesn't work I can give you a link of the camera fix made for my phone and you can compare it and replace your libfiles.
Also does your phone have a thread if so give me a link
northwindtrades said:
Major camera libs are libdpframeworks,libfeauterio,libcameracustom,libcameraparamsgr(I'm nor sure of the correct name of this one),libjpego.so
Libcamdrv,libcamalgo.
For audio the only I can't think of is Libaudioprimarydefault.so.
PS if the camera still doesn't work I can give you a link of the camera fix made for my phone and you can compare it and replace your libfiles.
Also does your phone have a thread if so give me a link
Click to expand...
Click to collapse
But can TW libs will work for CM?
Yes we have a thread for our device here
http://forum.xda-developers.com/showthread.php?p=65585446
somadsul said:
But can TW libs will work for CM?
Yes we have a thread for our device here
http://forum.xda-developers.com/showthread.php?p=65585446
Click to expand...
Click to collapse
Use your phones libs and you should be fine preferably from your phones lollipop firmware.
BTW if this is a case of replacing files your dev would have fixed it, no?
northwindtrades said:
Use your phones libs and you should be fine preferably from your phones lollipop firmware.
BTW if this is a case of replacing files your dev would have fixed it, no?
Click to expand...
Click to collapse
No dev is lost his phone to compile this rom and now he using other phone so there is no new development since 6 months.
Lollipop firmwares? But its a Marshmallow for this CM [emoji53]
somadsul said:
No dev is lost his phone to compile this rom and now he using other phone so there is no new development since 6 months.
Lollipop firmwares? But its a Marshmallow for this CM [emoji53]
Click to expand...
Click to collapse
Far as I know os version doesn't matter when it comes to libs
northwindtrades said:
Far as I know os version doesn't matter when it comes to libs
Click to expand...
Click to collapse
Ok good to know will try

Categories

Resources