Related
I cant seem to get any roms to load; when i choose a rom the screen goes blank for a second and then goes back to the rom selection menu. Yes I have tried many many different roms and bios files. and Yes i did have them in the right format. running CM6 test 8. Anybody have any idea what the problem is?
the problem is it is a known fact that psx4droid doesnt work on test 8... try a different rom and try again
Mthodmn101 said:
the problem is it is a known fact that psx4droid doesnt work on test 8... try a different rom and try again
Click to expand...
Click to collapse
I have also tired many different roms same thing happens with all of them.
same here. Only ones I've been able to get "working":
- FF7: runs perfectly
- Tekken3: runs, but very slow
- Metal Gear Solid: boots up the main menu, but nothing after that
- Silent Hill: graphics a lil buggy, stops working after needing to load a new scene
try loading the new leaked 08/01/10 rom, i tried that and it runs fine on mine... eboot pbp roms seem to run a little bit faster than other filetypes.
End0fLine said:
same here. Only ones I've been able to get "working":
- FF7: runs perfectly
- Tekken3: runs, but very slow
- Metal Gear Solid: boots up the main menu, but nothing after that
- Silent Hill: graphics a lil buggy, stops working after needing to load a new scene
Click to expand...
Click to collapse
some games will run better than other... i tried the crash bandicoots and those play fine with a bit of slowdown, MGS doesnt load for anyone... just keep tryin different games
Sorry double post
For those that got Psx to work what Roms are you running?
kizunaencounter said:
I cant seem to get any roms to load; when i choose a rom the screen goes blank for a second and then goes back to the rom selection menu. Yes I have tried many many different roms and bios files. and Yes i did have them in the right format. running CM6 test 8. Anybody have any idea what the problem is?
Click to expand...
Click to collapse
PSX4DROID is NOT compatible with Cyanogenmod-6 Test builds (This will likely be fix in future builds).
I've installed many different ROMS, the only ones that work is Cyanogenmod-6 Nightly builds.
But I stopped using Cyanogenmod-6 for HTC Incredible since Test#8 and since nightly build 7-28-10.
I love the idea that you can use the Wii remote controller to control the emulators, but in its current state, it's too buggy.
Switching to the leaked froyo (leaked on 8/1/10) is probably best, if you don't care for the option to use the Wii remote controller as a bluetooth device.
xstahsie said:
PSX4DROID is NOT compatible with Cyanogenmod-6 Test builds (This will likely be fix in future builds).
I've installed many different ROMS, the only ones that work is Cyanogenmod-6 Nightly builds.
But I stopped using Cyanogenmod-6 for HTC Incredible since Test#8 and since nightly build 7-28-10.
I love the idea that you can use the Wii remote controller to control the emulators, but in its current state, it's too buggy.
Switching to the leaked froyo (leaked on 8/1/10) is probably best, if you don't care for the option to use the Wii remote controller as a bluetooth device.
Click to expand...
Click to collapse
Which nightly build worked for you i tried the newest build but still no luck; does the froyo 8-1-10 leak change the radio at all? can i just flash that rom like i would with any other?
kizunaencounter said:
Which nightly build worked for you i tried the newest build but still no luck; does the froyo 8-1-10 leak change the radio at all? can i just flash that rom like i would with any other?
Click to expand...
Click to collapse
Yeah, you'll need to update your radio. Therefore, your Baseband version will be upgraded to 2.05.00.06.11.
Regarding the nightly build, I believe the last one I used was 7-27-10. (From: http://droidfiend.com/roms/htc-incredible/cyanogenmod-6/ OR http://mirror.kanged.net/cm/nightly/inc/)
Did you make sure that your PSX4DROID has a BIOS file?
xstahsie said:
Yeah, you'll need to update your radio. Therefore, your Baseband version will be upgraded to 2.05.00.06.11.
Regarding the nightly build, I believe the last one I used was 7-27-10. (From: http://droidfiend.com/roms/htc-incredible/cyanogenmod-6/ OR http://mirror.kanged.net/cm/nightly/inc/)
Did you make sure that your PSX4DROID has a BIOS file?
Click to expand...
Click to collapse
Yes i have tired four different bios files nothing and tired three different nightly's still nothing; for the most part i have just giving up on trying to make this work because it doesn't.
Please do a search next time for this, you can add on to information/problems for this application specifically to a thread already made.
More information on this app here - http://forum.xda-developers.com/showthread.php?t=734635
Thread moved to General.
kizunaencounter said:
Yes i have tired four different bios files nothing and tired three different nightly's still nothing; for the most part i have just giving up on trying to make this work because it doesn't.
Click to expand...
Click to collapse
Since you did not mention anything about keeping Bluetooth controller support, I suggest upgrading to the leaked OTA (Froyo ROM). Which would mean updating your radio...
OR, wait a bit cuz HTC is planning to release the official Froyo update but you gottta be careful with that as it will unroot your phone.
The problem is that we're talking about two different ROMs here. The people that are saying use a different ROM are talking about the build on your phone. PSX4Droid doesn't work with CM6 yet.
Try SkyRaider or the 8/1 Leak.
PSX4Droid works well on the 8-1 leak. You shouldn't run it without updating your radio first, though.
Also, if you use a ZeeMote or an MSI BGP100, you can use a bluetooth remote with an HTC Sense phone. You just only have those two choices. Drivers are available in the market. It's called GamePro.
Hello guys. I know this is for Android development while what im posting should be in general section but i want to point out that on certain custom ROM like Darky ROM, when i apply Voodoo lag fix, my wifi connection on the galaxy S stopped working on WPA/WPA2 EAP.
According to a few sites, this is normal in 2.2.1 as the software itself is buggy. I dont experience this on my Motorola Droid running 2.2.1 but on galaxy s, it doesnt work.
I search in this forum but ive found no ans, so i google it. and apparently theres a bug fix for the wpa_supplicant
http://www.dead-end.info/wp-content/uploads/2010/12/wpa_supplicant_froyo_eap.gz
Download this in replace your current one in system/bin/wpa_supplicant.
Credit goes to Cova at http://www.dead-end.info/2010/12/13/samsung-galaxy-s-froyo-wpa_supplicant-fix.
All developers should replace their WPA_supplicant with these in all the 2.2.1 rom and perhaps 2.3 rom too.
Cheers! Now my galaxy S is able to connect to my home network on wpa2!
Hi,
me run Darky v.7 Rom too, and guess what ... no wifi wpa/wpa2 problems here!
so no need to install stuff like this
Yeah. Only for those who have these problem. i have the problem after i enabled voodoo. I tried reflashing clean and then apply darky rom, i dont have tht problem too. but once i enabled voodoo, the problem came. Ures has voodoo on?
yep voodoo enabled! even on /system
Just for Info:
On 2.6.35 / gingerbread the kernel module bcm43XX.ko at /system/modules/ must match the kernel.
It means when you compile a kernel, you've to use the bcm kernel module which will be compiled with these kernel. Otherwise Wifi won't work at all.
It's not possible to flash another kernel without replacing the module.
Hi
Running darkys 8.0 rom and it's not working on the WPA/WPA2 EAP at work. Tried your file change but it did nothing ..
codeworkx said:
Just for Info:
On 2.6.35 / gingerbread the kernel module bcm43XX.ko at /system/modules/ must match the kernel.
It means when you compile a kernel, you've to use the bcm kernel module which will be compiled with these kernel. Otherwise Wifi won't work at all.
It's not possible to flash another kernel without replacing the module.
Click to expand...
Click to collapse
Good info to know.
Thanks codeworkx
Your File is Not Working Here is Working file with how to do it
http://www.emoiz.com/how-to-connect-samsung-galaxy-s-to-ad-hoc-wifi-network
this worked 100%
you neet to root the phone and use root explorer to acces it, replace the file with the new one, good as new
but this files still doesn't work with WPA-EAP access points
On xwjv1, no need this, as I can connect to most wifi network...
Sent from my GT-I9000 using XDA App
Hello!
Since there is a fully working CM7 for Bravo (thanks Quarkx), does anyone know how can I port an existing ROM from Defy (example: WhiteRabbit 1.3 which is based on CM7)?
Anyways, here is the link of TweetyPeety's ROM: WhiteRabbit 1.3
http://forum.xda-developers.com/showthread.php?t=1510063
Thanks!
When I port Defy roms, I start by replacing the radio files with the ones that BravoMotorola posted in an earlier thread, adding in Quarx's camera libraries, editing media_profiles.xml, and editing the build.prop. There are a few apps included with some Defy roms, like Torch and Rom Updater, that are completely incompatible with the Bravo, and they need to be removed (or never used...).
I've attached a CWM compatible zip that removes the Defy radio, Defy camera libraries, Torch, Rom Updater, media_profiles.xml, and build.prop and replaces them with BravoMotorola's radio, Quarx's camera libraries, updated media_profiles.xml, and a CM72 compatible build.prop. I've tested this with various Quarx, Epsylon3, and Maniac103 CM7 nightlies and always had success.
If you want to use this for other Defy roms (not CM7 based) either remove or edit the build.prop accordingly and check\modify the updater-script to ensure it's compatible with the rom you want to use. By modify the updater-script, I mean to either add or remove apk's or libraries your custom rom may or may not have.
The libraries included are for Gingerbread roms and won't work on Froyo or ICS. Don't bother trying cause you'll bootloop at best, flash the sbf at worst. If anyone is interested, I can make a similar patch for Froyo roms, and an ICS patch for radio and apn settings. And don't bother asking about ICS camera, I've tried many, many, many library combos and no camera or bootloop. Your best bet on ICS camera is to donate to Quarx.
Install the included zip AFTER installing your rom.
Good luck on your Defy rom porting.
Newbery ryViewse
I've been using the White Rabbit 1.3 rom for the past 6 hours or so and have really been enjoying it. It does have a few issues though. The apn settings for att are incorrect so it won't connect (same as CM9) and I can't get usb tethering to work at all. At first, the phone recognizes usb as being connected, then when you enable, it instantly disables and the phone will bootloop every 5 minutes or so. Not really bootloop, but it does reset to the boot screen. It really sucks because this is a good rom I'd like to use but usb tethering is a must for me. Other than the tethering issue, this seemed to be stable rom and its worth trying it out.
I've included a patch to fix the camera, apn problems, and an edited build.prop. Install the rom as usuall, reboot to change to 2nd_boot, go to recovery and install the bravopatch-whiterabbit1.3.zip.
Does anybody know which program controls usb tethering? I suspect usb.apk but I'm not sure. Since I haven't had any problems whatsoever with Epsylon3's 20120212 nightly, I'll try using it's usb.apk and hope it works.
I tried upb.apk and usbd from 20120212 with no success, but it did stop the bootloop issue. I also noticed that this rom was based on KANG 20.02. I've never used or ported a KANG rom, so maybe the tethering issue is kang specific? I'll flash a kang rom tomorrow to check.
full
skeevy420 said:
I've been using the White Rabbit 1.3 rom for the past 6 hours or so and have really been enjoying it. It does have a few issues though. The apn settings for att are incorrect so it won't connect (same as CM9) and I can't get usb tethering to work at all. At first, the phone recognizes usb as being connected, then when you enable, it instantly disables and the phone will bootloop every 5 minutes or so. Not really bootloop, but it does reset to the boot screen. It really sucks because this is a good rom I'd like to use but usb tethering is a must for me. Other than the tethering issue, this seemed to be stable rom and its worth trying it out.
I've included a patch to fix the camera, apn problems, and an edited build.prop. Install the rom as usuall, reboot to change to 2nd_boot, go to recovery and install the bravopatch-whiterabbit1.3.zip.
Does anybody know which program controls usb tethering? I suspect usb.apk but I'm not sure. Since I haven't had any problems whatsoever with Epsylon3's 20120212 nightly, I'll try using it's usb.apk and hope it works.
I tried upb.apk and usbd from 20120212 with no success, but it did stop the bootloop issue. I also noticed that this rom was based on KANG 20.02. I've never used or ported a KANG rom, so maybe the tethering issue is kang specific? I'll flash a kang rom tomorrow to check.
Click to expand...
Click to collapse
work full..
Edit
3g and Usb Tethering don't work. My apologies on that. I only use wifi and 3g only when necessary. Data plans suck. Calls work with good signal, not sure about texting, don't really text much.
It's fully working if you don't require usb tethering . The touchscreen in the installer is sometimes unresponsive when pressing the next and previous buttons, but the menu key works as next and back as back. No other issues with the installer. While it may have been wifi and running a lot of crap in a short time as a basic stress test, I thought the battery drained faster than usual.
The rom is worth checking out. I really like its theme and set up more than anything.
Just tried your patch, yet it I get the bad zip, and aborts... any ideas?
Sent from my MB525 using XDA
ianstump said:
Just tried your patch, yet it I get the bad zip, and aborts... any ideas?
Sent from my MB525 using XDA
Click to expand...
Click to collapse
After typing all of the below, I realized I for got to ask--Did you enable signature verification by accident or have a bad download? I've been using the cm72 patch since the day Quarx released a proper bravo rom and haven't ever had a bad zip error, and the white rabbit patch is identical to the cm72 patch other than the build.prop and apns-conf.xml. I'm not sure if it matters, but I've only used the wr patch with the recovery from epyslon3's latest cm72 nightly 0212.
If its the patch for white rabbit, remove the build.prop from the patch and remove the line
"/system/build.prop"); from /META-INF/com/google/android/updater-script. We probably had conflicting installer options. Once you reboot after updating both zips, make sure to boot into 2nd boot like the installer says...although 2nd init booted it up just fine after the initial post-install bootloop last night for me.
You'll also need to edit the build.prop for the camera and device settings with the ones I included. You also need to make sure do delete strings for flash under OLD Tags as well.
I have a habit of editing the build.prop manually before flashing a new rom, and the one in the patch was also the build.prop in the white rabbit rom, both times I installed it.
#///////////////////////////////////////////////
#OLD Tags///////////////////////////////////////
ro.media.capture.maxres=3m
ro.media.capture.classification=classA
ro.workaround.noautofocus=0
#///////////////////////////////////////////////
#[Product Tags]/////////////////////////////////
ro.product.model=MB520
ro.product.brand=MOTO
ro.product.name=MB520_KOBE
ro.product.device=umts_kobe
ro.product.board=kobe
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=omap3
#///////////////////////////////////////////////
#[Build Tags]///////////////////////////////////
ro.build.product=umts_kobe
ro.build.description=umts_kobe_emara-user 2.3.4 4.5.1-134_DFP-74 1313117579 release-keys
ro.build.fingerprint=MOTO/MB520_KOBE/umts_kobe:2.3.4/4.5.1-134_DFP-74/1313117579:user/release-keys
ro.cm.device=kobe
Tried out latest KANG cherry pick today and its usb tethering works, 3g doesn't however. Tried multiple basebands and replacing radio with no luck. The att apn wasn't correct, and fixing didn't help.
Also, the 3g on White Rabbit doesn't work either. Anybody here port a defy cm7 after 0212? Other than these two I really haven't, and I'm wondering if newer defy cm7's are bravo incompatible, glithcy, or just that the KANG cherry picks don't like us.
I've also since downloaded the White Rabbit patch from here and didn't get any zip errors. Here's how I installed if anybody's interested:
reboot recovery
select WhiteRabbitEdition-1.3.zip
English
Install Type->Custom
Rom Options->Full Wipe, Moto Defy MB525, Google Apps, ICS Standard
Tweaks Options->AGPS Version, CM7 Stock, Off, Gingerbread, Standard
Style Options->ExDialer, ADW Launcher, CM7 DSP Manager
No other changes
Exit Installer
apply bravopatch-whiterabbit1.3.zip
reboot to bootmenu
set 2nd_boot to default
reboot to bootloop
remove and insert battery
power on
enjoy
I just realized I downloaded it wrong. Working great! Thanks!
Sent from my MB520 using XDA
Does usb tethering and 3g work? I never had them working with White Rabbit. To be specific, does turning on wifi then using usb tethering work. I use my phone as a wireless nic instead of running an ethernet cable through the house to my linux box. Kinda hard to update debian with no internet.
Ugh miui Pikachu edition works before I try to make camera work then just bootloops... Darn it's such a good rom!
Sent from my MB520 using XDA App
How were you trying to make the camera work?
I've also heard good things about that rom, just haven't bothered trying it yet.
Also, the latest quarx cm7 nightly is pretty stable. Using it now... my earlier cm7 patch works, but a new line in build.prop is needed and the apn-conf.xml from the white rabbit patch is required unless you like setting up the apn each time. Actually, I've had to change\fix the apn-conf.xml for every cm7 nightly after epsylon3's feb 12 nightly. epsylon3's feb 12 nightly is a real good rom to use if you want a good defy rom to use. I used it as my primary rom till quarx's latest 7 and I'm switching to epsylon's tomorrow.
add to build.prop under #Default Network Type
ro.telephony.ril_class=motow3g
skeevy420 said:
How were you trying to make the camera work?
I've also heard good things about that rom, just haven't bothered trying it yet.
Also, the latest quarx cm7 nightly is pretty stable. Using it now... my earlier cm7 patch works, but a new line in build.prop is needed and the apn-conf.xml from the white rabbit patch is required unless you like setting up the apn each time. Actually, I've had to change\fix the apn-conf.xml for every cm7 nightly after epsylon3's feb 12 nightly. epsylon3's feb 12 nightly is a real good rom to use if you want a good defy rom to use. I used it as my primary rom till quarx's latest 7 and I'm switching to epsylon's tomorrow.
add to build.prop under #Default Network Type
ro.telephony.ril_class=motow3g
Click to expand...
Click to collapse
I tried using the CM7 patch that was posted earlier in the thread and it made it stuck at the M logo
Sent from my MB520 using XDA App
That's the problem, that patch was made for cm7 only.
The steps to PORT CAMERA ONLY to any GB ROM.
Does not work with MS2Ginger2.1
Do everything preflash.
Open WhateverRomForDefy.zip in Archive Manager
Under system/etc, delete cameraCalFileDef5m.bin & cameraCalFileDef8m.bin, and replace mot_ise_imager_cfg.bin & media_profiles.xml from cm7 patch
Under system/lib, replace libcamera.so, libcamera_client.so, & libcameraservice.so with the same from cm7 patch.
Edit build.prop for camera like in post 7 under the OLD Tags. While the post is for WR, the camera changes are the same, & all changes are almost at bottom of build.prop. If you can read, you'll see them....
If the above doesn't work, whatever rom your trying is either
That's how I port roms normally. Again this is bare minimum camera. If that doesn't work, you\we're up the that creek with that rom in regards to the camera. FYI, I do all my rom edits with Archive Manager and GEdit\JEdit on Debian Linux. I'm not sure of the Windows alternative (7zip and Notepad++ I'd imagine) cause I haven't used Windows for anything more than SuperOneClick and other Win exclusive\non-wineable apps since XP was released....Win2K was awesome, I miss it.
skeevy420 said:
That's the problem, that patch was made for cm7 only.
The steps to PORT CAMERA ONLY to any GB ROM.
Do everything preflash.
Open WhateverRomForDefy.zip in Archive Manager
Under system/etc, delete cameraCalFileDef5m.bin & cameraCalFileDef8m.bin, and replace mot_ise_imager_cfg.bin & media_profiles.xml from cm7 patch
Under system/lib, replace libcamera.so, libcamera_client.so, & libcameraservice.so with the same from cm7 patch.
Edit build.prop for camera like in post 7 under the OLD Tags. While the post is for WR, the camera changes are the same, & all changes are almost at bottom of build.prop. If you can read, you'll see them....
If the above doesn't work, whatever rom your trying is either
That's how I port roms normally. Again this is bare minimum camera. If that doesn't work, you\we're up the that creek with that rom in regards to the camera. FYI, I do all my rom edits with Archive Manager and GEdit\JEdit on Debian Linux. I'm not sure of the Windows alternative (7zip and Notepad++ I'd imagine) cause I haven't used Windows for anything more than SuperOneClick and other Win exclusive\non-wineable apps since XP was released....Win2K was awesome, I miss it.
Click to expand...
Click to collapse
Thanks man. I will try later.
Sent from my MB520 using XDA App
Any luck? I have some free time today and can make a pikachu patch if necessary. Currently I'm trying out Idiot to port the WR framework over to Epsy's latest nightly.
Why are most of the cool Droid tools windows/dos based? You'd think there'd be more Linux tools for modding a Linux-based os.
skeevy420 said:
Any luck? I have some free time today and can make a pikachu patch if necessary. Currently I'm trying out Idiot to port the WR framework over to Epsy's latest nightly.
Why are most of the cool Droid tools windows/dos based? You'd think there'd be more Linux tools for modding a Linux-based os.
Click to expand...
Click to collapse
If you want you can me a pikachu patch. I won't have time today to try it out
Sent from my MB520 using XDA App
Got busy with MSGinger today.....I'll have a patch up sometime tomorrow.
marquae11 said:
If you want you can me a pikachu patch. I won't have time today to try it out
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
Here ya go. Got busy with real life the past few days. This isn't flashable, but isn't hard to do either.
Instructions:
Open PikachuEdition2.3.2b.zip
Delete boot.img and devtree.img
Replace files under /system with the ones provided
Make sure to delete the *.jordan.so's under /system/lib/hw
Replace updater-script @ /META-INF/com/google/android/updater-script
When Installing:
Install as Defy
Don't use any Defy+ options or settings, some of them change files we just replaced.
Thanks man! You are helping us alot!
i just didn,t wanted to bother dev's every time on development thread so made this one!! found that there are many other threads which are asking questions related to only one ROM cm11....so why don't make only 1 thread and start discussion!!!
Wifi Hotspot Not working in CM 11 build 20131214 by Pawitp.
I just upgraded from build 20131211 to build 20131214 and Found that Wifi hotspot is not working. It shows "Error".
I rebooted phone several times but it didn't worked.
Hotspot was working well in previous version
Does anybody faced this problem?
I tried to post in development thread but since I am a new member I was unable to do so.
Now Downloading Build 20131215.let's see if this reoccurs.
Screenshot Attached.
Thanks.
ashwin77sgg said:
I just upgraded from build 20131211 to build 20131214 and Found that Wifi hotspot is not working. It shows "Error".
I rebooted phone several times but it didn't worked.
Hotspot was working well in previous version
Does anybody faced this problem?
I tried to post in development thread but since I am a new member I was unable to do so.
Now Downloading Build 20131215.let's see if this reoccurs.
Screenshot Attached.
Thanks.
Click to expand...
Click to collapse
same happening in my build too...realized now
latest build might not have that problem !
i asked and pawitp replied that tethering is working in latest build hope i helped!
WiFi not working on build 20131214
raghavsharmaxda said:
i asked and pawitp replied that tethering is working in latest build hope i helped!
Click to expand...
Click to collapse
I just realized WiFi is not working
I hope wifi is fixed in next build too.
ashwin77sgg said:
I just realized WiFi is not working
I hope wifi is fixed in next build too.
Click to expand...
Click to collapse
Wifi is working fine here. Do you use k2wl's evolution kernel?
naufalhadyan said:
Wifi is working fine here. Do you use k2wl's evolution kernel?
Click to expand...
Click to collapse
Yes,You are right.but i didn't flashed any k2wl's kernel
1. I installed the build 20131214 again, wiped cache.
2. after booting wifi was working.
3. I tried to enable Wifi Tethering but again same error.
4. I tried to enable Wifi. But it didn't.
5. I rebooted system and wifi was working.
I am attaching the screenshots.
May be tethering error is causing that.
BTW Thanks for mediafire link for 20131215. Downloading failed 2 times on goo.im link.
Anybody tried Build 20131215 ?
I flashed it over previous one. I noticed that WIFI tethering problem is not gone.
As respected Pawitp said, tethering is fixed in 20131215. then there is possibility that i must be doing wrong
please help. Everything else excluding "Not working" is working.
Again I am not using k2wl's kernel.
Edit:
I cleaned all Data/Cache/Dalvik Cache.
Did a Clean install of 20131215. WIFI Tethering is working fine Now.
ashwin77sgg said:
Anybody tried Build 20131215 ?
I flashed it over previous one. I noticed that WIFI tethering problem is not gone.
As respected Pawitp said, tethering is fixed in 20131215. then there is possibility that i must be doing wrong
please help. Everything else excluding "Not working" is working.
Again I am not using k2wl's kernel.
Edit:
I cleaned all Data/Cache/Dalvik Cache.
Did a Clean install of 20131215. WIFI Tethering is working fine Now.
Click to expand...
Click to collapse
strange, I got it working without a clean install...
as far as per my experience... wifi related and any connectivity related bugs r fixed in latest build......and i dint do clean install too...:what:
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is KITKAT(Android 4.4.4).
Current version: 4.0.0p1
Current Items not working/Buggy
Updated 4-4-14
Bluetooth working --Still a WIP as some devices don't connect
Camera working --Still a WIP as the camcorder records in blue and a few minor issues
home key doesn't turn device on need to use power button--FIXED in the next nightly should be 4-5-2014
Battery draw around 50mA in sleep
Some experience SOD when hotword detect is active
Location service has stopped with Googles update looking into now
You tell me what you find.
4G Models are not currently supported
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(New Site is up Check it out)
Evervolv Bug Tracker: http://bugs.evervolv.com/
(Please have discretion when reporting issues, and be descriptive / helpful. Also understand that we'll have some growing pains with this. So don't expect everything to be perfect.)
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
If you already have evervolv installed you should see this build under testing if you refresh and can download that way.
No more nightlies Moved to 5.0 Lollipop
ev_tenderloin-1-23-15 Last and final for 4.0 -> Fix netflix
FLINTMAN-TWRP-touch-data_media-SELINUX-2.7.1.0-6-7-2014.zip
--This is a flashing TWRP recovery with data/media and SELINUX support. I have tested 100% of the features and everything is working great as far as i can tell. Soo
with that being said. Use at your own risk 8). Make sure you save a backup from your current recovery just in case. BACKUP BACKUP BACKUP
--Broke Vibration as i updated kernel.
Click to expand...
Click to collapse
NOTE: Recommend a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
GAPPS
---These are the gapps i use. You should be able to use any that are KitKat compatible
http://forum.xda-developers.com/showthread.php?t=2397942
Grabbing logcats and dmesg along with last_klog.
These are helpful in figuring out what is going on
Install the sdk in you PC http://developer.android.com/sdk/index.html
Logcat
"adb shell logcat >logcat.txt"
This will run until unplugged or ctrl c and all the content will go into that file
dmesg
"adb shell cat proc/kmsg >dmesg.txt"
This will run until unplugged or ctrl c and all the content will go into that file
Last_klog
"adb shell cat proc/last_klog >lastklog.txt"
This is for if you have a reboot run this right after the device starts back up and it will get me the last dmesg from before it reboot and will help determine the cause of the reboot.
This will help me and everyone that uses this ROM as i can determine the cause of issues.
Thanks
Thank you for the continued HP Touchpad Development and support Flintman.
Cheers:highfive:
Touchpad Toolbox By Jcsullins
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"
[GAPPS][4.4.x/4.3.x] OFFICIAL 0-Day PA-GOOGLE APPS (Use Mini or Micro packages)
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Moody66 said:
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Click to expand...
Click to collapse
I haven't tested as its still a wip from Google. I do have it as broken in the op. But good to know that it boots 8)
Sent from my SCH-I545 using xda app-developers app
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
flintman said:
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
Click to expand...
Click to collapse
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
I have flashed with this recovery about 20 times now and only got the reboot to hang once. I'm looking into it.
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
install xposed + gravitybox. it works like a charm and has this feature and many others.
Sent from my Nexus 4 using Tapatalk
Okay, I am doing something wrong. I have downloaded the recovery multiple times from multiple devices. I have tried installing via TWRP and manually extracting the image to /boot.
Each attempt, I get:
Checking uImage... Invalid Size
BOOT FAILED!
Please SELECT to continue
Any thoughts? I can still load my backup copy of TWRP without issue.
Update:
After purging the other copies of TWRP from /boot, the new version loads without issue. Thanks flintman!
Discovered that the TP 4G not compatible with the test 3.X Kernel yet
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
If we flash your twrp will it remove cwm or add another entry? I've never been able to have two recoveries working. I would much rather not have to use the power button and what not all the time in cwm but want to make sure I'm covered if something goes wrong. Thanks
Sent from my TouchPad using Tapatalk
Due to the limit of the boot directory it will remove all recoveries before installing this one.
Sent from my SCH-I545 using xda app-developers app
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
SteveoSupremo said:
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
Click to expand...
Click to collapse
So I replaced the ulimage in the boot directory and was able to install the 1/10/14 rom. So I guess I needed to search and just try a little more.
anyway -- I think it's a little slower than the first 4.4 version.... Maybe I need to reboot.... thoughts?
steve
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
I am curious. Have you tried turning the 4g off. Like airplane mode then just turning wifi back on? Was thinking of getting one of these models to tinker with.
Moody66 said:
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
Click to expand...
Click to collapse
I think it was because of sync.... it's running smooth now. after I loaded a different set of GAPPS.
Now I have to figure out the camera apk. it would help if I RTFM.... Thanks Flintman for the awesome update!
Which version of gapps is recommended for 01-10-14 version?
New Test build up which fixes vibration
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
Do you think you can get me some dmesg and logcats??