This thread is primarily for ROM developers. So please chime in only if you have something development oriented to add. I suspect many of us are looking to port the new Sensation Sense 3.0 leak over to the DZ/G2. So I figured it would make sense to start a thread to discuss what our findings and collaborate on getting a port working.
I just started looking at the leak myself but have a few initial thoughts. This is obviously Gingerbread and the only real GB sense kernel comes from the 2.30 leak. I suspect that's the kernel we're going to want to use. Next, the system image is almost ~500MB and is already deodexed. We're going to need to slim it down by ~120MB or so to fit on the G2 partition (which is smaller than the DZ).
If you're a developer and want a fast mirror of the leak, PM me.
somehow i overlooked this partition size, anyways iv slimed it down to 238mb compressed. will see how it goes.
trying to port qHD sense ui to wvga? good luck with that..
shenshang said:
trying to port qHD sense ui to wvga? good luck with that..
Click to expand...
Click to collapse
Seriously?...
shenshang said:
trying to port qHD sense ui to wvga? good luck with that..
Click to expand...
Click to collapse
As long as HTC didn't hard code anything in the frameworks, you should be able to decompile the framework files, resize the HDPI files to the correct size for G2/Glacier/Ace screen size and repack them back into the framework... Lots of work but not impossible...
What's hard are the kernel and libraries.... At least G2, you guys have a true GB (2.6.35 kernel) to start with, then you need to somehow find libs that would play nicely with 3.0 Sense Framework... This is might be much harder than just the graphics. From what was presented, HTC has modified/rewrote quite a bit of framework for 3.0.... So finding libraries (even from Sense 2.1 ROMs) to work with 3.0 will be a major challenge....
i see no indication that this rom is only for qhd phones, checking the htc frameworks i saw hdpi folder, so that mean this rom must support res of 800x480
for some reason i cant get logcat working.
siulmagic said:
for some reason i cant get logcat working.
Click to expand...
Click to collapse
That's a function of kernel/ramdisk. Which of those are you using?
rmk40 said:
That's a function of kernel/ramdisk. Which of those are you using?
Click to expand...
Click to collapse
i tried the kernel from the official leak, and a cm7 one witch i changed the bootclasspath.
Well, here's where I'm at now. After pushing the entire Sensation ROM to system, I've replaced the following libs with those from the GB leak:
libandroid_runtime.so
libaudio.so
libaudioalsa.so
libaudioeffect_jni.so
libaudioflinger.so
libaudiopolicy.so
libhtc_acoustic.so
libhtc_ril.so
libreference-ril.so
libril.so
libsurfaceflinger.so
libsurfaceflinger_client.so
Replaced bins:
app_process
bluetoothd
rild
rmt_storage
sound7x30
surfaceflinger
Entire /system/etc/firmware directory replaced with GB leak.
All /system/etc/*.csv replaced with GB leak.
And here are the errors I'm seeing on startup: http://pastebin.com/YR5UVNbB.
E/JNIHelp ( 2854): RegisterNatives failed for 'android/server/BluetoothService'
E/AndroidRuntime( 2854): Unable to register all android natives
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): Cannot open audience_2051 device (-1)
E/AudioHardwareMSM7X30( 2856): set_tpa2051_parameters fail
E/AudioHardwareMSM7X30( 2856): set_aic3254_parameters failed
E/AudioPolicyManagerBase( 2856): mSupportBacMic = 0
If anyone is further than I am, I'd be interested to hear what you've done.
rmk40 said:
Well, here's where I'm at now. After pushing the entire Sensation ROM to system, I've replaced the following libs with those from the GB leak:
libandroid_runtime.so
libaudio.so
libaudioalsa.so
libaudioeffect_jni.so
libaudioflinger.so
libaudiopolicy.so
libhtc_acoustic.so
libhtc_ril.so
libreference-ril.so
libril.so
libsurfaceflinger.so
libsurfaceflinger_client.so
Replaced bins:
app_process
bluetoothd
rild
rmt_storage
sound7x30
surfaceflinger
Entire /system/etc/firmware directory replaced with GB leak.
All /system/etc/*.csv replaced with GB leak.
And here are the errors I'm seeing on startup: http://pastebin.com/YR5UVNbB.
E/JNIHelp ( 2854): RegisterNatives failed for 'android/server/BluetoothService'
E/AndroidRuntime( 2854): Unable to register all android natives
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): ioctl ACOUSTIC_UPDATE_ADIE failed -1
E/HTC Acoustic( 2856): Cannot open audience_2051 device (-1)
E/AudioHardwareMSM7X30( 2856): set_tpa2051_parameters fail
E/AudioHardwareMSM7X30( 2856): set_aic3254_parameters failed
E/AudioPolicyManagerBase( 2856): mSupportBacMic = 0
If anyone is further than I am, I'd be interested to hear what you've done.
Click to expand...
Click to collapse
Not sure if it helps, but in time i was ported ROM i changed next libs:
Code:
ibwbxml_jni.so
libwebcore.so
libxml2wbxml.so
libandroid_runtime.so
libaudio.so
libaudioflinger.so
libaudiopolicy.so
libAudioTrimmer.so
libc.so
libcamera.so
libcameraservice.so
libdrm1.so
libdrm1_jni.so
libdvm.so
libEGL.so lib
flsaplayerlib.so
libgps.so
libhardware_legacy.so
libhtc_acoustic.so
libhtc_ril.so
libhtcbitmapfactory.so
libicudata.so
libmedia.so
libmedia_jni.so
libmediaplayerservice.so
libnativehelper.so
liboemcamera.so
libOlaBase.so
libOmxCore.so
libOmxH264Dec.so
libOmxMpeg4Dec.so
libopencore_author.so
libopencore_player.so
libopencore_rtsp.so
libpdfreader.so
libreference-ril.so
libril.so
libskia.so
libskiagl.so
libsoundpool.so
libsurfaceflinger.so
libui.so
libutils.so
libwbxml.so
libwbxml_jni.so
libwebcore.so
libxml2wbxml.so
It is obvious not all of libs required, but it seems u missed some libs which are important.
rmk, can u please pm me link ?
your lucky you got logcat working, mine dosent even work.
btw rmk40 did you replace the sound csv files in the etc folder?
edit : nvm you did
siulmagic said:
your lucky you got logcat working, mine dosent even work.
Click to expand...
Click to collapse
Have you tried using my ramdisk/kernel from the 2.30 leak rom?
http://pastebin.com/GDVTuSwi thats how far my brother rafyvitto has gotten it, on his mytouch 4g, still not booting =/
rmk40 said:
Have you tried using my ramdisk/kernel from the 2.30 leak rom?
Click to expand...
Click to collapse
yea , it still does not work, it might be my update script? can you upload yours?
siulmagic said:
yea , it still does not work, it might be my update script? can you upload yours?
Click to expand...
Click to collapse
I've actually been doing all my work without flashing anything. Just manually pushing files onto /system and /data. Pushed the entire thing to /system with the exception of app, which is sitting in /data/system.app. There's a symlink from /system/app -> /data/system.app, just to make it all fit. I think the key is to make sure the permissions are correct in /system/bin.
Have you tried the same process I used to get to the state I'm at?
rmk40 said:
I've actually been doing all my work without flashing anything. Just manually pushing files onto /system and /data. Pushed the entire thing to /system with the exception of app, which is sitting in /data/system.app. There's a symlink from /system/app -> /data/system.app, just to make it all fit. I think the key is to make sure the permissions are correct in /system/bin.
Have you tried the same process I used to get to the state I'm at?
Click to expand...
Click to collapse
it dosent really matter if you push the libs or flash them, i just cant get logcat too work it complains the sh binary is not present when it actually is. and i stripped the rom off a couple of things like livewallpapers, the weather video previews etc etc, iv fitted the whole system folder on the g2 nand just fine.
siulmagic said:
it dosent really matter if you push the libs or flash them, i just cant get logcat too work it complains the sh binary is not present when it actually is. and i stripped the rom off a couple of things like livewallpapers, the weather video previews etc etc, iv fitted the whole system folder on the g2 nand just fine.
Click to expand...
Click to collapse
No, of course, I understand that it doesn't matter whether you push or flash. Does adb shell work? Wondering if you're failing to mount /system entirely.
Related
I appreciate the time you are taking to read this. I searched a lot, but could not find an answer to my problem.
I am trying to implement a recent patch to bidi text rendering that was created for CM rom and runs on Nexus 1. I downloaded the vanilla source code to 2.1, and compiled it with and without the patch. Then I disassembled framework.jar and compared the smali files, to discover that the following ones were modified:
android/graphics/Canvas.smali
android/graphics/Canvas$EdgeType.smali
android/graphics/Canvas$VertexMode.smali
android/text/Layout.smali
android/text/SpannableStringBuilder.smali
android/text/Styled.smali
android/widget/TextView$CharWrapper.smali
My idea was that if I run baksmali on the framework.jar file from my Desire, replace these files with the new ones, run smali on the result, repack it as framework.jar and upload it to the device - the fix will be implemented.
This actually worked very well for a previous fix, which involved only the file StaticLayout.smali. It worked without having to sign framework.jar; however, that fix did not change the file size, whereas the current one does change it - especially for Canvas.smali. I did not try to sign framework.jar - I don't really know how to and if it is necessary.
The result was a bootloop. Logcat showed that the device is unable to load a native library:
Code:
D/AndroidRuntime( 103): --- registering native functions ---
W/dalvikvm( 103): Unable to register: not native: Landroid/graphics/Canvas;.drawText (Ljava/lang/String;FFLandroid/graphics/Paint;)V
E/JNIHelp ( 103): RegisterNatives failed for 'android/graphics/Canvas'
E/AndroidRuntime( 103): Unable to register all android natives
This is where I am stuck. What I really wanted to do was to create a script-based fix that would work on any device running 2.1. It was possible for the StaticLayout fix. Now I'll settle for figuring out how to make it work for the Desire.
I am attaching Canvas.smali, the file I think is responsible for the problem, in 2 forms: vanilla is compiled from source with no modification, patched is compiled from source after the patch. It seems that the other Canvas files were unchanged by the modification.
Thank you very much in advance!
I am a fool - you would need, of course, the smali file that actually works on the device. Attached here.
ClassicalDude said:
I am a fool - you would need, of course, the smali file that actually works on the device. Attached here.
Click to expand...
Click to collapse
this is a bit off topic but how to change in .jar file? thanks
jullejul said:
this is a bit off topic but how to change in .jar file? thanks
Click to expand...
Click to collapse
http://www.villainrom.co.uk/viewtopic.php?f=61&t=921&start=0
this will teach you how to patch a jar file..
hi thanxxxx
Well this thread basically contains all beta builds of ROM ports which everyone maybe working on for everyone to basically test and give feedback on before they become official releases i'll be holding the first post for all my ports
hopefully all the other porters take the first few posts and reserve em for their test builds
firstly i found a 2.1 ROM from cdma forums which is known as RegaWMOD
i got fond of the features so i thought i'll make a quick port of it
i have no clue if its running at all since i havent flashed it myself
hoping one of the flash junkies could test it n see if its working
RegaWMOD 2.1update-1 ROM
flash only if ur willing to test and give me feedback on it!
the second ROM i made was the TeamHeroc build of cm7 which very similair to decked up for life but untested.....it is AOSP GB as decked........i havent applied Gapps package so plz REMEMBER TO FLASH GAPPS WHEN TRYING THIS ROM!
Link to TeamHEROC 22OCT
TeamHeroC build
DietGB from the Sapphire forums
GB aosp ROM same as decked and Teamheroc but only ported from the sapphire forums....its a test build again n no gapps included jus remember to install gapps after installing the ROm
Diet GB!---DONT FLASH I HAVENT FINISHED THIS YET MADE A FEW MISTAKES IN THIS BUILD!
AOSPC MOD based on the aospCMOD from the cdma
forumsLink to original thread!
This is by far the lightest gingerbread rom i came across so far,ROM size is 45.1MB which is like WTF!!!
anyway it is by far one of most stable ports so far n i compare it to decked wit respect to speed and stability......
u will find it is based on gingerbread 2.3.4 sources and very smooth as a daily....
Link to download
as always i look forward to feedback!
based on your feedback i'm hoping to pursue a future in these ROMs and get em to more stable states!
PLZ REMEMBER THESE ARE FOR TESTING ONLY AND NOT OFFICIAL RELEASES!
downloading, trying the RegaWMOD 2.1update-1 ROM
Did you do anything special to make the TeamHeroC port working? I compiled it from source but I can't seem to get it booting.
From logcat:
Code:
I/Netd ( 558): Netd 1.0 starting
E/Netd ( 558): Unable to start DnsProxyListener (No such file or directory)
E/SocketListener( 558): Obtaining file descriptor socket 'dnsproxyd' failed: No such file or directory
E/NetdConnector( 128): Communications error
E/NetdConnector( 128): java.io.IOException: No such file or directory
E/NetdConnector( 128): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 128): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 128): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 128): at java.lang.Thread.run(Thread.java:1019)
E/NetdConnector( 128): Error in NativeDaemonConnector
E/NetdConnector( 128): java.io.IOException: No such file or directory
E/NetdConnector( 128): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 128): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 128): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 128): at java.lang.Thread.run(Thread.java:1019)
Maybe the latest sources are broken...
Will try your port!
Did you do anything special to make the TeamHeroC port working? I compiled it from source but I can't seem to get it booting.
From logcat:
I/Netd ( 558): Netd 1.0 starting
E/Netd ( 558): Unable to start DnsProxyListener (No such file or directory)
E/SocketListener( 558): Obtaining file descriptor socket 'dnsproxyd' failed: No such file or directory
E/NetdConnector( 128): Communications error
E/NetdConnector( 128): java.io.IOException: No such file or directory
E/NetdConnector( 128): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 128): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 128): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 128): at java.lang.Thread.run(Thread.java:1019)
E/NetdConnector( 128): Error in NativeDaemonConnector
E/NetdConnector( 128): java.io.IOException: No such file or directory
E/NetdConnector( 128): at android.net.LocalSocketImpl.connectLocal(Native Method)
E/NetdConnector( 128): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:238)
E/NetdConnector( 128): at android.net.LocalSocket.connect(LocalSocket.java:98)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.listenToSocket(NativeDaemonConnector.java:99)
E/NetdConnector( 128): at com.android.server.NativeDaemonConnector.run(NativeDaemonConnector.java:83)
E/NetdConnector( 128): at java.lang.Thread.run(Thread.java:1019)
Maybe the latest sources are broken...
Will try your port!
Click to expand...
Click to collapse
Lol no sources aren't broken its a cdma Rom remember? U jus have to change the netd file in system/bin wit one of our Roms,n remember all radio related files have to b changed
Sent from my HTC Hero using xda premium
bharat_goku said:
Lol no sources aren't broken its a cdma Rom remember? U jus have to change the netd file in system/bin wit one of our Roms,n remember all radio related files have to b changed
Sent from my HTC Hero using xda premium
Click to expand...
Click to collapse
Ahh, something must be wrong in my vendor tree that makes it compile all those binaries for CDMA...
Testing RegaWMOD 2.1update-1 ROM
After installing RegaWMOD 2.1update-1 ROM and I'm really surprised.
I've tried for about 3 hours without any FC
almost everything works.
Camera: ok
Video: ok
Zoom in camera and video: ok
WIFI: ok
GPS: ok
USB network sharing: ok
WIFI Tether: ok
Led Notifications: ok
Language:Only English
Little bugs
APN: was empty .. but it works after inserting it manually...
I've only been able to authenticate on facebook after updating it with the version of the market
This is the result of Antutu-Benchmark
RAM: 68
CUP integer: 151
Float-point CPU: 13
2D Graphics: 301
3D Graphics: 316
Database IO: 45
Total Score: 1067
CPU Frequency 518
jkballero said:
After installing RegaWMOD 2.1update-1 ROM and I'm really surprised.
I've tried for about 3 hours without any FC
almost everything works.
Camera: ok
Video: ok
Zoom in camera and video: ok
WIFI: ok
GPS: ok
USB network sharing: ok
WIFI Tether: ok
Led Notifications: ok
Language:Only English
Little bugs
APN: was empty .. but it works after inserting it manually...
I've only been able to authenticate on facebook after updating it with the version of the market
This is the result of Antutu-Benchmark
RAM: 68
CUP integer: 151
Float-point CPU: 13
2D Graphics: 301
3D Graphics: 316
Database IO: 45
Total Score: 1067
CPU Frequency 518
Click to expand...
Click to collapse
Hmm I guess they r pretty minor bugs any more reviews on this build?
Sent from my Hero using xda premium
Installed RegawMod rom.
At first it was pretty slow and laggy. I kept getting a FC stating OMADM was not working..... seems to have stopped after setting up.Seems to speed up a bit after 20 mins use. I have also clocked from the 518 up to my usual 652 and it made a big difference.
Wifi works, Camcorder and camera work. Market is old but works. No problems installing anything. Felt very much like my original stock 2.1..... I didnt keep that for long.
I would suggest Rose v* feels faster and definitely looks a lot better.
Just installed Endomondo which has been an issue recently for me. No problem from the market and it quickly got a good GPS lock.
I cant really comment on tethering as I dont ever use it.
USB links to my Win7 laptop quickly. Actually... all feels pretty quick now..... but for me no where near quick enough to warrant a return from a well polished GB rom.
---------- Post added at 11:17 PM ---------- Previous post was at 11:16 PM ----------
OK. Installed TeamHeroC build using the 20110613 gapps
All feels very familiar as I use Decked Up For Life as my daily rom.
Installed with no issues, personalised ok, No problems at all with apps.
CPU runs from the box at 576 so I set to 652 as usual. Benefits from Fly13 kernel so Smartass V2 is my option.
Market is old version from this gapps but found and installed apps quickly.
Wifi set up quickly, GPS got an instant fix with endomondo app.
USB links to my Win7 laptop quickly.
All in all.... this feels the same as all the decked roms.
Not quite as fast perhaps but I'm comparing it to my daily use which is tweaked a lot.
Good rom
Well I am gonna check out this RegaqMOD one. And see what I can do with it
---------- Post added at 01:03 AM ---------- Previous post was at 12:33 AM ----------
Ok well I ofc changed the package and removed all the Sprint stuff that well is useless for me. and I am booting it now.
Changes I made so far
-FlyKernel 13 in it as default
-Superuser 3.0.5 (or 6 XD )
-Other boot animation (Not really a Geregirl
-Some small build.prob edits
-Added Maps. The latest. From the heroine topic. Wonder how that one works.
-Added very few ringtones
-New market and removed marketupdater.
That was about it, I did not even remove social crap. And I even hate that.
And I am suprised it is booting. The way I did it was well messy XD
Ok ended in bootloop XD
Now on Try 2
---------- Post added at 01:24 AM ---------- Previous post was at 01:03 AM ----------
Ok it is booted. Gonna continue on it tomorow.
Booted. the theme looks weird. it has 1.5 android aspects and some other espresso parts, Don't know if I really like that but then agian I can easely install the normal theme from the reg topic but I will see what I will do with this tomorow. No FC's and stuff so far. its faster then Kimera. And well its nice XD
Lirasina said:
Well I am gonna check out this RegaqMOD one. And see what I can do with it
---------- Post added at 01:03 AM ---------- Previous post was at 12:33 AM ----------
Ok well I ofc changed the package and removed all the Sprint stuff that well is useless for me. and I am booting it now.
Changes I made so far
-FlyKernel 13 in it as default
-Superuser 3.0.5 (or 6 XD )
-Other boot animation (Not really a Geregirl
-Some small build.prob edits
-Added Maps. The latest. From the heroine topic. Wonder how that one works.
-Added very few ringtones
-New market and removed marketupdater.
That was about it, I did not even remove social crap. And I even hate that.
And I am suprised it is booting. The way I did it was well messy XD
Ok ended in bootloop XD
Now on Try 2
---------- Post added at 01:24 AM ---------- Previous post was at 01:03 AM ----------
Ok it is booted. Gonna continue on it tomorow.
Booted. the theme looks weird. it has 1.5 android aspects and some other espresso parts, Don't know if I really like that but then agian I can easely install the normal theme from the reg topic but I will see what I will do with this tomorow. No FC's and stuff so far. its faster then Kimera. And well its nice XD
Click to expand...
Click to collapse
Faster than kimera? xD
Sent from my Hero using xda premium
bharat_goku said:
Faster than kimera? xD
Sent from my Hero using xda premium
Click to expand...
Click to collapse
Yes.
But one problem XD When I want to dial a number it smashes a 1 in front of it... And me no like that.. XD
Check call settings n disable home dialing ,should do the trick,how's ur rom running otherwise???any chance of a release?
Sent from my Hero using xda premium
bharat_goku said:
Check call settings n disable home dialing ,should do the trick,how's ur rom running otherwise???any chance of a release?
Sent from my Hero using xda premium
Click to expand...
Click to collapse
Well I could release it. But then again. It is almost like all the other sense roms. And Heroine beats it head on. So if you like a fast 2.1 rom. Go for that one XD I could release a basic theme for it. so it looks a little like this one. Not that it will look 100% the same cuss that one is Odexed.
But yea I can release one. If people like that XD
Just asked I won't use it though
M happy wit my decked build or rose fr sense
I just thought this is a complete 2.1package n ppl might like it,ur choice anyhow
Sent from my Hero using xda premium
bharat_goku said:
Just asked I won't use it though
M happy wit my decked build or rose fr sense
I just thought this is a complete 2.1package n ppl might like it,ur choice anyhow
Sent from my Hero using xda premium
Click to expand...
Click to collapse
The reason why it is so fast. cuss lots of HTC stuff aint in it. So that is a minus. It was a nice test but for my taste it is not worth it to post it up I am on Heroine now and I am happy with it for now. Need a working phone for the next couple of days
@Bharat_Goku, just a suggestion. Maybe it wouldn't be bad if you tried to port some froyo edition from CDMA forum. I mean, if GB is lot faster than current ports from GSM forum then froyo could be blazingly fast . Of course if you got time
Cheers
I have been looking at the difference from CDMA roms and GSM. And well I think 99% is placebo effect why people think it is faster. If someone says. its faster :O well yea noo XD I ran a GB CM7 nightly and well it ran at the same speed as Decked. and well SFM rans a little faster then Rose. mostly cuss Rose has more crap in it (no pun intended). Speedmachine is the fastest Froyo rom we got for the Hero and faster then that is like not possible in my eyes.
Lirasina said:
I have been looking at the difference from CDMA roms and GSM. And well I think 99% is placebo effect why people think it is faster. If someone says. its faster :O well yea noo XD I ran a GB CM7 nightly and well it ran at the same speed as Decked. and well SFM rans a little faster then Rose. mostly cuss Rose has more crap in it (no pun intended). Speedmachine is the fastest Froyo rom we got for the Hero and faster then that is like not possible in my eyes.
Click to expand...
Click to collapse
different opinions from different people I guess. from my personal experience on my phone with my style of usage:
- floyo 1.2 is fastest froyo rom, speedmachine isn't all THAT fast but is a very nice rom all the same.
- cm7 is noticeably slower than decked gb, for example. I tried ele's "custom" gb rom last week - it wasn't any where as quick and responsive as decked, in fact SFM is faster than it when running launcher pro with the same config in each rom (yes sfm is sense but I run LP on it and it's super fast).
but besides that I definitely do agree in placebo effect - it's happened to us all at times. it's human nature. but for some reason cdma roms have long since solved the cm slowdowns in froyo and gb and the gb responsiveness issues that otherwise plagued the gsm developed roms.
Keep in mind it isn't really cdma developed roms that are faster than gsm.
It's roms that were developed by super experienced developers or teams and released for several different models of phones. For example, sfm is super fast and it was developed by a really experienced guy who devs for several platforms (or at least for his own platform and then ports it to several other platforms and tries to support them), not just the hero. so it's no surprise that it's such a solid rom. and most other gb sense roms use some of SFM's code apparently.
Same with roms like decked... I don't believe decked is based on an original cdma hero rom. I think it's based upon a gb aosp-style rom (with a few cm pieces included) that was made for several phones. So again, with a team like that behind the rom there's no surprise that they can get further than we can here with single solitary yet very hard working and clever people like erasmux, elelinux, jieehd, Riemer, etc and of course our Lira.
I dont buy fully into the placebo effect.
There is a definite difference from one rom to another. Switching between rom backups to run them for a while only re-afirms to me that each rom has its characteristics, good and bad.
On top of that, each one of us will use different apps for clocks, I use a lot of widgets over 7 screens, live weather, emails, etc etc and and A.N Other will only have 3 home screens with a few shortcuts and an analogue clock.
Other sociable people will have friendstraem running all day with Twatter n all the other kak..... Then there's gamers (who have no friends)
I setup every rom the same.... (sense roms differently obviously) so I can see them operate on a level playing field.
What I'm saying I suppose is that in answer to peoples asking "Is Rom X faster than Rom Y............ How does this compare to that.....?".... Install it..... set it up and YOU tell US if its faster for you.
----------
Code:
25/1/13
N3
Bluetooth Updated
Grab the new kernel for sdcard fix
-------------------------------------
23/1/13
N2 (NIGHTLY2)
WIFI fixed
Audio Fixed
-------------------------------------
23/1/13
2nd build
sd fixed up
-------------------------------------
23/1/13
1st build everything is fuked
Any Off topic will be met with me raging at you and getting your post deleted
Ok this section is the F&Q so if anyone ask's me a question that's been listed here, you'll be ignored.
Q:I cant find all my stuff on the sdcard, where is it?
A: It's in the 0 folder, it's advisable to move all of your stuff to the 0 folder before flashing.
Q:Where's developer options gone?
A: Go to about phone and bash Build Number until it says "you are now a developer"
Q:I flashed your rom and all of my sdcard stuff is gone..I HATE YOU!
A: Did you move it to 0 before hand?.
Q:DO i need to full wipe?
A: YES!
Q. OMG this rom sucks
A. Not my problem
Q. X Rom has X feature, can you put it in?
A. No
sdcard is working, i'll put it in the next build, i'll throw builds out everyday as "nightlies" also guys
LOGCATS OR THE BUG DOES NOT EXIST
Sdcard working build uploaded
Just popping in here to say that it is good to have you although you don't have the device and I am up for any testing if you want any.
Also I will test this soon!
Good Luck with this....,
Shubham.
Re: [ROM] WIP EverVolv 4.2 PrimoU
Lloir said:
sdcard is working, i'll put it in the next build, i'll throw builds out everyday as "nightlies" also guys
LOGCATS OR THE BUG DOES NOT EXIST
Click to expand...
Click to collapse
I never get tired of hearing that
Sent from my One V using xda premium
First of all, there are some issues that stops this rom to be a daily driver. I only tested for a small amount of time due to the fact that i was in a rush to go to work. What I've tested, I guess I covered almost all important parts. There is one issue I couldn't make a logcat for it because I was running out of time but that should be easy to do - the sound.
Second of all, although this is 4.2, who said that 4.2 will not run well on our small device - he is wrong. This boy is capable of running 4.2 with stock speeds - 245 mhz min, 1024 mhz max - at a respectable smoothness. I was amazed how well it moves considering that this is the very first build. There are things that work and others that don't. The largest issue of all is the sound. Why? Because, leaving apart the fact that you can't hear UI sounds, media sounds, the biggest of all is that - you can't hear anything when you call someone and the other person doesn't hear you back as well. GSM is working, celullar data is working well - tested with the stock browser.
Here are a few things that doesn't work so far:
Menu - Manage apps - Slide to SD Card apps AND Settings - Apps are crashing both at the same location - SD Card apps.
Here is a logcat for Menu - manage apps - Slide to SDcard:
View attachment logcat.txt
Here is a logcat for Settings - Apps
View attachment settingsappscrash.txt
As we managed to do 4.1 in the past and even 4.0, we encountered issues with WIFI and bluetooth - Not turning ON. This issue occurs again in this build - It SHOULD be an easy fix to do, i guess.
Here is the logcat for WIFI:
View attachment wifinotworking.txt
Code:
E/WifiHW ( 1885): Supplicant not running, cannot connect
E/WifiHW ( 1885): Supplicant not running, cannot connect
E/WifiStateMachine( 1885): Failed to setup control channel, restart supplicant
D/SoftapController( 1482): Softap fwReload - Ok
D/CommandListener( 1482): Setting iface cfg
D/CommandListener( 1482): Trying to bring down wlan0
E/WifiHW ( 1885): Unable to open connection to supplicant on "wlan0": No such file or directory
I/wpa_supplicant( 3950): Successfully initialized wpa_supplicant
E/wpa_supplicant( 3950): wlan0: Unsupported driver 'nl80211'
Here is the logcat for Bluetooth:
View attachment bluetoothnotworking.txt
As I've said, the sound doesn't work at all. I will make a logcat today, when sdk is downloading at my work place (currently downloading at 40 kb/s) if someone doesn't do it before me.
Another small and minor issue is the following behavior - Mount your SDCARD - everthing works as normal - when the sdcard is mounted, you can notice that the text for the radio button to mount the sdcard says "Mount your sdcard". This is a very minor issue and it can be fixed easily if it is only a textbox to be changed in "unmount your sdcard". (ONE TIME ISSUE)
Will continue to investigate the build today - doing some video playback and other things that i didn't tried but so far and I mean it, it works flawlessly.
LATER EDIT:
Found out a little more issues while I was going through the logcat for Wifi:
CAMERA - Doesn't work - Module couldn't be loaded:
Code:
V/CameraHolder( 3075): open camera 0
E/CameraService( 3567): Camera HAL module not loaded
E/CameraHolder( 3075): fail to connect Camera
E/CameraHolder( 3075): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 3075): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 3075): at android.hardware.Camera.<init>(Camera.java:340)
E/CameraHolder( 3075): at android.hardware.Camera.open(Camera.java:302)
E/CameraHolder( 3075): at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
E/CameraHolder( 3075): at com.android.camera.CameraHolder.open(CameraHolder.java:210)
E/CameraHolder( 3075): at com.android.camera.Util.openCamera(Util.java:358)
E/CameraHolder( 3075): at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:327)
V/StateManager( 3075): startState class com.android.gallery3d.app.PhotoPage
Screenshot couldn't be saved - Something with SDcard issue - Maybe a path or a super user issue? (logcat coming soon)
Gallery could not load photos - External storage not mount error (logcat coming soon)
Trying to go to Camera from the lockscreen by sliding right - "Unfortunately, Gallery has stopped"(logcat should be the one above).
Other issues:
Lockscreen freezes while phone is connected with a usb cable to your PC (not in mount option)
SDCARD is not visible within gallery, file managers etc.
Toolbox - Interface - Tablet & DPI - Custom display density - Not sticking after a reboot
Thank you for a well done job, Lloir.
Your friend,
1ce.
Re: [ROM] WIP EverVolv 4.2 PrimoU
Really good mate...keep up the good work
Sent from my One V using xda premium
Re: [ROM] WIP EverVolv 4.2 PrimoU
Omg ice that's a very nice bug report.. I'll try to come up to your standards
Sent from my One V using xda app-developers app
Nightly\Experimental link updated grab that build and let me know what works\doesn't work
-Lloir
Kernel?
Very good job with the slim bean, lloir. Now, the JB 4.2 . It's the foot.
I'm ready to try it. But I can' t find the kernel. When I try to download, I arrive on a page with a very very long text but not on a boot.img. have I made a mistake?
Thank's a lot for all your hard work
patgou.007 said:
Very good job with the slim bean, lloir. Now, the JB 4.2 . It's the foot.
I'm ready to try it. But I can' t find the kernel. When I try to download, I arrive on a page with a very very long text but not on a boot.img. have I made a mistake?
Thank's a lot for all your hard work
Click to expand...
Click to collapse
the kernel is in the OP....kind of hard to miss it.........
Guys KEEP off topic posts out of this thread, this is DEVELOPMENT
patgou.007 said:
Very good job with the slim bean, lloir. Now, the JB 4.2 . It's the foot.
I'm ready to try it. But I can' t find the kernel. When I try to download, I arrive on a page with a very very long text but not on a boot.img. have I made a mistake?
Thank's a lot for all your hard work
Click to expand...
Click to collapse
The same happened for me a couple of times. Try right clicking on the link to kernel and save linked file as...
Re: [ROM] WIP EverVolv 4.2 PrimoU
want to make a logcat about the phone dialer lagging, how to specific the logcat?
Sent from my One V using xda app-developers app
ryanlow134 said:
want to make a logcat about the phone dialer lagging, how to specific the logcat?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
Code:
http://forum.xda-developers.com/showthread.php?t=1987232
Re: [ROM] WIP EverVolv 4.2 PrimoU
@ryanlow134:while the logcat is running,open the dialer and fiddle around.once done,save it.
Sent from my One V using xda app-developers app
N2 is up...let me know if display is refixed and if audio works
Lloir said:
N2 is up...let me know if display is refixed and if audio works
Click to expand...
Click to collapse
N2, you mean nightlies?
sorry for extreme noob question
Hi,
Is there any mod for increasing maximum sound volume?
Im looking for the exact same thing. Have tried suggestions of using Viper but to be fair I dont find it does alot. Need a proper solution like they had on the S4 and on my HTC One.
viperFX 10.1(2014) working solution KK 4.4.3
Viper is amazing. I've been using it for about 1 year under 4.3 .. i consider it one of the essential apps for my 10.1 (2014).. But when i upgraded to 4.4.2 I could not install.. I tried all the basic comobinatios (install busy-box first..then SU, flash SU then install buxybox install driver, ok install SU then flash viper, then blah blah ) the error message was always the same.. "you don't have a full-root, or your busy-box is not correct/complete" or some such.... I'm sure the developer is not trying to be deceptive, but these error messages were not that helpful, indeed this is just a symptom of many possible issues. SO I decided to dig in and sort it, took awhile , but I'm posting my very long winded howto..In case others might have this specific issuue you will know if ou read this..and (hopefully) you can fix your viper too.
(0) My kit: samsung/lt033g:4.4.2/KOT49H/P601XXUCNJ5:hanspampel Linux version 3.4.39-3098518 xkat-3.0 ROOTED . Cool ROM, but I at first since I had no cluse, I wondered if this inability to install V was due to this R..I tried antoher hydronium-ROM same prob, scratch that.Next I started reading, and I discovered to my horror this symptom has been reported many places, I found countless solutions in various posts not very helpful but entertaining something like "flash this file, then flash this, then dude enable this and then DUDE ITs AWESOME sounds KILLER BRO.." .. The rpint is that this one symptom has many different underlying causes, no one has explained (or I have not seen a post) yet that does that. so that is what you are geting here.
(1) installing viper (standard way the way you have done it) app store, or click on apk never worked..What is partial root anyway? doesn't matter.. So my stragety here is , when I"m lost in this situation, I have two things to look at..
debug (logcat -vv time ) or
specifc level of debug logitE='logcat -v time process tag *:E' (i put this under /system/etc/mksh after remountin /system RW so I can have a decent working environment.. And or figure out what the apk was having trouble with..So get a copy of the apk . first you might see a zip file ViPER4Android_FX_v2340.zip. this contains two files
ViPER4Android_FX_A2.3.apk (XHiFi)
ViPER4Android_FX_A4.x.apk (effects)
I've always used the FX_A4 version before, I don't really know what the A2.3 is.. anad have a look.
(2) Looking at the APK. Apk's are just zip files. change the .apk extension to .zip and unzip it on your PC (by the way it helps to have adb working, but it is not required).. In the apk for viper I saw directories.. an assets, lib and res dir to be exact I haven't developed anythig on android yet mostly xcoder person. so I was clueless.. but you can work out by the directory's what its trying to do..The top level dirs were res, lib, assets and META-INF, I don't care about the UI stuff in META or res, that was working, in otherwords when we installed the apk, you see the VIPER user interface installs and launches..Its at that point you are asked to install the drivers to get viper to work, so we know the UI is OK and the SU thing make me suspect permissons.. BY the way there was conversation about SE_Linux regarding this install..(permissive / enforcing). I tried that too, so since KK 4.4.3 , SE_Linux was made to be in enforcing mode, before it was just permissive (sending warnings but did not deny any thing)..Now SE_Linux is for real,, If you look at the app-permissions, not file permissions but app permission of VIper there was one funny permissions issue.. "PERMISSION_ACCESS_SUPERUSER" " was unknown. I thoguht maybe this was it! I got "SELiuxModeChanger" (this needs root but apparently can change SE_LIN back to permissive.. its not clear if it really wokred) but I tried it..switched my phone back to permissive mode but i still got the same error.Even after rebooting.. and I set the notificagion "You are In PERMISSSIVE mode" but you open the app and it's in enforcing.. (smell some cheese here..?) .
Sorry for the side traack.. back to the APK, So the apk had a lib directory, an assett directory, are what we are intereseted in.. also I saw on the web there were two system files that needed modifying:
/system/etc/audio_policy.conf /vendor/etc/audio_effects.conf
So know I knew I have to manually place some lib (librarys) and modify some system files.. After rebooting at this point (with this totally broken install) "logcat -v time | grep -i viper
4111): Jni library status = false..
if you look on the apk:
lib/armeabi/libV4AJniUtils.so*
so the system is complaiing about a JNL lib is missing, which means the system files or a system file was modified so the sysem knows to look for the jnl file, and this jnl file is pert of the install which failed..... So plop libV4AJniUtils.so* /system/lib. (via any means you choose) FiLE permissions to 644 "chmod 644 libV4AJniUtils.so* reboot and clean cleared cache(s) in recovery , then rebooted and volla one small step:
I/ViPER4Android( 4111): Jni library status = true
So YOU must see the message as part of the criterial for successful install.
but I still had probelms..
0I/ViPER4Android( 4111): Starting service, reason
I/ViPER4Android( 4111): Check driver
I/ViPER4Android( 4111): Found 13 effects
I/ViPER4Android( 3744): ViPER4Android engine not found, create empty service
04-12 19:57:55.374 I/ViPER4Android( 3744): Service:nStartCommand [Begin check driver]
04-12 19:57:55.374 E/ViPER4Android( 3744): Service:nStartCommand [V4A Engine not found]
I/ViPER4Android( 4111): could not find ViPER4Android engine at 13..
So we are still missing a lib, the viperEngine.. that probably one of the files located in the assets dir..
[email protected] 10 mikel staff - 340B 11 Apr 06:42 ../
[email protected] 1 mikel staff - 926K 12 Feb 11:15 libv4a_fx_ics_X86.so*
[email protected] 1 mikel staff - 810K 12 Feb 11:15 libv4a_fx_jb_NEON.so*
[email protected] 1 mikel staff - 814K 12 Feb 11:15 libv4a_fx_jb_NEON_HQ.so*
[email protected] 1 mikel staff - 810K 12 Feb 11:15 libv4a_fx_jb_NEON_SQ.so*
[email protected] 1 mikel staff - 554K 12 Feb 11:15 libv4a_fx_jb_NOVFP.so*
[email protected] 1 mikel staff - 818K 12 Feb 11:15 libv4a_fx_jb_VFP.so*
[email protected] 1 mikel staff - 926K 12 Feb 11:15 libv4a_fx_jb_X86.so*
[email protected] 1 mikel staff - 923K 12 Feb 11:15 ViPERDDC.db*
[email protected] 1 mikel staff - 810K 12 Feb 11:15 libv4a_fx_ics_NEON.so*
[email protected] 1 mikel staff - 814K 12 Feb 11:15 libv4a_fx_ics_NEON_HQ.so*
[email protected] 1 mikel staff - 810K 12 Feb 11:15 libv4a_fx_ics_NEON_SQ.so*
[email protected] 1 mikel staff - 554K 12 Feb 11:15 libv4a_fx_ics_NOVFP.so*
[email protected] 1 mikel staff - 818K 12 Feb 11:15 libv4a_fx_ics_VFP.so*
[email protected] 1 mikel staff - 16B 10 Feb 15:37 ver.txt*
(3) finish intsall
I don't know what to do with any of those files.. and I don't know what chanegs need gto be made to the .conf files.. this version of the driver I can't find anything that looks like a script.. it must be hidden in the install stuff somewhreer.. stuck..so where do you go when you are stuck?
xda-developers of course..and usually someone will have said something..Many people had alot of posts (because viperFX is so kick ass everyone wanted to get it to work). Yes all the posts about my problem were so last year.. well what I say I'm slow.. and none of them could explain to me exactly how to get it to work... I saw one post that had some zip files:
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
This is the lollipop viper for nexus.. not my phone, but it had lots of conversation. Remember I am on Kit Kat so my story differs, regardless I read along and found 3 zip files:
Viper4A-_Build.Prop-Tweaks_-CWM.zip
Viper4A-_Soundfix-LibFiles_-CWM.zip
viper_v2.3.3.0.zip
I did not put a link to the files because you don't need these files, I just used them to understand how to get 2.3.4.0 to work. So if you want to down load these files, you have to find them, because if you install them on anytying but the proper device it will bric your phone (hang it..)
However they were useful, because they showed me:
audio_effects.conf.txt*
audio_policy.conf.txt*
/system/lib/soundfx/libv4a_fx_ics.so*
how the install was supposed to look like.
The fact that I had files designed for CM mod, means I am at rrisk for BRIC-OLA.. but I had no intention of using any of the binaries, I just used the conf files to modify my sysem comf files.. If you do a diff you can see the changes..the big for me was the engine location:
/system/vendor/etc/audio_effects.conf
ibraries {
v4a_fx {
path /system/lib/soundfx/libv4a_fx_ics.so
}
bundle {
path /system/lib/soundfx/libbundlewrapper.so
}
...
I knew where to put the enginelib. However none of my lib in the apk/asset dir were of the name libv4a_fx_ics.so Well looking back at the logs I saw an message (I did not save it) that said from the viper install something like "CPU IS NEON xxx, CHoosing Driver libxxx" so I was able to see what lib the viper install would have chosen.. what about HQ/SQ naming? I remembered that we have 3 choices to install the driver, basic or low battery drain, high, and super..we have 3 ibs nohting HQ (highQuality) andSQ (SuperDuperQuality).. so thats how that works..I went ahead and pushed the ibv4a_fx_jb_NEON_HQ.so* /system/lib/soundfx dir..renamed the lib to libv4A_fx_ics.so changed file permissions to 644.. and rebooted. It worked sorta..
I saw this:
Check driver
04-11 10:31:09.970 I/ViPER4Android( 4111): Main activity onResume()
04-11 10:31:09.970 I/ViPER4Android( 4111): onResume(), Binding service ...
04-11 10:31:10.005 I/ViPER4Android( 4111): Query ViPER4Android engine ...
04-11 10:31:10.010 I/ViPER4Android( 4111): Found 13 effects
04-11 10:31:10.010 I/ViPER4Android( 4111): [1], SoundAlive, Samsung
....
04-11 10:31:10.015 I/ViPER4Android( 4111): Android System this driver not supported
found ViPER4Android engine at 13
Service:nStartCommand [V4A Engine not found]
I/ViPER4Android( 4111): could not find ViPER4Android engine at 13..
So.. viper driver was being rejected? I tried a few others.. same message.. then I rememberd that I was not clearing the cache .. so I tried again after claering the cache and I got this:
I/ViPER4Android( 4111): Perfect, found ViPER4Android engine at 13
I/ViPER4Android( 4111): The version of ViPER4Android engine is 2.3.4.0
I/ViPER4Android_v2( 2291): Welcome to ViPER4Android driver [Happy new year!]
I/ViPER4Android_v2( 2291): ViPER4Android is normal audio quality mode
I/ViPER4Android_v2( 2291): Use 24bit fixed point calculating arch, round res
THis is the second message YOU must have for VIPER to work on your phone.
OK everything is great! I rebooted turned on my favorite music (RUSH 2112) and what do you know.. it didn't work. Opening Viper and checking the driver status, it said "not enabled" but it was installed.. WTF.?.It did have power, but still nothing..So I remembered reading that someone their bluetooth worked, but going through speaker mode did not. I switched to a bluetooth speaker.. and this time I had:
NEON enabled: yes
enabled: yes
process NO
Process NO? but eerything else yes.. How hard are we today..man.. I knew I was close, so i looked in the logs..
AudioPolicyManagerBase( 2291): selectOutputForEffects outputOffloaded 0 outputDeepBuffer 0
04-12 14:33:00.784 V/AudioPolicyManagerBase( 2291): selectOutputForEffects outputOffloaded 0 outputDeepBuffer 0
W/BufferQueue( 2285).ViPER4Android] cancelBuffer: BufferQueue has been abandoned!
Seems like somehow a buffer is not happening.. this is getting alittle deep for me, but there are many different combinations to try (turn on viper first, then music, then bluethooth.. or BT first, music viper..etc) Also happily I have a "music effects" in my settings where I can choose MUSICFX (samsun's binary) or Viper. SO I found that did not do much, but if I killed Viper, then started it (go to the UI) and powered it up) it had processing set to yes) at that point viper works perfectly. I'm not exaclty sure what the buffer issue is, and I have not made changes to my audio_policy file.. I want understand that first.. but good enoght for now.. Finally Hats off to VIperDevelopers.. its hands one of the most amazing music enhancements I have ever heard.. Don't quite know why its such a pill to install.. sorta feels like no one is taking care of the baby.. well this baby rocks.. someone aught to.. (I'll do it!) anyway all I can say is you are genius and Brilliant software / hareware developers.. when i grow up I wanna be just like you guys.. thanks again hope this post help.. Hope I am not posting anything I shouldn't I have never posted to xda before..
When you found a bug when porting a ROM, you can try to fix using
this methods!
Just replace it from Stock ROM to your Custom ROMs.
Bootloop when porting:
/system/lib/libandroid_runtime.so
/system/lib/libandroid_servers.so
/system/lib/libmedia_jni.so
*Repack boot.image
Showing black screen after logo:
\system/lib/libMali.so
Sensors :
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware(folder)
/system/bin/servicemanager
Bluetooth :
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
/system/bin/brcm_patchram_plus
Wifi :
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
/system/bin/netd-> Fix wifi hotspot
/system/lib/libhardwarelegacy.so-> Fix wifi
/system/etc/wifi (folder)
/system/etc/firmware (folder)
Camera :
system/lib/libfeatureio.so-cameranotworking
/system/etc/media_profiles.xml
/system/lib/libcamera.so
/system/lib/liboemcamera.so
\system\lib\hw\camera.default.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcameraprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so
\system\lib\libmhalcontent.so
\system\lib\libmhaldrv.so
\system\lib\libmhalmdp.so
\system\lib\libmhalpipe.so
\system\lib\libmhalscenario.so
\system\lib\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
\system\lib\libOmx*.so-fixcamcoder
\system\lib\libfeatureo.so-fixcamfocus
#camera not working or force close or any other problem
copy all libs starting with /libcam*.so
#Camera showing wrong model in pic property?
Change model in build.prop
Still not working? Replace following file from STOCK to PORT
system/lib/libexif.so
SD card/Memory:
/system/bin/vold
\system\etc\vold.fstab->edit file for swap internal and external
\system\etc\vold.fstab.nand
*Note:If not present leave this. from kitkat4.4.x this file has been moved into boot.img
Storage not mounting:
Decompile framework-res.apk using apk tool or apk multitool and
replace following file from STOCK framework-res.apk to PORT
framework-res.apk
/res/xml/storage_list.xml
GPS:
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen (Haptic):
/system/usr
/system/usr\keylayout\Generic.kl->fixHomeKey
Sim1/2 (RIL):
\system\etc\firmware\modem.img
\system\etc\permission(RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Audio/Sound:
\system\lib\libaudio*.so
Ads:
/system/etc/hosts->replace with new files or use tweak.
Resolution problem:
open build.prop and add following line
ro.sf.lcd_density=240
[ex:240 but your dpi may be different]
Pixalation in video:
Replace following file from STOCK to PORT
system/lib/libvcodecdrv.so
Flipped touch screen:
Replace following files from STOCK to PORT
system/lib/libinput.so
LED not working:
Replace following files from STOCK to PORT
system/lib/libfeatureio.so
Fix Network / 3G Network:
/system / etc/agps_profiles_conf
/system / etc/APNs-conf
/system / etc/epo-conf
/system / etc/spn-conf
/system / etc/virtual-spn-conf-by-efspn
/system / etc/virtual-spn-conf-by-IMSI
#Most of it works.
Need some guides
[email protected]!C said:
When you found a bug when porting a ROM, you can try to fix using
this methods!
Just replace it from Stock ROM to your Custom ROMs.
Bootloop when porting:
/system/lib/libandroid_runtime.so
/system/lib/libandroid_servers.so
/system/lib/libmedia_jni.so
*Repack boot.image
Showing black screen after logo:
\system/lib/libMali.so
Sensors :
/system/bin/akmd*
/system/lib/libsensors.so
/system/lib/libms3c_yamaha.so
/system/etc/firmware(folder)
/system/bin/servicemanager
Bluetooth :
/system/bin/bd_prov
/system/bin/uim*
/system/bin/hcid
/system/bin/bluetooth*
/system/bin/hciattach
/system/bin/sdptool
/system/xbin/hciconfig
/system/bin/brcm_patchram_plus
Wifi :
/system/bin/netcfg
/system/bin/dhcpcd
/system/bin/ifconfig
/system/bin/hostap
/system/bin/hostapd
/system/bin/hostapd_bin
/system/bin/pcscd
/system/bin/wlan*
/system/bin/wpa*
/system/bin/netd-> Fix wifi hotspot
/system/lib/libhardwarelegacy.so-> Fix wifi
/system/etc/wifi (folder)
/system/etc/firmware (folder)
Camera :
system/lib/libfeatureio.so-cameranotworking
/system/etc/media_profiles.xml
/system/lib/libcamera.so
/system/lib/liboemcamera.so
\system\lib\hw\camera.default.so
\system\lib\libcamera_client.so
\system\lib\libcameracustom.so
\system\lib\libcameraprofile.so
\system\lib\libcameraservice.so
\system\lib\libmhal.so
\system\lib\libmhalcontent.so
\system\lib\libmhaldrv.so
\system\lib\libmhalmdp.so
\system\lib\libmhalpipe.so
\system\lib\libmhalscenario.so
\system\lib\libmhalutility.so
\system\etc\permission\android.hardware.camera.front.xml
\system\lib\libOmx*.so-fixcamcoder
\system\lib\libfeatureo.so-fixcamfocus
#camera not working or force close or any other problem
copy all libs starting with /libcam*.so
#Camera showing wrong model in pic property?
Change model in build.prop
Still not working? Replace following file from STOCK to PORT
system/lib/libexif.so
SD card/Memory:
/system/bin/vold
\system\etc\vold.fstab->edit file for swap internal and external
\system\etc\vold.fstab.nand
*Note:If not present leave this. from kitkat4.4.x this file has been moved into boot.img
Storage not mounting:
Decompile framework-res.apk using apk tool or apk multitool and
replace following file from STOCK framework-res.apk to PORT
framework-res.apk
/res/xml/storage_list.xml
GPS:
\system\xbin\libmnlp
/system/etc/gps.conf
Touch Screen (Haptic):
/system/usr
/system/usr\keylayout\Generic.kl->fixHomeKey
Sim1/2 (RIL):
\system\etc\firmware\modem.img
\system\etc\permission(RIL)
/system/bin/stmd
/system/bin/rild*
/system/etc/rril
Audio/Sound:
\system\lib\libaudio*.so
Ads:
/system/etc/hosts->replace with new files or use tweak.
Resolution problem:
open build.prop and add following line
ro.sf.lcd_density=240
[ex:240 but your dpi may be different]
Pixalation in video:
Replace following file from STOCK to PORT
system/lib/libvcodecdrv.so
Flipped touch screen:
Replace following files from STOCK to PORT
system/lib/libinput.so
LED not working:
Replace following files from STOCK to PORT
system/lib/libfeatureio.so
Fix Network / 3G Network:
/system / etc/agps_profiles_conf
/system / etc/APNs-conf
/system / etc/epo-conf
/system / etc/spn-conf
/system / etc/virtual-spn-conf-by-efspn
/system / etc/virtual-spn-conf-by-IMSI
#Most of it works.
Click to expand...
Click to collapse
Why don't you post some Rom Porting Guides.. I Know That There Are Lots Of Them Available Here On XDA But I Tried Them (Result : Stuck on bootanimation or bootloops).:silly:. i mean none of them worked.. if you are having experience with porting Please Put up some porting guides also..:good:
Yeah
mohit sethi said:
Why don't you post some Rom Porting Guides.. I Know That There Are Lots Of Them Available Here On XDA But I Tried Them (Result : Stuck on bootanimation or bootloops).:silly:. i mean none of them worked.. if you are having experience with porting Please Put up some porting guides also..:good:
Click to expand...
Click to collapse
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008
[email protected]!C said:
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008
Click to expand...
Click to collapse
oops sorry for that !
and thanx for guide
Error Loading
matrixex said:
Buddy let's try with some ROMs and this info is very useful I think I will try this with Stock ROM vs liquid smooth lollipop
And here is guide for porting ROM from another device by Rishab Raj
http://forum.xda-developers.com/showthread.php?t=1908008
Oops Someone is already posted this link no prob.
Click to expand...
Click to collapse
Liquid smooth is lollipop based rom......for porting CM13 rom to our jellybean we will need source codes + CM13 device tree and further compiling in ubuntu will give us CM 13 Rom....This method is insane :silly:
Try porting 4.4.x based or 4.1.2 based roms using this guide :good:
mohit sethi said:
Liquid smooth is lollipop based rom......for porting CM13 rom to our jellybean we will need source codes + CM13 device tree and further compiling in ubuntu will give us CM 13 Rom....This method is insane :silly:
Try porting 4.4.x based or 4.1.2 based roms using this guide :good:
Click to expand...
Click to collapse
END
matrixex said:
We already have liquid smooth lollipop by Ahmad hardy just try it.
Click to expand...
Click to collapse
it is the most buggy rom for X/XL
[email protected]!C said:
First things first. Don't quote whole OP.
And the guide I use is this one http://forum.xda-developers.com/showthread.php?t=1908008
Click to expand...
Click to collapse
First thanks for Tips, Let me add this, it'll be very helpful in porting
Nokia X Vendor Files https://github.com/NormandyLP/android_vendor_nokia_normandy
Nokia XL Vendor Files https://github.com/Nokia-xl-legacy/vendor_xl
Is their any way to test the ported rom other than flashing on device
Sent from my Nokia_XL using XDA Free mobile app
There is hissing noise that comes out of the speaker after playing media.
I replaced all audio libs, libcustom_nvram.so
How can i fix it?
zenowaren said:
There is hissing noise that comes out of the speaker after playing media.
I replaced all audio libs, libcustom_nvram.so
How can i fix it?
Click to expand...
Click to collapse
Well, i unpacked stock system.img and flashed via cwm without modifying any files, there is the same problem again. It is not related to port