OK,
So I made an aosp build from source for my nexus 7 2013 , but every time I go in youtube and click on a video to watch it the tablet make a hot reboot.
I tried watching a video that I downloaded from the internet within the gallery app(the aosp one) and no problem the video display fine.
Before I built the ROM I extracted the nexus binaries properly i don't know what's wrong.
Also I can't root my tablet with this build every time I flash supersu in recovery it fails.
Another thing, how can I root the ROM before building it, I mean , implementing supersu and busybox inside the ROM before the build process?
Thanks in advance.
Sent from my AOSP on Flo using XDA Free mobile app
Please someone.
Sent from my Nexus 4 using XDA Free mobile app
Related
Hey Guys.
I need some logs from Nexus S for our SGSport project.
Someone with a Nexus S has to build a kernel with following options enabled:
CONFIG_FB_S3C_DEBUG=y
CONFIG_VIDEO_FIMC_DEBUG=y
CONFIG_VIDEO_MFC50_DEBUG=y
CONFIG_VIDEO_JPEG_DEBUG=y
After flashing open Youtube and watch a video.
While watching the Video:
adb shell
dmesg
^^ copy the whole output to http://www.pastebin.com
logcat
^^ copy the whole output to http://www.pastebin.com
Would be very nice if someone can do it.
Same for Camera please.
Thank u guys.
Pl0x nexus S people??
Sent from my GT-I9000 using XDA App
I can compile a stock kernel with these options selected later and post it up if someone wants to flash it and get the info.
Sent from my Nexus S using XDA App
Here's a stock kernel with the debug options selected as requested above. I'm not running a stock rom or I'd flash it and grab the results (stock rom breaks the CM camera if I recall correctly). Anyone who wants to grab the data just nandroid, flash the kernel, push the wifi module and go to town.
can anyone post exactly which battery model or battery driver is used for the nexus s? can either look in the config file when compiling your own source ROM. or perhaps find the battery driver folder using root explorer etc.
just curious to see if similar changes could be made like we did with the nexus one battery driver (the app link in my sig).
WARNING:This ROM can't start-up and requires for suitable kernel,if you have suitable one you can flash it
I have used CM10.1[4.2.1] source and Evervolv's Device and build this one,my other device can start-up very well and everything works fine,but for evo4g,it have no kernel which is suitable and after flash it always stop at the second screen.
FOR CM10,I used MAZWOZ'S sbc kernel,and everything works fine contains video camera.Now I want some help and requires some kernels for CM10.1[4.2.1]
Download Links:
CM10.1[4.2.1-12.22]:http://pan.baidu.com/share/link?shareid=179848&uk=992269513&third=0
[email protected] said:
WARNING:This ROM can't start-up and requires for suitable kernel,if you have suitable one you can flash it
I have used CM10.1[4.2.1] source and Evervolv's Device and build this one,my other device can start-up very well and everything works fine,but for evo4g,it have no kernel which is suitable and after flash it always stop at the second screen.
FOR CM10,I used MAZWOZ'S sbc kernel,and everything works fine contains video camera.Now I want some help and requires some kernels for CM10.1[4.2.1]
Download Links:
CM10.1[4.2.1-12.22]:http://pan.baidu.com/share/link?shareid=179848&uk=992269513&third=0
Click to expand...
Click to collapse
I've never compiled my own Android kernel , so can't help.
I hope others with more experience can help you. You have contributed to the community.
can't wait to see this baby running
In original development, evervolve latest is 4.2.1 based so you can use that kernel. Also, the changes between 4.2.1 and 4.1.2 are so small that Maxwoz kernel will work with 4.2.1. So if you can boot it with his kernel, you have a successful build.
Anyone brave enough to try? ? ?
Sent from my ever-changing OG Evo...
pmacevad said:
Anyone brave enough to try? ? ?
Sent from my ever-changing OG Evo...
Click to expand...
Click to collapse
It doesn't have a kernel, unless someone has a kernel and is willing to share there's no point in flashing it.
Sent from my PC36100 using xda app-developers app
88exp88 said:
It doesn't have a kernel, unless someone has a kernel and is willing to share there's no point in flashing it.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
What they are asking is flashing this with Maz's kernel. For someone willing to try it. And if it still don't work then the build itself is a bad build.
Sent from my PC36100 using xda app-developers app
Lol if no one has tried by the time I get my N4 I'll try. Incase of a brick.
Posted from my ReLoaded EVO
I tried his last ROM and it was not bad at all. I would give it a shot but until I get to a WiFi connection I can't do anything. I have already hit my data cap. Too many nightly downloads from evervolv.
Sent from my PC36100 using xda app-developers app
Tried this ROM with mazwoz's kernel SBC and it wouldn't boot. I got too happy. Would the kernel from evervolv work?
Sent from my Amazon Kindle Fire using xda app-developers app
I am going to download tonight. Will check install script and merge with evervolv then rezip and see what happens. Will post back with details.
Sent from my PC36100 using xda app-developers app
OK no go looks like a bad build. Gets to boot animation and hangs. Rebooted and did adb logcat. Some audio device fails to load I think. Did not save logcat.
I extracted cm zip. Extracted evervolv. Placed boot.img into cm and compressed. Also did a scan over both install scripts and didn't notice anything bad there.
Sent from my PC36100 using xda app-developers app
well i pushed a tweaked kernel zimage made for my self and it boot looped like previously said, i did a logcat and same seems to be an audio problem more related to the rom itself not so much of a kernel issue. if its useful here is the logcat :View attachment logcat.zip
After searching far and wide (and checking the cyanogenmod website) I have not been able to find a stable cyanogenmod file for my tablet that also supports the ir blaster. One of the big issues I have is that the keyboard does not work when the rom is installed and always throws an error even when SwiftKey is the default keyboard. Also I couldn't get gapps to work so I had no play store access. Has anybody found a good stable cyanogenmod file for this particular device or am I limited to using a "stock" custom rom?
Sent from my GT-P5113 using xda app-developers app
Dmoser211http://forum.xda-developers.com/showthread.php?t=23146043 said:
After searching far and wide (and checking the cyanogenmod website) I have not been able to find a stable cyanogenmod file for my tablet that also supports the ir blaster. One of the big issues I have is that the keyboard does not work when the rom is installed and always throws an error even when SwiftKey is the default keyboard. Also I couldn't get gapps to work so I had no play store access. Has anybody found a good stable cyanogenmod file for this particular device or am I limited to using a "stock" custom rom?
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
Hello man,do you not read?
For gt5113 use ROM for 5110 recommend ROM cm 10.1.0 and kernel dhollman
Link rom http://download.cyanogenmod.org/?type=stable&device=p5110
Link kernel http://forum.xda-developers.com/showthread.php?t=2176563
Link google aps http://forum.xda-developers.com/showthread.php?t=2314604
Copy ROM.ZIP and kernel.ZIP and gaps on external SD card
Use recovery
Wipe data factory reset
Clear dalvik
Format all file
Choose install from external sd 1 ROM 2 ZIP
Enjoy
Hi,
I decided to post my own topic and not in the CM11 thread, because this is probably not a CM11 issue. As you know, the Nexus S has only 512MB of RAM including video. Mine has been having quite a lot of slowdowns (apps refreshes/restarts) for the past weeks. I am wondering what I could do to help it and avoid buying a new phone (no money and I still love that phone).
However now, there are few things that I can't do anymore.
- I can't listen to BeyondPod (podcasts) and receive/send SMS in Hangout. There's not enough RAM to run both apps and even when I am listening to BeyondPod, the SMS alert might not trigger when a SMS is received. This happens in few apps here and there.
- Sometimes, someone calls me and the screen stays black so I can't answer. Again, this is due to RAM usage.
- I use SwiftKey as keyboard and it can't take 30-45 seconds to load in some apps such as Chrome.
I am running CM11 Nightlies. I usually update CM11 once per 2 weeks with the lastest Nightly available. I don't wipe the entire configs, I just upgrade. It's been a while since I've wiped everything to be honest. I probably updated CM10 to CM11 without wiping the configs. This might be one thing to try but I am not sure if it would help to regain some RAM/juice. I am running the stock kernel of CM11. I know there are few kernels with a bigmem patch, but does it really work ?
As for launcher, I am running Apex Launcher as well with SwipePad. Greenify runs in the background and hibernate pretty much every apps it can. I don't have the Greenify donation package, so it won't hibernate on the system apps.
I am wondering if wiping everything and installing a stable version of CM11 (or another lighter ROM?) would help. I would use TItanium Backup to reinstall the apps and their settings. I wouldn't use TiB to push the configs of the ROM if CM11 is reinstalled. Would a kernel or ROM with bigmem patch a good idea ?
This would probably be a temporary fix, because apps and ROMs are asking for more and more CPU/RAM these days.
Thanks for any input,
Neo.
A clean flash isn't a bad idea, just backup your rom first.. Backup your apps/ data on your SD with titanium backup and then you can just restore them.. You could try my stable v1.1 script and use Guru (CM kernel with bigmem) or Devil and you will notice the improvement.. Also the CM m9 is a very nice rom.. Happy flashing..
Sent from my One A0001 using XDA Premium 4 mobile app
Setting.Out said:
A clean flash isn't a bad idea, just backup your rom first.. Backup your apps/ data on your SD with titanium backup and then you can just restore them.. You could try my stable v1.1 script and use Guru (CM kernel with bigmem) or Devil and you will notice the improvement.. Also the CM m9 is a very nice rom.. Happy flashing..
Sent from my One A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your answer Setting.Out.
Before I receive your answer, I did some research on my side as well. It turns out that I have downloaded your ROM (the Farewell edition) and the cn.fyodor AOSP 4.4.3 ROM. I decided to go ahead and install the AOSP ROM instead of yours. I wanted to try AOSP instead of CM, being a CM user for the past 2-3 years. While I was satisfied with the AOSP ROM for the past day or 2, I am now unsure if I will keep it. While performances are good compared to what I was used to, I have some issues. The videos in YouTube are lagging like crazy (although videos in VLC work fine) and the audio stutter sometimes. I listen to a lot of music and each few minutes, it will stutter for a split second. I never had that issue with CM11. Also, I can't find a kernel with bigmem on AOSP. There is the marmite kernel from bedalus which seemed promising, but everyone is having FC with the Google Play Store and BLN/BLD isn't working anymore on this kernel.
How does your ROM compare with CM11 ? I know yours is CM based. Is there less "bloatwares" in yours ? CM install lots of stuff (themes, bugs reporting, etc) and I don't want that. I prefer to use the Xposed Framework instead of a ROM with multiple settings that I don't use. Having a CM based ROM would be nice to be able to flash the Guru kernel.
spookyneo said:
Thanks for your answer Setting.Out.
Before I receive your answer, I did some research on my side as well. It turns out that I have downloaded your ROM (the Farewell edition) and the cn.fyodor AOSP 4.4.3 ROM. I decided to go ahead and install the AOSP ROM instead of yours. I wanted to try AOSP instead of CM, being a CM user for the past 2-3 years. While I was satisfied with the AOSP ROM for the past day or 2, I am now unsure if I will keep it. While performances are good compared to what I was used to, I have some issues. The videos in YouTube are lagging like crazy (although videos in VLC work fine) and the audio stutter sometimes. I listen to a lot of music and each few minutes, it will stutter for a split second. I never had that issue with CM11. Also, I can't find a kernel with bigmem on AOSP. There is the marmite kernel from bedalus which seemed promising, but everyone is having FC with the Google Play Store and BLN/BLD isn't working anymore on this kernel.
How does your ROM compare with CM11 ? I know yours is CM based. Is there less "bloatwares" in yours ? CM install lots of stuff (themes, bugs reporting, etc) and I don't want that. I prefer to use the Xposed Framework instead of a ROM with multiple settings that I don't use. Having a CM based ROM would be nice to be able to flash the Guru kernel.
Click to expand...
Click to collapse
It basically is CM11, a little less bloated, but similar feature set.. Give it a try, you can always flash another rom if it doesn't suite you.. Slim 5.1 is another favorite of mine, if you'd like to try that one you'll need to search their thread as it wasn't a public release..
Sent from my One A0001 using XDA Premium 4 mobile app
Setting.Out said:
It basically is CM11, a little less bloated, but similar feature set.. Give it a try, you can always flash another rom if it doesn't suite you.. Slim 5.1 is another favorite of mine, if you'd like to try that one you'll need to search their thread as it wasn't a public release..
Sent from my One A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Your "Farewell edition" is Kitkat 4.4.4 or 4.4.2 ? So that I can download the appropriate Gapps. I also understand that the Gapps you provide in your thread are a minimal package, so my Nexus S doesn't run out of space (which happened to me few months ago due to the new official Gapps package).
Thanks
spookyneo said:
Your "Farewell edition" is Kitkat 4.4.4 or 4.4.2 ? So that I can download the appropriate Gapps. I also understand that the Gapps you provide in your thread are a minimal package, so my Nexus S doesn't run out of space (which happened to me few months ago due to the new official Gapps package).
Thanks
Click to expand...
Click to collapse
4.4.4 minimal/micro are better on the NS..
Sent from my One A0001 using XDA Premium 4 mobile app
This thread is for any questions regarding the CM12 build I'm making.
Link to ROM thread: Coming soon.
Sent from my GT-I9003 using XDA Free mobile app
Waiting for the rom
Excited to test it.
Still building..... Keeping my fingers crossed
Sent from my GT-I9003 using XDA Free mobile app
God I'm *this* close to success and it just won't get to the boot animation. *sigh*
Sent from my GT-I9003 using XDA Free mobile app
Has there been any progress on this ROM?
Why is porting so hard
As far as I understood, to get a new Android on Device X is as following: :silly:
1) Download latest CM-ROM
2) Copy drivers from Device X´s stock ROM to latest CM-ROM
3) Configure build.prop eg. screen resolution/DPI&co.
4) Zip and flash it
Am I right? Wrong? :cyclops::fingers-crossed:
[email protected] said:
As far as I understood, to get a new Android on Device X is as following: :silly:
1) Download latest CM-ROM
2) Copy drivers from Device X´s stock ROM to latest CM-ROM
3) Configure build.prop eg. screen resolution/DPI&co.
4) Zip and flash it
Am I right? Wrong? :cyclops::fingers-crossed:
Click to expand...
Click to collapse
I wish it were that simple
The thing is that there could be kernel and initramfs changes necessary, which is something to be built from source. Also, there are device specific files spread all over the ROM, not to mention architecture differences and lack of space. Therefore, it's better to build from source by forward porting the device
ahsanovich said:
Has there been any progress on this ROM?
Click to expand...
Click to collapse
I have a build of NamelessROM 2.0 on GDrive but it's not suitable for daily use. Also, due to the ever-increasing resource usage of Google Play Services, Android seems to be no match for our low end devices. I'm giving one last try for Omni 7.1 and if that doesn't work out, I'll scrap Android for Ubuntu Touch
Thread closed as per OP request.
Wood Man
Forum Moderator