Related
1. Can you do an incremental upgrade from 024 to the latest version?
2. Is there a version that does not crash the browser when you enter into downloads?
2. How do you modify the notification ringtone (add some more into that list)?
eug3nius said:
1. Can you do an incremental upgrade from 024 to the latest version?
2. Is there a version that does not crash the browser when you enter into downloads?
2. How do you modify the notification ringtone (add some more into that list)?
Click to expand...
Click to collapse
1. Yes
2.try opera mini
3.flash the sound pack
Come to insanity to ask questions!
Sent from my GT-I9000 using XDA Premium App
Thanks for the answers ... I can't post in the Insanity ROM thread because I'm a new user, restricted to Q&A.
1. What I meant by incremental upgrade is an upgrade that does not require wipe/factory reset. I know you can use an app to back up your apps and restore them ... I don't want that, I want a procedure for update without reinstalling all the apps, because that does not work perfectly, you still lose settings.
2. I tried to install 026 over 024 without factory reset/wipe and ended up in an infinite reboot cycle. After that, I still did the factory reset and tried 026 just to see if the android browser doesn't crash anymore when I enter into downloads ... sadly, it still crashes, so I just restored my backup of 024.
It's "insanity" that such a basic function stays broken in so many rom revisions IMO. The android browser is the best browser on android overall ... I don't want to use opera, firefox or whatever.
3. I thought I did, but I'll check again. But even if there are more sounds to pick from, that does not help me in adding my own notification ringtone to that list.
To update just download to sd card, go to nitrality/backup & restore/flashcwm and flash, all apps and settings stay, then just repeat procedure and flash packs and nitrality apps as required, job done
Sent from my GT-I9000 using XDA Premium App
To add your own sound just create the file and push to relevant folder
from my GT-I9000 using XDA Premium App
Also re. Browser, google browser really isn't that good, I have heard problems downloading with it, but that isn't unique to insanity, go forth and experiment!
edit.....if you want to get into insanity thread to post all you have to do is notch up 10 posts, then i think you can post anywhere
Sent from my GT-I9000 using XDA Premium App
Do I need a special upgrade package for that?
Because ... isn't nitrality/backup&restore/flash_cwm_package the same as entering recovery mode and selecting the cm026 zip that got me into an endless reboot?
I searched for the Altair notification and the ringtone folder is:
/system/media/audio/notifications
The actual notification is an ogg file, but I presume mp3's will work.
Hard to believe there's no actual UI option for that ... you can set the ringtone using the music player, but you can't set the notification ringtone that way.
I'm all for light/fast software, but if the software is buggy and it's lacking basic functions that are super simple to add but are ignored because the developer did not do a proper specification, it becomes pointless. Fast and light is nothing without stable and elegant.
slaphead20 said:
Also re. Browser, google browser really isn't that good, I have heard problems downloading with it, but that isn't unique to insanity, go forth and experiment!
edit.....if you want to get into insanity thread to post all you have to do is notch up 10 posts, then i think you can post anywhere
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I disagree, the google browser is the best, and it's especially fitting for the light and fast concept of insanity rom.
My suggestion is do a fresh install
Procedure
A) download cmxxx
B) download all the cm packs
C)flashezbase 2...allow to reboot
D) flash cmxxx through recovery...allow to reboot
E)go to nitrality/backup restore
F)flash each pack..allow to reboot each time
G)go to nitrality/apps and load apps you want (calender apps important)
H)change dpi in nitrality ui if required
I)explore and play
J) marvel at speed/donate/thank
* when you restore your apps don't restore data, and dont restore any samsung apps, they won't work
Smile
Sent from my GT-I9000 using XDA Premium App
eug3nius said:
I disagree, the google browser is the best, and it's especially fitting for the light and fast concept of insanity rom.
Click to expand...
Click to collapse
well from what i have gathered it doesnt work well at the moment with deodexed roms so my comments still stand.....and i very much doubt any of your problems are due to nitr8 errors, he is a very well respected dev who is very thorough, if you dont like his rom there are plenty more to try out there, as for the mp3 thing, im guessing that you will need to convert to .ogg, but that is just a guess
sometimes you need to do a double flash if it reboots,ie flash through nitrality, if it loops then do 3 button recovery and reflash, but this problem was sorted im sure, but worth a try,
the point of this rom is that it is as small as possible, so adding your own notification tone isnt such a big deal, he wont change things just for one little moan!
Thanks for your help ... maybe I wasn't clear about what I mean by apps ... I don't mean the app packs you download to complete the insanity install, I meant my own installed apps.
You know, installing a new OS version shouldn't mean a re-format of the system partition and a re-install and re-customization of all 3'rd party apps.
That is ABSOLUTE basic functionality, just like changing the notification ringtone. If a ROM doesn't include that, there is something wrong with the concept ... Still, I didn't request anything.
But as it is, it's also not worth donating for insanity rom. I only donate for perfect roms. I donated for darky 9.5 but not for 10.1, that drove me to insanity.
I have to ask you slaphead20, are you associated with nitr8 and insanity?
eug3nius said:
Thanks for your help ... maybe I wasn't clear about what I mean by apps ... I don't mean the app packs you download to complete the insanity install, I meant my own installed apps.
You know, installing a new OS version shouldn't mean a re-format of the system partition and a re-install and re-customization of all 3'rd party apps.
That is ABSOLUTE basic functionality, just like changing the notification ringtone. If a ROM doesn't include that, there is something wrong with the concept ... Still, I didn't request anything.
I have to ask you slaphead20, are you associated with nitr8 and insanity?
But as it is, it's also not worth donating for insanity rom. I only donate for perfect roms. I donated for darky 9.5 but not for 10.1, that drove me to insanity.
Click to expand...
Click to collapse
if you are updating from insanity to insanity all user apps and system settings stay put...as i stated before, i recommended a fresh start to eliminate the bad flash factor, as it seems that you have a some time corrupted or made a mistake... of course you will deny that but it is just part of the process of elimination!
as for am i associated to nitr8, im just a user that helps out a lot on his thread, and anywhere else i can as i have time on my hands due to the fact that i have terminal cancer...so stop being paranoid, im just trying to help you and get to the bottom of your problems and share my experience as i have been with insanity for a long time and know nitr8s work pretty well....in short im just an ordinary joe! also donating is up to the individual, nitr8 has a full time job, all donations go towards future dev and equipment to speed up rom production, and if you start looking around you would appreciate just how much of his own time he puts in FOR FREE....into this forum...as do all devs
Relax, I am not paranoid and I don't suspect you of anything ... LOL, what would I suspect you of? Liking specific ROM's is not a crime (or maybe on XDA it is, I have to check the FAQ).
I just went to the insanity ROM thread and saw you help a lot of people there, and thought maybe you're associated with the project. Which you should think about IMO, if you do it anyway and plan to do it in the future.
I'll try and update from 024 to 027 ... maybe it was a bad flash before, you never know. I still have the 024 backup so there's nothing to lose.
And about donation: if commercial developers only get money for finished ready-to-use software, why should open source developers get money for less? That would just make them less than they have to be.
PS: Good luck with your health. My mother had a breast cancer scare 5 years ago ....
eug3nius said:
Relax, I am not paranoid and I don't suspect you of anything ... LOL, what would I suspect you of? Liking specific ROM's is not a crime (or maybe on XDA it is, I have to check the FAQ).
I just went to the insanity ROM thread and saw you help a lot of people there, and thought maybe you're associated with the project. Which you should think about IMO, if you do it anyway and plan to do it in the future.
I'll try and update from 024 to 027 ... maybe it was a bad flash before, you never know. I still have the 024 backup so there's nothing to lose.
And about donation: if commercial developers only get money for finished ready-to-use software, why should open source developers get money for less? That would just make them less than they have to be.
PS: Good luck with your health. My mother had a breast cancer scare 5 years ago ....
Click to expand...
Click to collapse
well im involved in as much as when trojan went on hols i stepped in to cover him and try and turn the thread into a less hostile place where everyone helps, and i did a little bit of beta testing so what i do i do with nitr8s bllessing, but right now with going through chemo i have stepped back a bit and just help out, thankyou for kind wishes edit....only 3 more posts and you can post on insanity, and you have your 1st thanks now
like it ^^
Thanks for thanks!
In process of flashing 028 over 024 .... and it's the same, endless reboot, restoring the backup.
When the browser bug is solved, I'll re-format and flash a new version (if I don't try darky 10.2 in the mean time) ...
eug3nius said:
Thanks for thanks!
In process of flashing 028 over 024 .... and it's the same, endless reboot, restoring the backup.
When the browser bug is solved, I'll re-format and flash a new version (if I don't try darky 10.2 in the mean time) ...
Click to expand...
Click to collapse
did you do a fresh install as I suggested? I always do factory reset before and and after the ezbase install and never have problems, and the browser bug as you know is not a problem with insanity, but a conflict between the browser and deodexed roms. All the best
Sent from my GT-I9000 using XDA Premium App
No, there's nothing in the changelog that would deserve the effort to wipe/reinstall.
Yes I know the browser situation, but I think there are fixes for the browser already .... I don't know if they're for cyanogen though.
On a whim I tried darky 10.2 and sadly it has bugs too:
- twlauncher hangs when you try to save the settings and restart it
- the browser sometimes just shows a blank white page instead of the loaded webpage.
What's funny is this - when you press windows you see the miniature of the actual webpage, it isn't blank, so the page is loaded, the browser just doesn't want to show it.
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://www.multiupload.com/XT9QPPQYF1 thanks xploited for uploading
md5: 670068584eb94bf1d660c0450815ad0d
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Not sure how the dev team would react to this ..we do not want any bricked phones because of this ..there maybe some experimental dangerous code in there in those sources as of now ..not sure though
Hmm... figured since I spent quite awhile getting a build set up, it might be worth sharing. I am happy to take down if it is inappropriate.
Well I am not the best person to answer that ...but yeah thanks for your work.
Eh, I wouldn't be mad about it, but I think it needs more caution. I would just wait. As you say, it kindof screwed with a lot and wasn't very usable, so why flash it? Maybe ok for someone who wants to look at the code, but I wouldn't flash it.
Awesome news man. Thanks for being a lab rat and giving us an update.
Sent from my MB860 using xda premium
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
samcripp said:
Not so much take it down as change the title of the post.
the current internal atrix-dev-team cm9 is way further ahead of this, we have some different patches. this is missleqading as it makes it sound official and is not.
Could you please change the tittle to [KANG] CM9 Test Build by "your name"
and please link to the sources, as is proper practice for open source projects
thank you
Click to expand...
Click to collapse
and I guess you guys deserve a Xmas break now ...
It's nice to see that! Thanks for your hard work.
I'm looking forward to the CM9
Thank you for this.
!
Anyways, Just out of curiosity... where can you find the official Atrix Dev team's CM9?
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
I always forget what kang means.
Sent from my MB860 using XDA App
wrldsuksgo2mars said:
I tried the latest build of CM7 done by the Atrix Dev Team and it is awesome. Very reliable, fully functional, etc. I figured I'd give a whirl to compiling the real ICS version to see what that was like.
CM9 build system with the appropriate Atrix Dev Team repos in place actually spit out a working ROM. There are a number of issues aside from the general preview state of CM9. I figured I would share them in case anyone else was as curious as me. Apparently, the internal atrix dev teams are well beyond these issues already, so kudos.
Probably related to CM/atrix specific stuff
- Camera and finger print sensor don't work
- Launcher crashes pretty often
- Some openGL demos don't seem to work right (or at all)
- No mounting the SD as USB storage
Probably related to the specific gapps package I used.
- Maps crashes after 3 seconds (signal 11 - native code crash)
- Maps wants to update, but it can't (sharedId conflict if you actually remove maps)
- Earth won't run (missing the earthmobile library)
- Google Voice Search bombs (signal 4 - illegal instruction - currently suspecting the native packages might have some NEON instructions that the atrix cpu doesnt support)
- Calendar will not sync for google or exchange. App loads, but the sync service is failing
- Lots of null pointer exceptions for the NFC stuff in the log.
Anyway, this is just a build of the code that's out there, nothing special done by me. It might be useful for a dev phone or something but not for use on a real day-to-day device. Obviously it doesn't have the google apps embedded in it.
http://goo.gl/39NnA
Personally, I had trouble going back to CM7 afterwards, my clockwordmod backups were screwed up (bad boot.img? cross-linked files on the SD card) and I had a very hard time getting back to the good ole working state. Ultimately, I had to restore the partial backup and then reflash the CM7 image + gapps.
So, if you were curious what building a random repo on the web and installing it on your phone would do, then feel free to try and lose all of your data. There are no updates/support for this, etc. It's just a curiosity... what is the state of this stuff right now?
BTW... I am back on CM7/Atrix now which is AWESOME!!!!
Source Code Links:
https://github.com/CyanogenMod/android
https://github.com/Atrix-Dev-Team/android_device_motorola_olympus
Click to expand...
Click to collapse
Thinks for your works,
Come from Chinese thinks!
i shall say this.. if this is behind where the dev team actually is...things are looking good! and btw.. i believe fruitcaker maker works. installed and is now creating;]
edit: yep. it does.
Thanks man very very good work android congratulations for share work whith comunity
Sent from my MB860 using xda premium
it looks very nice but id needs a bit more work to be a experimental daily driver.
ps: to solve the corrupt backup problem just copy the files to your computer before flashing and copy to your phone before restoring.
good luck!
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
try the one on this link
http://rootzwiki.com/topic/11854-romcm9-encounterics-x-beta-2-with-working-radio-401/
good luck!
---------- Post added at 07:52 AM ---------- Previous post was at 07:47 AM ----------
ilya11g said:
where can I get google apps for this rom? Tryed gapps for CM7 from CM wiki - fail, setup wizard crashes.
Click to expand...
Click to collapse
try the one on this link
http://rootzwiki.com/topic/11854-rom...ing-radio-401/
good luck!
For a preview build it looks pretty nice. Surprisingly stable for what it is. Definitely keeping an eye on this, especially since the code is out there to make DIY kangs with.
samcripp said:
The one been worked on by turl is with him, that is not for public release.
Dont forget to tell him merry xmas!
Click to expand...
Click to collapse
Random SamCripp memory....
"We're rapping them, we're rapping them!!!"
Sorry, guess you had to be there.... aahhh memories... nevermind, sorry for the off topic post.
Thanks though for the effort of getting this ported btw.
I don't have 10 messages yet, so i have to do it here.
So any questions i will have i will ask here.
About (ROM) (CM10) ParanoidAndroid v2.23 Hackfest JB (build8)
http://forum.xda-developers.com/showthread.php?t=1875564
tonyP writes : Don't restore system apps (like Settings) or system data (like Wifi data) with TitaniumBackup!
What about after the first install?
1. After that and after i installed my own apps and settings, can i then restore backups from titanium?
originally from the beginning the Gapps chrashed a lot (google.com apps), so i flashed the latest Harsh kernel,so far this works great.
2. Is that OK or does it have other risks?
Answer found
After a few reboots the camera simply dissapeared, nowhere to be found, not even in /system/app.
(it wasn't even there when it was working)
Off course that happend right after i installed all apps, widgets and their settings, and before i could make a backup of them.
So i had to do it all over again. :crying:
3. Where is the camera apk located?
4. Where are the downloaded apps located?
I want to install the agenda 201210120 apk on a different device.
Answer found
Didn't know that was possible with es file explorer, before i always used file manager.
Bored about trolling XDA? Too lazy to use scroll on general section?
There's a thread made by tonyp for that. Use it intead of making chaotic tread.
?? you automatically assume i don't search before i ask?
i am a mod on a Wii softmod site, i create softmod tutorials, so don't judge people you don't know please.
Yes i have searched, and as we say in Holland, sometimes you don't see the forrest because of all the trees.
So answer honestly, do you search through hundreds of posts to find an answer?
Yes? , then you have my respect, cause your one of the few.
I quit searching after a few dosen and simply ask.
Edit:
I discovered something new.
I lost the camera again right after i installed tomtom navigation.
Don't know why, but i wil solve it for now with a backup from cm7 camera.
That's practicly the same anyway.
Please use this thread here - http://forum.xda-developers.com/showthread.php?t=1813113 - Thanks.
Thread Closed
The-Hulk
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!
The Unlegacy-Android Project​Introduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?