[INTRODUCTION]
This ROM is mainly created by Scanno with the help of EJTagle (for kernel work and drivers). This ROM is based on the CM10.1 sources and has the most CM10.1 features included.
Why a CM rom after a couple of AOSP ROMS? Well the main reason is that android 4.2 has a new interface and i do not like it that much. CyanogenMod includes some inteface enhancements that i personally think adds some additional value.
Please remember that I and EJtagle are *NOT* professionals and do this in our spare time. We all have full time jobs and a family. So be happy that there is an Android ROM based on Android 4.2 / JellyBean for a device that was sold with Android 2.2 and never had an update.
We do our best to make this ROM as good as possible. With VegaCream and VegaBean we gave you a ROM that gave a new life to your tablet and unleashed its full potential. But we are not wizzards and there might be problems that we cannot solve or do not have time for.
[FEATURES]
This ROM is an unofficial CM10.1 and has most CyanogenMod features included.
[INSTALLATION]
As you all might know we have very limited internal storage space. So this ROM needs a different internal memory layout. The whole /data partition (where the user data and apps are installed) needs to be on the sdcard.
[SDCARD]
You SDCARD needs to be partitioned the following way:
- First partition needs to be FAT32
- Second partition needs to be EXT4
- Make sure there is NO extended partition
[FLASHING]
The first time you flash this ROM you *HAVE* to flash the NVFlash version to make sure the internal memory is formatted the correct way.
Make sure you have the GApps downloaded and put on your SDCard (see goo-inside.me/gapps)
[NVFLASH]
Download the NVFlash version and make sure your tabet is connected to the power supply and that the tablet is connected to your computer.
Put the tablet into NVFlash mode (by using 2 seconds back key, 2 seconds power key, 2 seconds back key)
Run the NVFlash executable and if everything goed right, the ROM will be flashed.
Reboot the tablet and as soon as the tablet finishes booting, reboot the tablet into recovery mode.
Once in recovery, do a factory reset and then right after that flash the Google apps zip file you downloaded.
[RECOVERY]
Download the zip file and put the file on your SDCARD.
Boot into recovery.
Do a factory reset (or you can try just clearing cache and dalvik-cache).
Flash the zip file.
Right after flashing the ROM, flash the gapps zip file.
Reboot.
[WORKING]
- 3G
- Audio
- Video
- Wifi
- Touchscreen
- Most regular things
[NOT WORKING]
- Bluetooth. Due to the fact that Google has introduced a new Bluetooth stack in 4.2, Bluetooth
*NOT* work. Efforts to get Bluetooth working has ended.
[CREDITS]
- Ejtagle
- Scanno
- CyanogenMod for their sources
- LeoP for his zRAM implementation
[DOWNLOADS]
Gapps for android version 4.2.2: Goo.im Downloads - Downloading gapps-jb-20130301-signed.zip
Gapps for android version 4.2.1: gapps-jb-20121212-signed.zip
Here are some other Gapps that are specific for Tegra2 non neon devices. These Gapps fix the closing of the default keyboard. But it also disables the gesture typing. These GApps were made for the XOOM and can be downloaded over at XDA:
[ROM][4.2.2] My Android 4.2 for Xoom Wi-Fi (20130217) - xda-developers
[BUILD 20130815]
CWM-ZIP: http://www.mediafire.com/download/zuy41bx10afvx6s/cm-10.1-20130815-UNOFFICIAL-shuttle.zip
NVFLASH: http://www.mediafire.com/download/3j7r8dbd7204y25/cm-10.1-20130815-UNOFFICIAL-shuttle.exe
[BUILD 20130727]
CWM-ZIP: http://www.mediafire.com/?orvrlhdr5x58ahq
[BUILD 20130721]
CWM-ZIP: http://www.mediafire.com/download/rc2kve9ccc6sadf/cm-10.1-20130721-UNOFFICIAL-shuttle.zip
[BUILD 20130712]
CWM-ZIP: http://www.mediafire.com/download/jzxqqtygd58atra/cm-10.1-20130712-UNOFFICIAL-shuttle.zip
Build 18:
CWM-ZIP: http://www.mediafire.com/?u63rb3nt4dni37z
Build 17:
Only flash the CWM-ZIP if you already have a working Build 16 !!!
CWM-ZIP: http://www.mediafire.com/download.php?m2iakdr0x2j0lk0
NVFLASH: http://www.mediafire.com/?aeleqc618v21b3h
Build 16:
NVFLASH: CM10.1-Shuttle-P10AN01-build_16.exe
Build 15:
CWM-ZIP: CM10.1-Shuttle-P10AN01-build_15.zip
NVFLASH: CM101-Shuttle-P10AN01-build_15.exe
Alpha 10:
CWM-ZIP: CM10.1-Alpha10-Update.zip
Alpha 8:
CWM-ZIP: CM10.1-Alpha8-Update.zip
Alpha 7:
CWM-ZIP: CM10.1-Alpha7-Update.zip
NVFLASH: CM10-1_NVFlash_alpha7.exe
Alpha6:
CWM-ZIP: CM10.1-Alpha6-Update.zip
Alpha5:
CWM-ZIP: CM10.1-Alpha5-Update.zip
NVFLASH: CM10-1_NVFlash_Alpha5.exe
[BUILD 20130815]
- Included a patch to dalvik for low memory devices.
- Synced with the CM10.1 repository
[BUILD 20130727]
- Synced with the CM10.1 repository
[BUILD 20130712]
- Synced with the CM10.1 repository
This version includes all the changes that the CM team has introduces, including
the privacy options.
Build 18:
- synced with the cm10.1 repository
Build 17:
- Synced with CM10.1 repo
- Two patches to the kernel from clemsyn that might solve some remaining SOD's
Build 16:
- This build will be the base that next builds will use !!!
- New partition layout. So only an NVFLASH version for build 16
- TWRP 2.5.0.0 recovery included
- Synced with CM10 repo
Build 15:
Well a lot of changes:
- synced with cm on march 7. 21:00 CET
- there should be no more SOD
- sdcard changes. EXT4 is now used as /data and as "internal" sdcard.
- a lot of optimalisations
Alpha 10:
- Android 4.2.2
- Refactored device make files
Alpha 8:
- 3G working
Alpha 7:
- Synced with CM repo on 13-01-2013
- Some more tweaking. Seems to work better. I have removed journaling from my sdcard and some more optimizing on my own sdcard. Perhaps i can do that in the update zip. Will have a loo at that.
- Included the RIL from VegaCream. Small change it will work. Cannot test myself.
Alpha6:
- Synced with CM repo on 04-01-2013
- Did some tweaking. Values can be changed as they are stored in /system/etc/init.d/rc1.d/01sysctl
Nice to see, that you are working on a new ROM!
VegaBean ist not running stable. So i will go back to VegaCream!
( I'll hope that i can use 3G in this Case - if not - my modem is defekt. i'll see it. )
Pleas go on and don't stop working - so that i have many months fun with my new tablet!
Edit: After a few Test with the older ics Version, i will try to Test ths on. Ich think my 3g Modem is defekt.#
EDIT2: I have try to install this via CWM - First Result: BRICK. I landing in a bBootloop - now i will try to install this via the NVFLASH.
Damn, i flash my tab @Silvester - cause i am ill
I will report again
Edit3: After install via NVFLash i Brick the Tablet hard. Try the second time to install an older NVFLASH. No Chance, no way. Whats happen? I have no idea!
Damn i hope - i can fix this problem. but it seems hardly to solve!
Edi4: Try 4 flashs again. But every time its stucking at the point where i attached the picture below. After flashing bevor i do a reboot, is this screen showing me. But i cant read what is standing there on the top!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NEED HELP - PLEASE GIVE ME A SOLUTION... Will not brick my 6 day old tablet.
Edit5: I have start the tablet und forgott it by watching a film. What is happen? I see a screen and the OS.
But: the Problem 1 is: after restarting i have wait 15 minutes that the OS is start up.
Problem 2: The touchscreen isn't working. i cant touch nothing! so i have reflash again
Wait that the alpha is going to be a beta please keep on working!
Edit6: Okay, today i have found the cause of my problem. It was my problem! i have flash the rom in the first step wrong. So my Touchscreendriver are broken: With this Manual i solve the problem:
[GER] http://www.android-hilfe.de/point-v...u-touchscreen-keine-funktion.html#post4332295
[ENG] http://www.modaco.com/topic/355021-...t-vega-viewsonic-10s-point-of-view-mobii-ect/
After this i flash this Alpha-Version new. And it is Insane FAST! For an Alpha very, very FAST and faster than the latest Version auf VegaBean. Only One thing is missing: The Playstore!
Now i'll try to Restore this.
In the Future, i'll hope that your work will going on.
FAZIT: THERE ARE NO PROBLEMS WITH THE ROM - IT WAS ALL MY FAULT! RUNNING VERY FAST AND ITS GOING IN THE RIGHT WAY! But only ONE SMALL bug, in the Craddle its reboot every 5 Minutes...
And shows me the error :"System UI" was accidently stopped ( in German is there standing: "Systen Ui" wurde beendet )
So i'll going back and will wait
Nice. Will flash this 2moro and report back
Sent from my Nexus 4 using xda premium
Doesn't work.
I have tried flashing this about 12 times. It doesn't work. I have both files the nvflash and also the update. I have been able to flash beta6 just fine. but the nv alpha5 just sits on the boot tried leaving for 30 minutes no change tried over and over again. even tried isntalling beta6 and then doing the update to alpha5 with gapps and just got boot loop. Both of these files dont' work at all or in anyway. Again I have been installing this over and over and over and over and over this simply does NOT work.
Myah said:
I have tried flashing this about 12 times. It doesn't work. I have both files the nvflash and also the update. I have been able to flash beta6 just fine. but the nv alpha5 just sits on the boot tried leaving for 30 minutes no change tried over and over again. even tried isntalling beta6 and then doing the update to alpha5 with gapps and just got boot loop. Both of these files dont' work at all or in anyway. Again I have been installing this over and over and over and over and over this simply does NOT work.
Click to expand...
Click to collapse
Do you have a correctly partitioned sdcard?
In my tablet infinite boot loop
this does work - use minitool partition wizard to create the EXT4 partition (i recommend 1gb)
http://download.cnet.com/MiniTool-Partition-Wizard-Home-Edition/3000-2094_4-10962200.html
Its working But following you have shoud to do:
Frist One:
- Flash The Beta 6 without the SDCARD in the Bay:
- Now Format your SDCard; First Partition FAT32, Secound Partition ext4. All Partition must SET UP as "PRIMARY"
- After this you can Copy the rom.zip on your FAT32 partition.
- Plugin your SDCARD in Tablet's SDBay and Reboot in CWM.
- With CWM you can flash the new ROM Now.
After this the Rom was working fine. Only the Reboots and the UI-Probs was getting on my nervs.
New version posted. See second post.
Verstuurd van mijn Transformer Pad TF300T met Tapatalk
Nice rom.
Installed and tested a little, amazingly fast, without gapps.
Once gapps are installed, I don't know what exactly happens (neither spent the time to find it), but system becomes unusable, extremely sluggish.
I have an 8GB Class10 lexar microsd, 4GB for FAT32 and remaining space for the EXT4.
I have yet to test, but been unable to reboot a couple of times and had to re-flash.
Particularly, on the case related to the sluggish performance, I have done some testing with jellybean and left /data on localstorage, and mounted microsd EXT4 (mmcblk0p2) to /data/app.
After this configuration change, speed came back to normal.
Problem with microsd cards is that they are not designed for random i/o, are between the worst performers on this matter, specially on random writes, typical OS usage.
I believe that the multiple i/o operations happening on /data is causing an extremely high iowait.
Well guys I must thank you I was about to get rid of my Vega when I thought I'll just check xda and see if for the old guy was receiving any updates and vola here is cm10 on 4.1 its great thankyou!!!
Can I get my titanium bkup working on this using my existing data from my jellybean biftor ROM from my galaxy s2? In fact does titanium work with this ROM?
Any help appreciated cheers
hoppi05 said:
Well guys I must thank you I was about to get rid of my Vega when I thought I'll just check xda and see if for the old guy was receiving any updates and vola here is cm10 on 4.1 its great thankyou!!!
Can I get my titanium bkup working on this using my existing data from my jellybean biftor ROM from my galaxy s2? In fact does titanium work with this ROM?
Any help appreciated cheers
Click to expand...
Click to collapse
BTW this is android 4.2 not 4.1.
4.2 even better been playing with it a little tonight and it is a massive improvement! I do have the issues then user above posts with sluggish behavior and random stoppages with the launcher? Can someone give me an overview of what the zram app does on this ROM plz never used it before? It reported an error the first time I started it but its working away now just not entirely sure at what lol
Cheers for any info....
Hey guys been running this for a few days as you can see above, I must admit and thank you all this has made my tablet usable again so thankyou. I have been collating some logs and test results to try and resolve the sluggish/lag on my device, unfortunately I haven't found a cure nor a real cause for it? I have used a little software to tune the ROM and switch some of the CPU governors etc but to no real avail.
Does anyone have any tweaks I can try to help resolve the lag?
The main area is when the tablet is multitasking it hangs and freezes and prompts to close the on screen app??
I also have my backs from my S2 working on my device via titanium bkup and a point to note is it is extremely slow to restore apps via titanium? Is this down to the SD ext4 again?
Again guys any help appreciated or any other links to another forum where this is been discussed would be great
Cheers
Awesome!
I'm gonna download and try it out when I have time!
There's still some life in the Advent
And I like it!
I have posted alpha 8 in second post. 3G is working
Verstuurd van mijn TF300T met Tapatalk
I've tested the rom for 2 days now and I can say that I really like the multiuser support now :9
The only problem is that it's a bit unstable, compared when you had aosp before.
It freezes sometimes works slow every now and then and newly installed programs may require a reboot to work properly.
But it's just alpha so what can I say?
This rom is good anyway
Waiting impatiently for a final release, i'll use my tablet again that's very cool from you
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This thread will be for my ICS builds which will slowly develop into Kyorarom Serenity (not to be confused with Eternity which will be Gingerbread based).
Basic Features
JIT
Rooted
CM9 built from source code (repository updated extremely often as I use it for my S2)
Kyoratweaks
Kyoralock (coming soon)
Kyoraapp
Hybrid Data2SD and SD card swap
Serenity Kernel
Overclock to 1.2GHz
CWM 5 recovery
Multi-boot
Voodoo Sound v10 (need to add app - coming soon)
What Doesn't Work
Bluetooth
Mobile AP
Camera previews
GPS
USB Mounting (UMS/MTP/PTP)
WiFi signal in the status bar
Still very slow (animations <- due to still immature drivers)
Camera.apk crashes for some
Sound recording
Live streaming of audio
SIM PIN lock (you MUST disable your SIM PIN code before using this ROM)
Sources
android/device/samsung/apollo
android/vendor/samsung/apollo
android/kernel/samsung/apollo
android/vendor/hillbeast
android/bootable/recovery
CM9 repository (Google for it)
Screenshots
Will come when I get time.
Demonstration Video
Might make one at some point.
Kyoraapp Thread (For Guides And Help With It)
Bugs And Questions Thread
Performance
Who really cares?
Credits
Team G3MOD for their kernel
marcellusbe for his work on the Galaxy 3
Kyrillos for all the scripts he's gotten working on this phone
moikop for his assistance with G3MOD Kernel and Kyoraapp
Shree_Jamdar for the Kyorarom Demo video
Rudolf895 for all his guides
RafayelG for helping and pointing me in the right direction
apollo5801 and Arakmar for their work on ICS to date
tom3q for his work on OpenFIMG and helping me with porting kernel 3.x
A big thanks all the respective developers of the included apps
And lastly thanks to Samsung for making a great phone and then screwing it up with weird software
Thanks For Donations
Check the Ascendency thread for the donations.
Planned Features/Requested Features
fs.convert
fs.options (easy peasy)
Do not enable Data2SD while in recovery
Touch recovery
Fix dictionary
/system/sd mount for Titanium (really wish that Titanium would stop being stupid and using a ridiculous location for it's SD-EXT partition...)
Changelog
27-06-2012
Updated OpenFIMG
CM9 RC1
12-06-2012
ROM branded as Kyorarom in modversion
New update.zip naming convention
Updated CM repo
Loads of tweaks all over the place from CM team
This fix didn't happen on the G3, only big phones - Boot animation now has Cid in it, rather than Andy (if you don't understand, you'll know what I mean when you see it) (I will be giving it my own boot animation at some point. I need to make my animation though. It's in my head, I just need to get the time to create it.)
Took MIUI out again seeing CM9 finally fixed the media player
Added 'hold Menu to search' function.
05-06-2012
Lock screen options easier to locate
Lock screen weather
New music player that ****ing works. (called Apollo - coincidence?)
Screen off CRT animation works
28-05-2012
Updated CM repo
Changed default background
21-05-2012
Data2SD
Hybrid Data2SD v2
Added MIUI Music (a lot of features aren't working right in it though, I will look at that when I care enough).
Updated to latest CM repo (nothing too interesting to see there)
init.d is now working
Kyoratweaks are working
08-05-2011
2-stage kernel boot
CWM 5.5 (non touch)
Force boot mode functionality (hold HOME to force normal boot, and hold MENU to force recovery boot - could be useful for people with broken volume buttons)
Faster boot
Removed G3MOD boot logo
Boot logs have moved to /tmp/ (stage1.txt for stage1 log, fsdetect.txt for FS Detection module, fs.current for showing current filesystem structure)
Updated CM to latest repo
Theme Chooser (see Settings -> Interface/Themes)
Lock screen shortcuts (see Settings -> Interface/Settings -> Lock screen)
DSP Manager has better support for WM8994
04-05-2012
Kyoraapp
Kyoratweaks (not working just yet, but the script is all there)
Kyoralock (not automatic yet)
Fixed assert issue in update.zip
Added SamsungServiceMode application. Use *#*#0011#*#* and *#*#4636#*#*. There's probably more but those are the ones I know.
bmlunlock built from source (smaller)
Using kernels busybox when updating rather than using a packaged one (saves space in update.zip)
Fixed adb install/pm command
Added File Manager
03-05-2012
Update.zip format (which will be the format for all future releases. If you cannot flash update.zips, then flash G3MOD kernel first).
G3MOD Inline Kernel Building (latest G3MOD on every release)
Fixed reboot menu (now says Download instead of Bootloader, and it reboots to download mode)
Fixed Superuser
Fixed Camera
Fixed Phone.apk
Fixed sensors
More free space in /system
Test 003
ODIN TAR
Integrated G3MOD Kernel (HB Test 002)
Test 002
First Build
Download Links
Serenity 2012-06-27 (update.zip)
Serenity 2012-06-12 (update.zip)
Test 2012-06-05 (update.zip)
Test 2012-05-28 (update.zip) (Dev-Host)
Test 2012-05-28 (update.zip) (Mediafire)
Test 2012-05-21 (update.zip)
Test 2012-05-08 (update.zip)
Test 2012-05-04 (update.zip)
Test 2012-05-03 (update.zip)
In case people are wondering where the ODIN.tars and system.imgs are, I am not going to release Serenity in those formats as they are not standards compliant, and make the file much bulkier than an update.zip. As well as that, they require more effort to produce. I am only releasing one ODIN version (the foolproof version) for in case people experience issues flashing the update.zip, and these issues should only exist first time.
Extra Downloads
Google Apps Mini <- small Google Apps package that gives you the basics to get running.
ODIN Version (foolproof method) <- For if installing the update.zip doesn't work right for you. This will make sure everything is set up how it should be. This release is outdated now so I suggest downloading this and the latest update.zip and updating after flashing the ODIN version. Includes G3MOD 2.5 OC version.
Non-OC Kernel (G3MOD 2.5)
LatinIME.apk <- full keyboard from SGS2 with all the dictionaries and such if they aren't working for you. This can be installed like any normal APK.
Guides
Installing update.zips
You will need to flash a kernel that includes CWM, or install CWM on a stock ROM. There are guides on how to do this. I recommend installing G3MOD to get CWM.
Copy update.zip to SD Card
Reboot phone into CWM (turn off the phone and turn it back on while holding both volume keys and the home key)
Go to "install zip from sdcard"
Choose to install the update.zip
Reboot phone
Enjoy Kyorarom
Adding Kyorarom support to your kernel
Add all the CM7/9 support functionality (basic stuff like USB and audio)
Make a copy of the defconfig (either .config or apollo_rev_02_defconfig) called cyanogenmod_apollo_defconfig
Edit the config to locate your initramfs (this will depend on where you keep your initramfs). If you use old G3 style (G3MOD, Fugumod) of storing the kernel with initramfs in a directory below the kernel you will want source/../initramfs, whereas if you use Kyorakernel style (initramfs inside kernel directory), you want source/initramfs. If you want 2-stage style, you will want source/usr/initramfs.list. Refer to my kernel to see how I did it as 2-stage is quite tricky and different to what we used to use.
Compile the kernel with the config (make -j2 cyanogenmod_apollo_defconfig) to test it works
Modify scripts/kconfig/Makefile as shown in this commit: https://github.com/dharamg3/G3MOD/commit/c8adf776285365d7fece528e20914d778e2a8d1a#diff-2
Clean the kernel repository (make clean) and (make mrproper)
Full Feature List
In a code box to save space
Coming soon
Bugs And Questions Thread
FAQs
nice going here Mark
I hope you'll be able to fix BT soon
What about Camera.apk?Does it work?
edit: lol...i missed camera app not working in 1st post
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sent from Galaxy
Hercolubus Rom v 2.1
powered by
G3mod by Arakmar 12/04/2012.zip
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It may be interesting
Good luck with this version.
Good Luck With This mate......!!!
Looking Forward to it....
Looking forward to Eternity. But all the best of this one too.
Interesting.
I think we can expect good rom because you are the one in cm9 devs.
All the best
Test 003 uploaded to Mediafire
Linky Brinky
I made an ODIN TAR this time not to annoy Linux/Mac users, rather to try to fix the issues people were having of boot looping in 002. If it still doesn't work then wipe your data. If it still doesn't work then take the SD card out. If it still doesn't work then your phone is broken.
Changelog
* ODIN TAR now
* Updated CM9 repo (more translations, and a few fixes that probably won't apply to the G3).
* Compiled with a few tweaks here and there.
great !!! tryin now
EDIT: what do you mean by sensors? all the sensors already work right?
nice work, Mark!
Tried Test build 003. First was stuck at the bootanimation. Factory resetted from the cwm and booted in.
The build seem to be more smoother than the other build.(I maybe wrong cause i havent tested the other ics build for quite a time). Other than that its nothing more special.
@hillbeast waiting for the kyoralock and other tweaks. Also can you try to port the same - kyoralock, kyoraap, and kyoratweaks into CM7. That would really boost the performance.
Thanks!
EDIT
BTW Does hybird data2sd work on ics??
EDIT2
There is a problem in calls. FC's when you call someone.
Good job ! For the next build, can you :
Include the newest GApps ? When I flash, Gplay is missing
Add an File Explorer ?
after flashing gapps, still the setup wizard not shown, not able to sign in to google. also browser fcs and no keyboard
Edit 1: No way to get to the market, no way to get to the SD Card, no way to browse the net or download any app via browser, no way to sign in to google, No setup wizard after flashing Gapps, infact no google app after flashing gapps Wierd problems...
By the way, ROM is blazing fast...
How happy am i to see this thread?
VERY HAPPY!!
Hum, yeah, I too can't seem to install Google Apps... It takes a very long time to start installing from the update.zip, but once I restart the phone, there's no Play or Talk... I can add my account, even though it doesn't work with calendar, etc.
jpaisneto said:
Hum, yeah, I too can't seem to install Google Apps... It takes a very long time to start installing from the update.zip, but once I restart the phone, there's no Play or Talk... I can add my account, even though it doesn't work with calendar, etc.
Click to expand...
Click to collapse
Don't try to install gapps, it will fail as the core ICS system itself take 90-95% of disk space. So gapps will not be completely installed when u try installing it. Only if we remove some core apps/files then only we can able to install it.
If you are interested then try my rom MPICS which has integrated gapps.
Phonerty CyanogenMod 9.1 (Android ICS 4.0.4) for HTC HD Mini (Photon)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome, This is My first page Photon OS ROM I uploaded, These ROM are based on Liberty ROMs. I modified it to work on HTC HD Mini Phones (Photon). This has Multi Languages support, It's Fast and smooth ROM for HTC HD Mini.
Most Things are working.
Known problems:
- Audio is Mono, means it doesn't have Stereo (Left & Right) Audio.
- Audio via Car's Bluetooth for Calling doesn't work only, but it's activated.
- Video Capture Recording doesn't stop, freezing for seconds then quits unexpectedly.
- Video Player is buggy, it plays videos fine at 240p but higher quality and above not very well.
- Sometimes USB cable doesn't wake automatically until you unlock the screen, Checking the (Stay Awake) in Settings is recommended.
- with some small other bugs,
Note: You have two options about Wifi & GPS, (You should install it after Phonerty Installed at CWM Recovery)
1- if you want Wifi, you will have to choose +Wifi-Photon, this will make Wifi work normally. but you won't have GPS.
2- if you want GPS, you will have to choose +GPS-Photon, this will make GPS work, and Wifi will work But connecting to network by Wifi may cause your CPU Clock at 100%, surfing internet by this once will be okay for about hour. and after that you should Turn Off Wifi and Restart Android.
By default the ROM is set on +Wifi-Photon. save those +two files on SDCard.. and you can always choose whatever time you need it.
Tip: Some Devices may have audio issue while calling person, So just tap on Speaker Button two times while in Call.
With 3rd Party Apps, you can Record video by using Videocam illusion Pro, and for Radio you can use Spirit FM. or find another apps that works.
It's Better & Recommended to Partition your SDCard using CWM Recovery in Advanced menu (this will erase SDCard completely) & to have a lot of space for many reason. choose 1GB Size, and Swap size 32MB. or whatever you like to be. and then Install/Open app "Link2SD" to active your Second Partition ext3.
This is only for installing on NAND, SDCard test not available.
- Note: Backup your Important Files, This may erase your Photon's Partitions automatically, also it may delete the "Android" folder with ".android_secure" folders on SDCard if include.
Downloads:
- Date Version 1 October 2013,
Phonerty CM9.1 OS ROM
Google Apps
Download Google Apps for CM9:
GoogleAppsICS(ics-20120429).zip
For latest Google Apps (CyanogenMod Wiki)
ClockWorkMod Recovery
Download; Munjeni's CWM Recovery Boot (16 July 2012):
CWM LK Boot Recovery (16-July-2012).zip
- Beginning,
Instructions: first you need a good microSDHC to Install the ROM. Don’t try on damaged or bad microSDHCs.
Steps: (Skip steps 1 & 2 if you already installed Munjeni's CWM Recovery LK Boot)
1- Beginning, Extract the "LK Boot" to some where you like to begin, open folder and extract the "LK Boot Photonic SDCard.zip" and copy its files in "LK Boot Photonic SDCard" without folder to the Root of SDCard, also copy the Google Apps with CM9 Photon ROM to SDCard.
2- Installing Recovery, In the Phone WM6.5, Open Explorer and navigate to SDCard and touch at HaRET, or if you're on another CWM Recovery, Restart & in White HTC press & Hold Volume Down until you're in FastBoot Mode, You should be in Fast Boot Mode to Install Recovery both in WM6.5 or others, Connect the USB cable to the PC (it may ask you the Divers needed for the device) and the Drivers are in the folder in "LK Boot - Photon" in "Google Windows USB driver" folder. After that click on “Update.bat” and Install both of them, when it’s finished fine try reboot it.
3- Installing the CM9 ROM, On HTC Boot Screen White Press and hold “Up Volume” the phone until you see entered Recovery, So in Recovery *, Go to (Install from SDCARD), then (Choose zip from SDCard), and now you're on the microSDHC, so choose the (Phonerty ROM) and choose Yes- Install, Wait about Minutes and it should be done, and then reboot the Phone.
Remember to Install the Google Apps after the OS installation completed, or you can also reboot Android to come back to recovery by press & holding “up volume” phone’s on HTC Boot Screen and choose the "Install from SDCard" and then "Choose zip from SDCard" so choose the Google Apps to Install, done and reboot.
* Make sure that you Wipe your Phone & format manually the Boot, Cahe, System, Data, by Recovery. only be careful that you don't format your SDCard at Recovery time.
More info about Restoring/Installing: Schlund's Information Page for HTC HD Mini
"Finally, you're ready to go Android. Have a nice try.."
The ROM is based on (WinSuk's 5 November 2012 Liberty CM9.1 ROM)
Kernel Source is made by Munjeni and Derefas, Kernel Link, or click this Link for more informations.
Themes,
As a Tip, Don't do that, only if you're tired of the CM9 theme or you've backed up Nicely.
You can simply Download the CM9's Themes on the Web. but it's not easy as MIUI, and at this stage it can be risky too (specially CM10 and above are risky), if you do wrong things, your phone may restart and wont reach android Boot... so you have to reinstall Android or the User knowledge knows to do. Do a backup before doing this, and if you lost your control on Android, your datas wont erase but you have to connect to computer and doing uneasy things.
All you have to do is active the Theme in CyanogenMod Theme chooser's Settings, And this a tested Theme by myself on my HTC HD Mini, iPhone Theme, Enjoy with Cyanogen Themes.
Soon I may add more Themes.
.
.
.
Credits:
& a Special Thanks to Munjeni, and Thanks to Schlund, derefas, SP3Dev, -r0bin-, RomanM82, Abdulla_91, tm.bax, WinSuk, blackphoenix50, ELdaArk, konnichiwa, & Thanks to other friends and all who helped to bring Android better for HTC HD Mini.
thank you for your effort firstly . I have some questions iplasm.
1-is this rom have black screen problem in call
2- how is the battery life
draltus said:
thank you for your effort firstly . I have some questions iplasm.
1-is this rom have black screen problem in call
2- how is the battery life
Click to expand...
Click to collapse
1- Sorry, I'm only on 2G Network, So I can't know how is it with 3G Black Screen Call Problem.
2- Battery Life is Perfect, just like Munjeni's Latest Photon CM9 ROM.
Edit; 3G Black Screen is Fixed now!
What is the difference between your rom with munjeni's rom
draltus said:
What is the difference between your rom with munjeni's rom
Click to expand...
Click to collapse
Like as I said as above: I edited it to work better on HTC HD Mini.
for example: Camera is Perfect both Preview and Save Image. also Camera360 works fine when you go to Camera360's Settings and check the Compatible Hardware Mode, it's Liberty Device, etc.
gps works?
Nice Rom
Hi,
just installed this rom....good work iPlasm...
Camera works good...and as said in first post Video not
Music is mono only :crying: as in all Android releases
GPS and Bluetooth also not working.
kosmachev said:
gps works?
Click to expand...
Click to collapse
Before changing rom, aspect GPS fix
the camera does not needed for me
Been checking DAILY looking for either a more functional ICs or CM9 ROM. Cant wait to test. Thanks!
ELdaArk said:
Been checking DAILY looking for either a more functional ICs or CM9 ROM. Cant wait to test. Thanks!
Click to expand...
Click to collapse
I'm stuck on the CM9 boot animation. I was running SCREAM CM7 before so I wiped the caches and formatted data, boot and system mounts but its still stuck on the boot animation. Been there for over 10 mins now.
Any ideas?
I am testing this rom yesterday. but I have a problem. I dont understand but I think this rom's battery life is not good. because I full charged the battery and I started to wait. last 8 hours I did not anything. no call no sms no internet no anymore. only open screenlock for the battery level control. now the battery level is 60%
I think munjeni's cm9 battery life is better than this rom
Found something in [email protected] commands for gps, but you need to try if it will enable gps! For this procedure you need to comunicate with radio!
Procedure is:
You need 2 window opened at same time. First window:
Code:
adb shell
stop rill-daemon
In seccond window:
Code:
adb shell
cat /dev/smd0 &
Back to first window again:
Code:
echo 'ATV1' >/dev/smd0
echo 'ATE1' >/dev/smd0
echo '[email protected]' >/dev/smd0
In seccond window you will see response from radio something like "start gps ok"... If gps message was ok, close seccond window and back to first window:
Code:
killall -9 cat
start rill-daemon
Close first window and... let me know if gps working! For info I have done new version for Aria and will upload it today to aria forum!
thank you I can not understand. I did it what you say .
result : I did not saw any message in second window from radio ?
I'm not sure I made the right
Ok, so its something liike not supported on photon
munjeni said:
Ok, so its something liike not supported on photon
Click to expand...
Click to collapse
I'm still using schlund's CM7.2 and GPS works like a charm.
Maybe I can help with some logs, etc.?
Or CM9 is much different then CM7?
Sound got better since it's a consistent aria rom now? DSP working by any chance?
RomanM82 said:
Hi munjeni,
I am new user of XDA Developers. I am not permitted to post in your thread or theard by iPlasm - new USER :-( .
I tried exchange gps files between ROM by iPlasm (YOUR modified ROM) and ROM - HTC HD MINI Sense 3.5.
Copy files from Sense 3.5 to iPlasm ROM: gps.conf, gps.goldfish.so, gps.liberty.so, gps.photon.so and libgps.so
Now, my phone see satellites. I tried navigation... OK! )))
I didn't want hack HD Mini Sense 3.5. Only try something to do.
I wrote similar message to iPlasm.
I hope that it is good for your and iPlasm develop.
RomanM82
Click to expand...
Click to collapse
Hi guys, This message was sent by new user that is not allowed to post in development forum, so he say he got gps working using these libs! These libs is from old SDK so I think there will be (maybe?) segfaults! After you replace libs, and if gps realy working you need to look in logcat to be surre that if there is not a problems!
ELdaArk said:
I'm stuck on the CM9 boot animation. I was running SCREAM CM7 before so I wiped the caches and formatted data, boot and system mounts but its still stuck on the boot animation. Been there for over 10 mins now.
Any ideas?
Click to expand...
Click to collapse
Still hoping someone can help. I wondered if it might be my SD Card which is and 8 gb SD HC. Backed up all my data, formatted it, copied the ROM zips back and reflashed. On first boot, same story; I'm stuck in the boot animation. I'm running CWM 5.0.2.7 and I've repeatedly flashed CM7 ROMS so I don't think its a CWM issue.
Is there something I need to do prior to upgrading to CM7?
Any ideas at all?
sorry friends, I was too busy in this three days... anyway let me answer
draltus said:
I am testing this rom yesterday. but I have a problem. I dont understand but I think this rom's battery life is not good. because I full charged the battery and I started to wait. last 8 hours I did not anything. no call no sms no internet no anymore. only open screenlock for the battery level control. now the battery level is 60%
I think munjeni's cm9 battery life is better than this rom
Click to expand...
Click to collapse
draltus, before this three days, I fully charged to 100%, and after three days taken some pictures and battery percentage 13% at night, I can't get that even in WM6.5, so I don't know how was that with you.?
munjeni said:
Found something in [email protected] commands for gps, but you need to try if it will enable gps! For this procedure you need to comunicate with radio!
Close first window and... let me know if gps working! For info I have done new version for Aria and will upload it today to aria forum!
Click to expand...
Click to collapse
Munjeni, I going to try it soon as possible.
munjeni said:
Hi guys, This message was sent by new user that is not allowed to post in development forum, so he say he got gps working using these libs! These libs is from old SDK so I think there will be (maybe?) segfaults! After you replace libs, and if gps realy working you need to look in logcat to be surre that if there is not a problems!
Click to expand...
Click to collapse
yes, he write to me also, and I will see it then upload new ROM it here.
another thing Munjeni, I tried your new Aria ROM [9 July 2012], but it stuck at the Boot screen, I can see the new Cyanogen Man Logo.
-----
ELdaArk, did you installed the new LK boot from munjeni?
I think maybe boot.img need to be repacked, or at least maybe not enought space for system? Try adb shell df and see how many free mb is in system partition!
Maybe?: Final Note
Hello everybody,
I'm sad to announce that my Galaxy Y has died on me.
Not completely, but the USB port seems to have died on my phone.
Charging through the connector still seems to work, but other then that the device is not recognized by any computer anymore.
I know a lot of you are thinking of drivers right now, but this is not the problem.
Not even the phone detects anymore when it's connected to the phone.
This renders the device rather useless for developing as a USB port is really important in this case certainly when having a bad kernel.
I have three options left right now.
- First option would be to hand over the complete development to another developer owning this device. Of course I will help you get started with my sources so you can get started where I left.
The second and third option is up to the community
- If there is anybody in the community who knows somebody who doesn't use the Galaxy Y anymore or is willing to donate his/her own phone this would help out a lot as then I can continue myself in this development.
- Or if anyone could spare some money you could also donate it to me over PayPal. These donations will only go towards buying a second hand Galaxy Y, and will be evenly divided between all donates all money which is left in this case will be reimbursed evenly to everyone who donated to me.
Whichever everyone chooses, I want to let everybody know I enjoyed developing for this community.
Greetings PsychoGame
Big Update: First alpha release for CM7.2 Samsung Galaxy Y (GT-S5360) Alpha 5
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation instructions are simple:
If you are not working with my kernel:
- Flash my provided boot2.tar file to you're phone using odin (You can download the boot2.tar from here)
If already on my kernel:
- Download the cyanogenmod5.zip file from my dev-host: here (Older releases can be found later in the post!)
- Download the Google Apps from here
- Copy the cyanogenmod.zip and the downloaded gapps file to somewhere on your SD-Card
- Boot in CMW by holding (Volume UP + Select) button while powering up.
- In CWM go to Mounts and Storage first and format /system, /data and /cache.
- Go back to main menu in CWM and choose install zip from sdcard and choose zip from sdcard.
- Apply cyanogenmod.zip
- After installation also apply the gapps-... from here
- Do a wipe data/factory reset from the CWM main menu and reboot the phone
- Be patient while the phone boots for the first time, the phone needs to build up the dalvik cache.
- When fully booted happy testing , and don't forget to report you're findings and bugs.
What works:
- Audio
- Bluetooth (Partially: The device is able to scan for other devices and is also found by other bluetooth devices. Sending files works, receiving does not)
- Camera (Partially: Can take pictures but unable to record film material For more info look at: "known bugs")
- Display "Hardware Accelerated" (Also with some small bugs and glitches, look at "Known bugs")
- GPS
- Input
- Lights
- Network interfaces (Mobile internet)
- Power management
- Radio (Phone "Incoming and Outgoing calls")
- Sensors
- Storage
- Vibrator
- Wifi
What doesn't work:
- Media, media_profiles.xml is included, but the OMX interface still needs to be properly ported which is a WIP.
Known bugs:
- Display: Sometimes there appear to be some glitches. This is known, and due to the usage of a released test binary. I'm currently working myself to reverse engineer the test binary released by BroadCom and the proprietary binary included in the GT-S5360 to come up with a hopefully fixed driver.
- Camera: Still has the white screen bug in the preview of what you're taking a picture of. This is not easily fixable, but will do my best. Movie recording is not yet possible as codecs still need to be included in my build.
Troubleshooting:
Sometimes the Google Apps are giving some troubles with Force Quitting etc., a solution for this is to boot to recovery, clear the cache and dalvik cache and after this do a Fix permissions from the Advanced menu. When rebooting the boot process will take a little longer because the dalvik cache needs to be rebuild.
When anybody has some problems getting it to install through my instructions feel free to ask help in this topic.
Downloads:
- CyanogenMod 7 Alpha 1 Release: http://tinyw.in/VJll
- CyanogenMod 7 Alpha 2 Release: Build Removed (No incoming calls)
- CyanogenMod 7 Alpha 2.1 Release: http://tinyw.in/r4Xs
- CyanogenMod 7 Alpha 2.2 Release: http://tinyw.in/AB92
- CyanogenMod 7 Alpha 3 Release: http://tinyw.in/1G7T
- CyanogenMod 7 Alpha 4 Release: http://tinyw.in/DLUU
- CyanogenMod 7 Alpha 5 Release: http://tinyw.in/dZz0
Changelog for Alpha 2:
Bugs Fixed:
- Not all apps had a ldpi overlay. This has been fixed in the last build I forgot to set the overlay in my full_totoro.mk
- USB Mount didn't work in android. This has also been fixed, I forgot to add the string "file" in the path to the lun file. USB mounting now works as it should work.
- Somebody pointed out that MAC address in the settings wasn't set correct. I researched this problem and it was indeed a bug in my build. This has been fixed now by including the get_macaddrs script in /system/bin. The MAC address wasn't correct because the RIL didn't pass through the MAC address.
Added functionality:
- Compcache has been added to this build. Standard it isn't enabled. To enable this you have to go to: Settings -> CyanogenMod -> Performance -> Compcache. You can choose to allocate 10, 18 or 26 percent. The most recommended value I believe is 18%, but using compcache also has some downfalls. See here for more information: http://en.wikipedia.org/wiki/ZRam
- Wireless Hotspot. This has been tested by me, and I can confirm this function is working perfectly. USB Tethering will be supported hopefully next week.
Changelog for Alpha 2.1:
Bugs Fixed:
- Small fix, I changed the system.prop this week, and in the process forgot to put the ro.telephony.ril_class=samsung option back in the system.prop which results in no incoming calls.
Changelog for Alpha 2.2:
Bugs Fixed:
- Big breakthrough, Headset Support Working. A name in the /system/lib/modules folder of the file brcm_headsetsw.ko had to be bcm_headsetsw.ko. This was why the kernel didn't swich to headset. This was a bug which had slipped my eye as the module name is wrong when compiled from kernel source. This is now completely fixed. And as far as I know this phone doesn't have the Headset Volume Bug. At least not on my phone. Credits go to bluestarfish who pointed this out.
Changelog for Alpha 3:
Bugs Fixed:
- Reverted my system.prop so the tweaks from my first build are included again. Also added some extra tweaks which should reduce the graphics glitches.
- Unsure if GT-S5360L is now able to boot. I haven't got this phone myself, so I can't test it. If it's not working sent me a PM I'll add you on GTalk so we can communicate more easy and fix.
Added functionality:
- Camera: You are able to take pictures, only movie recording is still not possible. This will be a project for later as I'm very busy with bluetooth at the moment.
- Bluetooth: Bluetooth is able to scan for devices and is able to be located by other devices. Pairing or sending from/ to the device is still not possible. Hopefully this will get fixed next week.
Changelog for Alpha 4:
Bugs Fixed:
- The Force Close issues have been resolved. So installing gapps now after CM7 is installed doesn't result in a Force Close error anymore. This is thanks to Gadgetroid.
- Proper apns-conf.xml file has been placed in the /system/etc folder, so this build contains almost all provider APN data now.
- Bluetooth has been made more stable. You can enable bluetooth now without Bluetooth crashing. You're now able to sent files to other devices, only receiving is still not possible. But were getting closer every build .
- Headset: Has been fixed again. My build sources got mixed up a little bit so bcm_headsetsw.so by accident got renamed to brm_headsetsw.so which rendered it unusable.
Added functionality:
- FileManager: The standard filemanager for CyanogenMod has been introduced into this build for everybody who was missing it.
Changelog for Alpha 5:
Bugs fixed:
- The compatibility issue with different basebands and GT-5360L has now been solved.
If you're on alpha 4 you dont need to download the whole alpha 5 again. Only use the boot2.tar provided above to flash the new kernel with Odin.
Credits:
- Myself
- Bluestarfish
- Gadgetroid
- WhiteXP
- Squadzone
- Cyanogen
If you appreciate my work please hit thanks or donate me one beer by clicking the "donate to me" button. I'm investing a great deal of time in this project to make this a very stable product.
Greetings Psycho Game, and have a nice weekend everybody. My sources will be released to my Github next week, so I ask everybody to be patient for that .
Everything below here is old information, you can still read it though to get an idea of the project:
As I already said in another thread about a CWM included kernel I'm also working on a version of CyanogenMod myself with another approach than WhiteXP's build.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y myself at first (until 2 day's ago), but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the makefile of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: Complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary (RFS has been removed, only FSR remains for later. [status: WIP -> stalled]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: Complete]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. (Only ADBD has to be fixed) [Status: 99% Complete]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
CM already compiles fully without much warnings, but still isn't ready to be released until all predecended steps have been completet.
At the moment I'm also uploading all sources of the kernel into github, so everybody can revieuw the proces i'm doing, and also point out mistakes maybe and give suggestions.
Update 1: Yes already an update. It's more difficult to work you're way around the FSR kernel modules. What I now want to do is convert the BML block layer (which uses the FSR modules) to MTD which is an opensource version of a Flash Transition Layer. I know this is possible, because it's also done on the Samsung Epic 4G. The only downside of this is that I cannot use the promised ext4 anymore on the final product, but I'm forced to use YAFFS2 filesystem (which is luckily also opensource).
Update 2 (1 Feb. 2013): Hello everybody. After almost a week I have another update on the Kernel modifications. I stalled the removal of the fsr module parts for now and started with the inclusion of the ClockWorkMod recovery in the kernel. The way I included the CWM recovery is other than Merruk and WhiteXP did. I left the stock recovery in place, and added the CWM on top of it. Standard it boots in the CWM recovery, but if for some reason you would need the stock recovery you can also call it. Just by leaving a file called .stock_recovery in the root of the /cache partition. So in short it contains 2 recovery's in one image. To make it all fit the InitramFS and kernel have been compressed using the lmza method. This allows for a smaller resulting boot.img file, but comes with a little extra boot time. When android has booted you don't notice any difference. Appart from this it's a stock kernel with ext4 included, and the rfs filesystem modules removed, so it's a ext4 kernel only! The completely changed initramfs can be found on my github over here: https://github.com/PsychoGame/totoro_initramfs_files.git so everybody can study what I've done.
Update 3 (8 Feb. 2013): Hello everybody. Again an update of my kernel, and a weekly build to test in the weekend . There have been some changes in this release, the most major change has been that the kernel has been patched from 2.6.35.7 to 2.6.35.14. Also a little change in the recovery.fstab stopped the nandroid backup from making a useless recovery.img. Also I now know for sure that it's possible to do a full nandroid restore. As long as the FSR modules still function also the boot.img backup will be restored. The only thing still not working is the Android Debugging Bridge in the recovery self. This seems to be a harder to tackle problem then I thought before. It seems that adbd is not working properly so it doesn't see the device. The new kernel can be obtained from here:
boot.tar (08/02/2013)
With this new 2.6.35.14 kernel you also need to have all other updated compiled modules which are available here:
Version14Modules.zip
These files should be placed in /system/lib/modules
This is not a CWM installable package at the moment because I'm a little bit busy at the moment, so this means you have to copy the files manually to the directory.
I recommend using ES File Explorer in which you need to have full read/write acces to the disk.
When anybody needs some extra help please let me know.
There are two small bugs at the moment:
- ADB still not working inside recovery
- Sometimes the touchscreen has a little problem getting out of it's sleep state. I don't know how to describe it, but will look into this problem very soon. It's not a harmfull bug.
Question to other developers: Hopefully there are other kernel developers among us as well. If you think you can contribute to this as well, then please PM me. At the moment I hope everyone together including myself will look into implementing MTD into out device.
The kernel source is uploaded to https://github.com/PsychoGame/android_kernel_samsung_totoro.git Updated
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Installation Instructions
It's wise to make a EFS backup first to be sure you're IMEI data etc. is safe at all times. It's not only wise for this project but other projects as well. A good tool for this is Galaxy ToolBox. This tool saves the backup on you're SD card which you should keep safe on you're computer
Here are the installation instructions of the first kernel release:
Known bugs:
- Adb is not working in the CWM at this moment. I'm pretty sure it's a simple problem, but will solve that later on. It's not very annoying as anyting else is in my opinion functioning.
In my walktrough I will cover the steps for installing my kernel on a fresh install of Android.
There are a ton of walkthroughs already on the subject of flashing android to the Galaxy Y (GT-5360) through odin.
I didn't test it yet on a working installation, but I'm pretty sure this should work in there also.
Step 1: First of all, download the needed files
- cwm-madteam-galaxY.zip
- boot.tar (01/02/2013)
- boot.tar (08/02/2013)
- Version14Modules.zip
- Odin 1.85 Used
- update-signed.zip (Su Binary)
Step 2: Make a nandroid backup of you're device using Madteam's ClockWorkMod.
Step 3: Enter download mode (Holding down button + Select) + Power button until the phone seems to boot. In download mode flash my supplied boot.tar by putting it in the PDA field in Odin. No .pit file is required, and just leave anything default and click the (flash button).
Step 4: Enter CWM recovery (holding up + select) + Power button until the phone boots, and go to mounts and storage and one by one do (format /data, format /system and format /cache).
Step 5: Also in the menu Mounts and storage click on mount USB storage while the mobile is connected to the computer with the USB cable, or use a cardreader to open you're miniSD card. On the miniSD card there is a folder which is called clockworkmod which contains the backup you just made in the folder backup. Here you should change as an example (system.rfs.tar to system.ext4.tar), and also do this for the data.rfs.tar. Also inside nandroid.md5 these filenames have to be changed accordingly to resp. system.ext4.tar and data.ext4.tar.
Step 6: Reboot the ClockWorkMod Recovery and in the backup and restore menu click on "advanced restore" and choose you're nandroid backup. Choose only to restore (System and Data.)
Step 7: Just reboot and enjoy you're Galaxy Y with CWM included in kernel. As far as I tested everything is working as it should be, if you come across something that doesn't work please report this.
Step 8: Copy the modules supplied in Version14Modules.zip to /system/lib/modules/
If you flashed a fresh android rom you should Root it again using the update-signed.zip I supplied above this article (Before you install the update-signed.zip you have to mount the /system partition in the "Mounts and storage menu" first the mount is forgotten in the installer script.)
I hope you'll enjoy this little beginning, there's a lot more to come. I'll be gone for the weekend, so after the weekend I will be able to respond to any bugs and problems everyone came across.
Greetings
Psycho Game
gud luck !!!!:good: buddy
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I smell a new developer here.. Or maybe a reincarnation of maroc
Good luck bro!
Sent from my GT-S5360 using XDA
:good:
:highfive:
keep it up bro..
reserved
great initiative
really appreciate your efforts - good luck and go on !
hell_lock said:
I smell a new developer here.. Or maybe a reincarnation of maroc
Good luck bro!
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
i think reincarnation of maroc....
good luck bro...
carry on ur work..
good luck bro, i can be pray for you
Thanks for the positive comments already, I will try to be as open about the development as I can.
By this I mean that I try to explain every step I do, in my github, but also in the forum so that somebody else could reproduce all the steps I did to create the same thing as me.
So also people beginning with development can try to understand what I'm doing.
Also I will keep this thread as updated as possible.
Greetings PsychoGame
PsychoGame said:
... I will try to be as open about the development as I can.
By this I mean that I try to explain every step I do, in my github, but also in the forum so that somebody else could reproduce all the steps I did to create the same thing as me....
Click to expand...
Click to collapse
I am as excited about that as I am the ROM itself, I will be following this with interest!
Thanks for your efforts so far and for all the work you will put in to realise this project in the future :good:
Stokey
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
Subscribed +2
Awesome work
I expect more from u :thumbup:
jasonxD Leveled to 2
Just wanna ask one question -
Isn't kernel 3 made to make it compatible with ICS/JB ?
If yes, then isn't White's kernel based on kernel 3 ?
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
Ramdisk makes ics/gb/jb boot.. U dont need 3.x kernel for that.. Just make some changes in stock ramdisk and u r good to go.
Sent from my GT-S5360 using XDA
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I like thread.
I subscribe.
---------------------------------------
Questions? Better go to [Help Thread] Ask ANYTHING! xD
Gamer R said:
Just wanna ask one question -
Isn't kernel 3 made to make it compatible with ICS/JB ?
If yes, then isn't White's kernel based on kernel 3 ?
Click to expand...
Click to collapse
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
PsychoGame said:
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Click to expand...
Click to collapse
Very complicated it is..
Sent from my GT-S5360 using XDA
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
I love u
Phone Slow? go ------>HERE<------
Ubuntu phone OS announced
what do u think share your thoughts --->HERE<---
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
--Sent from the future with a galaxy s4 like a freaking BAWS--
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
PsychoGame said:
No, ICS for the Samsung Galaxy S Plus was running on the 2.6.35.14 kernel at first.
Only there was a big interest in using kernel 3.0 because this contains many new features and improvements over 2.6.35.14.
So that's why they ported the 3.0 kernel.
White's kernel is also based on the 2.6.35.7 kernel which is used by samsung.
On this moment the Galaxy Y is still limited this kernel serie because the use of RFS and also the FSR (Flash Transition Layer) which are both closed source.
Getting rid of RFS isn't a big deal, that's a matter of converting all the filesystems to EXT4.
The problem is getting rid of FSR, this is a module that's needed to make the NAND accessable for the kernel.
So if you want to break free from the 2.6.35 serie of the kernel you need to use opensourced modules.
As I already found out this isn't very easy to do.
An opensource version of a "Flash Transition Layer" is MTD.
But to use this you have to enable the MTD support in the kernel, and convert the BML to MTD.
That is what I'm currently trying to do.
The problem is that the promised EXT4 support for the /data, /system, /cache, and other phone partitions will not be possible anymore.
In that case I'm forced to use YAFFS2, which is also an opensource filesystem luckily.
Greetings
Psycho Game
Click to expand...
Click to collapse
The amount of ur knowledge in this kind of stuff is TO DA*N HIGH
Thanks for ur hard work...
jasonxD Leveled to 2
Re: [CWM & CM] Port of CM7 with kernel 2.6.35.14 & EXT4 as base without RFS & FSR
jasonxD said:
The amount of ur knowledge in this kind of stuff is TO DA*N HIGH
Thanks for ur hard work...
jasonxD Leveled to 2
Click to expand...
Click to collapse
Maroc 2.0
Phone Slow? go ------>HERE<------
Ubuntu phone OS announced
what do u think share your thoughts --->HERE<---
_____________________________________
This post uses the patented TingTingin®™ method I would teach it to you but you are not yet worthy (come back in a hundred years)
--Sent from the future with a galaxy s4 like a freaking BAWS--
IMHO most of problem from cm 7 (source) porting come from vendor's proprietary library. i don't think putting effort to porting sgy kernel to 3.x version is worth it. fs and partition only 'small' thing to do. you still have to port gpu, camera, baseband, and other modules which is more difficult.
Latest versions: Clean ICS (in 3rd post) /H1N1 CM9(in 2nd post,updated: 2013.05.03) /H1N1 CM10 (updated: 2013.08.20)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
H1N1 CM10.1 (from bagyusz)
cm-10.1-20130803-UNOFFICIAL-cocktail
Code:
[LIST]
[*]Changelog from [I]cm-10-20130803-UNOFFICIAL-cocktail[/I]:
- Updated CM source
- Data usage monitor fixed
- BT permission problems fixed
- Background running apps set to 10
[/LIST]
[LIST]
[*]Kernel (only major fixes listed):
- 3.0.90 updated
[/LIST]
[LIST]
[*]Known problems:
- if using HDMI, do not push power button...
[/LIST]
Sources:
THX IUSS/FONIX232
Codeaurora
CyanogenMod
legaCyModandroid_device_alcatel_cocktail ||commits
android_kernel_alcatel_cocktail ||commits
Downloads:
1: OT-995 CM10.1 Gapps(2013 08 03)
2: cm-10.1-20130819-UNOFFICIAL-cocktail
3: CWM_6_20130615
+1: patch for phones with GB bootloader
Installing:
- download base rom and googleapps, copy to SD card
- use/boot to CWM_6_20130615
- make full wipe, format "system", "system/app" , "data" partitions too
- CWM "Install zip from sdcard" ->"choose zip from sdcard" , select rom then install
- repeat previous step, but choose gapps pack
- if your phone has GB bootloader, use GB patch (it will be released always after 1-4day)
Important: After installing rom, double reboot to fix MAC addresses and USB ID
Dont use independent boot.img for older CM releases becasue of changed SD card mount path.
Im just post that, bagyusz made this!
I personally recommend to use Seeder app, to make system more fluid (in apps, like facebook, etc)
CM9 project
Test version is out - CM9 + gApps. Use CWM5 to install.
No 720rec/hdmi/PC sdcard mount. Touch same as CM10. Shared for testing purposes.
Sources. (working tree, of course)
Clean ICS project
Download and install from recovery. Shared for testing purposes.
*if cant boot or display errors, use attached boot img. (fastboot flash boot boot_245.img)
If you able, support developers.
Great, I hope plenty of feedbacks to help determine what needs to be work on
Good work h1n1 team
Now we're talking....
Good job H1N1 team!!!
Thanx wwenigma & bagyusz and ı see flash cwm 5 is possible ? i think it must be cwm 6 ? and about battery life and scrolling ? and what next come 4.2 or better 4.1.2 ?
HoScHaKaL said:
Thanx wwenigma & bagyusz and ı see flash cwm 5 is possible ? i think it must be cwm 6 ? and about battery life and scrolling ? and what next come 4.2 or better 4.1.2 ?
Click to expand...
Click to collapse
In my opinion, battery life is much better than other ROM before. about scrolling it stills a little beat laggy...
If we could have a 4.2 ROM that would be awesome, really awesome!
Iuss try to modify CWM to use CUSTPACK partition to System/app automatically. (he say'd we wont get official CWM support if we not able to install official gapps packs) This CWM wasnt finished. I cant see any sign of official CM support so this is not need.
Scrolling and battery life. Scrolling is little "jumpy", but not bad. Need some fix (bagyusz working on it) Battery life is under testing (1 charge = 10minute call + 30minute using + 36hour standby), power management is not applied.
About upcoming releases. Time will tell.
Today the third day when i wake up the clock's alarm sound. Its working.
Torch app - i never use, on original ROM it cant working after few day. I recommend this app: https://play.google.com/store/apps/d...uni.flashlight
Wifi/3G switch working.
Click to expand...
Click to collapse
OK, maybe I was too sleepy and couldn't ear the alarm sound... I'll test it later.
About the flashlight I do not use it too much times but sometimes is very useful. I'll try the app you have recommended.
About Wifi/3G switch is working for me either...
OTG
Have anyone tried to connect mouse/keyboard via USB? Is it necessary for connected device to have its own power supply? Right now I do not have OTG cable to try.
Sv: [ROM][OT-995][CM10.x] H1N1 CM10 ROM (from bagyusz)
wwenigma said:
Iuss try to modify CWM to use CUSTPACK partition to System/app automatically. (he say'd we wont get official CWM support if we not able to install official gapps packs) This CWM wasnt finished. I cant see any sign of official CM support so this is not need.
Scrolling and battery life. Scrolling is little "jumpy", but not bad. Need some fix (bagyusz working on it) Battery life is under testing (1 charge = 10minute call + 30minute using + 36hour standby), power management is not applied.
About upcoming releases. Time will tell.
Click to expand...
Click to collapse
First of all, nice work!
About gapps, it's not legal to distribute them with a ROM without a license from Google and since it's closed source there is no way around it.
Cyanogenmod were threatened with legal action for doing so a few years back so they removed it.
Here's a link with info regarding that: http://androidandme.com/2009/09/hacks/cyanogenmod-in-trouble/
A simple way around it would be to provide a gapps package with an updater-script that installs them into /custpack.
Skickat från min ALCATEL_one_touch_995 via Tapatalk 2
jinxxed, from what i see, they provide it separately, so no issue on that
Sv: [ROM][OT-995][CM10.x] H1N1 CM10 ROM (from bagyusz)
BENETNATH said:
jinxxed, from what i see, they provide it separately, so no issue on that
Click to expand...
Click to collapse
I missed that completely, my bad.
Skickat från min ALCATEL_one_touch_995 via Tapatalk 2
Jinxxed said:
First of all, nice work!
--------------
A simple way around it would be to provide a gapps package with an updater-script that installs them into /custpack.
Click to expand...
Click to collapse
Ty!
Cyanogenmod team wants a solution to install gapps without any modification. Thats why modded CWM6 released anno, because not enough space in System partition and partition resize isnt available. Then Iuss and fonix cant finish that project. (we talk about that with heimdallr75 , maybe there is a way to resize partitions, but first resize is dangerous)
FilipFry said:
Have anyone tried to connect mouse/keyboard via USB? Is it necessary for connected device to have its own power supply? Right now I do not have OTG cable to try.
Click to expand...
Click to collapse
I think 200-300mA is available via OTG.
Sv: [ROM][OT-995][CM10.x] H1N1 CM10 ROM (from bagyusz)
wwenigma said:
Ty!
Cyanogenmod team wants a solution to install gapps without any modification. Thats why modded CWM6 released anno, because not enough space in System partition and partition resize isnt available. Then Iuss and fonix cant finish that project. (we talk about that with heimdallr75 , maybe there is a way to resize partitions, but first resize is dangerous)
I think 200-300mA is available via OTG.
Click to expand...
Click to collapse
Yeah, resizing requires QPST scripting and there is a good chance of destroying the phone.
One solution is to use mini_phone.mk that will put out a rom that is less than 180MB in size.
Of course, it's easier to just change the recovery to fix it like ius did.
All you really need to do is to add the mount lines to recovery and nandroid before compilation.
Skickat från min ALCATEL_one_touch_995 via Tapatalk 2
Anyone tried USB OTG ? If it's working i would be like a barrel filled with happiness rolling down the floor, because i always wanted to have that particular feature on a mobile device
i didn't even know that It was be possible to enable OTG on any device, because i thought it was hardware based modification. Great job, seriously.
i've made some modifications, listed in my github, after inclusion of bagyusz commits (branch:master)
here is my build : http://pa-ot-995.googlecode.com/files/cm-10-20130220-UNOFFICIAL-cocktail.zip
changelog :
- ics and gb bootloaders should work
- Torch works
- battery stats are working
wwenigma, can you add it to OP ? i don't think i have to create a new topic for that. Hopefully, bagyusz will update his git to track his progress, i'll do on my side.
BENETNATH said:
i've made some modifications, listed in my github, after inclusion of bagyusz commits (branch:master)
here is my build : http://pa-ot-995.googlecode.com/files/cm-10-20130220-UNOFFICIAL-cocktail.zip
changelog :
- ics and gb bootloaders should work
- Torch works
- battery stats are working
wwenigma, can you add it to OP ? i don't think i have to create a new topic for that. Hopefully, bagyusz will update his git to track his progress, i'll do on my side.
Click to expand...
Click to collapse
BEN, can we flash it over the latest release from H1N1 or does we have to wipe everything?
yep, but you'll need to wipe cache and i think also flashing gapps again, may be not useful, give a try and inform us
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fire Nexus ROM
Introduction
This ROM is based off AOSP marshmallow. I have merged changes from CAF and Cyanogenmod to enable this boot on our HDX devices.
Features
- AOSP with optimisations from CAF
- Open GAPPS nano is built-in
- Clear all recents
- Advanced Power Menu
- Substratum Theming Support
- Init.d Support
- SuperSU is built-in
Prerequisites for Installation
- Unlocked bootloader is a must
- TWRP 3.0.2-0 installed
- This does NOT work with Safestrap
Downloads
*** Please do NOT create any mirrors ***
- Fire Nexus ROM for APOLLO
- Fire Nexus ROM for THOR
Issue List
- Sideloading of some apps may be necessary
- Bluetooth
- LTE
- WiFi may need to be manually toggled after wakeup
Kernel Source Code
- https://github.com/CyanogenMod/android_kernel_amazon_hdx-common
Credits
- AOSP
- CodeAurora Forum
- Cyanogenmod
- Substratum Team
XDA:DevDB Information
mm-fire-nexus-rom, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-10-22
Last Updated 2019-10-02
Release Notes / Change log
22 October 2016
- Initial Release
- Xposed needs testingConfirmed as working
Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).
schr01 said:
Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).
Click to expand...
Click to collapse
Yes, rotation is a problem. If I remember rightly it is the same issue as with other custom ROMS. Try locking the screen rotation in the correct aspect then running open camera again. The app should then appear correctly.
Thank you for your tip. It works.
Woohoo!
Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!
Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.
The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.
Really nice work, @ggow. Clean and simple.
Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.
Davey126 said:
Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!
Good to hear Xposed is working and your problematic messaging app
Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.
I would expect CM 12.1 data restore to not work. The framework in this ROM is very different from CM 12.1.
You might also run into problems dirty flashing from the KitKat build of the ROM.
Clean flash would be recommended in both cases when coming from an older or different ROM.
The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.
Kids sometimes use my tablet so having the reboot to recovery options etc can be a problem.
Really nice work, @ggow. Clean and simple.
Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.
Click to expand...
Click to collapse
Thanks for the detailed feedback :good:
Thank you for nexus rom.
Thank you for nexus rom.
It works almost good for me, but google contacts cannot synchronize gmail account.
In nexus5 (6.0.1), it can be synchronized by contacts->settings->accounts->google.
In thor, contacts->settings->accounts->(not shown google).
Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?
rootnooby said:
Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?
Click to expand...
Click to collapse
FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)
ADB Backup/Restore
May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).
Anyone else experiencing this?
I had no installations problemes with TWRP 3.02.
Davey126 said:
May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).
Anyone else experiencing this?
Click to expand...
Click to collapse
Will take a look, before the next release.
ggow said:
Will take a look, before the next release.
Click to expand...
Click to collapse
Thanks. Two reasons for wanting this:
- transfer apps and all associated data between devices
- create targeted backups or nandroid clone on devices with limited internal storage
Titanium used to be the go-to choice but it hasn't been updated in nearly two years (struggles on Android 6+) and also utilises adb functions for transport.
FYI - I was able to get this rom to dirty boot a CM 13 build but that's as far as it went. Processor pegged on lock screen judging from heat and sluggish response (5+ sec per key press). Obviously a clean flash is highly recommended by dev but was looking for a path to bring my existing CM 12.1 build (apps and data) forward. Probably hang out on Lollipop for awhile as it meets my needs with no meaningful loss of functionality vs Marshmallow with Greenify, Nova and a few Xposed modules thrown in.
Might give Nexus 6 another whirl once adb backup/restore is working (see previous posts for background). I do miss AOSP ...
Also sad CyanogenMod can't get their act together and fix the ridiculous bug that throws up a fur ball when SIM access is requested on CM 13 if there ain't no SIM card installed (hello...tablets!!). Regression was introduced in a nightly build last March and never resolved.
Camera isn't working on apollo
@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.
chipsugar said:
@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.
Click to expand...
Click to collapse
I have been looking into Bluetooth as I need this working too. But with these new versions of android running with old binaries, it becomes really difficult to get everything working as it should.
Davey126 said:
FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)
Click to expand...
Click to collapse
Installed with 2.8.7, Apollo, with no issue!
My Apollo was on 4.5.5.1, then installed with Safestrap v4, and then Fire Nexus KK ROM. After waiting weeks for the 1-Click bootloader unlock tool, I finally decided to go for the step-by-step unlock procedure and managed to have my Apollo unlocked yesterday afternoon.
I clean flashed your TWRP 3.0.2.0 and this Fire Nexus MM ROM immediately after unlock and am really pleased with the new ROM and the newly found freedom. The ROM works quite well so far except for 1) camera (tried Snap Camera and Camera MX), 2) Google Contacts cannot sync with Gmail account.
As I came over from SafeStrap v4, is there any old files and folders need to be tidy up?