Related
I tried to word the title correctly to establish that I want to ask 2 different questions, but dont want to clutter up the board with 2 separate posts
Please help if you can
1. Kernel
Why do some kernels work with some roms and not others? I have taken a Sprint Rom, ran it through the kitchen, and tried flashing any number of kernels. The only one that works is Zenulators AnyKernel. I know at times only the stock overclocked worked, but I think at certain times I have gotten the no perf lock to work (though that may have been with an NFX Rom, and not one that I created myself). This leads me to ask why would a kernel work for a rom that is built from the same base that I am using, but not on mine? Is dsixda's kitchen not the one everyone uses? I just dont understand why I am limited to one kernel that is not undervolted and overclocked. I would like to put a 768 overclocked, undervolted kernel with this rom, but cant get any to flash. Should I just use the kitchen to "port" the kernel. How does nfinitefx45 get the kernels he posts to work with a Sprint base? Is the kernel edited in some way? Im not calling anyone out, just trying to learn how to get a good kernel to work with my rom.
2. MAJOR issue: when running df, I get an error that etc/mtab: no such file or directory. What I have done is in the paragraph below
I decided to take another cracked at a minimal Sprint 2.1 Rom. I used dsixda kitchen 0.107 to root, add busybox, remove boot sounds, deodex, add data/app, add nano + sysrw, sysro, bash, and zipalign the .7 Rom. I then removed all Sprint apps except for VVM, all google apps, all htc apps and widgets that were not explicity needed (need the contacts and ime apks among a few others), removed a ton of system apps (can provide a list of current system/app dir and a list of all that was removed if it will help). I edited the lockscreen so it wasnt in landscape mode all the time. Added an OMADM.apk file that didnt FC when I tried to update the prl (tested the update and it works). I did find an EPST.apk that adds ## codes back to the dialer (should I include that in the rom...wasnt intending on it as the only ## code that doesnt work is the prl...data works) OMADM.apk is smaller that the EPST...but EPST does exist already...and I might be able to pull OMADM meaning 0 firmware, profile, or prl updates...but you could do ##prl manual...I dont know, still thinking it through. I did end up creating a google apps zip file with the apps from the .7 rom so that market will work (removed maps as it wasnt up to date and the Streets.apk never worked, but left gmail, youtube, voice search to work with jonasl's htc keyboard, and of course gtalk). In doing this, I am thinking about creating some packs for the rom, but really need the above 2 questions answered to find out where to go from here.
evilvoice said:
1. Why do some kernels work with some roms and not others?
2. MAJOR issue: when running df, I get an error that etc/mtab: no such file or directory. What I have done is in the paragraph below
Click to expand...
Click to collapse
afaict, the 'kernels' are literally just the linux kernel that provides some basics to the os... altho linux IS a monolithic kernel, it is not a bsd-system that has all the tools completely-compiled for the system together...
thus, the answer to 2. is that you have deleted too much of the periphery, for instance the actual mount-table system that df uses to to check... (ie: some prog creates the mtab, and apparently it is not the kernel, i guess)
alternatively, the answer to 1. is that there is actually too much in the roms that are using something unique to each kernel that you are trying to install (altho that seems odd to me)... thus, the only way that the rom will work is if you give it the kernel with the tools that it (the rom) needs...
tbh - im not exactly sure - ive not gone into the depths of kernel-swapping that youre trying to explore... in full-linux-systems, the kernel is fairly easy to update without breaking all of the miscellaneous tools - however apparently the android-roms are more tied-together than a normal linux system...
gl and maybe someone with more experience will give an accurate (rather than a guessing) answer...
I was really getting tired of my carrier name showing up twice on the lockscreen and taking up extra real estate on my notification drop-down so I figured out how to disable the SPN from showing and how to customize the PLMN to say whatever I want.
KEY FILES TO EDIT
/data/data/com.android.providers.telephony/optable.db
/system/etc/apns-conf.xml
/system/etc/spn-conf.xml
In the apns-conf.xml make sure your provider is listed with a numeric value.
Here's an example: numeric="311370" mcc="311" mnc="370"
* As you can see the numeric is the MCC plus the MNC.
In the spn-conf.xml make sure your provider is listed with an spnOverride.
Here's an example: <spnOverride numeric="311370" spn_display_rule="SPN_RULE_SHOW_PLMN" spn_override_only_on="310,311"/>
The optable.db needs to be edited with SQLite Database Browser to add your numeric and the text to display.
Here are a few pre-configured downloads:
PLMN: CyanogenMod
http://www.4shared.com/file/BawWWTpv/cm7_plmn_gsm_crespo.html
PLMN: The Ultimate Droid
http://www.4shared.com/file/jo0455rx/tud_plmn_gsm_crespo.html
PLMN: GCI Wireless
http://www.4shared.com/file/l3fZUzGu/gci-apns-plmn.html
PLMN: B*** I Got An Android (with no asterisks)
http://www.4shared.com/file/Vkz6poYC/*****_plmn_gsm_crespo.html
NSFW YouTube Video - B*** I Got An Android
Flash these files AFTER you have flashed a ROM and booted up at least once! I tested all four files on TUD 3.0.0 Beta, CM7 A3, and various CM7 Crackflasher builds.
*Screenshots are from CM7 Crackflasher build #54 with the Jungle Waterfall livewallpaper
Very cool mod. I will try this out when I have the time!
thank you
Love this, it worked great on Bionix with 1.3 kernel. For some reason running the same rom with the new 1.4b kernel it no longer works and yes I tried reflashing and wiping a few times. Any ideas?
Hey could you make me one and either PM me or post it up?
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Did not work on Modaco R9, CM7 or The Cracker builds...
nickmv said:
I'm on CM7 on a Nexus S, and I don't see a '/system/etc/spn-conf.xml' file. It doesn't seem to exist on mine. I'm on the latest nightly (#8) and have updated everything. Am I missing something?
Click to expand...
Click to collapse
spns-conf.xml does not exist on the Nexus S originally, but if you place it in /system/etc/ the OS knows to use it.
nickmv said:
How exactly did you get these files? I'm having all sorts of trouble with this. First off, the optable.db file is zero K, even when I extract it through ASTRO or Root Explorer with R/W permissions. Secondly, as I mentioned in the last post, the 3rd file is missing from the stated directory.
Use the optable.db from my zip and just edit it as you see fit.
I'm really confused, as it seems that none of these instructions add up for a Nexus S. I'd like my T-Mobile message to instead display "Nexus S: Pure Android, Pure Google"
Click to expand...
Click to collapse
I'm not sure what the character limit is but that might be too long.
I have all the files in the proper folders but it still doesn't work. Modaco R9
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
tsalate said:
for those having problems getting this to work try using clockwork and press mount/storage then mount/system. hope this works.
Click to expand...
Click to collapse
You might be on to something, it worked for about 3 seconds then went right back to T-Mobile.
Still doesn't work. Mounted /system and /data. Does it only work for certain carriers? I'm using a&t
Is there a way to apply this to ALL carriers, rather than selecting one manually.
thanks
** Edited: Instructions at the bottom **
I have the Nexus S, and when I upgraded to ICS I found that opening the recent app dialog could take a while.
I wanted the ability to quickly switch to recent apps, so I thought the power and volume up/down buttons combination could be used to do this.
Quickly tapping on the power and volume up/down buttons together brings the previous/next recent app to the front
I prepared a short video to demonstrate (sorry for the lack of interesting audio in the video):
http://youtube.com/watch?v=ndGd2y9ro14
I created this and tested it for about a week.
It works fine, but still needs a bit tweaking and maybe some configuration through the settings screen (enable/disable completely, tapping time, cycle/don't cycle apps).
One major issue is that I believe it is only comfortable when the power and volume keys are located on opposite sides, like on the Nexus S.
This is a small modification to CM9, so I have a few questions maybe you could help:
Is there a way to include features per devices? I saw that the code checks for devices with or without the search button. Is there a way to know which device has the power button on the right? Or do I need to map it before-hand? Which brings me to..
Do you think this is this something worth uploading to CMGerrit for review to be included in CM, maybe enabled as an advanced feature in the settings section?
Do you know any ROM maintainer that would want this feature?
Any suggestions to improve (or drop) this are appreciated, maybe adding an indication of the app switching.
** INSTRUCTION **
Please follow one of the next instructions to get it (whatever suits you):
Install using a flashable zip
Download the attached flashable zip file (quick-switch-0.01-signed.zip), and flash it from recovery.
This is compiled from CM9 RC1. While it may work with later nightlies or other similar ROMs, I cannot guarantee that it does.
To revert, flash your ROM over it.
Install the jar file manually
I've also attached the JAR file so that you could install it manually.
The JAR should replace /system/framework/android.policy.jar
Backup the current one, copy the one from this post over it, clear the dalvik cache, and reboot.
You'll probably need to remount the /system folder so you could write over it (adb remount).
Note: You cannot do this from recovery because recovery doesn't mount /system automatically. To mount /system from recovery just type "mount /system" from "adb shell".
To revert, just copy the JAR from the backup and clear the dalvik cache.
Get the source (Advanced)
I forked the relevant project (android_frameworks_base) on github.
The commit is: https://github.com/lightpriest/andr...mmit/28e2caa1459d9be287d5e0b68b6ca04fee45970d, and it is present both on ics and ics-release branches.
An important note
While this is a nice thing to play around with, I've noticed that the power button started to wear on my device. I'm not 100% sure it's related, but I'll take a "wild" guess that it does. Not to say that the power button doesn't work at all, but I noticed that now sometimes it's enough to just slide a finger on it to actually press it. So, you've been warned
I'll probably make another build for JB, once it gets stable.
Attached files checksum:
quick-switch-0.01-signed.zip - 474e5d53cff57a163f9c24ec8301b2a7
android.policy.jar - eba03024571866fc0161e19484dc200a
youtube.com/watch?v=ndGd2y9ro14
That feature actually looks quite interesting, and usable. Would love it, myself.
I'm not sure whether or not it'd be accepted in CM, since they want their builds to be much more streamlined and easy to understand than GB builds. Who knows though, as I said, it's an interesting feature. There's also the problem with power- and volume keys that wear out. And this mod would no doubt accelerate that.
With that said, I would absolutely love a smali-version guide for this.
Edit: evilisto created a guide on how to map the multitasking button the the search key, which helps a lot. I recommend you check that out.
It is also possible to map the GB taskswitcher to search button. The gb is imo faster than the ics one
yeah its a cooool feature.. but the thing is...jelly bean has got super speedy task switchin even on our nexus s...
I'm not sure on what's the best way.
I can generate a diff of the smali files, and then maybe create a guide out of it.
I also created a signed update zip file, with the JAR that needs to be replaced.
The flashable zip was created from CM9 RC1, do you prefer the zip or the smali?
I'm not yet sure on how to provide this kind of guide smali, because the diff looks quite large.
Updated the post with instructions and notes (at the end).
Amazing work . Though they removed the lag in displaying recent applications in Jelly Bean. Its very snappy now.
Thanks!
I thought it was just a matter of time until the recent app overlay would work faster. From the beginning I considered this as an experiment.
This was just a nice thing to work with (and create), experimenting with the Android building environment and creating a flashable zip..
Learned a lot actually.
Actually, it is a great mod! I like it very much, makes simple two-task switching a breeze (like chatting on GTalk and writing an email simultaneously). Would you consider porting this to JB releases? AdamG's JB-Oxygen will be for sure a popular, stable release. I also think that AOKP team would love to implement your idea in their releases, since they offer feature rich roms.
Here's link to Adam's JB Oxygen : AdamG's JB Oxygen release
Great job lightpriest!
LG O4X UnoX SENSE4 ALPHA RELEASEYou thought you never see a HTC SENSE with BeatsAudio interface on O4X? This is the ALPHA release of SENSE 4.0 (version 2.17.401.2) and using STOCK LG kernel for your LG Optimus 4X HD
Latest update 10.Jan.2013
Changed build to avoid conflict with team venoms mods, this should be more stock now.
It is now a ClockWorkMod Update.zip using AROMA installer.
alot changed and yet, no GSM is working but i am getting closer.
***STATUS***
Click to expand...
Click to collapse
This is very early developer release, more a proof of concept, to help others start porting or even developing roms, without thinking the locked bootloader will limit the distribution. so regular users, will probably not use this for anything since mobile connectivity is not working.
but if you wish to check performance and maybe test some performance here, this is a way to do it and compare.
Any contribution to fixing the RIL driver in this one or other fixes are appreciated, feel free to make patches if you can help improve this.
***WHY***
Click to expand...
Click to collapse
So the O4X community have been almost dead and not a single custom rom has been released, primarily because many believe a unlocked bootloader is needed.
WHAT WORKS
Click to expand...
Click to collapse
GSM Mobile Radio - NO
AUDIO - YES (+ BEATS AUDIO works fine with headset)
PHOTO CAMERA - YES (FRONT is very,very dark, BACK camera is ok)
VIDEO CAMERA - YES (for now only 1080p recording, 1280x720 closes camera, change in settings)
VIDEO PLAYBACK - YES
MICROPHONE - YES
WIFI - YES
GPS - YES
BLUETOOTH - YES (Wifi seems affected by enabling bluetooth at bootup, and no wifi connectivity exists, so disable BT at bootup)
ROTATION - YES
YOUTUBE - YES
MOST SENSORS - YES
VIBRATION - NO
NFC - YES (No icon when activated, but works fine with included NFCtag+)
PC CONNECTION - NO (not worked on it)
INT / EXT SDCARD - YES (without sdcard, camera cannot save to internal storage)
NOTES ON FIRST USE
Click to expand...
Click to collapse
- First start can take 5-6 minutes due to a process waiting for media scanner.
- in /system folder, you can rename "local.prop1" to "local.prop" , and you can enable adb root.
- its based on v10d, i do not know if the boot.img is required, but remove it if you wish to try it without. (remember to edit md5 checksum file if you do)
- do not try and install recovery from the CWM app, just use it to reboot into cwm, do NOT install recovery, its already in place and modified to work with sense.
DOWNLOAD
Click to expand...
Click to collapse
Download full as CWM update.zip ALPHA 1.0 here
Firefox users: Ignore warning, this is just a zip with a backup included, no executables here
great! i will flash i tmr morning and have a taste on sense
Its online now!
2.17.401.2, so it's Android 4.0.4?
reas0n said:
2.17.401.2, so it's Android 4.0.4?
Click to expand...
Click to collapse
yes i believe so, it was based on a onex rom i found, nothing special, but a testrom.
Dexter you are GREAT !!! :good: :good:
THANK YOU !!
Looks amazing!
thank you very much... sense 4 on 4x
can someone make a backup for TWRP recovery??
---------- Post added at 06:51 AM ---------- Previous post was at 06:48 AM ----------
Dexter_nlb said:
Its online now!
Click to expand...
Click to collapse
finally first custom rom for LG4X..how about CM10 on LG4X?? btw, thanks for making first custom rom on our device :good:
razerblade17 said:
can someone make a backup for TWRP recovery??
Click to expand...
Click to collapse
you can modify the existing backup, by editing the nandroid.md5 checksum file, remove the "system.ext4.tar" line in the md5 file
and rename the "system.ext4.tar.a" to "system.ext4.tar" . and of course do the same with the real tar file.
then it should look pretty much like old backups
-------------------------------------------------------------------------------
Update:
after the upload,
i have checked GPS and NFC.
GPS is confirmed working
NFC needed fixing but it works now , althoug icon is gone, and the NFCplus app works too, so you can modify tags
wow NICE!! almost had a mini heart attack when i saw this post!:fingers-crossed:
looking forward to working CALL XDD
THX a lot for ur work!!!
Dexter_nlb said:
you can modify the existing backup, by editing the nandroid.md5 checksum file, remove the "system.ext4.tar" line in the md5 file
and rename the "system.ext4.tar.a" to "system.ext4.tar" . and of course do the same with the real tar file.
then it should look pretty much like old backups
-------------------------------------------------------------------------------
Update:
after the upload,
i have checked GPS and NFC.
GPS is confirmed working
NFC needed fixing but it works now , althoug icon is gone, and the NFCplus app works too, so you can modify tags
Click to expand...
Click to collapse
no luck...btw any other method to install via TWRP recovery?? my sd card has a problem, and no money to buy new one...so any solution to restore this backup??
i've been stuck in the setup wizard for so long now, i managed to get past the language/locale selection screen but I'm stuck in the next screen where venom setup is.
Anyone managed to get past this screen? can i delete setupwizard to bypass this process?
EDIT: finally get past the setup wizard!!! ultra smooth rom!!!
i know this is ALPHA but thought i should post a list of things i found not working so maybe someone can fix it =)
- Vibration not working
- Google Voice Search not working
- mount ext-sdcard not working
- Flashlight not working
- Whatsapp doesn't work (it says "Tablet is not supported" so i guess there's sth wrong with the IMEI or build.prop)
- pressing "settings" in camera app crash the app itself
- "Share" option is unusable (tested both by email and by Google+)
BUT
- Camera app works GREAT with rear camera!!!!!
- most if not all widgets work (though i didn't test all of them, most of them work!!! without a lag)
- Speaker works
tomanlam said:
i've been stuck in the setup wizard for so long now, i managed to get past the language/locale selection screen but I'm stuck in the next screen where venom setup is.
Anyone managed to get past this screen? can i delete setupwizard to bypass this process?
EDIT: finally get past the setup wizard!!! ultra smooth rom!!!
i know this is ALPHA but thought i should post a list of things i found not working so maybe someone can fix it =)
- Vibration not working
- Google Voice Search not working
- mount ext-sdcard not working
- Flashlight not working
- Whatsapp doesn't work (it says "Tablet is not supported" so i guess there's sth wrong with the IMEI or build.prop)
- pressing "settings" in camera app crash the app itself
- "Share" option is unusable (tested both by email and by Google+)
BUT
- Camera app works GREAT with rear camera!!!!!
- most if not all widgets work (though i didn't test all of them, most of them work!!! without a lag)
- Speaker works
Click to expand...
Click to collapse
thanks for the report back, and yes, i am aware of the setup screen bug, it also seems to relate to the customization process hanging in the background, so it will hang for some time too, sorry. porting is not always easy
edit: i believe the problem rely in the SIMcard not being detected as you might note, the simcard screen normally shown is not being shown, which asks to insert sim. it also seems the the firmware seems to tell the htc software it is a CDMA phone, so this might also be the problem why gsm is not working. this is seen in the radio log.
- i noted the other things, and flashlight is the only one i am not looking at, as our flashlight is different and can be damaged if i try to make it like a lightbulb i think. (do not know and do not want to find out)
- we got no IMEI yet, since phone is not working, so the whatsapp might have a different issue or as you say, it does not exist. build.prop is pretty much OneX original here.
- external sdcard works fine here, i wonder why you cannot see it in storage settings?
- i do not know why googlevoice do not work, ill check up on it, probably relate to recording format, which i noted only works with AAC and not AMR format.
Dexter_nlb said:
thanks for the report back, and yes, i am aware of the setup screen bug, it also seems to relate to the customization process hanging in the background, so it will hang for some time too, sorry. porting is not always easy
edit: i believe the problem rely in the SIMcard not being detected as you might note, the simcard screen normally shown is not being shown, which asks to insert sim. it also seems the the firmware seems to tell the htc software it is a CDMA phone, so this might also be the problem why gsm is not working. this is seen in the radio log.
- i noted the other things, and flashlight is the only one i am not looking at, as our flashlight is different and can be damaged if i try to make it like a lightbulb i think. (do not know and do not want to find out)
- we got no IMEI yet, since phone is not working, so the whatsapp might have a different issue or as you say, it does not exist. build.prop is pretty much OneX original here.
- external sdcard works fine here, i wonder why you cannot see it in storage settings?
- i do not know why googlevoice do not work, ill check up on it, probably relate to recording format, which i noted only works with AAC and not AMR format.
Click to expand...
Click to collapse
external sd is not accessible in the default file manager? but if i use another file manager (FX Explorer), i can access the extSD
but in storage settings, everytime i try to unmount the sd, settings.apk crashes
but as an alpha "port" (sort of), the rom is ULTRA-SMOOTH, wish at least GSM call work soon:silly:
tomanlam said:
external sd is not accessible in the default file manager? but if i use another file manager (FX Explorer), i can access the extSD
Click to expand...
Click to collapse
ok i see now.
this the the HTC way of having external sdcard, the semi way, since they officially do no longer make many top models with sdcard.
the location of external sdcard is at /mnt/sdcard2 and internal is /mnt/sdcard
let me check up on the unmounting, i already got some fixes, but not GSM, sorry, that require alot more it seems to fix.
about the GSM part, it is strange that both OneX and O4X uses a radio chipset with QUO 6260 radio, but they flash firmware different ways, so that makes it incompatible somehow.
Great job man!
I will join your development as soon as I finish my exams (2-3 weeks) so the LG 4X community gets alive. Will read your thread in the meantime.
Making a backup now while downloading this rom.
Thank you so much for your time and effort Dexter!
Sense 4.1 is actually pretty smooth on our O4X. Too bad radio is somehow turned off. I would rock this rom as my daily once radio gets solved. But for now, everything else seems to be working. Beats works great too. Camera is good, but video FCs.
babymatteo said:
Sense 4.1 is actually pretty smooth on our O4X. Too bad radio is somehow turned off. I would rock this rom as my daily once radio gets solved. But for now, everything else seems to be working. Beats works great too. Camera is good, but video FCs.
Click to expand...
Click to collapse
getting DRM working little better here, i simply copied the generated RSA keys from /data to a tar file and extract it at every boot, but not sure how i get the lgeril to load it now, since its htc based.
for the camera, i simply use a camera from another htc 4.0.4 release and it works fine. probably related to resolution of camera and it works now recording in 1080p as well.
known bugs:
occasionally modem may take a while to come up. toggle with airplane mode and/or reboot
fixed bugs:
slider/onscreen kb / phys kb issue.
everything else i tested works. wifi, bt, hwc, camera, calls, webtop, etc
releasing as safestrap V3.10 backup for now., might do flashable zip later.
unzip to sdcard, don't overwrite your own backups, and
restore to a clean romslot, haven't tested overwriting any other builds. it might work since it was an ota but who knows?
Link: http://www.mediafire.com/?x9aec82a8xcm4c1
Updated framework-res.apk fixes keyboard issue.
http://www.mediafire.com/file/jfsc35gr40yf8g5/framework-res.apk
to install framework res: mount system of romslot in safestrap make sure it's the right slot
adb push framework-res.apk /system/framework/
adb shell chmod 0644 /system/framework/framework-res.apk
wipe cache and dalvik cache just to be sure, and reboot
please report bugs.
kernel source here: https://github.com/kfazz/kernel_mapphone_kexec/tree/razr_jb
this rom has been superseeded by this: http://forum.xda-developers.com/showthread.php?t=2199741
it's almost exactly the same, but based on D4 JB leak, and everything works.
Is this too good to be true?
Can I ask what specific things on the hardware keyboard isn't working?
captainstarbucs said:
Is this too good to be true?
Can I ask what specific things on the hardware keyboard isn't working?
Click to expand...
Click to collapse
the slider event doesn't trigger that the hw keybaord is out or away, so
with Hardware keyboard turned on: the rom thinks the keyboard is out all the time, onscreen kb doesn't appear
with Hardware kb off: onscreen kb pops up all the time, regardless of whether real kb is in or out, hardware kb still works
the "mapphone switch" device sends the slider event via /dev/input/event5
runing getevent -l /dev/input/event5 shows SW_LID events, they just don't do anything.
i tried editing keyboard bools inside framework-res.apk, but they don't appear to make a difference.
Boooooo motoblur crap... Otherwise nice port! Will stick with cm10.1 for now. We should be getting jb ota soon anyway
Sent from my XT894 using xda app-developers app
Nice work kfazz
MotoBlur or not, this is a GREAT example of the kind of things we can now do on the phones using the new kexec kernel.
Glad to see it's already being put to good use!
Kexec is amazing. More mods should be coming.
Sent from my XT897 using Tapatalk 2
Nice ;] Sounds good iam going to test it
still waiting for a JB release
Edit: it not coming up for me. It start and update the application after that it reboot in boot loop
cannot wait to test this first thing tomorrow. Thanks so much
Could hash use this rom for fixes to the current issues with the JB builds he is working on?
Sent from my Motorola Droid 4 via XDA-developers app
how do we install this? i'm unfamiliar
edit: specifically the framework-res.apk. I'm assuming that for the ROM we just wipe and open it as a backup
FWIW: restored this from SS 3.11 just fine.
Strange issues with my sdcard, but other than that, everything seems to work.
Would love it if someone could make a flashable patch for the framework. My USB cable is touch and go..
Sent from my DROID 4 using Tapatalk 2
huhu1312 said:
Nice ;] Sounds good iam going to test it
still waiting for a JB release
Edit: it not coming up for me. It start and update the application after that it reboot in boot loop
Click to expand...
Click to collapse
did you restore on a a fresh romslot? try wiping data/cache.
Sent from my DROID 4 using xda app-developers app
Well that didn't take long! Good work.
Sent from my XT894 using Tapatalk 2
This ROM also works on GSM with no tweaks other than APNs. Does this mean we can flash any RAZR stock-based ROM or is it more involved than that?
Only problem I have found with it (other than Verizon bloat) is the keymappings for ; and : (normally accessed via Shift + , and .) don't work right, they get you < and > instead. Also the SYM key doesn't work, capslock light doesn't work. I've tried copying over omap4-keypak.kl and .kcm from ICS but it doesn't help, it actually makes things worse.
Also the damn motocast cdrom automount is back, and olegfusion's patch for it doesn't work with this ROM. Will need someone a lot better than me to fix that one!
Here is my GSM variant of this ROM with the following changes:
apns-conf.xml preloaded
framework-res.apk fix pre-applied
"This sim is from an unknown source" error fixed
Verizon crud removed
Misc debloating
Part1: http://www.mediafire.com/?2tcisw2za29wrt7
Part2: http://www.mediafire.com/?m7dfoomkcojejpf
Lum_UK said:
This ROM also works on GSM with no tweaks other than APNs. Does this mean we can flash any RAZR stock-based ROM or is it more involved than that?
Only problem I have found with it (other than Verizon bloat) is the keymappings for ; and : (normally accessed via Shift + , and .) don't work right, they get you < and > instead. Also the SYM key doesn't work, capslock light doesn't work. I've tried copying over omap4-keypak.kl and .kcm from ICS but it doesn't help, it actually makes things worse.
Also the damn motocast cdrom automount is back, and olegfusion's patch for it doesn't work with this ROM. Will need someone a lot better than me to fix that one!
Here is my GSM variant of this ROM with the following changes:
apns-conf.xml preloaded
framework-res.apk fix pre-applied
"This sim is from an unknown source" error fixed
Verizon crud removed
Misc debloating
Part1: http://www.mediafire.com/?2tcisw2za29wrt7
Part2: http://www.mediafire.com/?m7dfoomkcojejpf
Click to expand...
Click to collapse
in order for a rom to work right the kernel driver parts and userspace driver parts for things like pvr and ducati need to be in sync.
ramdisk needs to be extracted and modified for safestrap. kernel modules need to be rebuilt for kexec kernel, frameworks hacks for keyboard need to be done, (there may well still be more of these to do) /system/lib/hw/* libraries need to match boardname. ie (lights.maserati.so instead of lights.spyder.so) build.prop needs to be edited...
it's not entirely trivial, but since i already had a kexec kernel around this only took me ~24 hours.
Edit: if you didn't want to kexec a kernel, you might be able to hack roms based on the same version as whatver your stock kernel is, so ics to ics, etc.
more of a pain to do it that way though.
Ahh, this is all probably somewhat beyond me then, though I am definitely interested in how to extract and modify the ramdisk as that's where I need to modify two files to get rid of the cdrom automount.
For now though, I think this ROM is going to be my daily one, even as I continue to fiddle with it.
Google 'android extract boot.img'
You'll need gunzip and cpio to take apart and mkbootfs and gzip to reassemble. Ramdisk is at /system/etc/kexec/ramdisk.img
Got Sym key working, ; and :, and caps light, just not all at the same time yet.
Sent from my DROID 4 using xda app-developers app
kfazz said:
Google 'android extract boot.img'
You'll need gunzip and cpio to take apart and mkbootfs and gzip to reassemble. Ramdisk is at /system/etc/kexec/ramdisk.img
Got Sym key working, ; and :, and caps light, just not all at the same time yet.
Click to expand...
Click to collapse
It was the location of the ramdisk that was defeating me. Thank you!
I gotta say this is the fastest and smoothest I have ever seen my droid 4 run.
I am far from current on how to install things and never got the framework-res.apk installed. If anyone can make a video on how to install the framework-res.apk I would greatly appreciate it.
Also wondering if there is any plans to use this to improve existing roms like "CM10.1 / Jellybean 4.2.2 for the Droid 4". I have fell in love with all the customization's in that rom.
Please forgive me if I used incorrect terms or said anything that is inappropriate. I really have no idea on how all this works.