An official OTA for GSM Nexus S (GT-i9020T/i9023) is now available:
http://android.clients.google.com/packages/ota/google_crespo/9ZGgDXDi.zip (thanks bl1nkk)
Because an official release is now available, this ROM is now EOL and will receive no further support.
By popular demand, here's a new thread for my port of the Jelly Bean SDK. This is a continuation of DaxMax's thread, so if you want to see previous discussion, look there. (Thanks to DaxMax for putting up with discussion of what is essentially a distant cousin of his original ROM for so long on his thread.)
http://files.mrks.me/update-crespo-JRN83C-preview-2012063001.zip http://goo.gl/40Cxf (thanks to bl1nkk for the hosting)
Code:
MD5: 015e322b048b7e1464a90a87a5a6bcb1
SHA1: 3aca40900b40625505d4b6c0afce93c31e33770d
SHA256: 3b0b76444c307f4ffe685205cb92ad6060d957152dadef72444b3f2407510a34
Service Pack 4 for this ROM: https://docs.google.com/uc?export=download&id=0BwGWbMaI9twWRHFrRUROcDhIeVk http://goo.gl/ZVlQS (many thanks to bl1nkk for hosting) (alternately, check thread for mirrors) (see this post for changelog)
Code:
MD5: ac85b1e309ba3a3f438efe0954c11c32
SHA1: d147f777f8594c5d33dfd480143758107ff1baab
SHA256: 951d39e75e8d4891e18a1da3896567f293074262d8aef3cd0021d4239492cf00
Flash the main ROM zip (update-crespo-JRN83C-preview-2012063001.zip) first, then the service pack.
These are zips which should be flashable from ClockworkMod or other recovery. They contain /system and a boot.img and will not touch your recovery, data, or SD card. I believe you need to do a full wipe if you're flashing over ICS or below.
This ROM is quite stable and almost fully working at this point. Highlights:
Based on the Jelly Bean SDK release (JRN83C), with Google apps and other components from the Nexus 7 factory image (JRN84D). Hardware-related files and kernel from the ICS IMM76D release for Nexus S. (The source for the GPL components (mainly the kernel) is available from http://android.googlesource.com/.) The wifi hack (libhardware_legacy.wifi.so) is posted farther down this thread (including source).
Remarkably smooth. Project Butter really lives up to its name. (I've made one tweak in the init.herring.rc to make the default ICS cpufreq governor more aggressive in upping the clock frequency, in order to simulate the change in governor in the Jelly Bean kernel.)
Wifi, Bluetooth, GPS, GSM all work. NFC should work.
Sound and calls work as of July 9 (SP1).
Video recording works as of July 10 (SP2).
Tethering, including wifi tethering, works as of July 11 (SP3).
Calls via a Bluetooth headset work as of July 11 (SP3).
Google Now/voice search, offline voice text input, voice dialing, and text-to-speech all work as of July 11 (SP4).
Broken:
Voice/video chat in Google Talk Patch available to fix video/voice chat, see this post. (thanks selectormoldy for the crash log leading to fix)
Media scanning (used by Gallery and Music to find files on the SD card, among other things) is broken for some, but not for others. This appears to be triggered by something stored on the SD card/external storage. (thanks spupuz)
High-performance WifiLocks (the wifi driver drops into low-power mode when the screen turns off, even though it shouldn't when a high-perf WifiLock is held).
Sound. Note that means no phone calls of any kind, not even emergency calls, so this isn't ready for serious day-to-day use. This is likely unreasonably difficult to solve given that we have an official OTA coming in 2-3 weeks; look upthread for an account of what's been tried.
Ambient light sensor. It worked in the Galaxy Nexus-based ROM, and I'm not sure why it doesn't work in this one; in any event I'm not planning on putting more time into figuring out why. The light sensor works, but automatic brightness setting does not -- presumably something in the Android framework needs to be changed.
Video recording (as reported by users in this thread).
The Google Now/Google Search app may crash (reported by users in this thread). (This should be fixed in SP3 -- if you're still having problems, please provide a logcat.)
Tethering via wifi.
Phone calls via Bluetooth.
Voice dialing.
Voice search in Google Now. (The app fails to recognize when you stop speaking, so the search is never performed.)
Text-to-speech functionality with Google TTS (Pico TTS works).
Notes:
If the first-run setup keeps crashing on you: from the language selection (first) screen, tap on the four corners of the screen, proceeding clockwise from top left. This will bypass the first-run setup; you can then set up a Google account manually in Settings. (thanks urko95) (If you are still experiencing this with SP4, please report in this thread. A logcat would be helpful.)
Note also that there won't be much in the way of support -- I do have other things that I really should be doing ...
Service Pack 4
Service Pack 4 for the 2012/06/30 SDK JRN83C ROM. This can be flashed on top of the original JRN83C ROM with or without any of the previous service packs applied.
https://docs.google.com/uc?export=download&id=0BwGWbMaI9twWRHFrRUROcDhIeVk http://goo.gl/ZVlQS (many thanks to bl1nkk for hosting) (alternately, check thread for mirrors)
Changes in SP4:
Added the files in /system/usr/srec/en-US from the Nexus 7 JRN84D factory image -- Google Now/voice search, voice dialing, and offline voice dictation input all work.
Added /system/lib/libpatts_engine_jni_api.so from the Nexus 7 JRN84D factory image -- Google TTS now works. (Pico TTS already worked in previous releases.)
Replaced /system/app/SetupWizard.apk with the version from the Galaxy Nexus JRN84D build -- first-run setup should now display properly. (For the curious, I got the apk from Koush's jb-takju.zip and verified that it matched the JRN84D OTA via the SHA1 sums in the OTA update package.)
Added /system/app/{LiveWallpapers,VisualizationWallpapers,HoloSpiralWallpaper}.apk from Nexus S IMM76D to provide some live wallpapers.
Reverted a change in /system/framework/framework-res.apk to the default wallpaper; defaulting to the Nexus live wallpaper hurts performance.
Changes in SP3 (included in SP4):
libhardware_legacy.wifi.so updated to support wifi tethering. (See the linked post for source code.)
Permissions on /system/etc/bluetooth fixed to allow BlueZ to see its config files -- fixes phone calls over a Bluetooth headset, plus lots of other Bluetooth-related functionality.
hwcomposer.s5pc110.so replaced with a build from Jelly Bean-based source -- hopefully fixes hwcomposer bugs people have been experiencing. (See this post for more information.)
Removed /system/app/QuickSearchBox.apk to prevent conflicts with Google Now -- should fix Google Now access for most people. If you're still seeing problems, please provide a full logcat. (thanks afzalarsalan)
Changes in SP2 (included in SP3 and later):
New boot.img with /init.herring.rc edited to fix a thinko which was preventing CPU governor tweak from taking effect -- should result in more smoothness.
/system/build.prop edited to report as a "user" build instead of an "eng" build -- resolves red border flashing on screen. (thanks capez)
/system/etc/media_codecs.xml and /system/etc/media_profiles.xml copied from the Jelly Bean device/samsung/crespo tree -- video recording now works.
/system/lib/libjni_mosaic.so copied from Nexus 7 JRN84D image -- panoramic camera now works.
More changes from Nexus S ICS /system/framework/framework-res.apk integrated -- automatic brightness setting now enabled, tethering menu now enabled (wifi tethering is still broken).
Changes in SP1 (included in SP2 and up):
Jelly Bean audio HAL modules included -- sound now works.
/system/build.prop edited to report as a "user" build instead of an "eng" build -- resolves red border flashing on screen. (thanks capez) I screwed up integrating this fix, so it's not actually part of SP1. Will be in SP2.
/system/bin/make_ext4fs and /system/bin/setup_fs replaced with Nexus 7 JRN84D binaries -- fixes installing apps to SD card. (thanks smojica for reporting)
Removed LegacyCamera app to avoid having two camera apps.
Code:
MD5: ac85b1e309ba3a3f438efe0954c11c32
SHA1: d147f777f8594c5d33dfd480143758107ff1baab
SHA256: 951d39e75e8d4891e18a1da3896567f293074262d8aef3cd0021d4239492cf00
This is safe to flash on top of your ROM, whether or not you have any of the previous service packs installed.
I'll probably continue to distribute updates to this ROM via these service packs, mostly to save everyone bandwidth. (As with MS Windows service packs, they will be cumulative -- e.g. SP5, assuming there is one, will be flashable on top of the base ROM or any of SP1-4.)
FAQ
Frequently Asked Questions:
Did you see that the Jelly Bean source is out?
Yes -- and we're using it to provide audio, among other things. It was faster to use bits and pieces of the source to fix the SDK port than it was to sync and build the whole thing from source -- particularly since Google has not released proprietary blobs matching Jelly Bean for the Nexus S yet.
How do I get root?
The same way you do on a stock ROM -- flash Superuser. (thanks DaxMax)
The first-run setup keeps crashing!
From the language selection (first) screen, tap on the four corners of the screen, proceeding clockwise from top left. This will bypass the first-run setup; you can then set up a Google account manually in Settings. (thanks urko95)
Google Now crashes when I try to use GPS/navigation!
Install Google Maps from Market. (Several of the standard Google apps were not included in the base ROM to save download time.) (thanks legolas93)
My language is something other than US English, and offline speech recognition/voice input doesn't work!
Google's only implemented offline speech recognition for US English at the moment -- all other languages (including other English variants) still rely on Google servers to perform speech recognition.
I can't install the XDA app.
I can't install apps to SD card!
Flash Service Pack 1 or later.
I flashed http://www27.zippyshare.com/v/48676662/file.html, and I still can't install apps to SD card!
Flash Service Pack 1 or later. That zip only includes audio HAL modules and a fix for the red flashes on screen, not the rest of the SP1 bugfixes.
What are those red flashes on screen?
Video recording doesn't work!
Where's the tethering menu?
Flash Service Pack 2 or later.
The bar at the top of the home screen doesn't launch Google Now!
Wifi tethering doesn't work!
My Bluetooth headset/hands-free kit can't be used in phone calls!
Flash Service Pack 3 or later.
Google Now doesn't recognize when I stop talking!
Text-to-speech doesn't work!
Why is "Welcome" in the first-run setup screen so giant?
Flash Service Pack 4 or later.
I flashed 1337kernel, and now XYZ doesn't work!
See this post by Oodie for advice.
XXX/YYY/ZZZ doesn't work!!!!!!
Make sure you've done a full wipe (including data) and flashed the ROM correctly (base ROM, then the latest service pack). Try using the stock kernel included with this ROM; people have reported problems using custom kernels, particularly with sound. If the problem persists, pleave provide a detailed description of the problem and a logcat so that we can help you.
Why not do a full build from source?
This was quicker for me and works quite well. That said, anyone who wants to attempt a build from AOSP and/or CM10 source is welcome to do so, and I'll be happy to answer any questions that may come up in the process.
From the first 30 minutes playing with it.. Google Search / Now takes into account what your saying but doesnt do anything with the data - But doesnt seem to crash with SP1 Also a little big laggy here and there. But pretty much perfect. EXCELLENT ROM Steven676. I have been so excited for this release Thankyou!!
EDIT: Also get a red flash around screen when unlocking phone (still not a huge thing) :]
Looks great, thank you!
So flash the rom, then flash the service pack in op and then service pack in second post?
g1user101 said:
So flash the rom, then flash the service pack in op and then service pack in second post?
Click to expand...
Click to collapse
Both are the same, as I understand
Flashed to SP1 half a day ago and it was rocking! Kudos for this! :good:
I tried flashing GN's JB-SuperSU.zip, it seems to be incompatible (constantly crashing on the permission dialog). Anyone got ideas of how to get root?
nice thread !! i want to try it but i use the Phone calls via Bluetooth on my car radio !! i cant make call when the bluetooth connect on my car radio ?
thanks
thanr said:
Flashed to SP1 half a day ago and it was rocking! Kudos for this! :good:
I tried flashing GN's JB-SuperSU.zip, it seems to be incompatible (constantly crashing on the permission dialog). Anyone got ideas of how to get root?
Click to expand...
Click to collapse
Superuser - Download it and flash it.
DaXmax said:
Superuser - Download it and flash it.
Click to expand...
Click to collapse
Worked
cant bypass the setup screen, tapping 4 corners does nothing? no idea
Bringing over some other tidbits from the other thread about what's broken in SP1:
Automatic brightness setting. I've checked that the ambient light sensor works through another app, so presumably something in the Android framework is missing.
Video recording. Trying to start video recording turns up this set of errors:
Code:
V/videocamera( 2240): startVideoRecording
D/CameraStorage( 2240): External storage state=mounted
V/videocamera( 2240): initializeRecorder
W/StagefrightRecorder( 97): Max file duration is not positive: 0 us. Disabling duration limit.
W/StagefrightRecorder( 97): Target duration (0 us) too short to be respected
V/videocamera( 2240): New video filename: /mnt/sdcard/DCIM/Camera/VID_20120710_025327.mp4.tmp
D/CameraSource( 97): Camera does not support setVideoSize()
E/CameraHardwareSec( 97): Non-metadata buffer mode is not supported!
W/StagefrightRecorder( 97): Failed to create the encoder
D/CameraSource( 97): reset: E
W/CameraService( 97): attempt to use a locked camera from a different process (old pid 97, new pid 2240)
D/CameraSource( 97): reset: X
E/MediaRecorder( 2240): start failed: -2147483648
E/videocamera( 2240): Could not start media recorder.
E/videocamera( 2240): java.lang.RuntimeException: start failed.
E/videocamera( 2240): at android.media.MediaRecorder.start(Native Method)
E/videocamera( 2240): at com.android.camera.VideoCamera.startVideoRecording(VideoCamera.java:1484)
E/videocamera( 2240): at com.android.camera.VideoCamera.onShutterButtonClick(VideoCamera.java:614)
E/videocamera( 2240): at com.android.camera.ShutterButton.performClick(ShutterButton.java:108)
E/videocamera( 2240): at android.view.View$PerformClick.run(View.java:16966)
E/videocamera( 2240): at android.os.Handler.handleCallback(Handler.java:615)
E/videocamera( 2240): at android.os.Handler.dispatchMessage(Handler.java:92)
E/videocamera( 2240): at android.os.Looper.loop(Looper.java:137)
E/videocamera( 2240): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/videocamera( 2240): at java.lang.reflect.Method.invokeNative(Native Method)
E/videocamera( 2240): at java.lang.reflect.Method.invoke(Method.java:511)
E/videocamera( 2240): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/videocamera( 2240): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/videocamera( 2240): at dalvik.system.NativeStart.main(Native Method)
V/videocamera( 2240): Releasing media recorder.
V/videocamera( 2240): Empty video file deleted: /mnt/sdcard/DCIM/Camera/VID_20120710_025327.mp4.tmp
This is suggestive of a problem with the video encoding or camera HAL, but replacing libstagefrighthw.so with one built from the Jelly Bean device/samsung/crespo tree doesn't make a difference, and building camera.herring.so from that tree completely breaks the camera app (segfault in a call to libc from camera.herring.so).
There's a thinko in /init.herring.rc which means the tweak to the ondemand CPU governor isn't actually applied.
Lots of reports of Google Now and/or Google Search crashing. A logcat would be helpful for anyone trying to diagnose the problem.
Other notes:
Any ICS kernel should work with this Jelly Bean ROM. People have reported a variety problems with custom kernels. Please make sure you're using the stock kernel before reporting bugs.
That said, it appears that the official release will use a different wireless driver (the bcmdhd driver which Galaxy Nexus already uses), so ICS kernel releases may need some changing for Jelly Bean.
If you're having problems with Market or something else crashing, please provide a logcat -- otherwise problems are difficult to diagnose. Make sure you've wiped all data if you're flashing over an existing ICS installation.
There will be an SP2 to fix the governor issue, along with any other easy wins that crop up, but I'd gently suggest that most further effort should be devoted to a build from source.
figured it out followed this to get past the setup screen:
http://www.youtube.com/watch?v=L5XjF6sPef4
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
urko95 said:
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
Click to expand...
Click to collapse
urko what u mean all fixed ??
urko95 said:
Uploading a version of the port zipaligned and deoxeded... All fixed...
Regards,
Urko
Click to expand...
Click to collapse
Can you explain more?
legolas93 said:
Can you explain more?
Click to expand...
Click to collapse
Sorry, I mean that all fixes are applyed, the fixes that Steve realased!
EDIT: Uploading it right now
Regards,
Urko
why is the "ro.build.type" in sp1 still "eng" in stead of "user"?
Hello steven i flashed this port this morning... working very smooth . One problem i have which I'd like to solve. When trying to restore to 4.0.4 cyber or m6 i got md5 mismatch
.. any way i could restore them ? Thank you
Sent from my Nexus S using xda app-developers app
Related
AzusaROM Android Custom ROM Series
Cooked by Coburn64.
>>> Access the Coburn's Domain version of this AzusaROM topic here <<<
What's this?
AzusaROM is a version of Android that is faster, sleeker and breathes new life into your HTC Tattoo. Named after Azusa in the K-ON Anime, the ROM is powered by a custom kernel and has a lot of the bloat removed from it's 1.67.405.6 RUU Update base. Android 1.6 is at the core of the ROM.
AzusaROM is not really intended to be a CyanogenMod for HTC Tattoo. But, you could look at it that way. Please note that AzusaROM will not be based on Android 2.x bases until later on in it's development cycles. While there are 2.1 ROMs for the Tattoo available, they aren't fully completed and/or working.
ROM Status
AzusaROM is currently in public beta. It has been tested and it can be used as a every day-to-day ROM on your HTC Tattoo. Everything works on the v1.04 CoburnKernel, which is version v6.2vanillla. If you have a suggestion or an improvement, please share it and I'll see what I can do.
Current Version: v1.04
Current Version (In-Dev): Unknown
How do I use this?
You will need a HTC Tattoo that has been rooted and has a custom recovery installed. You can find tutorials about rooting the Tattoo and installing custom recovery images in this threads' forum.
Copy the file onto your HTC Tattoo's MicroSD Card, reboot into the custom recovery (I recommend Amon_RA Recovery) and choose "Apply update from ZIP." Select "AzusaROM_v1.XX_Y.zip" (where XX is the version number, and Y is a build timestamp). Watch the screen, AzusaROM will tell you what's going on.
Where do I get help?
I can be either Private Messaged on the Coburn's Domain Message Forums, XDA-Developers, emailed or you can reply to this thread. I prefer either posts in this thread or Coburn's Domain, I have both threads here and at Coburn's Domain under my watch list, which will send out daily emails of new posts in those threads.
Credits
HTC (Making the Tattoo), Optus Australia (best. Australian. Telco. Ever.) ralle.gade (I'm in his debt!), Maxisma (you rock), Benocharm (support), Cyanogen (for CyanogenMod), Donators (for all the coffee), XDA-Developers (rock solid forums, best smartphone dev forums that I've ever been to), and all other developers that I've saved from losing their sanity. And you - for using AzusaROM.
Support The Coburn!
I can't do this without funding. I'm a part-time Android Hacker and I'm also a High School student. By donating, you'll help me get better gear to continue cooking ROMs and making them better. You can always get a Coburn's Domain Plus/Pro Account and support me that way, which in turn also allows you to use Coburn's Domain services.
Can I upgrade my ROM? Eg. AzusaROM v1.01 to v1.03?
In theory, yes, but I've found it will break a few things. Please backup your data and wipe before flashing newer ROMs.
Stuff that Coburn needs to fix/do
Everything works. Yay.
See posts to follow. Space reserved for future use.
Downloads
(OLD) AzusaROM v1.0.07042010 - Not Available (Old Build)
(OLD) AzusaROM v1.01.08042010 - Available (Download Here!)
(OLD) AzusaROM v1.02.27042010 - Not Available/Unstable (See AzusaROM v1.02-1)
(OLD) AzusaROM v1.02-1.28042010 - Available (Download Here! Or Download it here (Mirror)!)
(OLD) AzusaROM v1.02-2.28042010 (UNOFFICAL BUGFIX RELEASE BY TheSSJ) - Available (Download Here!)
(RETIRED) AzusaROM v1.03.13052010 - Available (Download Here!)
(NEW) AzusaROM 1.04.29062010 - Available (Download here)
Changelog
AzusaROM v1.04 "Speed Demon"
Final AzusaROM Release unless a bug crops up.
Camera and Camcorder fully working.
WiFi is working.
BlueTooth works (can sync to my GPS, etc etc).
Busybox installed in /system/xbin
Look in /system/xbin for an easter egg.
AzusaROM v1.03-1 Kernel Update
WiFi now works.
Camera actually takes pictures.
Camcorder works fine.
AzusaROM v1.03 "Red-Hot Fireball Spitting Firecrackers"
CoburnKernel v6 custom kernel
New Theme
Rolled back to working ROM base
Tattoo-hack.ko installed along with wifi.ko in /system/lib/modules
AzusaROM v1.02-2 "Even Coburn makes mistakes..." Bugfix Release 2
Unoffical Build, but boots now!
AzusaROM v1.02-1 "Oh sh*t the kernel spazzed out" Bugfix Release
Fixed Very bad kernel black screen fault on boot - rolled back the kernel.
WiFi broke.
Quick and dirty fixes.
AzusaROM v1.02 "Popcorn"
Very basic firstaid kit script (lol)
Trimmed down the fat.
Scripts in /system/xbin
Kernel has ext4 for backwards compatibility with ext3 and ext2 partitions.
SPEED SPEED SPEED.
Sense UI trashed, replaced with aHome Mini
Most HTC Apps Removed THAT MEANS NO HTC PEEP - SORRY FANS!
"Friday" ringtone is default ringtone
Azusa now greets you at boot (new bootscreen)
AzusaROM v1.01 "Meteor"
Removed some sounds, ringtones, etc
Tested it with swap file, bullet speed!
Uses CoburnROM v1.6 core with boot from miki's ROM
New Boot Screen (Azusa in Maid outfit from K-ON anime)
Dream Theme (from HTC Dream/G1) default ringtone
Flash-proof (no bricks on flash!)
Sense UI enabled by default (may be removed in future releases)
If someone would like to mirror them or make BitTorrent torrents of them, please let me know! (My server gets about 5-10GB just from my Android ROMs, and I have 1TB to fill... )
Screenshots
Taken using my mum's camera.
what are the features and what about app2sd on this rom? :O
I haven't thought of that, I think it would be better if apps where loaded on Internal NAND Flash, faster and more reliable. If there's a lot of need for it, I'll make it available.
I'll love you if you do that
anyway what about the general features of this rom? what are the differences among yours and other roms or the official one?
the tattoo is my first android device
The differences at the moment are just some removal of some stock apps and other tidbits that I tidied up. I also got swap file working, and busybox is installed in /system/xbin.
Coburn64 said:
The differences at the moment are just some removal of some stock apps and other tidbits that I tidied up. I also got swap file working, and busybox is installed in /system/xbin.
Click to expand...
Click to collapse
I actually have a modaco r1 with a2sd but I can stay without it...i partitioned my microsd with the amon-ra recovery in 32mb swap 512 ext3 and then fat32...
do I need to repartition? Do I need the ext3 partition with your rom? what about root access?
I prefer to cook my own ROMs, I don't like to use online kitchens. It's better the trial and error way!
I read you are going to do the update for the swap...why don't you think app2sd is necessary? I don't install more than 10-15 applications but without a2sd my rom was full
Can you give me a rough estimate of what app sizes you were installing? Like Bubble Blast may be 21.04MB. Just a range, like 1MB to 10MB will also do.
EDIT: Added swap instructions to Post #2.
Coburn64 said:
Can you give me a rough estimate of what app sizes you were installing? Like Bubble Blast may be 21.04MB. Just a range, like 1MB to 10MB will also do.
EDIT: Added swap instructions to Post #2.
Click to expand...
Click to collapse
I know that after installing every app I need I tried installing raging thunder 2 (that is really slow on the tattoo) and it told me there were no space enough
I may committ suicide if this appens again
Thanks!!
Downloading it...will post comments after testing..
could you please post some screenshots? it would be really appreciated
Nice to see AzusaROM again.
Suggestion:Add app2sd.
It would be nice.
ambuj said:
Thanks!!
Downloading it...will post comments after testing..
Click to expand...
Click to collapse
Ok..So I have downloaded and installed, boot up without any problem.
However, while doing the initial seeting, it could not connect to my wi-fi router.
I tried for 30 mins, changing this and that, refreshing router but could not succeed.
So, I have reverted back to my old Modaco ROM.
may be this wi-fi is problem for me only.
If someone has done it successfully please post it here.
alberto88a said:
could you please post some screenshots? it would be really appreciated
Click to expand...
Click to collapse
Screenshots will not be of any use as visually there is no difference between stock ROM and Azuas ROM.
Can anyone tells me if AzusaROM is based on stock ROM?
or taken by a vanilla or other ROM?
Thanks.
Thanks
Hello!
I just installed this ROM... it's running fine. But, now I'm not able to get the wireless to work. It detects my network, but it's not connecting
I can see this with logcat:
I/wpa_supplicant( 709): wpa_driver_tista_driver_cmd POWERMODE 0
I/wpa_supplicant( 709): wpa_driver_tista_driver_cmd BTCOEXMODE 2
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
I/wpa_supplicant( 709): CTRL-EVENT-STATE-CHANGE id=10 state=8
V/WifiMonitor( 77): Event [CTRL-EVENT-STATE-CHANGE id=10 state=8]
V/WifiStateTracker( 77): Changing supplicant state: COMPLETED ==> DORMANT
D/WifiStateTracker( 77): Deconfiguring interface and stopping DHCP
I/wpa_supplicant( 709): CTRL-EVENT-DISCONNECTED - Disconnect event - remove key
s
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
E/wpa_supplicant( 709): Set_key: Wrong Key
I/wpa_supplicant( 709): CTRL-EVENT-STATE-CHANGE id=-1 state=8
Click to expand...
Click to collapse
How can I solve that?
Thanks anyway for you work ;D
weren't u working
on openeclair 1.3 or latest ?
i thought you could take me to a full working eclair planet
@Above: Yes, I was working on OpenEcliar 1.3, but I decided to roll back to v1.6 to give it some lovin'. For the fun of it, I might even do a cupcake build!
But don't worry, the AzusaROM 2.x series will be using Android 2.x bases.
casidiablo said:
Hello!
I just installed this ROM... it's running fine. But, now I'm not able to get the wireless to work. It detects my network, but it's not connecting
I can see this with logcat:
[..snip..]
How can I solve that?
Thanks anyway for you work ;D
Click to expand...
Click to collapse
Hm, that may be a permissions issue. I'll look into that later - thanks for reminding me.
Glad to hear that everything else works apart from the wifi bug. I'll update the post when I get on my development oven tonight - Gotta update it to Ubuntu 10.04 64bit Beta 2.
Yes, this is a discussion thread, but you are not allowed to make "meaningless" posts in here.
If you have made some discoveries post it, but no one in here is interested in "thank you" posts or similiar.
Okay, let's try to get the Android 4.2 gapps working as good as possible on our phone.
As you know Google dropped support of non-neon phones and tablets with Android 4.2.
Our Tegra2 SoC doesn't support these neon instructions, which results in a couple problems with the default gapps package.
We need to replace a couple files with older ones to get everything back working.
Update 27.04: I finally found some time to work on gapps and provide a (hopefully) fully working non-neon gapps package in the second post now!
One example: the biggest annoyance is probably the dying keyboard.
This happens because the gapps package replaces the libjni_latinime.so file included in the ROMs with a proprietary one by Google to enable Gesture input.
Unfortunately it does need neon, so you should remove the file inside the gapps package (/system/lib/) before flashing it.
In the logcat you'll usually see a SIGILL error, like this one:
Code:
A/libc(3910): Fatal signal 4 (SIGILL) at 0x4f6233a6 (code=1), thread 3910 (putmethod.latin)
I/DEBUG(92): signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 4f6233a6
I'm starting this thread to colloborate together on a gapps package with as much stuff working as possible, so if you do have any insights please share them
You can download the CM10 gapps package and get the nonneon files (they're in /optional/nonneon) - but not all of them are still working with Android 4.2.
P.S.: For the love of God, don't call them fapps - fapps is a foss (free and open source) package which uses OpenStreetMaps instead of GMaps and so on.
We still want gapps, just without neon libs.
Okay, here's my non-neon fixed gapps package.
Important: If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
If you don't do that you'll have leftovers from the former package, which results e.g. in a dying keyboard.
Changes compared to the official package:
Fixed the aosp keyboard crashes
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google TTS
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Notes:
Swipe keyboard won't work - nothing I can do about that.
Complain to Google for dropping non-neon support
Same thing goes to Photoshpere - no neon: no love.
Don't try to update Google Now - the new version doesn't properly work without neon (not sure if this still applies?)
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you're interested in more details what parts I changed - here you go.
This will hopefully ensure that future gapps versions will get provided as well
to fix facelock: replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: remove libjni_latinime.so
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib and GoogleTTS.apk with the apk from the teameos gapps package.
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk with this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, thus this version disables the auto-update.
replaced Talkback.apk with a working version from the eos gapps package.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Robin2 said:
Just a thought here: since our cpu does not support neon instruction set, wouldn't it be an option to patch the P990's kernel with an neon-emulator? This way, the neon instructions will be translated into something the cpu can process. Corrrect me if I'm wrong.
I'm saying this because I've seen something similar happen on Mac OS X, where version 10.8.x requires a cpu capable of SSSE3 (not SSE3) instructions. They have patched the kernel with an SSSE3 emulator so that it works on older hardware and AMD cpus.
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
bugadani said:
I'm thinking about the exact opposite - try to disassemble the libs, replace the neon instructions and reassemble. Not sure yet how much work it would take though...
Click to expand...
Click to collapse
this will be an horrendous work. I've seen some projects trying to hack armv6 instructions into the newer armv7 packages - it's really hard as you have to do it in smali as Google won't release it's sources.
I'm extremely full with loads of projects currently - I'm still hoping some people will take this over and try to build a nicely working non neon gapps version. this only requires trial and error, no real technical knowledge. but the interest seems low
Sent from my LG-P990 using xda app-developers app
Developer or not... But since you said yourself that "this will be an horrendous work", allow me include a little something here.
Changelog:
* All apps updated to 4.2.2 versions
* Google Play Store updated to 3.10.14
* Google Play Services updated to 3.0.25
* Gmail2.apk (Gmail) and GoogleEars.apk (Sound Search for Google Play) removed since they are available in the Google Play Store
** May require uninstalling and reinstalling Gmail and Sound Search after flashing.
* Keeps previous version's Photosphere/Picasa sync install on Mako, Manta, and Tuna.
Click to expand...
Click to collapse
From the way I see it, this horrendos work wouldn't really pay off since the earlier version of Gapps has... well... more or less everything the so-called new version has. So why bother if I may ask?
Back to you sir
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
natalya said:
Soooo, I have been looking into this for the past few days. I think I have got an understand of this that is good enough to make this work.
Since you are working so hard on CM10.1, I'll be willing to put great effort into this. Already started out with some basics, but I am pretty confident that I can make it work by the end of this week.
Will do some proper testing when it has been finished, once everything has been worked out, I'll push it public so you all can have the joy of using it in whatever way you may please
Click to expand...
Click to collapse
Any news on your project?
Well, I'm a little disappointed that no one else worked on this - it's basically using Google and trial and error.
Thanks goes to massimo who has offered me some help and did some tests
Anyways, I decided to take matters into my own hands now, as I want to release CM10.1 over the weekend and don't want people to complain because they flashed the wrong gapps packages.
@natalya: If there's anything else you discovered which isn't working please provide it, but as you didn't post what you did in almost 2 weeks now I didn't want to wait anymore.
Changes compared to the official package:
Fixed the aosp keyboard crashes
(note: swipe won't work on non neon devices, nothing I can do about that)
Fixed Google Talk videochat crashing
Fixed Faceunlock
Fixed Google Now & Voice Search crashes on non neon devices & restored hot-word detection
Fixed Talkback
Removed unuseful stuff
Let me explain the steps taken so others can learn what has been done and can update gapps theirselves.
to fix facelock: I replace libfacelock_jni.so with non-neon lib (credits: Adam77Root)
to fix the keyboard closing: I removed libjni_latinime.so
(note: this diables the keyboard swiping - it will never fully work on non-neon devices!)
to fix google videochat: added libvideochat_stabilize.so, replaced libgtalk_jni.so with non-neon lib and removed libgtalk_stabilize.so
to (partially) fix TTS: replaced libpatts_engine_jni_api.so with a non-neon lib
to fix Google Now and Voice Search I replaced the QuickSearchBox.apk and added the libgoogle_recognizer_jni_l.so lib from this one by Steady Hawkin.
Note that the newest Google Now version isn't compatible with non neon devices anymore, so this one disables the auto-update
replaced Talkback.apk with a working version from the above gapps package[/url].
Note the English TTS not working, see below.
Partial credits for steps 1-4 go to bubor who already started with a non-neon gapps package.
Then I reflected these changes in the 70-gapps.sh backup script.
That's important because otherwise updating the ROM will break the gapps!
Why? Updating the ROM does wipe /system - only the files which are in the script will retain.
This means that e.g. the libvideochat_stabilize.so will poof away and the libjni_latinime.so won't get updates anymore.
Additionally I removed the g.prop file in /system/etc to prevent the GooManager from trying to update the gapps package if new (neon) updates come.
To reduce the package size I completely removed the photosphere stuff.
As for the swipe keyboard this feature requires neon-support and will not work properly on our phone, no matter what.
Known bugs:
Google text to speech doesn't seem to work in English. fixed
Download:
http://goo.im/devs/tonyp/non-neon-gapps
If you already flashed another gapps package do format /system, reflash your ROM then reflash these gapps.
This is needed to ensure nothing remains broken from former flashes.
Please give some feedback for this gapps package.
If something doesn't work don't forget to attach a logcat
Okay, I managed to fix the Google-text-to-speech engine as well by replacing the GoogleTTS.apk with the one from the teameos gapps package.
I pushed the new version online and removed the old one.
All bugs I am aware of are now fixed, if you notice anything else that isn't working please give feedback
Time to clean up the OP.
tonyp said:
[*]Don't try to update Google Now - the new version doesn't properly work without neon.
Click to expand...
Click to collapse
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
ciarpame said:
Play store is offering me to update Google Search after installing your CM10.1 ROM and this gapps package. Is Google Now part of Google Search so I should avoid this update too?
Click to expand...
Click to collapse
You can update it and you can use it.
Sadly it has huge lags (as in it freezes from time to time and the waiting times can be taking forever sometimes)
Sent from my LG-P990 using xda app-developers app
For those who want to use the aosp-keyboard, Google recently released Google-keyboard (witch is similar to the aosp, but fully non-neon compatible)
In the US it should be available through the play store, for the others http://dl.androidnext.de/com.google.android.inputmethod.latin.apk
our 2x learns gesture typing
Thread cleaned up.
This is the dev discussion subforum so it's not the right place to ask about specific ROMs.
If you'll find out something new for the non-neon gapps package then you can post in here, everything else goes into the other sections.
Thank you!
P.S.: I've tried extracted the new lib (libjni_unbundled_latinimegoogle.so) from the Google keyboard - it's not compatible to the AOSP one included in ROMs.
If you want to include it into the gapps package you need to rename the apk to LatinIME.apk and add the lib, then it'll overwrite the AOSP keyboard.
(I'm too lazy to update the gapps package in here for a keyboard you can simply install).
I created a non-neon gapps package with the keyboard included.
It will replace the AOSP keyboard by the very similar google keyboard (that fixes gesture typing). Everything else is like tonyps-non-neon-gapps.
Download gapps-jb-20130427-nonneon-tonyp-keyboard.zip
All credits to Google, tonyp and the others mentiont in the first post.
Have fun!
P.S. @tonyp if you want you can put it on the gooserver to the other gapps.
Latest Google Now (26/06/2013) seems to work just fine. I'm not getting those crazy UI lags I got before, if I updated Google Now from the play store
Since the files from tonyp on goo.im are down, here is the working downloadlink for non-neon Gapps:
http://tonyp.basketbuild.com/downlo...on-gapps-/gapps-jb-20130427-nonneon-tonyp.zip
New google keyboard is available: link
DJNoXD said:
New google keyboard is available: link
Click to expand...
Click to collapse
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Personally I include a mini/tiny gapps neon compatible package in all my ROMs which only contains the most important apps.
I've created the package quite some time ago, it is fully open sourced and can (and already is) used by everyone.
https://github.com/tonyp/android_vendor_google
I update the repo on my own accord, if someone needs a faster update pull requests are always welcome.
But gapps are capable of updating theirselves via the play store, so this usually isn't needed anyways.
I would prefer if others are using my repo and sent pull requests instead of forking and forgetting about the origin, but that's of course your choice.
To include the gapps into your own build you have to add the repo to your manifest and add the following lines to a makefile.
(it doesn't matter which one as long as it's called - an obvious choice would be somewhere in the device tree):
Code:
MINI_GAPPS := true
$(call inherit-product, vendor/google/tiny_gapps_nonneon_tonyp.mk)
P.S.: @DJNoXD This isn't directed at you, I know you're already using my gapps repo in your roms, just a headsup for other potential devs.
tonyp said:
Ah good that you're reviving this thread, I've been meaning to update it with some information.
I never intended to maintain a gapps package and won't do so.
So if someone wants to follow my instructions and offer updated neon-compatible packages for 4.3 and 4.4 go ahead.
The instructions should still apply, but things may have changed a little in the newer versions so they might needs some adaption (e.g. the Talk to Hangouts transition).
Click to expand...
Click to collapse
Hi @tonyp, I hope it's ok to revive this thread again resp. to hijack it a bit from your original intention!? Even if the origin of my following NEON related questions is founded in my lag problems with CM11 2014/11/13 build by @gucky01
gucky01 said:
http://sourceforge.net/projects/lgo...m-11-20141113-UNOFFICIAL-p990.m1.zip/download
Here we go, guys! As promised, here the first build. It`s 100% Tonys work. So we have to thank him for his great work!
All the best to you!
Click to expand...
Click to collapse
I find they fit this thread much better than any other CM10.x/CM11/CM12 ROM XDA thread. Not just one but all of those ROMs are affected by the missing NEON instruction set of the Tegra 2 SOC.
How can one prove wether a current ROM does not call any NEON instructions? Is it sufficient to see that there are no SIGILL entries in the logs?
Let's assume a dev releases a ROM that initially does not call any NEON instructions. Is it possible that updates of Google apps introduce calls of NEON instructions making the ROM misfunctional/unusable?
AFAI understood your trick to assemble non-NEON gapps is to replace shared opjects ( .so files) that call NEON instructions by their (more or less) equivalent non-NEON shared objects. Could there be Google apps or third party apps that call NEON instructions in their core binary?
If so, our P990 will not able to run them, right? I'd like to assemble a list of apps that won't run without NEON support (is there still any list?).
Do calls of NEON instructions on systems that don't support NEON always result in FCs, hot re-boots, or BSODs? Other way round: can calls of NEON instructions on systems that don't support NEON also result in lag or even heavy lag? (gmail 5.0.1 uses to take 10 seconds to start in my recently installed CM11 after the cleanest install possible; I just left the BB and system data/cal un-touched).
I am looking forward for your reply, well-knowing that you don't use the P990 as your daily driver any more for a long time now.
I wish you all a good 2015!
OpenPDroid is an awesome mod developed and maintained by CollegeDev, FFU5y, Mateor, Pastime1971, Syvat and Wbedard that allows you to configure for each app separately exactly which permissions it should have and block or spoof everything else. Unfortunately, it can only be used if the core platform is integrated directly into the ROM. (For more details, see http://forum.xda-developers.com/showthread.php?t=2098156)
Since I have completed the integration anyway during my attempts to fix the HDMI rotation bug (without success so far, I'm afraid) and the current version of CM does not seem to contain any more critical bugs, I thought others might like to make use of my ROM as well.
I therefore hereby present: CM 10.1 with OpenPDroid integration. Besides the platform integration I made the following changes:
PDroid Manager app integration.
Standard CM Updates are disabled by default.
CM anonymous stats collection is disabled by default.
Google Analytics integration has been removed from the CM stats collection module.
Updates and anonymous stats collection can simply be enabled again using the menu. (Warning! Applying a normal CM update purges the OpenPDroid integration!)
I will try to at least provide updates to newer versions at critical update moments and will perhaps provide some more in between.
You'll need to have ClockworkMOD installed in order to flash this ROM.
Downloads:
11/07/13: Version based on CM 10.1.1 stable. Steps:
1. Flash the stable version of CM 10.1.1 (10/07/13) for our device.
2. Flash this OpenPDroid patch.
3. Install PDroid Manager either from the Play Store or using the APK attached to this post.
10/07/13: (based on source code 09/07)
10/07/13: https://mega.co.nz/#!uswGGQ6K!Wt9JAFDBElZQ2i74yNxMrkz3y7kO4U8-LWK2dLx_L8s
10/07/13: MD5: 99fc3769c9b2354a844ac1ac92504650
16/05/13: (build with standard CM kernel)
16/05/13: https://mega.co.nz/#!StIyQbzD!GfgNa3Seha74UnSahokwIzvcZ9UVqKaa2P38_LlxuMY
16/05/13: MD5: ad036e4035291bba901ad90826ab0abf
13/05/13: (general source code cleanup)
13/05/13: https://mega.co.nz/#!KoxixajK!Wn91VGj5ooOFYXs-Vt8QJDkU8Bo7VuR40_939hd3YMg
13/05/13: MD5: dffad528804bf830c4b225b0bfff5a76
09/05/13: (WerewolfJB kernel v003 new)
09/05/13: https://mega.co.nz/#!2txwmS4S!aR4bHG6BHMkoTPabi8Z0K0r4hPsUICmKO9ROaaIYOg0
09/05/13: MD5: 4a75829296a167a563ad78ffe26991de
05/05/13: (vibration,memory management)
05/05/13: https://mega.co.nz/#!bsQERDaS!RHB4rHhQsDf9XauyOpeMySAiDt1gtc8Y7gnsckdWOlo
05/05/13: MD5: e05017acf9e50affcba7379050514d63
01/05/13: (merged in the WerewolfJB kernel, fixed headphone button actions)
01/05/13: https://mega.co.nz/#!ig5hCJYY!eHM5vwER9zEEZJRk9_C6vCvclH14rDcKa9CyBcU9kTc
01/05/13: MD5: 3ababb1c0cda47874ed7d688de032638
28/04/13 (adjusted some device references for improved custom recovery compatibility)
28/04/13: https://mega.co.nz/#!71BgVLBY!PEcEHAYxpDZVZcQycpgGJ2QeJZZ0HbgVdjaBkiD72bg
28/04/13: MD5: 7f2616736dd78940e37d1e14ea47084f
24/04/13: (storage, power profiles)
24/04/13: https://mega.co.nz/#!j44XWBDb!UrmGEhCUcjbj8Q3WTj1EkDrImXJXwcNGvEMIHFm-TvE
24/04/13: MD5: 491a500c5bef958d7575a6ce62fae1aa
23/04/13: https://mega.co.nz/#!75IDhCAA!EpwDqHm6W6fG3mk0lNaC0XPWvlsJxi2TjEpjJPEuj6Q
23/04/13: MD5: 609c76958796f19fb04aee217c44ba98
PS. If anyone ever discovers the correct procedure for calling the proprietary nvidia tegra driver api, please let me know.
is the baseband wakelock solved in this rom?
Who can change the other network disk ，thx
xtribas said:
is the baseband wakelock solved in this rom?
Click to expand...
Click to collapse
The main additional problem that this ROM currently fixes compared to standard CM is that of blatant privacy violation.
Since the wakelock issue seems to be related to mobile data use, and I don't have a data subscription, experimentation with this would quickly rack up my phone bill. If someone comes up with a solution I'd be happy to patch it out though.
Hansey said:
Who can change the other network disk ，thx
Click to expand...
Click to collapse
I assume you're referring here to the swapping of disk names when using MTP. I actually only noticed this bug last night and it should be easy to fix. I plan to have it patched out in the next version.
Update 24/04/13 uploaded, involving official CM patches for MTP storage & power profile settings.
Is there a guide how to compile it my self?
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1994860
DavidXanatos said:
Is there a guide how to compile it my self?
Click to expand...
Click to collapse
At the Cyanogenmod website there are instructions for compiling yourself. You can apply the OpenDroid patches using the link I included in the post. Make sure to synchronize the proprietary files with those provided by Cyanogenmod or some aspects will fail to work.
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
SimonTS said:
@Wenque - As the original CM on which you based this has the incorrectly labelled hardware platform which means it can only be flashed with the one particular version of CWM, could you possibly modify your version so the coding is for X3, not for P880 - then it could be flashed with any recovery.
Click to expand...
Click to collapse
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Wenque said:
Thanks for pointing this out, as I wasn't aware that my ROMs still suffered from this problem. I'll look into it.
Click to expand...
Click to collapse
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
SimonTS said:
No problem. I got the 'Status 7' message when I tried to flash it, due to the P880.
This problem goes away with the latest (v6.0.3.1) version of CWM, so it's not massively important I guess. It would be better if CM modified their builds to reflect the correct hardware identifier.
May be worth you expanding your OP slightly to contain a link to the correct CWM - just to make it easier for people to find.
Click to expand...
Click to collapse
Good idea. I'll probably just expand the model check in the update script for future uploads so it accepts both references.
Update 28/04/13 uploaded, for some improved custom recovery compatibility. As every update, it also contains all official CM patches.
All patches between this version and the last one are minor, so for people who have installed the previous version of the ROM there is no need to update to this one.
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
No-body?
I have tried ths both with Derek Gordon's gps.conf modification, and with my own one using just the UK NTP servers and no fancy settings.
If I reboot the phone and run GPS Status & Toolbox it takes between 3 and 5 minutes to get the first lock. This happens whether I do it immediately on reboot or leave the phone alone for an hour first. Once it has established a first good lock, GPS seems to be very good - relocks quickly and stays in the background happily.
The problem is the first lock - it's almost as if the hardware is actually starting off disabled and takes time to warm up or something.
Can someone else using this ROM please test to confirm? I will try this with the standard CM 10.1 build and also with the Stock ROM again, but can't do so for a couple of days.
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
SimonTS said:
Is anyone else having problems with GPS on this ROM? I am going to try going back to all the old methods I used on my HTC DesireS, but thought I'd ask here as well.
For those who wonder what the old methods were, have a look at derekgordon.com
Click to expand...
Click to collapse
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Wenque said:
Update 01/05/13 uploaded. I swapped the default CM kernel with the WerewolfJB kernel (thanks laufersteppenwolf!) and I fixed the headphone button actions (key 248 HEADSETHOOK).
Sorry SimonTS, but I don't know whether this version fixes your GPS problems. Perhaps I'll have time to look into it later.
Click to expand...
Click to collapse
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
SimonTS said:
No need to apologise mate. I have tried the WerewolfJB kernel, but it doesn't seem to make any difference. I'm going to look at running the WerewolfJB ROM for a while as GPS seems to work perfectly in that, but hopefully you will get time to build a new version as I really want a ROM with pDroid in it.
Click to expand...
Click to collapse
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Wenque said:
All you really need to do is copy the good /system/etc/gps.conf file to the PDroid ROM and make sure that you do not block too many permissions. You are probably using Google's SUPL server to help you obtain an initial location estimation and you don't want to block that if you rely on fast GPS locks.
You can do this by first copying the gps.conf file to a safe location (root of sdcard for instance in /mnt/shell/emulated/) and then performing the following steps:
- Use the terminal emulator with the following commands:
= su
= mount -o remount,rw /system
- Now copy the good gps.config file over the current one (for instance using root-permission File Manager or 'su', 'cp /mnt/shell/emulated/gps.conf /system/etc/' )
- Either reboot now or use the terminal emulator with the following commands:
= su
= mount -o remount,ro /system
Click to expand...
Click to collapse
It's not that simple mate, but thanks for the reply. I know all about the gps.conf file as we used to have real problems with GPS on my old Desire S. The problem I see with this build and the standard CM is almost as if it doesn't know how to talk to the GPS hardware properly.
With the WerewolfJB build and my own gps.conf file I can get a lock in under 10 seconds sometimes, and always under 20.
Note: This thread is here mostly for historical purposes. While Xposed is supported in various forms [EdXposed and LSPosed], developent on the Xposed primary app has completed. Xposed framework compatible modules are still in active development and supported by their respective developers..
Click to expand...
Click to collapse
Let me introduce the Xposed framework, which gives you the possibility to modify your ROM - without modifying any APK (developers) or flashing (users)!
For a quick start, have a look at XDA's "Android Basics 101" on Xposed:
Some technical details:
I extended the /system/bin/app_process executable to load a JAR file on startup. The classes of this file will sit in every process (including the one for system services) and can act with their powers. And even more: I have implemented something that allows developers to replace any method in any class (may it be in the framework, systemui or a custom app). This makes Xposed very powerful. You can change parameters for the method call, modify the return value or skip the call to the method completely - it's all up to you! Also replacing or adding resources is easy, thanks to many helpers in Xposed's API that developers can use.
Advantages:
No need to modify any APKs. This means:
No need to decompile, change things in smali, compile, sign, ...
It will work for odexed and deodexed ROMs.
Your mod is not bound to a specific version of the ROM. Unless there is a major change in the methods called for a certain functionality, your mod will continue to work even when you upgrade your ROM. Many modules work for a wide range of ROMs from different vendors.
Multiple mods can be installed at the same time, even if they modify the same app. So you can use these battery icons and those quick toggles. Even hooking the same method twice is possible. Of course, this only works properly if the mods are not trying to do incompatible things.
It does its magic at runtime. That means that developers can implement settings and do changes based on them (instead of statically forcing a certain behavior). Or you can have some extra logic for certain ROMs, without building different mod versions.
It can be disabled easily without having to reflash.
It's open source and free (as in beer and in speech).
There is a repository with many popular modules.
Download:
You can download the installer from http://dl.xposed.info/latest.apk. The attached disabler zip is only needed if you are in a boot loop.
An experimental version for Gingerbread made by liudongmiao can be found here: http://forum.xda-developers.com/showthread.php?p=44034334#post44034334 (no support from my side though)
How to install:
First step for everything you do: Create a nandroid backup and make sure you know how to restore it!
I'm not responsible for anything you do with your phone/tablet/rice cooker.
There is also the risk to soft-brick your device. In such a case, see below for ways to recover from it.
Installation of the framework:
Download the Xposed Installer APK and install it
Launch the Xposed Installer, go to the "Framework" section and click on "Install/Update"
Reboot
Done!
You can verify this by starting the Xposed Installer again and making sure that the numbers in the "Framework" section are green.
If app_process jumped back to an older version (or none at all), you probably have a ROM with S-On or similar, which reverts any changes to /system after a reboot. Use installation via recovery in such cases.
Installation of any modules:
Download <module>.apk (e.g. via the builtin repository browser) and install it
Launch the Xposed Installer and go to the "Modules" section (you will also get there if you click on the notification warning you that the module is not enabled yet)
Enable the module by checking the checkbox
Reboot
Done!
(note that you can install the framework and enable/disable multiple modules at once and reboot afterwards)
In case you get into a boot loop:
First, try using the safemode by pressing any hardware key repeatedly. You can find a short explanation how it works here.
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Modules:
The official repository for Xposed modules, which can also be access from within the app itself (with download/update support), can be found at http://repo.xposed.info
There is also a whole XDA subforum for modules and an index/request thread.
Please don't use the "Xposed General" forum for requests or problems with modules! Use the thread of the module instead.
How to write a module:
If you are an interested developer, give it a try. The development tutorial will help you get started. Further documentation (e.g. how to replace resources) is here. And of course, you can ask your development questions in the "Xposed General" forum.
If you have suggestions for new functions the framework could provide (which means they should be useful for more than your module), you can do this there as well. However, requests that I or somewhen else should write a module for xyz are NOT allowed. Again, this subforum is only about the framework.
Source code:
https://github.com/rovo89/Xposed (the C++ part)
https://github.com/rovo89/XposedBridge (the Java part)
https://github.com/rovo89/XposedInstaller (Installer app)
Where to get help:
First, read the FAQ and search the "Xposed General" forum. If you don't find your answer there, please check this explanation to find out where you should post your question (e.g. module requests/questions don't belong into the "Xposed General" forum).
Thanks to:
Tungstwenty for his many contributions, both in code and thoughts
XDA admins, news writers and supporters for making Xposed known to so many people
All those volunteers who help answering questions about Xposed
The people who donated to get me a Nexus 5 for earlier KitKat support
All the translators: http://translate.xposed.info/ (if you want to contribute more translations, please follow the instructions mentioned on that page)
Xposed Installer versions & changelog
In this thread, I will post announcements about new Xposed Installer versions (including test versions). If you want to be notified about new versions, subscribe to this thread.
Older versions:
1.0: Initial version
1.1: ???
1.2: Installer
1.5: Resource replacing
1.6: Some fixes and improvements [629 downloads]
2.0 rc2: Lots of thing redone. Supports (temporarily) replacing native libraries, lots of additions and changes for developers. [3,234 downloads]
2.0: Removed the native library replacement again, support for 4.1 and 4.2, Instagram crash fixed, ... [631 downloads]
2.0.1: Fixed a crash when a module tries to hook a function with "long" or "double" parameters [930 downloads]
2.0.2: Fixed a problem which resulted in a boot loop [4,310 downloads]
2.1: Various improvements, e.g. earlier callbacks for module loading. For details, see this post. [345 downloads]
2.1.1: Fixed a bug in drawable replacements [5,421 downloads]
2.1.2: Small fixes, added Chinese and Russian translations [11,415 downloads]
2.1.3: Reverted a change in 2.1.2 that caused bootloops; new translations and some more fixes [46,803 downloads]
2.1.4: Support for Galaxy S4 and HTC One plus a few minor fixes/enhancements (details) [208,176 downloads]
2.2: Builtin updater/module downloader, extended UI, support for Android 4.3 and more (details) [241,267 downloads]
2.3: x86, Knox, MIUI support (experimental), context menu in modules list and more (details) [18,219 downloads]
2.3.1: "Segmentation fault" during installation fixed [679,333 downloads]
2.4: Support for Android 4.4, performance improvements, log viewer, active check (details) [101,613 downloads]
2.4.1: Fixed bootloop on some x86 ROMs [2,537,642 downloads]
This is Xposed version 2.5 (final). The main new features and fixes in this version are:
Rewritten framework installation/uninstallation
Uses interactive su (via libsuperuser) to provide improved compatibility with different Superuser apps
Better feedback when root access fails (doesn't freeze the app anymore)
Offers installation via custom recovery (CWM/TWRP), either flashing the file automatically or manually
Safemode to disable Xposed with hardware keys to get out of (most) bootloops
Compatibility with Sony/LG ROMs (4.3 and 4.4), Meizu ROMs (4.4)
Debug setting to disable resource hooking as a temporary workaround for incompatibilities with some theming engines (not all modules can be used in this mode)
There are also other improvements and fixes, especially many translations updates.
In case you get a message "Segmentation fault" during installation, you can now download an additional app which provides statically compiled versions of BusyBox (a lot bigger, but should work with every ROM). It's not needed otherwise.
Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.
As always, you can download it via the in-app updater or from http://dl.xposed.info/latest.apk.
This is Xposed version 2.5.1. The changes in this version are:
Added compatibility with CM11's new theming engine
Avoid conflict with LG G2's icon theming engine
Translation updates
I would like to express my disappointment again that too many people don't even spend two minutes to read at least the last few pages of a thread before posting problems. I have invested hundreds of hours - probably even more - into developing and supporting Xposed, so it feels disrespectful for me. Users like this are the minority and many others are very supportive, but it's really annoying.
As always, you can download it via the in-app updater or from http://dl.xposed.info/latest.apk.
This is Xposed version 2.6 beta1. The main changes in this version are:
UI refresh using the Cards UI pattern, mainly contributed by @GermainZ
New logo, created by @DD-Ripper
Detection of several known issues, a warning with link to the FAQ item will be shown
Release type selection in the downloader (only stable version are shown by default)
Many internal improvements in the framework, e.g. better resources compatibility and performance
In case you're looking for the Xposed-*-Recovery.zip files, they are stored in a subdirectory (Android/data/de.robv.android.xposed.installer/files) of the SD card now. This is the official Android API and will hopefully fix installation on some ROMs.
Also a big "thank you" to the translators, many translations have already been updated. You can see the status on the brand new translation overview page, with completion status and templates containing the strings yet to be translated: http://translate.xposed.info/
Note that I have already informed the primary translators about the upcoming version.
The full change log is on GitHub:
https://github.com/rovo89/XposedInstaller/commits/master
https://github.com/rovo89/XposedBridge/commits/master
https://github.com/rovo89/Xposed/commits/master
You can download the beta version from this post. Keep in mind that beta versions come with a bigger risk because they aren't tested on a big variety of devices/ROMs yet.
This is Xposed version 2.6 (final). The main changes in this version are:
UI refresh using the Cards UI pattern, mainly contributed by @GermainZ
New logo, created by @DD-Ripper (and no, there won't be an option to change it)
Detection of several known issues, a warning with link to the FAQ item will be shown
Release type selection in the downloader (only stable version are shown by default)
Many internal improvements in the framework, e.g. better resources compatibility and performance
Developers, please check this and following posts for information about API changes.
In case you're looking for the Xposed-*-Recovery.zip files, they are stored in a subdirectory (Android/data/de.robv.android.xposed.installer/files) of the SD card now. This is the official Android API and will hopefully fix installation on some ROMs.
Also a big "thank you" to the translators, many translations have already been updated. You can see the status on the brand new translation overview page, with completion status and templates containing the strings yet to be translated: http://translate.xposed.info/
The full change log is on GitHub:
https://github.com/rovo89/XposedInstaller/commits/master
https://github.com/rovo89/XposedBridge/commits/master
https://github.com/rovo89/Xposed/commits/master
As always, you can download it via the in-app updater or from http://dl.xposed.info/latest.apk.
This is Xposed version 2.6.1. The main changes in this version (compared to 2.6) are:
Fixed a crash with some apps (Disa, Rdio)
Some minor UI improvements
A few translation updates
Commits: https://github.com/rovo89/XposedInstaller/compare/2.6...2.6.1
As always, you can download it via the in-app updater or from http://dl.xposed.info/latest.apk.
I updated the main thread to indicate that the primary Xposed app is no longer in active development, and that EdXposed and LSPosed are the spiritual successors to Xposed and support the Xposed framework modules.
hello exhibit community,
i successfully compiled slim rom for the t599n. i need assisstance with the camera. when i run the camera from the terminal, the results are -->I/ActivityManager( 2129): START u0 {act=android.media.action.IMAGE_CAPTURE flg=0 - Pastebin.com. the camera app disables a few moments after initial boot. the logcat shows -->E/HAL ( 1672): load: module=/system/lib/hw/camera.montblanc.so E/HAL ( - Pastebin.com which is clearly the problem. the error is referencing this -->https://github.com/SlimRoms/frameworks_native/blob/kk4.4-caf/libs/binder/MemoryBase.cpp. i swapped the camera libs from various roms, showing the same result. my guess is, a build with non caf source for native. any advice is greatly appreciated.
brandonabandon said:
hello exhibit community,
i successfully compiled slim rom for the t599n. i need assisstance with the camera. when i run the camera from the terminal, the results are -->I/ActivityManager( 2129): START u0 {act=android.media.action.IMAGE_CAPTURE flg=0 - Pastebin.com. the camera app disables a few moments after initial boot. the logcat shows -->E/HAL ( 1672): load: module=/system/lib/hw/camera.montblanc.so E/HAL ( - Pastebin.com which is clearly the problem. the error is referencing this -->https://github.com/SlimRoms/frameworks_native/blob/kk4.4-caf/libs/binder/MemoryBase.cpp. i swapped the camera libs from various roms, showing the same result. my guess is, a build with non caf source for native. any advice is greatly appreciated.
Click to expand...
Click to collapse
Our device ( included in the STE Novathor family of devices ) requires several ROM level patches in order to function. Thats one of the main reasons why we have very little "official" support. My patches are located here:
https://github.com/Meticulus/android_device_samsung_codinalte/tree/carbon/patches
You may also find some on the slimroms gerrit by @Android-Andi such as this one here:
https://gerrit.slimroms.net/#/c/8269/
BTW, I believe that SlimRom's latest ROM is dubbed "SlimKat" and not "Slim Jim" LOL :laugh:
Meticulus said:
Our device ( included in the STE Novathor family of devices ) requires several ROM level patches in order to function. Thats one of the main reasons why we have very little "official" support. My patches are located here:
https://github.com/Meticulus/android_device_samsung_codinalte/tree/carbon/patches
You may also find some on the slimroms gerrit by @Android-Andi such as this one here:
https://gerrit.slimroms.net/#/c/8269/
BTW, I believe that SlimRom's latest ROM is dubbed "SlimKat" and not "Slim Jim" LOL :laugh:
Click to expand...
Click to collapse
cool. i built caf branch btw, i will cherry pick andi's diff, rebuild, and post results. my slow pc wont complete the build until tommorrow.
http://pastebin.com/cc48puVg <-patch 6 fails
i ported the libs from his slimrom and the camera works. everything works now. i dont have data atm, so testers after he allows me to host.
thanks for pemission to andi. i found a possible bug would like to squash before hosting. i found the sim i recieved with the phone and it is not detected. this is my first gsm device developing for cdma previously. when i tick network settings, screen turns blank and the proccess android.phone quit. if i tick 4g, settings quit. possibly the sim card is no good. i will host the rom tommorrow. got work.
im hosting the rom @ af if anyone is interested in testing http://androidforums.com/galaxy-exh...90-wip-rom-test-slim-jim-rom.html#post6745103. data has yet to be verified. i will update the op when it is. everything else is working.
data fixed^